If you want you can enable debug logging for the deConz integration and press the buttons a few times and pm me the logs we can figure out if there are no events from Deconz or not
How can I activate debug leval for an addon?
With logger.set_level
data:
deconz: debug?
PS: found it but which loglevel is debug … 1?
And is it aps or info?
No home assistant debug logging :). There is an example on deconz integration documentation page.
Has anything noticed most of their sensors not working right after 2022.11? Motion sensors with lux readings no longer report Lux for example
There is one issue open. But I’m lacking good debug logs to understand why. So if you could enable debug logging for deconz integration and share those logs with me it would be helpful
Thanks to those users sharing logs I could resolve an issue that I had tests for (but unfortunately failed silently)
Released with Home Assistant 2022.11.2
1 Like
What comes to error:
…when setting up triggers for My_automation and my comment later
Today I noticed this method does not work anymore. Reloading automations even manually by button press in Developer Tools/ YAML configuration reloading does not seem to work. It looks like it flashes the button to green so smoothly, it makes me to think is it actually doing anything anymore?
This error does not happen during every restart, so I cannot tell exactly, when there was a change, but I updated to latest core 2022.11 just few days ago
EDIT: In 2022.11 Smarter reloading of automation & scripts was introduced.
Now I really need another way to get up from error
No deconz_event tied to device "My_button_name" found'
Anyone having issues with battery levels reporting? Strange behavior I abserved recently; when device gets disconnected from deconz (not sure why, happens from time to time) and is configured again, it does not report battery level anymore. I have 2 such devices now (IKEA power on/off switch and Aqara multisensor). I tried several times to delete and re-add these devices to deconz, but without success. I meand I can add them to deconz and devices are fully functional (e.g. sensor provides all environmental readings and switch operates properly), but battery level is unavailable… Any way to restore this?
EDIT: patience is a virtue… After ~2 hours Aqara sensor suddenly started to report battery level again. Yet Ikea switch does not…
Maybe write an issue that the removal of automation reload should be reverted?
An interesting thing would be to se full logs from homeassistant one from a good start up and one from a bad startup
I don’t know how and why but after updating Supervisor to 2022.10.2 lot’s of deconz sensors stopped working. I can see them from phoscon, but in HA they are reported as removed.
And strangeset things, that some Aqara temperature sensors works and some does not. Same to some innr outlet plugs which reports electricity usage: some of them work and some of them does not.
There are no changes related to supervisor which should affect the integration nor deconz AFAIK
Sorry those all home assitant core/supervisor/home assistant os are something that I often mislabel.
And I updated home assistant to 2022.11.X. (not to 2022.10 as stated previously) but cannot remember exact version
Anyway after restoring 2022.9.7 from backup all sensors are working again
Wait for 2022.11.2 and hopefully your issue is fixed
1 Like
Suddenly my deconz HA addon stops working after months/years.
I cant put my lights out (been on for +24 hours :() and i cant find the reason
I’m on latest HA version (rasp pi 4), deconz addon
In the logs from the addon i see
Tried rebooting/restarting/ unplugging… didnt add any new device/usb decvice
08:24:07:050 0x0017880104846CEF error APSDE-DATA.confirm: 0xE1 on task
08:24:07:854 0x0017880104A9F550 error APSDE-DATA.confirm: 0xA7 on task
08:24:08:734 0x00178801083CC172 error APSDE-DATA.confirm: 0xA7 on task
08:24:10:726 No presence sensor found for 0x001788010918AF04, endpoint: 0x02
08:24:10:727 ZCL attribute report 0x001788010918AF04 for cluster: 0x0406, ep: 0x02, frame control: 0x18, mfcode: 0x0000
08:24:10:729 SC tick → StateRead
08:24:10:730 SC tick → StateRead
08:24:10:735 0x842E14FFFEDFA22C error APSDE-DATA.confirm: 0xA7 on task
08:24:11:853 0x842E14FFFEDFA22C error APSDE-DATA.confirm: 0xA7 on task
Any idea what could cause this?
With the high energy prices, i would like to turn of my lights lol
Posted on deconz forum too
suddenly all is working again :-/ hate such things
deCONZ have been a real pain in the *** for me lately. It stops to function daily and I need to restart the HA system or replug the conbee stick and it will work again. I cant remember exactly when this started but I think it was with the latest update.
So basically everything is unresponsible and I can’t decipher what’s wrong from the logs.
I’ve had the following warning in my HA core logs however, but don’t know if its relating the the total failure I describe above but it shows up constantly even when it’s working as it should:
Logger: pydeconz.models.light.light
Source: components/deconz/light.py:167
First occurred: 21:56:35 (4 occurrences)
Last logged: 21:56:37
Unexpected light color mode 2
What does the above warning mean? Could it be related to the total failure?
What should I look for in the logs when it fails again?
On the last issue - see deCONZ - Unexpected light color mode 2 · Issue #2720 · home-assistant/addons · GitHub
On stability, I have had no such issues. But I run deconz on a different Debian machine and not as a HA addon.
Is this on HA side:
Logger: pydeconz.models.light.light
Source: components/deconz/light.py:167
First occurred: 10. november 2022 19:43:04 (2007 occurrences)
Last logged: 10. november 2022 22:19:02
Unexpected light color mode 2
?
Muller tint light e14 is going in byitself with adaptive light combination, something changed with ddf?
I’m running deConz as addon with HA OS on a HA blue! and have beside some trouble with my hue dimmer switches no other or stability issues.
Its just a warning of an unexpected value in the color mode property, IIRC this typically means something on deCONZ side with the device support. It shouldn’t really affect the daily behaviour and if it gets logged too much you can change logging level for deCONZ integration to errors only