-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ConBee 1 issue with Hue Remote #20
Comments
Could you try to re-add the remote and past the init logs here? The zero mac address might be the main issue here, and the IEEE address request seems not to work either. |
The empty space is where the joining was finished, I waited a bit and then pressed a button on the remote. Also, I've patched the code to print the Cluster Object pointer. As you can see, during the initial setup, it is a different pointer (0x56261fcd6b30) then later when the button press is handled (0x56261ff32ac0) |
The indication seems to come from a different node (different short address). Looks like the node was not updated correctly in the node table internally in the firmware. Please try to update and factory reset the stick firmware (delete all storage), factory reset the network on nymea and add the controller. This looks to me like a firmware bug. From nymea perspective, the indication is coming from a complete unknown node, it tries to initialize the unknown node, but failes. |
Did that... Updated to the latest firmware, reset the dongle with the flasher too. Then also from nymea, re-added. Still the same. |
The hue remote doesn't work with the ConBee 1 stick (it does work with the ConBee 2). Interestingly the ZCL indidcations appear in the log, but the signals never end up in the nymea plugin. I've tracked it down to this:
The remote first seems to set up fine, but eventually you'll get this message in the logs:
This causes the Node to be removed from the stack (Note: for some reason it doesn't seem to actually leave the network!).
When then pressing a button, this will show up in the logs.
The logs continue to create the endpoints and the clusters again and the ZCL indication arrives fine in the newly created cluster. However, the nymea plugin still thinks it's connected to the old node/endpoint/cluster pointers.
The text was updated successfully, but these errors were encountered: