Upgrade to 0.105 deconz devices all unavailable

Configuration Zigbee
1

Hi all,

I upgrade from 0.104.3 to 0.105.2 and it seems that my deconz no longer sees any devices (they’re all “unavailable”) … I’ve done the obligatory starting and re-starting everything.

2

For what it’s worth, when I “open web ui” in the plugin, I can see all lights and control them but they don’t show up in Home Assistant itself.

3

Apologies if I took anyone’s time with this.

Turns out a restart of the whole machine brought the devices back.

4

same issue for me with Z-wave devices, a lot of them were unavailable after 105.1, this is why I decided to rollback to 104.3. Now when I launch check config add-on, I’ve got an error, so I’m waiting for 105.3 :wink:

5

I have DeConz on a standalone Pi and HA core VE in a LXC container on a NUC - I have noticed that since 105.x that it does go unavailable quite often - at least 8 or 9 times a day for at least 1 minute (I have a Node Red flow that checks this and alerts me after 1 minute of unavailable).

Prior to 105, it was stable. When it shows as unavailable in HA, I can VNC to the standalone Pi from my MacBook and open the web ui to control everything - I can even use the Hue Essentials app on my phone, so it must be the HA integration going down rather than Deconz itself in my instance?

Anyone else notice this?

6

There is an issue reported on this behavior. Though it got closed a few days ago. Since the logs doesn’t actually show any errors what is needed is some kind of network trace between hass and deconz to see what actually fails

7

Thanks, I’ll see what I can do.

Was driving me crazy yesterday lol.

I thought the SD card may be failing on the Pi so re-imaged it to a new card, then I swapped out the Pi with a spare incase it was that. I then thought it may be my Proxmox that runs HA, node-red, mqtt, pihole etc so rebooted that. Had issues that pihole didn’t come back so i had no DNS in the house (took me 30 mins to work that out).

In the end i realised it must just be the add in. The reason it caused mayhem in the house (and the dreaded wife approval stakes) was that only last week I moved all 30+ hue lights to Deconz from the Hue Hub. We don’t use light switches in the house and everything is automated by motion/time of day/light or dark/voice etc. Seems the other half has got so used to it that she forgot what it was like in the old days. The positive is that it proves all the automations work if we don’t notice them :slight_smile:

8

Just FYI, I have noticed that in one of the latest changes, ome of my components switched type in deconz…

I have a couple of these: https://www.aliexpress.com/item/4000661444680.html?spm=a2g0o.productlist.0.0.32041d7an6kB44&s=p&algo_pvid=12a19a82-9fd2-455f-860c-8be58f7220a7&algo_expid=12a19a82-9fd2-455f-860c-8be58f7220a7-22&btsid=8b3bc396-9f0d-45b1-b475-ea00dfd941cc&ws_ab_test=searchweb0_0,searchweb201602_6,searchweb201603_55

and the component changed from (when it was registed) as being picked up as a light, to now being correctly identified in deconz as a switch which meant that all my Home Assistant entities relying on these components needed changing…

9

I didn’t realize it was such a widely used type. If I’d known I’d have marked it as a breaking change. Sorry!

10

So, the problem is back after about a day. :frowning: My lights become “unavailable”. This never happened before 0.105.x

11

Yep had 3 ‘unavailable’ events in the last 5 hours.

I am going to set up some monitoring from the HA machine to my deconz pi to see what traffic is dropping. Doesn’t seem to be pings, so must be something to do with the way the integration talks to deconz.

@Robban Does the integration effectively make calls to the REST API? or does it do something different?

Thanks

mb

12

Normally it just listens on websocket. Rest api is used when controlling devices on deconz, on start up and when using deconz configure service

1 Like
13

I have a couple of real work related bits to do today - I will set up some monitoring later to see if i can get any idea of what is happening

14

I just upgraded to 105.3 and my lights are back. (I was on 105.2 previously).
Now, if they will stay or not …

15

…and they are gone again :frowning:

I am seriously considering moving to WiFi bulbs instead. I have one that has never ever had an issue.

16

Rebooting the whole server brings them back. But soon after they disappear and go “unavailable”.
Again, never had this issue before 0.105.

17

Whilst mine still go offline occasionally, they do come back after about 2 mins. It happened three times yesterday again.

I am going to see if I can run some traces between HA and the Deconz Pi a little later in between meetings.

As you say, prior to 0.105 it was really stable.

18

Hve you checked your channel use against the channels you use for wifi?

19

My issue is slightly different but I also had issues with 105 and thought it was the sd card so I fully rebuilt my system. After rebuilding it on 105.3 I’ve noticed that the switches I have are not seen as Entities so things like node red can’t see them. I can’ be 100% sure but I thought these were Entities before the upgrade and not just devices.

After the full rebuild the Deconz devices were much more stable than they were in the upgrade.

20

I’m not sure whether it has anything to do with this problem, but the Phoscon app, as far as I can see, is still running at hassio.local (this is still the only place I can log on to it), while home assistant itself now runs at homeassistant.local after the name change?