Update athom-smart-plug-v2.yaml #42
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add: 1) Ability to define a timezone when sync'ing with SNTP. Normally plug will sync with timezone of the HA server, however this (optionally) allows defining a timezone for the plug in the substituions section. 2) Add support (optionally) being able to enable 'fast_connect' for the WiFi conenction. When the plug has previously connected to an SSID this allows the device to rapidly reconnect to it in future, without the delay caused by a full scan of the available SSID's in the area. 3) Add support (optional) for setting a dns_domain with the network connection. Defined in substitutions, instead of the plug obtaining a DHCP lease in your network and registering in the main dns zone, this allows allocating the plug to the correct network name / device purpose. i.e. In your 'home.lan' network if you have all IoT devices segemented off for security, you could use this to have the device register as 'smart-plug-v2.iot.home.lan' 4) Noticed the subsitutions has 'room:' as an entity, however it is not used. Added 'areas:' that calls the 'room' variable. This is in line with ESPHome adding the ability to inform the HomeAssistant (HA) server which 'area' with HA it should be allocated. This is instead of manually having to select this when (re)adding devices to HA. BTW could the Repository owner please look to add the 'Discussions' feature to the Repo? ATM there is no way to communicate about possible changes, features to add or issue fixes. This means the only way to do any of this is to Request a Pull.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add:
Ability to define a timezone when sync'ing with SNTP. Normally plug will sync with timezone of the HA server, however this (optionally) allows defining a timezone for the plug in the substituions section.
Add support (optionally) being able to enable 'fast_connect' for the WiFi conenction. When the plug has previously connected to an SSID this allows the device to rapidly reconnect to it in future, without the delay caused by a full scan of the available SSID's in the area.
Add support (optional) for setting a dns_domain with the network connection. Defined in substitutions, instead of the plug obtaining a DHCP lease in your network and registering in the main dns zone, this allows allocating the plug to the correct network name / device purpose. i.e. In your 'home.lan' network if you have all IoT devices segemented off for security, you could use this to have the device register as 'smart-plug-v2.iot.home.lan'
Noticed the subsitutions has 'room:' as an entity, however it is not used. Added 'areas:' that calls the 'room' variable. This is in line with ESPHome adding the ability to inform the HomeAssistant (HA) server which 'area' with HA it should be allocated. This is instead of manually having to select this when (re)adding devices to HA.
BTW could the Repository owner / @athom-tech please look to add the 'Discussions' feature to the Repo? ATM there is no way to communicate about possible changes, features to add or issue fixes. This means the only way to do any of this is to Request a Pull.