I’m not using it because it’s still beta
But i’m interested in it!
Hi,
Sensors using deCONZ integration stopped refreshing yesterday in Home Assistant and I’ve been trying to find out, what’s the matter with them. The only way to get the sensor values refreshed is to restart Home Assistant, hence I created a cronjob restarting HA every 5 minutes… Not very fancy but at least my sensor values are updating
In Phoscon App I can see that the values are changing, but for some reason HA only reads those when it starts. The strange thing is that I have not updated or reconfigured anything so system should have been in steady state.
My setup is Raspbian, Conbee II, HA Core 2021.1.5 and deconz-2.09.03
Any idea how I would be able to debug this further?
That typically means that the websocket session is not set up for some reason
How can I check that and also make sure, that it will be set up?
Enable debug logging for the integration and see what you receive over websocket (if anything) on hass side
Did that and taking a look at log it seems like the sensor events are coming to Home Assistant:
2021-03-04 18:16:25 DEBUG (MainThread) [pydeconz.websocket] {"e":"changed","id":"16","r":"sensors","state":{"lastupdated":"2021-03-04T16:16:25.001","temperature":-633},"t":"event","uniqueid":"00:15:8d:00:04:0e:42:55-01-0402"}
I’m just wondering, why this value does not update to Lovelace UI?
I have a Hue color bulb. It always turns on using the color that was used before turning off and then changes to the new color. How can i turn it on with the new color only?
Thank you very much to point me to a solution of Deconz connection who caused me a lot of headcache. For some reason DeconZ IP was in my case 172.30.33.2, but after HASSIO reboot or just DeconZ plugin restart it becomes 172.30.33.1, that’s why HA can’t connect anymore to DeconZ.
Hi,
I try to configure Deconz with HA.
I add a new Xiaomi sensor with no problem. It appears in HA and everything is ok.
But I try to add now two switches … They appear in HA. But all events are triggered twice. So I cannot configure automation because they are launched twice.
I launch the listening of event and events are really fire twice as you can see in screenshot.
Any ideas ?
How can i update to deconz 2.10beta?
Until 2.09. is a Bug, its Not possible to
Run ZBMini
Either wait till next official release of the addon. Deconz non beta is on a monthly release cycle.
Or install Deconz on another machine and not as a Home Assistant addon. Then you decide when to upgrade. See my earlier posts about this. In your case, waiting is probably your best option
I am no longer able to connect to the conbee II on my hassos running in a kvm. This used to work perfectly and the device is still attached to hassos as normal. Could this be related to changes in the deconz addon? I saw recent commits tweaking things related to privileges etc…
Im runinng a intel nuc with homme assistant os. I hate that the deconz addon is so far after beta branch. Is there a way to fix this?
2.09.03 is the latest stable release ( Release Roanoke · dresden-elektronik/deconz-rest-plugin (github.com)) which was released less than a month ago, the date you see there is when v 2.9.0 beta was released
i doubt they will base it on beta builds so all we can do is wait till new version released from dresden-elektronik
see version history here
Releases · dresden-elektronik/deconz-rest-plugin (github.com)
Im runinng a intel nuc with homme assistant os. I hate that the deconz addon is so far after beta branch. Is there a way to fix this?
I run Deconz on a separate Raspberry Pi (they provide ready made SD-card images). That way I have full control over which version I use.
same issues here. creating a scene in phoscon can solve this, but … its quite annoying
I’m having the exact same issue @exrx! It’s been driving me bonkers!
I thought I was going crazy… it happens about once a day at random times, and always with a very specific set of entities. Everything in deconz is updated correctly, but it’s “stuck” in HA. Only a restart to HA works.
I have a hunch it might have something to do with this commit, which changed how the WebSocket connection works (though I went over the code and I haven’t spotted anything significantly different):
Did you ever find a solution to this, other than restarting HA every 5 mins?
What does the logs say if you enable debugging for the integration? I think it also might b better to create an issue on hass github. It’s easy to forget or loose track of problems using the forums
Unfortunately I was not able to find out, what was the issue in the end of the day. Luckily I had a a month old backup of my setup so I was able to revert to working configuration. I haven’t seen the issue since.
Well, of course, I’ve been running it in debug for 2 days and all of the sudden it doesn’t happen anymore I’ll wait longer and I’ll add that to the issue on github.
EDIT: It just happened now, and I see nothing special in the debug logs.
Some insights:
- It looks like the pydeconz.websocket connection just dies at some point (or maybe it’s just the thread that dies?), however the pydeconz.gateway is still live because I still see log entries.
- I’m able to control entities from HA, but I don’t see their state gets updated. For example, I’d turn on the light from HA, the light would actually turn on, but the state would remain OFF in HA, and in deconz it is ON. In the debug log I would only see pydeconz.gateway messages but no pydeconz.websocket messages after a certain point in time.
- The last message I see from pydeconz.websocket looks like a normal state update message:
2021-03-21 10:40:29 DEBUG (MainThread) [pydeconz.websocket] {"attr":{"id":"53","lastannounced":"2021-03-15T11:53:13Z","lastseen":"2021-03-21T10:40Z","manufacturername":"LUMI","modelid":"lumi.plug","name":"REDACTED","swversion":"09-04-2018","type":"Smart plug","uniqueid":"REDACTED"},"e":"changed","id":"53","r":"lights","t":"event","uniqueid":"REDACTED"}
- After this, no log entries from pydeconz.websocket.
I’ll add this to the issue I’ll open on Github.
EDIT2:
Issue opened: