-
Notifications
You must be signed in to change notification settings - Fork 40
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
Group binding does not work for rwl021 #58
Comments
If i recall correctly, it also worked with the |
Hmm. I tested this out with a bulb and a sniffer when adding the command and both the bind and unbind commands were sent over the air. Your first log shows the coordinator sending the bind request a few times but it never receives a reply. The second log with the unbind request shows that it does work and the device replies to the unbind request with a Is the dimmer joined directly to the coordinator as a child? I don't have Hue devices but I will try this with a battery operated IKEA dimmer and see what happens. |
Hi @puddly Thank you very much for your help. I confirm, the dimmer is joined directly to the coordinator. I have tried to disconnect all router devices, reset remote, rejoin. No more luck. |
Hi, I manage to unbind coordinator by using zha_custom.execute with data from this comment : Group binding is now working. I call zha_custom.execute with data: ieee: ieee_address_of_rwl021_remote ieee: ieee_address_of_rwl021_remote ieee: ieee_address_of_rwl021_remote |
Great that you was getting it working !! I don't understand way your attempt using unbind in the device card cluster commands was not working and you can doing it successful zha_custum commands. I was for 3 days ago rejoining my after one firmware update on EZSP NCP without doing backup (NOT by the book) and was losing the network. I was only selecting the coordinator and on/off, level and scene cluster and unbind from device and then the the same cluster with bind groupe and the prefered groupe and it was working. My RWL021 is connected to one good router in the network if it can giving one clue and the coordinator is EZSP one. One thing with controlling device is that it can being necessary sending one "configure this device" from device card then attribute reporting is being broken after new binding is done and also the pull control can being problems and your device is draining the battery @puddly IKEA controllers is normally no problem doing one new groupe binding without unbind then there is new joined but the RWL021 is not accepting any new binds until its being compleet unbinded from the coordinator (i think the RWL021 is adding the 0x0000 as default then being reseted = binding table is populated and the IKEA is not adding it but is defaulting to 0x0000 after being reseted = binding table is not populated). I have testing it in Tasmota and adding binds command is working OK (the device is replaying OK) but its not working until sending one unbind from the default bonded coordinator then its start sending the commands to the new groupe. @TheJulianJES I think you is having one new TI coordinator and the dimmer. |
Hi @MattWestb , Maybe it's not working because i use zha_custom.execute. I'm not sure but maybe it's working because I use unbind coordinator on endpoint 0xFC00 (or maybe is it a coincidence) I tried to start from zero again :
Full log : https://pastebin.ubuntu.com/p/Tdwp7dBt33/
Full log : https://pastebin.ubuntu.com/p/cx82VSmm6s/
ieee: 00:17:88:01:04:ef:c7:b4 ieee: 00:17:88:01:04:ef:c7:b4 ieee: 00:17:88:01:04:ef:c7:b4
Full log : https://pastebin.ubuntu.com/p/p89Hv3bzKV/
I though it is ok, but my remote does not work and has no effect on the group Maybe because i have not seen that 😇
So i tried again to unbind coordinator from remote endpoint 0xFC00 with this data (because i have done that the last time , when i get remote ieee: 00:17:88:01:04:ef:c7:b4 and do again all unbinding coordinator / binding group many times because it's not working. And finally its working :/ I don't have the skill to understand... |
@MattWestb |
@Jsl-1 You have doing great logging but the past bin is little wrong but i think its no problems. You can see in your log if the commons wos ok received by the device if its sending one And if you is getting this @TheJulianJES I deleting my remote and trying to joining it and binding with my EZSP for see is its only one TI problem or one zigpy / ZHA one. |
@TheJulianJES I was deleting it and joining it (hardware reset thru pinhole on the back side for 10 seconds) OK. Deleting and joining OK. I can remember that the scene cluster (0x0008) have making troubles before and should not being bonded and its braking the other (perhaps its cant handle so many different bindings ?). |
Thank you @MattWestb for your time and explanations. I close this issue as it's not related to zigpy-znp. I will try later with another RWL021 and read the log more carefully when doing bind/unbind ;) Thank you all for your help ! |
Hi
I have just migrated from zigpy-zigate to zigpy-znp with CC2652RB device and I try to bind my philips RWL021 to a specific group.
I use dev branch to unbind coordinator first ( 62de24d , #54)
I am not sure witch one of bind unbind failed first, but it's not working for me
Log for unbind coordinator : https://pastebin.com/6BrNmeLC
Log for bind remote to group: https://pastebin.com/7S7Ai5Sr
I'ts working before with zigpy-zigate by doing this:
Does anyone had success with this ?
The text was updated successfully, but these errors were encountered: