That’s why i name them in deconz, i get the same if i need to remove the integration to clear up anything.
I use customise.yaml for all other device/entities i want to change name for, that way remove a device and as long as they get the same entity id as before they are the same. only a couple of times have i had to change the entity name to fix that up. used this way for last 4 years or so
I do the same. But we cannot assume all knows how to do it and how the names are converted to entity names (spaces, upper case, non alphanum characters). So the advice to remove the integration should be mentioned as the last option to try if nothing else works.
Updated to 2021.7 and the electricity usage stopped working on the Xiaomi wall switches.
I get the following in the logs:
2021-07-07 15:36:22 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/home/hass/homeassistant/lib/python3.8/site-packages/pydeconz/gateway.py", line 128, in session_handler
self.event_handler(self.websocket.data) # type: ignore
File "/home/hass/homeassistant/lib/python3.8/site-packages/pydeconz/gateway.py", line 169, in event_handler
device_class.process_raw({device_id: event})
File "/home/hass/homeassistant/lib/python3.8/site-packages/pydeconz/api.py", line 40, in process_raw
obj.update(raw_item)
File "/home/hass/homeassistant/lib/python3.8/site-packages/pydeconz/api.py", line 126, in update
async_signal_update()
File "/home/hass/homeassistant/lib/python3.8/site-packages/homeassistant/components/deconz/sensor.py", line 166, in async_update_callback
super().async_update_callback(force_update=force_update)
File "/home/hass/homeassistant/lib/python3.8/site-packages/homeassistant/components/deconz/deconz_device.py", line 92, in async_update_callback
self.async_write_ha_state()
File "/home/hass/homeassistant/lib/python3.8/site-packages/homeassistant/helpers/entity.py", line 419, in async_write_ha_state
self._async_write_ha_state()
File "/home/hass/homeassistant/lib/python3.8/site-packages/homeassistant/helpers/entity.py", line 456, in _async_write_ha_state
extra_state_attributes = self.extra_state_attributes
File "/home/hass/homeassistant/lib/python3.8/site-packages/homeassistant/components/deconz/sensor.py", line 199, in extra_state_attributes
attr[ATTR_CURRENT] = self._device.current
File "/home/hass/homeassistant/lib/python3.8/site-packages/pydeconz/sensor.py", line 546, in current
return self.raw["state"]["current"]
KeyError: 'current'
I could be barking at the wrong tree here but just want to understand what’s going on.
It’s been reported here Phoscon/deCONZ no longer getting current from Aqara smart plugs · Issue #52481 · home-assistant/core · GitHub
I’ll try to fix it tomorrow evening
Tseven, saved me heaps of time! Thanks for the post. Last time spent hours rebuilding everything not knowing this solution…
Does anyone knows how to set the attributes through the addons for the Hue bulbs not to be on after every electricity outage ?
I am running HAOS on a Raspberry Pi 4 using ZHA with a ConBee II. I had the issue where deCONZ would not start since the upgrade to 2021.7.0 or 7.1 All my zigbee devices were showing as unavailable. Role back to 6.6 all working fine again.
2021-07-12 14:13:59 ERROR (MainThread) [zigpy.application] Couldn’t start application
2021-07-12 14:13:59 ERROR (MainThread) [homeassistant.components.zha.core.gateway] Couldn’t start deCONZ = dresden elektronik deCONZ protocol: ConBee I/II, RaspBee I/II coordinator
The upgrade to 2021.7.2 seems to have fixed this, although I can’t see anything in the release notes specific to my issue.
The errors you’re posting is ZHA related and not deconz.
Trying again 
@lbouriez You have to click the second circle in the lights’ bar in deConz (bottom right in my screenshot), and then a menu pops out. (the thing with ‘Light Link’ at the top, just below the lights’ bar).
In that menu, click on ‘on/off’.
Next; make sure you’ve got the Cluster Attributes panel or sidebar enabled (your previous screenshot shows the Node Info panel, that is not the one you need). There you will see a ‘PowerOn OnOff’ line. Doubleclick on the value for that line, and in the popup that appears; click ‘read’. It now reads the setting of of the device. Select your preferred setting and hit ‘write’. if everything went correctly, after clicking ‘read’ again, it will show the new value.
@duncank , Thousands of thanks, it’s perfect, I set it up everywhere, I will do some tests later.
Is it also possible to change the power on behaviour of lights using this method? I have a combination of Hue and Innr GU10 bulbs.
When the Hue bulbs are powered on the fade in, but the Innr bulbs will seem to wait for as long as the Hue bulbs took to reach full illumination and then they would instantly power on (no fade). The same behaviour happens when powering off (only in reverse).
Is this something that can be configured, or is it a limitation of the Innr GU10 bulbs perhaps?
I believe you can set the transition time with the onTime value in my screenshot. If that is not it; I’ve seen the word ‘transition’ somewhere in these settings, so you’ve probably got to look for that.
Hi All,
I have a self infected problem. However, not sure about the next step to solve it.
I have a RPi4 running Home Assistant with a Conbee2 stick. Everything have been running OK for 3 month (from when it was installed) until now. Adding and removing devices and all events/actions handled perfectly using ZHA zigbee. Until yesterday…
The update of the Conbee2 firmware have not been working for some time through the phoscon SW, and yesterday I made a dumb move. I disconnected the conbee2 from the RPi, installed Deconz/Phoscon on a Windows10 machine and plucked in the conbee2. Made a firmware update using the update function in the Phoscon web interface. It claimed it worked, however something must have gone wrong.
After inserting the conbee2 into the RPi4, it did not work. I tried to change serial in the Deconz app under supervisor. It will only allow my to chose “/dev/ttyAMA0” (I do not remember the setting in the working model), It did not help. The ZHA integration reports this error.
Have tried a number of different things to get it all to work again. I have removed ZHA, and Deconz and installed it again. Same error
I have made a clean install of HA, setting up Deconz and ZHA as the only stuff on the HA. Deconz seems working, however ZHA will not accept the serial connection during the install.
I have been a lot in the logs, where there is numerous errors, however not giving me good indications on where to solve it, except from this one.
I think it might all have something to do with this from the supervisor log. It repeates it self every 10 seconds.
21-08-01 14:17:03 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.ADD usb hardware /dev/bus/usb/001/034
21-08-01 14:17:03 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.ADD serial hardware /dev/ttyACM0 - /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2437384-if00
21-08-01 14:17:04 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.REMOVE serial hardware /dev/ttyACM0 - /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2437384-if00
21-08-01 14:17:04 INFO (MainThread) [supervisor.hardware.monitor] Detecting HardwareAction.REMOVE usb hardware /dev/bus/usb/001/034
First detecting the Conbee2 and the second after removing it again.
This behaviour is the same on a new fresh install and on the old working setup (from a restore). On the clean install I even get it wothout Decons supervisor addon.
Im right now on the path of beliving it is a hardware error on the conbee2. I might actually buy a new one just to try it out.
Any ideas before I clean the setup to scratch and, buy a new conbee2 and try again?
Im quite frustrated, even more as Im fully aware that It is all my own fault.
EDIT: Have just ordered a new conbee. Hope this will solve my life😊
Hi,
Received the new conbee2, the “Remove USB” did not happen. Tried on the old install, however ended up with some problems in discovery of devices as they were all “known”.
Hence, made a reinstall of HA. Everything is now OK, except the hours needed to bring all the configuration back:.-)
I have a issue with deconz Addon:
since last night the Addon crashes every 10 seconds.
restoring a snapshot brings no solution, also install a backup on a second system let crash the Addon…
here are the last lines from the log:
10:01:11:928 APS-DATA.confirm request id: 85 → erase from queue
[10:01:12] INFO: Starting VNC server (local/yes)…
2021/08/08 10:01:12 [notice] 316#316: signal 15 (SIGTERM) received from 311, exiting
2021/08/08 10:01:12 [notice] 754#754: exiting
2021/08/08 10:01:12 [notice] 754#754: exit
In exit
Closing socket listening at 127.0.0.1:5901
2021/08/08 10:01:12 [notice] 316#316: signal 17 (SIGCHLD) received from 754
2021/08/08 10:01:12 [notice] 316#316: worker process 754 exited with code 0
2021/08/08 10:01:12 [notice] 316#316: exit
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
my conbee 2 usb-stick cant hold the Zigbee channel:
i switch to 11, 20 or 25. i switch self to the 15 back.
12:22:03:595 Current channel 15
12:22:13:568 channel 15 does not match channel mask 0x00000800 (TODO)
12:22:23:568 channel 15 does not match channel mask 0x00000800 (TODO)
12:22:33:568 channel 15 does not match channel mask 0x00000800 (TODO)
12:22:43:568 channel 15 does not match channel mask 0x00000800 (TODO)12:25:15:569 change channel with nwkUpdateId = 2
12:25:15:569 change channel to 11, channel mask = 0x00000800
12:26:03:596 Current channel 15
12:26:13:568 channel 15 does not match channel mask 0x00000800 (TODO)
Version: 2.11.05 / 9.5.2021
Firmware: 26660700
Does somebody use Aqara DJT11LM vibration sensor via deCONZ? It looks like the sensor isn’t fully implemented yet. I can see the x/y/z tilt axis attributes via deCONZ GUI, but they are missing in Home Assitant.
Also the Sensor does not trigger an event when using Node-RED, on which my whole logic relies on.
HI All,
reciently had a few problems with HA and had to start from Scratch.
having a problem logging into the Phoscon Gateway, the user is different to my account… how do I change that?
I do get the option to reset my password to the default… but erm… what is the default?? where do I find out? I tried the website but got lost looking…
any help?
Thank you
I’m running Hass os on a Ras Pi 4
