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
ZHA Light platform group fails to control all lights in group #21456
Comments
I had quite some problems with getting the conbee to work as well. After a while, or some switching of groups these 'Failed to receive transmit confirm for request id:' messages start to appear. When you restart home assistant it looks like it does receive these confirms (you get errors about unexpected confirms after a restart). I went back to deCONZ for now. |
@StyxyDog @jurriaan this is being tracked in several tickets already. #21422 #21423 The core of the issue is the same for all of them. @StyxyDog can you try something for me? can you get it so that all the lights respond to individual commands (to ensure they are all connected and available) then issue a reconfigure node command from the ZHA configuration panel for each one? wait about 30 seconds between each command to give them time to finish. After this is done, restart HA and see if the problem is any better. if that doesn't work please try this branch: https://github.com/dmulcahey/home-assistant/tree/dm/zha-forgive-missing-basic and let me know if that helps at all. I need feedback to determine if these changes help because the Sengled bulbs that I have do not exhibit this behavior. |
@dmulcahey I'd been keeping an eye on those issues -I thought this might all be related, maybe this will help shed some light on the problem :) All lights in the set of 5 were responsive (although I noticed some had gone out of sync with their current actual state). However they all responded when toggled. Reconfigure gave me this on bulb 1...
this on bulb 2...
and something similar on the others. So that appears to have been successful :) Thank you! I'll keep an eye on it and let you know if that changes in time. |
Yeah I’ll keep looking at this too. Something is definitely up here. |
They all seem to have gone unresponsive I'm afraid. I have turned them all on, and they lit, but the status didn't change in home assistant. i.e. turned on, but looked like they are still off in HA.
I'm going to try dropping the forgive-missing-basic branch you mentioned before. |
by dropping do you mean using? or are you already using it? and can you do me a favor? go in to the history or logbook and tell me when they became available initially and then when they became unavailable? I need the full times please. Thanks for helping to track this down! |
Ah I meant I dropped the zha directory from your branch into custom_components :) i.e. I am now using it, I wasn't before. Sorry I'll try to be clearer. So before when I did the reconfigure and restart on the standard 0.88.1 it seemed to work for about 1 hour 19 minutes, but I think the reason that they went offline is because I rebooted - the lights had become unresponsive but were still showing as available (eg the zha.stairs_1). I don't know exactly when they became unresponsive. Now (from about 16:52 GMT) I am using your forgive_missing_basic branch. After a reboot and power-cycling the 5 lights, and the light group that controls them together, all seem to be working again. I'll monitor this and let you know any timings. |
1 hr 20 was what I was expecting. That means the lights aren’t sending any traffic for 2 hours... do you know what the signature is for these (endpoints, input and output clusters) |
And another failure just a few minutes later...
|
I spammed the button to turn the group on a couple of times and it seemed to break it. Could this be something to do with receiving too many simultaneous requests to switch? If I don't do anything for a minute or so the lights become responsive again. I have quite a lot of zigbee devices approx 25 and two rooms are using these light groups. So the living room has 4 zigbee switches/lightbulbs and the stairway has 5. If these two groups get triggered in short succession it seems to make it fail for a bit. Sorry for all the messages, just thought it might be relevant. |
@StyxyDog don't apologize... i'll take all the info I can get. How many bulbs are there total? I guess it could cause an issue... but it really shouldn't. also, it looks like you need a fix that is in development for zigpy_deconz: zigpy/zigpy-deconz#20 based on this log: |
I have: 8 Tradfri bulbs; 7 Tradfri control outlets (these behave very well); 8 xiaomi motion; 2 xiaomi door. Just as a test I tried clicking the light group on and off in rapid succession, about 10 times and I did manage to make the group fail with the |
@StyxyDog that’s good to know. I’ll get working on a permanent fix. |
@StyxyDog if you have some time and don't mind helping... can you try 2 things for me? 1st, try the HA dev branch. it has some other changes that may make the other branch unnecessary. if that doesn't work i'll give you another branch to try if you're up for it :) |
Happy to help, if it helps you get to the bottom of the problem. I don't think I can get on the dev branch as I'm running hass.io. Had a quick google around but couldn't find anything, do you know if that's possible? I can easily try your other branch by dropping the files into my custom_components directory. That's how I'm currently running the forgive_missing_basic branch. |
You can do that with the dev branch too. Just do the same thing. |
If you are still able to reproduce |
@dmulcahey Ok, just taking a back up. |
Thanks @Adminiuga I will do, but I've not properly tried the fixed zigpy-deconz yet. I'll move on to that next. I did briefly try it, but I was getting too many errors at the time and I didn't want to complicate the issue with too many changes. The 10 clicks and error was with the un-fixed version of zigpy-deconz. |
@StyxyDog just ZHA |
@dmulcahey Looks good. No errors appearing - just the start-up warnings. I can leave it running for the evening and let you know tomorrow how its going. I would certainly have seen issues within that time frame previously. |
Nope, thx man |
@dmulcahey FYI a couple of warnings in the logs. I think some of these are new to me. Nothing was happening at the time, apart from maybe a dog moving around the house and triggering the motion sensors/lights. Things seem to be working correctly. Quite a few of This is a new one...
This is on the dev branch. |
The error one is a question for Zigpy deconz. The other happens from time to time and is a warning... safe to ignore. |
Morning @dmulcahey , a few errors to report from the dev branch. The group of 5 'stairs' lights were turned off by a node-red HA automation at 22:23 and became unavailable at 00:29 (just over 2h). This happened to all 5 lights at the same time, but no other lights. This also happened to one other light different timings, the first time it failed it was a 3 hour gap, the second a 2 hour gap between last operation and unavailable. One light has behaved itself and is still working this morning. Happy to change things or continue testing on this branch. At the moment the group is still unavailable and I'll leave it like that for now, can't guarantee someone won't go and physically toggle the switch though. log messages...
|
This requires fix for zigpy-deconz which is in the master. Copying it custom_component folder won't do it, as it is not a custom component |
No easy way to apply that fix to hass.io then, @Adminiuga? |
unfortunately I don't think there's a way to do it on hass.io
the sequence assertion error is definitely related to zigpy-deconz bug and I'd be really surprised if it has anything to do with the issues the @damarco any chance to push zigpy-deconz sequence leak fix before the next HA release? |
Thank you @Adminiuga I've found that in the dev branch I can click reconfigure and the device becomes available without a HA restart or a powercycle. As a workaround, @dmulcahey, is there any way that we could have the reconfigure button as a service available to HA. I'm thinking that I could automate the process of doing a zha reconfigure when a device becomes unavailable. zha.reconfigure perhaps? Edit: Nope, it can't find that service. Not sure why. I'll try and check things through later. |
@StyxyDog I’m working on a better solution. Hopefully will have something for you to try by the end of the weekend. |
@dmulcahey thanks you. |
@StyxyDog I’m working on something to do that automatically. |
Slight glitch overnight. The lights became unresponsive - not all, but most. A reconfigure didn't work nor a restart of HASS. A reboot of the PI didn't fix and in the end I had to shutdown and pull the power. HASS has restarted and everything looks fine. The group of lights is working again. Something a bit odd going on there.
|
I think that’s zigpy_deconz |
I've removed the dev branch and installed HA 0.89.0. Seems to be functioning pretty well - a few errors still, but I think these are with the underlying zigpy_deconz. I'm going to close this issue and open a new issue if problems persists in 0.89. |
Home Assistant release with the issue:
0.88.1
Last working Home Assistant release (if known):
0.87.1
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io on Raspberry Pi 3 with a conbee USB zigbee coordinator
Component/platform:
ZHA
Description of problem:
I've had a few issues and several errors since moving from 0.87.1 to 0.88 (and now 0.88.1).
I think that I have found the source of some of my problems.
I have a light configured as a group (see YAML below). Physically this is 5 Tradfri bulbs all on a single switch - they are grouped (light: -platform: group) to behave as a single light, in this case light.stairs_light.
All the light seem to work individually, but only one will work when controlled by the light.stairs_light group. However turning on any one of the lights will effect the state of the group.
e.g.
In version 0.87.1 (which I have tried restoring to confirm), all lights are controlled by the light.stairs_light group. I think this is something to do with the light being initially unavailable in version 0.88.1, when that group is created. Only the first light is correctly added, perhaps?
I can get around this by not using this configuration, but it seems like there is a bug somewhere.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Various errors - not sure which are relevant or helpful... These are from around the time I was switching lights on and off.
Additional information:
The text was updated successfully, but these errors were encountered: