Skip to content
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

Open
Hassefar opened this issue Mar 2, 2022 · 13 comments
Open

deconz not recheable #203

Hassefar opened this issue Mar 2, 2022 · 13 comments
Assignees

Comments

@Hassefar
Copy link

Hassefar commented Mar 2, 2022

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

  • deCONZ plugin version: 2.3.3
  • Node-RED version: 2.2.0
  • Node.js version:
  • npm version:
  • Platform/OS: Rasbian
  • Browser:
@Zehir Zehir self-assigned this Mar 3, 2022
@Zehir
Copy link
Member

Zehir commented Mar 3, 2022

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

@Alex-joomla
Copy link

Same situation here!

@ghost
Copy link

ghost commented Apr 25, 2022

Same for me - when you say not properly cleaned, what do you mean?
On my side, the node does not work and consequently none of the flows the node is connected to.
Thanks for helping!

@shlagwuk
Copy link

Same problem here. Did you find a solution?

@Hassefar
Copy link
Author

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.

@shlagwuk
Copy link

shlagwuk commented Jul 19, 2022

It's at least once everyday for me. Anything I can do to investigate this error?

@Zehir
Copy link
Member

Zehir commented Jul 19, 2022

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

@shlagwuk
Copy link

shlagwuk commented Jul 19, 2022

in the docker node red log, I get this :
19 Jul 06:06:46 - [warn] [deconz-server:Phoscon-GW] WebSocket connection timeout, reconnecting
19 Jul 06:06:46 - [warn] [deconz-server:Phoscon-GW] WebSocket disconnected: 1006 -
19 Jul 06:06:56 - [info] [deconz-server:Phoscon-GW] WebSocket opened

@Zehir
Copy link
Member

Zehir commented Jul 19, 2022

in the docker node red log, I get this error:
19 Jul 06:06:46 - [warn] [deconz-server:Phoscon-GW] WebSocket connection timeout, reconnecting
19 Jul 06:06:46 - [warn] [deconz-server:Phoscon-GW] WebSocket disconnected: 1006 -
19 Jul 06:06:56 - [info] [deconz-server:Phoscon-GW] WebSocket opened

Yep that is an unexpected deconnection. You can't really do something about it...

@Zehir
Copy link
Member

Zehir commented Jul 19, 2022

In earlier version of the plugin theses errors wat not showed to the user

@Zehir
Copy link
Member

Zehir commented Dec 21, 2022

@Hassefar @shlagwuk @Alex-joomla @svenschuldt do you still get theses errors ?

@Alex-joomla
Copy link

Hi @Zehir, good start for 2023 :-)

Just checked and I still get the same messages
Bildschirmfoto 2022-12-31 um 11 50 09

@Zehir
Copy link
Member

Zehir commented Dec 29, 2023

Could you try again with latest version of node red and the plugin ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants