-
Notifications
You must be signed in to change notification settings - Fork 485
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
General thread on the 0.77 dropping/slow connection issue. #2875
Comments
So is it being fixed? As when I look at my Deconz it says “commercial version” Not one response to any of the issues, just a downgrade. Two months without an update and when it comes it destroys people’s systems. |
Unfortunately, the Home-assistant Addon is not maintained by DE. Their decision to downgrade is solely their own. Currently, in Discord devs are trying to figure out whats wrong. Also, the user who created the PR to downgrade the addon in HA is there to fix the "lost connections" issue on that. Feel free to join the discussion in Discord :) |
I have Deconz running on a separate RPi 2 from my Home Assistant installation on my x86 PC server, and I haven't had any issues. Not sure how useful that info is, just to pitch in that it also might work correctly I guess. 😊 |
Have been running the 2.05.77 beta (not the later alpha with the APS ACKs reverted) in a larger network with 144 devices during the day, with RaspBee II firmware version 0x26570700 which is equal to ConBee II firmware 0x264A0700. No issues here so far. Note this network doesn't have sleeping end-devices, which have another impact when queuing up many APS requests. My home network with 58 mixed devices, doesn't show the issues either. It would be really helpful if anybody experiencing the issues could try the alpha .77 version and provide feedback if that improves the network operation. http://deconz.dresden-elektronik.de/raspbian/alpha/deconz_2.05.77-raspbian-jessie-alpha_armhf.deb |
Since we are already on beta 77. Why not make it .78 alpha? |
Report from openHAB user (2.5.5):
|
Hi Dennis, is #2273 also related to this? If yes could you please link it and if not could you please have a look into this problem #2273 and maybe give us an update on it? Thanks Beat |
@easybeat It's not connected as the version wasnt out then. The only thing i've seen is that the database might be corrupt. Go back to basic: if stuff doesnt save, why does that happen? 9/10 it happens because it's some local thing that prevents writing. In the case of Klucky, He doesn't provide info requested. Most stuff here isn't just 1 case. If there was a bug that hit all of you, more would have this. I suggest you to open your own issue as none stand on its own. |
here every time i lauch .78 , Some loose lights. Staying on .77 |
@MattL0 Could you open a new bug report on this? |
From what i've read and heard, the newest firmware solves the issue. Can anyone elaborate on their issues after the FW update? |
Since zigbee in general doesn't have any connections (and therefore, neither has deconz), I cannot really follow you. |
@vegetate7 Do you have any logs from the pydeconz component? I don't see anything here that is a problem for deCONZ. |
Hi @Mimiix here i have the logs from pydeconz, as you can see theres a lot of reconnecting: 2020-07-07 10:28:34 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"lastannounced":null,"lastseen":"2020-07-07T14:28:34Z","manufacturername":"dresden elektronik","modelid":"RaspBee","name":"Configuration tool 1","swversion":"0x264a0700","type":"Configuration tool","uniqueid":"00:21:2e:ff:ff:05:ac:17-01"},"e":"changed","id":"1","r":"lights","t":"event","uniqueid":"00:21:2e:ff:ff:05:ac:17-01"} |
Like I have said on discord, it s not deconz deconnection by only websocket disconnection. |
The problem is when in home assistant my devices are unavailable, if i go to Phoscon UI my devices are all available and transmiting without problems (i test my motion sensor and i can see that detect motion when in HA is unavailable). So, for this behavior I assume that the problem is the connection between HA and deconz addon |
So try to check you network config. |
Websockets are requested by clients (and closed by clients). This is not something deCONZ manages. If everything works in phoscon, you should check with HA. We do not manage nor maintain the HA Addon |
As this issue seems to be solved in 0.78, i proceed to close the issue. If there is people having issues on 0.78, please open a own bug report! |
Hello there,
Since 0.77, there has been various reports on dropping connections:
#2863
#2866
Home-assistant has chosen to revert back to 0.75.
home-assistant/addons#1375
In regards to that this topic will be the center on solving this issue.
Currently, @manup and other developers are still not sure what causing this. It might has to do with the introduction of APS ACKs(#2612) . I've been provided with the following Alpha version in which APS ACKs have been disabled. If anyone can test that and share their feedback, please do in this topic!
http://deconz.dresden-elektronik.de/raspbian/alpha/deconz_2.05.77-raspbian-jessie-alpha_armhf.deb
Cheers!
Dennis.
The text was updated successfully, but these errors were encountered: