Replies: 4 comments
-
update: I can manually address the second gang by specifying the endpoint in the zbsend command.
so that bit is resolved. help on how to get these addressed separately by alexa is still needed please. |
Beta Was this translation helpful? Give feedback.
-
I have the answers now. I found in the code that ZbName allows for naming of each endpoint and ZBLight allows for hue emulation of each endpoint. The manual does not reflect this so I have edited and proposed a PR. From looking at past issues and the PR implementing the code @s-hadinger proposed these PRs in 2022 (thank you Stephan) |
Beta Was this translation helpful? Give feedback.
-
Sorry, where or which is the pull request? Could you update documentation? Thanks a lot |
Beta Was this translation helpful? Give feedback.
-
PR submitted yesterday but it hasn't worked. redone today. |
Beta Was this translation helpful? Give feedback.
-
Hello
With the above device tasmota pairs correctly and reports power and power2 in the zbinfo response. the device is reported by blakadder as being supported by tasmota (https://zigbee.blakadder.com/Moes_MS-104BZ.html)
Using zbsend and send:power:1 results in the first gang switching as expected.
Power2:1 results in "unrecognised ZigBee command".
What is the appropriate JSON to send to switch the second gang please?
And how are each of the gangs mapped to Alexa in hue emulation? As the zblight command takes the device ID rather than endpoint as an argument.
zbinfo
gang 1
gang2
zblight
a light named 0x7048 is found by alexa. no second light is found.
Beta Was this translation helpful? Give feedback.
All reactions