-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
deconz not recheable #203
Comments
I think theses errors are just not properly cleared. There is no to worry about but I will look in to it when I have time |
Same situation here! |
Same for me - when you say not properly cleaned, what do you mean? |
Same problem here. Did you find a solution? |
I chabged the Deconz server reference in the nodes to a specific IP which have helped alot. The problem is still there but only very rare. |
It's at least once everyday for me. Anything I can do to investigate this error? |
You can check the node red logs for errors. Also try to connect to the websocket if there is any connexion lost |
in the docker node red log, I get this : |
Yep that is an unexpected deconnection. You can't really do something about it... |
In earlier version of the plugin theses errors wat not showed to the user |
@Hassefar @shlagwuk @Alex-joomla @svenschuldt do you still get theses errors ? |
Hi @Zehir, good start for 2023 :-) |
Could you try again with latest version of node red and the plugin ? |
Current Behavior
Deconz connects fine but after some time, I get the "deconz not recheable" under several of my nodes. If I re-deploy the flow, the nodes will connect again. Basically the same issues as: #162
However, this is not resolved for me. :-(
I am currenlty of the newest version of NR and 2.3.3 of node-red-contrib-deconz
Expected Behavior
No response
Steps To Reproduce
No response
Example flow
paste your flow here
Environment
The text was updated successfully, but these errors were encountered: