search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.5k stars 30.7k forks source link

deCONZ unavailable status every hour for one or two minutes #31072

Closed cobirnm closed 4 years ago

cobirnm commented 4 years ago

Home Assistant release with the issue: 0.104.2

Last working Home Assistant release (if known): 0.103.6

Operating environment (Hass.io/Docker/Windows/etc.): Raspberry Pi 3B+ Docker

Integration: deCONZ

Description of problem: deCONZ integration (all devices) get unavailable status every hour (more or less) for one or two minutes. On Home Assistant logs I get no error but in deCONZ logs i can see the error:

19:20:42:923 Remove websocket 192.168.1.77:40340 after error Unknown error

19:58:07:128 Remove websocket 192.168.1.77:45302 after error Unknown error

20:58:16:152 Remove websocket 192.168.1.77:46276 after error Unknown error

I have reverted my instalation to 0.103.6 and since then no errors have occurred.

Can someone help me to debug this?

Thank you in advance.

probot-home-assistant[bot] commented 4 years ago

Hey there @kane610, mind taking a look at this issue as its been labeled with a integration (deconz) you are listed as a codeowner for? Thanks!

Kane610 commented 4 years ago

If you get the error on deconz side you should report it in deconz github.

You can enable debug for the integration to see what the last messages are over the websocket. The integration doesn't send anything over websocket, only receives data

Kane610 commented 4 years ago

A thought, have you tried to upgrade again to see if you get the same behaviour?

cobirnm commented 4 years ago

A thought, have you tried to upgrade again to see if you get the same behaviour?

I have tried during the day to run 0.103.6 and had no error. Again I updated to 0.104.2 and again after more or less one hour I get the unavailable state. At this point I have activated debug but the log shows no errors. For sure this is being caused by home assistant I just can’t figure out why. By what I have seen in home assistant forum I’m not the only user with this error.

belinned commented 4 years ago

Same problem: unavailable entities HA 0.104.3 and phoscon gateway. Went back to 0.103.6 and the problem disappeared again.

Kane610 commented 4 years ago

Are you guys running custom components or other components? Any difference if you disable all of them?

Can you share debug logs from hass?

belinned commented 4 years ago

Unfortunatly, There was nothing in the logs at the times that the event occured. What do you mean with custom components? I disabled node red, but that didn't help. Gonna try to enable logging for deconz integration and going back to 0.104.3.

belinned commented 4 years ago

@Kane610 , at 16u06 and 16u18 my entities became unavailable. Here is the log: deconz.txt

Kane610 commented 4 years ago

Im gonna need to add more debug logging in order to understand this better

cobirnm commented 4 years ago

Are you guys running custom components or other components? Any difference if you disable all of them?

Can you share debug logs from hass?

I only have 2 custom components: smartir climate_group

It makes no difference if I disable them.

Just to add that today I had to start deconsz from scratch and still I get the same unavailable.

Regarding the debug log do you need home assistant debug log or Deconz?

Kane610 commented 4 years ago

I pushed a commit to HASS dev branch that improves debug logging, could you try out the beta after it is built today?

Happytodd commented 4 years ago

I'm having same issue since updating, all my sensors become unavailable for a minute or two, about 6 times per hour. They all happen at the same time. Some of my sensors don't even trigger automations, and when I load up Deconz in TightVNC they don't appear, or seem to have a connection with my Raspbee. Quite a frustrating process over the last week or so and haven't gotten a fix!

Kane610 commented 4 years ago

I'm having same issue since updating, all my sensors become unavailable for a minute or two, about 6 times per hour. They all happen at the same time. Some of my sensors don't even trigger automations, and when I load up Deconz in TightVNC they don't appear, or seem to have a connection with my Raspbee. Quite a frustrating process over the last week or so and haven't gotten a fix!

If you can't see the sensors in TightVNC you have a different issue. This issue is about the websocket shutting down due to some error making the sensors unavailable in hass.

Kane610 commented 4 years ago

What else you can do here is to try to take a network trace to see what is happening with the websocket communication

Kane610 commented 4 years ago

Apart from disabling custom components did you guys try to disable other integrations?

belinned commented 4 years ago

I pushed a commit to HASS dev branch that improves debug logging, could you try out the beta after it is built today?

Thank you. I'm just a noob. Do I just need to add this: logger: default: info logs: pydeconz: debug homeassistant.components.deconz: debug

And how do I know when the HASS dev branch's new debug logging is ready?

Apart from disabling custom components did you guys try to disable other integrations?

Next to Deconz, I only have the google cast integration.

Kane610 commented 4 years ago

I pushed a commit to HASS dev branch that improves debug logging, could you try out the beta after it is built today?

Thank you. I'm just a noob. Do I just need to add this: logger: default: info logs: pydeconz: debug homeassistant.components.deconz: debug

And how do I know when the HASS dev branch's new debug logging is ready?

Apart from disabling custom components did you guys try to disable other integrations?

Next to Deconz, I only have the google cast integration.

Everyone's a noob at something and at some point in time. If you want to use the beta you need to change your setup to follow the beta track and that differ between different installations

cobirnm commented 4 years ago

I pushed a commit to HASS dev branch that improves debug logging, could you try out the beta after it is built today?

Since Friday that I have been running 0.105.0b2. Up until now I have had no errors. Besides the the logging did you change anything else?

Kane610 commented 4 years ago

I pushed a commit to HASS dev branch that improves debug logging, could you try out the beta after it is built today?

Since Friday that I have been running 0.105.0b2. Up until now I have had no errors. Besides the the logging did you change anything else?

Nothing that should affect this, then again I don't see that any changes I did prior is the cause of this issue either :)

ghost commented 4 years ago

I am currently having the same problem, returned to 0.103.6 for now. If I can be of any assistance on my version I'm glad to help!

Kane610 commented 4 years ago

I am currently having the same problem, returned to 0.103.6 for now. If I can be of any assistance on my version I'm glad to help!

You're the first one reporting this issue for 0.103.6. This makes me think even more that it is not related to the integration

Kane610 commented 4 years ago

@cyberoida I've suggested a few things some comments up that could help understand the reason for this issue

ghost commented 4 years ago

@Kane610 no I'm sorry! I returned to 0.103.6 because it was not working in 0.104.x. Sorry for the misunderstanding. Everything is perfectly fine with 0.103.6

ScharfAsATack commented 4 years ago

Just chiming in at @Kane610 's request. I was also on 0.104 and my Home Assistant (Running in Docker on an Ubuntu VM on Windows 10) was seeing my Deconz entities (Hue motion sensors and dimmer switches) cycling between proper function and "unavailable" every 10-20 seconds. My Deconz installation is running on an RPi (on my local network) with a Conbee 2 stick with Phoscon appearing to report/function properly throughout.

To remedy the problem, I joined the HA beta channel and installed 0.105.0b0 (initially to access new debugging features). I also deleted my Home Assistant database file, as it had gotten to be very large. Between these two actions, the problem has completely disappeared and everything has been functioning flawlessly for over 96 hours at this point.

Kane610 commented 4 years ago

@ScharfAsATack thanks for you trying it out! 0.105 will be out on Wednesday, lets hope we can close this issue after that

belinned commented 4 years ago

I am running 0.105. The problem seems to be disappeared. Thank you!

cobirnm commented 4 years ago

Hello,

Fot the past day an half I have run 1.105.0 and 1.105.1. In both versions I have had no issues, so i'm closing the issue. Thank you all for your help and comments.

BananaPukeh commented 4 years ago

Hi, I'm still having this issue all DeCONZ devices becoming unavailable every two minutes or so. My setup is divided into two servers: a main server and PI 3 with a RaspBee radio.

https://imgur.com/a/PE8dCa7

Main Server:

PI 3:

I've already tried wiping my database, restarting both systems.

When I downgrade to 0.104.1 everything works fine.

ghost commented 4 years ago

Unfortunately, I also have to chime in. I upgraded my 0.103.6 installation (working perfectly) to 0.105.3, and the issue has gotten a lot better (unavaibale once or twice a day), but it still is not gone.

My timeline was: 0.103.6 (working without issues) -> 0.104.x (a lot of "Unavailable" states, maybe 2-3 per hour) 0.104.x -> 0.103.6 (still no issue) 0.103.6 -> 0.105.3 ("Unavailable" once or twice a day)

My setup:

main server running Debian 10.3 and home-assistant in the official docker

raspberry pi 3 with Raspbian and DeConz in current docker image, Conbee 2 stick.

The raspberry is connected using WiFi, but the connection is usually very stable.

If you need and logs from deconz or HA, please let me know!

ghost commented 4 years ago

@cobirnm could you reopen the issue please? something fishy is still going on with the integration...