Insteon: Improve Support for Deaf Devices; Add Delete Orphans Capability #399
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.
The management of deaf devices, such as motion sensors and remotelincs, has always been a little weak in MisterHouse. The problem is these devices must be "awakened" before MisterHouse can speak to them. Normally we wake devices by pressing the set button for 10 seconds. This leaves the device awake for about 4 minutes.
However, these devices also remain briefly awake immediately after they send a command, this seems to last about 2-4 seconds, although with some devices this awake time can be modified and extended.
Due to this "awake" requirement, MisterHouse ignores these devices when performing batch actions (Sync All Links, Scan All Device Tables, Delete Orphan Links). Generally, the user could manually awaken the device and call the device equivalent command to achieve the same results. However, there was no device equivalent "Delete Orphans" which meant there was no way to remove extraneous links from deaf devices without resetting them. Additionally, it was often annoying to be forced to manually place a device in awake mode.
This branch solves all of these issues.
noticed any downside in enabling this feature.
Everything appears to work well in my setup. However, keep in mind that deaf devices are one of the most difficult devices to communicate with since they are RF only, so you many encounter some issues trying to maintain a sustained conversation (such as scan links) without moving them closer to an access point or other dual band device.
Fixes #183 & #182