-
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
Restarting deconz computer fails connecting nodes #2015
Comments
A lot of people seem to have this issue, including me, for the past month now, I would like to help fix this, but I can't find any information on where to start debugging this. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
As per request re-opened. Can you add some details on versions and such? What firmware version are you running and what version of deconz is running? |
Thanks for re-opening. Since the original posting, we've made some further tests. We have this problem ONLY if all the devices are Philips HUE lights. As soon as we add another device (such as an Innr plug) to the network, that seems to "fix" the problem. All devices then appear after a reboot. But if we remove the Innr plug, leaving only the HUE lights in the system, the problem comes back. That may explain why not everyone has this problem, as many users have a mixed set of devices. The HUE lights are all brand new. When they're not seen by ConBee, they can still be turned on/off using the Hue remote, so the zigbee bus seems to work fine. -JM |
Also add the Device type (conbee 1 or 2?) and logs if that happens. Also, what is the host device? |
It was a Conbee I, and we were running it on Ubuntu 16.04 on an Intel NUC. Regarding version numbers, I will need to take a look since this was quite a while back. -JM |
Sounds good. Just update all to latest first, then check again. Also: you are running it on bare nuc? No VM involved? |
On 10 Jun 2020, at 13:40, Dennis D ***@***.***> wrote:
Sounds good. Just update all to latest first, then check again.
Will do.
Also: you are running it on bare nuc? No VM involved?
Bare NUC.
…-JM
|
@TheWizz Hey there! How's things? Any news? |
I'm sorry. Summer holiday got in the way. We'll pick this up after the break. Hopefully, by then the updated firmware/software has been released, so we can just install that and see if it works OK now. Will let you know. -JM |
I think the update is already out ;) For now, i'll close this issue then. Tag me when your back. Enjoy your summer! #familyfirst :) |
I have a simple test system in preparation for a larger system to be deployed shortly. It currently consists of a single HUE light and an Innr switch. I can add those devices OK to deconz, and they operate normally. I can quit and relaunch deconz, and they appear and re-connect OK. Hoerver, if I quit deconz, disconnect the ConBee dongle, plug in the ConBee Dongle then restart deconz, they fail to reconnect.
They first appear to connect (green wires appear), but the light and the INNR plug flash red instea of the normal blue circle. After a while, the green wires disappear.
I can make both devices reconnect again by turning power to the HUE light off then on again. Then they always reconnect, and work normally.
I can also recreate the same problem by restarting the Ubuntu box I run this on. After restart, the same problem as described above happens. Again, I can fix it by power-cycling the HUE light.
I've tested both the current shipping version of deconz as well as the current beta. Both behave the same. This is running on Ubuntu 16.04, starting deconz in GUI mode as a regular program.
-JM
The text was updated successfully, but these errors were encountered: