-
Notifications
You must be signed in to change notification settings - Fork 506
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
groups/0 (all devices) not working #3744
Comments
Try with 0xFFF0 = 65520 that is the "new" groupe Al |
Thank you for your help.
Any hints? PS.: why should the groups/0 be changed? |
Then taking on look in zigbee.db in the table group wot number "All" is having but not the one that is marked "deleted" |
About group 0 is in Zigbee 3 reserved for global scene commands and not as one trashcan for HA devices. |
ok, can you please guide me in the right direction regarding zigbee.db. I just updated deconz yesterday to 02.05.88 and now my groups/0 is gone :-( |
Now when i'll do an:
i'll get:
So it seems the all group is working under id 65520 now. Sadly the "Power off" button in phoscon, HUEEssentials ... does not work because they will switch "0" instead of 65520. Does it work when i just rename it to "0" in the sql table? |
Its looks little normal deCONZ. One warning only saving the DB then deCONZ is not running or it is overwriting you changes. I think the system was little sleepy adding it after restart :-)) The last Q you can try but me experience is that deCONZ is redoing it to deleted after next boot. |
Then you is having around 50 lights you should using real light groupe that is bounded to your remotes like the HUE dimmer switch so they is working if deCONZ is offline or having problems !!! |
Found the related commit which deletes group 0x0000 and adds a new non zero group which mostly happens to be 0xfff0: Devices are added to the new group 0xfff0. The REST-API group "0" is mapped to Zigbee group 0xfff0. I need to find the discussion behind this, not using (Zigbee) group 0x0000 has reasons but adding routers to that new 0xfff0 group has shown it's side effects and problems recently. I think it's best to use broadcast instead group cast when controlling REST-API group "0". |
@MattWestb: I have now changed the 0xfff0 to 0x0000, stopped deconz before and than restarted. @manup thx |
Actual group Zigbee group 0x0000 was never used, the REST-API group "0" was transformed into a broadcast to all routers, which I think is good, but likely there were other problems leading to the change. Note that change was made over a year ago long before v2.5.84. |
thx, got you.
Until now (~5 Minutes) REST-API group "0" is working again. Now its gone again :-( REST-API group "0" not working. thx |
Now both are deleted.
After that the DB is looking like this: How can i get it to work again? |
Great that Manup was not sleeping ;-)) In the latest Zigbee 3 papers is groupe 0 is reserved for scene command (globale one i think) and it was added then LL (light and occupancy) was added to ZCL. Its more zigbee groupes that is reserved at 0xffxx somthing and to 0xffff but i cant finding the paper its written for the moment (its about using touchlink in zigbee3 from NXP and sirlabs). |
@popy2k14 If i reading the code change and the discussion is the groupe 0xfff0 in the database linked to the "group 0" in the API. The groupe 0 is inactivated and 0xfff0 added if not there after restart. deCONZ can taking little time doing some magic after restart but if all is working the groupe 0 sould working in the API that hue essential is using (i dont like tapping on the switch in my handy then its being little dark all over then so i have not testing if its working). My feeling is that the adding and deleting is working in the DB but perhaps not the linking for the API calls. "Some kind of magic (Queen)" Then you is restarting deCONZ open the new debug window and you can see how the system is reading the groups from the DB and adding the lights in it. |
yeah i know, but the issue is that it "deletes" zigbee 0x0000 (which is ok because 0xfff0 is used) and 0xfff0 after a few minutes of deconz start. So i can not use REST-API groups/0 (which should be internally 0xfff0). How can i disable/prevent this behaviour? |
If you having windows: Sorry I think its one bug because its written in the discussion to the PR how it is working but perhaps is not tested in real then the DB part is working. As work around you can do one new normal groupe and adding all your (around 50) lights in it and rewriting your automations AND hope its works OK. I was finding theise behaviour for 3 weeks ago then sniffing IKEAs remote and the scene select function that is not working. Was deleting all groups in one light and some seconds the 0xfff0 was automatically added by deCONZ all the time and i was hunting the groupe 0xff09. The DB i have seeing the deleting / cleaning the DB from crap after moving devices to ZHA. |
@popy2k14 Pylips looks very interesting if having one Philips TV !!! |
That's my commit. Sorry I broke things for you. There is a config setting which stores in the database which zigbee groupid (normally 65520) is used for rest api group 0. This is in the database as under table "config2", variable "group0". If "group0" is 0, the zigbee group is deleted and a new one is created. Sounds like something is going wrong there. Could you find out what you have in the database for config2/group0? |
@KodeCR no problem :-) i can help debug |
I dont have that proble then i dont using API (Only HUE Essentials) bit this os the record: "14" "group0" "65520" I think the DB part is working but not the linking to API. |
api linking is working! i can access REST-API "groups/0" after fixing the DB (set deleted to normal) and starting deconz. Currently fetching an debug log.... |
In HA i have the IKEA scene defalt groupe "Group 65289" from deCONZ but no 0 or 0xfff0 perhaps is hidden or the linking is not working to API. |
Thanks, I can't see in the commit I made how it would be deleted. In the original commit that only happened if group0 from the database was 0. I did commit a "fix", but that one deleted the group only if the zigbee address is 0. So it's working right after starting deCONZ? |
After "fixing" DB (set deleted to normal) on 0xfff0 entry and starting deconz it works for a few minutes. |
i think i found the issue, see here from the debug log:
The interesting part is:
Thats an ikea fyrtur rollo and deconz deletes the 0xfff0 (65520) group here. Any hints why? |
Having config2/group0 set to 65520, and having the 0xfff0 group entry as "normal" is the default behaviour and how it is currently working for me. I need to figure out why the group is deleted after a while. Perhaps the debug log gives some information. I'm afraid I'll have to look at it further tomorrow though. |
Ok, I know what is going on now, and I've changed the code to only add lights to the all group, hence the blinds will never be added. Could you please test the following plugin based on the 2.8.0 release: I expect that the group0 will be removed one more time removing the group from the blinds, and then will stay after that. Sorry for the wait. |
@KodeCR thx a lot. Don't worry about the delay in this crazy times. Can I test/use this plugin on my raspbian 02.07.01 installation? (because it's based on 2.8.0) Thx |
@KodeCR using your rest plugin now for 15 minutes in my 02.07.02 system and group 0 was not deleted. Will the PR be merged into the next release? |
Seems good for me also after ~3h. |
Great, thanks for testing and confirming. The PR will need to be reviewed before it's merged, so assuming there aren't any unforeseen issues, probably next release, or the one after. |
Nice, thx for the info. |
As there hasn't been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs. |
Waiting on merge of PR #3966 |
Just to let you know guys, the test build from above running without an issue over a month now. |
As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again. |
Not solved! |
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs. |
Not solved yet |
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs. |
Describe the bug
Yesterday i have updated to 2.05.88 from 02.05.84 and now my groups/0 doesnt work at all.
I cant set it with phoscon "all off switch" or over rest api.
There is a 404 error with HUEEssentials.
Steps to reproduce the behavior
Switch the group 0 as stated above.
Expected behavior
All lights should be controlable with group 0.
Screenshots
Environment
02.05.84 (downgraded again)
26660700
deCONZ Logs
Additional context
When ill do a get on group "0" manuall with the browser the answer is:
GET: http://192.168.0.9:8080/api/XXXXXXXXXX/groups/0
Answer: [{"error":{"address":"/groups/0","description":"resource, /groups/0, not available","type":3}}]
With other groups all is working.
ANy hints how i can get my group/0 working again?
The text was updated successfully, but these errors were encountered: