Conversation
938976c to
91d84e2
Compare
d220375 to
7cea8c6
Compare
07d21c9 to
79c957a
Compare
3340d6a to
3f85d8e
Compare
befb741 to
db6308e
Compare
|
There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. |
This is currently untested.
This is currently untested.
This is currently untested.
|
There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. |
|
There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. |
|
There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. |
There's still some work to do on this:
mainafter that lands.durations expire. (For Blue switches under ZHA, it's the receival of0x24which corresponds to either all or individual LEDs expiring and is easy to consume via an event handler).Obtaining Parameter Values
We need to determine if it's possible to get the state of various parameters.
ZHA stores these values in sensors (with well known translation keys and unique IDs ending in
-disable_clear_notifications_double_tapand-local_protection).Why it matters: obviously, without the 2x tap to dismiss enabled, the switch doesn't disable the notification. We shouldn't clear it in this case—it should just be left alone. However, with local protection enabled, the switch will send the 2x tap message, but it doesn't disable the notification in this case either. In this case, we should send a message to clear it.
Prior Art & Documentation Resources