deCONZ - Official thread

cdrom1028 · July 3, 2019, 8:02pm

I’m not certain where to get those from…

19-07-03 19:07:58 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
19-07-03 19:07:58 INFO (MainThread) [hassio.host.services] Update service information
19-07-03 19:07:58 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
19-07-03 19:07:58 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'}
19-07-03 19:07:58 INFO (MainThread) [hassio.host.services] Reload local service hassio-apparmor.service
19-07-03 19:07:58 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1
19-07-03 19:07:58 INFO (SyncWorker_1) [hassio.docker.interface] Attach to homeassistant/qemux86-64-homeassistant with version 0.95.4
19-07-03 19:07:58 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/15ef4d2f repository
19-07-03 19:07:58 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/a0d7b954 repository
19-07-03 19:07:58 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/3833edd4 repository
19-07-03 19:07:58 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/core repository
19-07-03 19:07:58 INFO (MainThread) [hassio.store] Load add-ons from store: 63 all - 63 new - 0 remove
19-07-03 19:07:58 INFO (MainThread) [hassio.addons] Found 26 installed add-ons
19-07-03 19:07:58 INFO (SyncWorker_4) [hassio.docker.interface] Attach to homeassistant/amd64-addon-mariadb with version 1.2
19-07-03 19:07:58 INFO (SyncWorker_2) [hassio.docker.interface] Attach to hassioaddons/vscode-amd64 with version v0.6.0
19-07-03 19:07:58 INFO (SyncWorker_5) [hassio.docker.interface] Attach to samccauley/amd64-googlebackup with version 1.6.2
19-07-03 19:07:58 INFO (SyncWorker_1) [hassio.docker.interface] Attach to hassioaddons/portainer-amd64 with version v0.7.0
19-07-03 19:07:58 INFO (SyncWorker_0) [hassio.docker.interface] Attach to hassioaddons/influxdb-amd64 with version v3.1.0
19-07-03 19:07:58 INFO (SyncWorker_7) [hassio.docker.interface] Attach to homeassistant/amd64-addon-check_config with version 2.1
19-07-03 19:07:58 INFO (SyncWorker_3) [hassio.docker.interface] Attach to homeassistant/amd64-addon-deconz with version 3.1
19-07-03 19:07:58 INFO (SyncWorker_5) [hassio.docker.interface] Attach to hassioaddons/ide-amd64 with version v2.0.0
19-07-03 19:07:58 INFO (SyncWorker_1) [hassio.docker.interface] Attach to hassioaddons/appdaemon3-amd64 with version v4.0.0
19-07-03 19:07:58 INFO (SyncWorker_3) [hassio.docker.interface] Attach to hassioaddons/sonweb-amd64 with version v0.8.0
19-07-03 19:07:58 INFO (SyncWorker_8) [hassio.docker.interface] Attach to homeassistant/amd64-addon-samba with version 8.1
19-07-03 19:07:58 INFO (SyncWorker_7) [hassio.docker.interface] Attach to homeassistant/amd64-addon-configurator with version 3.4
19-07-03 19:07:58 INFO (SyncWorker_5) [hassio.docker.interface] Attach to esphome/esphome-hassio-amd64 with version 1.13.6
19-07-03 19:07:58 INFO (SyncWorker_6) [hassio.docker.interface] Attach to homeassistant/amd64-addon-letsencrypt with version 3.0
19-07-03 19:07:58 INFO (SyncWorker_2) [hassio.docker.interface] Attach to hassioaddons/log-viewer-amd64 with version v0.6.0
19-07-03 19:07:58 INFO (SyncWorker_4) [hassio.docker.interface] Attach to hassioaddons/node-red-amd64 with version v4.0.1
19-07-03 19:07:58 INFO (SyncWorker_9) [hassio.docker.interface] Attach to hassioaddons/glances-amd64 with version v0.5.0
19-07-03 19:07:58 INFO (SyncWorker_3) [hassio.docker.interface] Attach to hassioaddons/adb-amd64 with version v0.5.0
19-07-03 19:07:58 INFO (SyncWorker_7) [hassio.docker.interface] Attach to homeassistant/amd64-addon-ssh with version 6.0
19-07-03 19:07:58 INFO (SyncWorker_0) [hassio.docker.interface] Attach to hassioaddons/grafana-amd64 with version v2.2.1
19-07-03 19:07:58 INFO (SyncWorker_2) [hassio.docker.interface] Attach to hassioaddons/zwave2mqtt-amd64 with version v0.2.0
19-07-03 19:07:58 INFO (SyncWorker_1) [hassio.docker.interface] Attach to hassioaddons/bitwarden-amd64 with version v0.2.0
19-07-03 19:07:58 INFO (SyncWorker_4) [hassio.docker.interface] Attach to homeassistant/amd64-addon-mosquitto with version 5.0
19-07-03 19:07:58 INFO (SyncWorker_5) [hassio.docker.interface] Attach to hassioaddons/adguard-amd64 with version v2.0.0
19-07-03 19:07:58 INFO (SyncWorker_6) [hassio.docker.interface] Attach to homeassistant/amd64-addon-git_pull with version 7.3
19-07-03 19:07:58 INFO (SyncWorker_8) [hassio.docker.interface] Attach to hassioaddons/thelounge-amd64 with version v0.4.0
19-07-03 19:07:58 INFO (MainThread) [hassio.updater] Fetch update data from https://s3.amazonaws.com/hassio-version/stable.json
19-07-03 19:07:59 INFO (MainThread) [hassio.snapshots] Found 4 snapshot files
19-07-03 19:07:59 INFO (MainThread) [hassio.discovery] Load 3 messages
19-07-03 19:07:59 INFO (MainThread) [hassio.ingress] Load 0 ingress session
19-07-03 19:07:59 INFO (MainThread) [__main__] Run Hass.io
19-07-03 19:07:59 INFO (MainThread) [hassio.misc.dns] Start DNS port forwarding for host add-ons
19-07-03 19:07:59 INFO (MainThread) [hassio.api] Start API on 172.30.32.2
19-07-03 19:07:59 INFO (MainThread) [hassio.addons] Phase 'initialize' start 0 add-ons
19-07-03 19:07:59 INFO (MainThread) [hassio.addons] Phase 'system' start 5 add-ons
19-07-03 19:07:59 WARNING (MainThread) [hassio.addons.validate] Unknown options quiet_logs
19-07-03 19:07:59 INFO (SyncWorker_5) [hassio.docker.addon] Start Docker add-on homeassistant/amd64-addon-deconz with version 3.1
19-07-03 19:08:00 INFO (SyncWorker_9) [hassio.docker.addon] Start Docker add-on homeassistant/amd64-addon-mosquitto with version 5.0
19-07-03 19:08:00 INFO (SyncWorker_2) [hassio.docker.addon] Start Docker add-on hassioaddons/zwave2mqtt-amd64 with version v0.2.0
19-07-03 19:08:00 INFO (SyncWorker_7) [hassio.docker.addon] Start Docker add-on hassioaddons/sonweb-amd64 with version v0.8.0
19-07-03 19:08:00 INFO (SyncWorker_4) [hassio.docker.addon] Start Docker add-on homeassistant/amd64-addon-mariadb with version 1.2
19-07-03 19:08:00 INFO (MainThread) [hassio.services.modules.mqtt] Set core_mosquitto as service provider for mqtt
19-07-03 19:08:01 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_zwave2mqtt
19-07-03 19:08:05 INFO (MainThread) [hassio.addons] Phase 'services' start 11 add-ons
19-07-03 19:08:05 WARNING (SyncWorker_9) [hassio.docker.addon] Glances run with disabled protected mode!
19-07-03 19:08:05 WARNING (SyncWorker_7) [hassio.docker.addon] Portainer run with disabled protected mode!
19-07-03 19:08:06 WARNING (MainThread) [hassio.api.security] No API token provided for /api/config
19-07-03 19:08:06 INFO (SyncWorker_9) [hassio.docker.addon] Start Docker add-on hassioaddons/glances-amd64 with version v0.5.0
19-07-03 19:08:06 INFO (SyncWorker_0) [hassio.docker.addon] Start Docker add-on homeassistant/amd64-addon-ssh with version 6.0
19-07-03 19:08:06 INFO (SyncWorker_8) [hassio.docker.addon] Start Docker add-on hassioaddons/adguard-amd64 with version v2.0.0
19-07-03 19:08:07 INFO (SyncWorker_5) [hassio.docker.addon] Start Docker add-on homeassistant/amd64-addon-samba with version 8.1
19-07-03 19:08:07 INFO (SyncWorker_7) [hassio.docker.addon] Start Docker add-on hassioaddons/portainer-amd64 with version v0.7.0
19-07-03 19:08:08 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_glances
19-07-03 19:08:08 INFO (SyncWorker_4) [hassio.docker.addon] Start Docker add-on hassioaddons/vscode-amd64 with version v0.6.0
19-07-03 19:08:08 INFO (SyncWorker_2) [hassio.docker.addon] Start Docker add-on hassioaddons/grafana-amd64 with version v2.2.1
19-07-03 19:08:08 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_adguard
19-07-03 19:08:08 INFO (SyncWorker_6) [hassio.docker.addon] Start Docker add-on hassioaddons/adb-amd64 with version v0.5.0
19-07-03 19:08:09 INFO (SyncWorker_1) [hassio.docker.addon] Start Docker add-on hassioaddons/bitwarden-amd64 with version v0.2.0
19-07-03 19:08:09 INFO (SyncWorker_3) [hassio.docker.addon] Start Docker add-on samccauley/amd64-googlebackup with version 1.6.2
19-07-03 19:08:09 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_portainer
19-07-03 19:08:09 INFO (SyncWorker_9) [hassio.docker.addon] Start Docker add-on hassioaddons/influxdb-amd64 with version v3.1.0
19-07-03 19:08:14 INFO (SyncWorker_7) [hassio.docker.interface] Start homeassistant/qemux86-64-homeassistant
19-07-03 19:08:16 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_vscode
19-07-03 19:08:18 WARNING (MainThread) [hassio.api.security] No API token provided for /api/config
19-07-03 19:08:19 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_influxdb
19-07-03 19:08:19 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_bitwarden
19-07-03 19:08:19 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_adb
19-07-03 19:08:19 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_grafana
19-07-03 19:08:23 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_sonweb
19-07-03 19:09:06 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-07-03 19:09:06 INFO (MainThread) [hassio.addons] Phase 'application' start 5 add-ons
19-07-03 19:09:06 INFO (SyncWorker_9) [hassio.docker.interface] Clean addon_a0d7b954_thelounge application
19-07-03 19:09:07 INFO (SyncWorker_2) [hassio.docker.addon] Start Docker add-on esphome/esphome-hassio-amd64 with version 1.13.6
19-07-03 19:09:07 INFO (SyncWorker_4) [hassio.docker.addon] Start Docker add-on hassioaddons/node-red-amd64 with version v4.0.1
19-07-03 19:09:07 INFO (MainThread) [hassio.api.security] /host/info access from 15ef4d2f_esphome
19-07-03 19:09:08 INFO (SyncWorker_9) [hassio.docker.addon] Start Docker add-on hassioaddons/thelounge-amd64 with version v0.4.0
19-07-03 19:09:08 INFO (SyncWorker_0) [hassio.docker.addon] Start Docker add-on hassioaddons/log-viewer-amd64 with version v0.6.0
19-07-03 19:09:08 INFO (SyncWorker_3) [hassio.docker.addon] Start Docker add-on homeassistant/amd64-addon-configurator with version 3.4
19-07-03 19:09:08 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_nodered
19-07-03 19:09:09 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_logviewer
19-07-03 19:09:09 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_thelounge
19-07-03 19:09:13 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
19-07-03 19:09:13 INFO (MainThread) [hassio.core] Hass.io is up and running
19-07-03 19:09:25 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-03 19:09:25 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-07-03 19:09:25 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
19-07-03 19:09:25 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request running

Martin_Granger · July 3, 2019, 8:14pm

I had that very same behaviour!

cdrom1028 · July 3, 2019, 8:15pm

how did you fix it?

Martin_Granger · July 3, 2019, 8:26pm

Martin_Granger · July 3, 2019, 8:36pm

Yay! VNC support! Hang on, what the hell is this plate of spaghetti ??
Literally no idea what I’m looking at here (closes window quietly and pretends it never existed!)

oleggold · July 4, 2019, 2:59pm

Thanks for your reply.
Could you please confirm that you have deconz Conbee II zigbee network with Xiaomi sensors that are connected to the zigbee network thru routers (repeaters) ?Please let me know the manufacture and model of those routers are.
I am in US and Osram plugs are not a good choice for me, but I will try them if Xiaomi connects to them. Thank you.

yan · July 4, 2019, 7:42pm

Most zigbee devices which are Not battery powered are routers like Hue lights or Smart plugs.
I have some lights and Smart plugs to expand my mesh.
It works great!

Anwen · July 11, 2019, 6:48pm

Using a Conbee I, with the official Deconz add-on for Hassio. Everything is up to date. I have one Hue bulb, two Xiaomi door/window sensors, and a Xiaomi switch, all working. In the Deconz VNC viewer I can see all of those connected to the controller with green lines, so all is working well. However, the Hue bulb (which is on the latest firmware) doesn’t reflect brightness correctly in HA. In the frontend, I can turn it on with the brightness slider, and change the brightness just fine, but if I turn if off and then on again with the HA frontend switch, the light turns on but the slider does not reflect the true state - it stays at zero and does not reflect the current brightness state of the bulb. It has worked for me in the past, but I can’t figure out what breaks it. When it does work, I have a brightness slider in the Phoscon app. But it disappears, for what reason I don’t know. I can turn the bulb on and off in the Phoscon app, but have no brightness slider anymore.

In the debug log below, using the HA pop-up, I turned the bulb on by using the brightness slider about halfway, then moved it to full brightness, then used the switch to shut it off, and then used the switch to turn it on again.

2019-07-11 14:32:40 DEBUG (MainThread) [pydeconz.utils] Sending {'data': '{"on": true, "bri": 255}'} to http://172.30.32.1:40850/api/AC314636F6/lights/1/state

2019-07-11 14:32:40 DEBUG (MainThread) [pydeconz.utils] HTTP request response: [{'success': {'/lights/1/state/on': True}}, {'success': {'/lights/1/state/bri': 255}}]

2019-07-11 14:32:40 DEBUG (MainThread) [pydeconz.websocket] Websocket data: {"e":"changed","id":"1","r":"lights","state":{"alert":null,"on":true,"reachable":true},"t":"event","uniqueid":"00:17:88:01:03:4c:4e:bd-0b"}

2019-07-11 14:32:40 DEBUG (MainThread) [pydeconz] Unsupported event {'e': 'changed', 'id': '65520', 'r': 'groups', 'state': {'all_on': True, 'any_on': True}, 't': 'event'}

2019-07-11 14:32:40 DEBUG (MainThread) [pydeconz.websocket] Websocket data: {"e":"changed","id":"65520","r":"groups","state":{"all_on":true,"any_on":true},"t":"event"}

2019-07-11 14:32:47 DEBUG (MainThread) [pydeconz.utils] Sending {'data': '{"on": true, "bri": 114}'} to http://172.30.32.1:40850/api/AC314636F6/lights/1/state

2019-07-11 14:32:47 DEBUG (MainThread) [pydeconz.utils] HTTP request response: [{'success': {'/lights/1/state/on': True}}, {'success': {'/lights/1/state/bri': 114}}]

2019-07-11 14:32:52 DEBUG (MainThread) [pydeconz.utils] Sending {'data': '{"on": false}'} to http://172.30.32.1:40850/api/AC314636F6/lights/1/state

2019-07-11 14:32:52 DEBUG (MainThread) [pydeconz.utils] HTTP request response: [{'success': {'/lights/1/state/on': False}}]

2019-07-11 14:32:52 DEBUG (MainThread) [pydeconz.websocket] Websocket data: {"e":"changed","id":"1","r":"lights","state":{"alert":null,"on":false,"reachable":true},"t":"event","uniqueid":"00:17:88:01:03:4c:4e:bd-0b"}

2019-07-11 14:32:52 DEBUG (MainThread) [pydeconz] Unsupported event {'e': 'changed', 'id': '65520', 'r': 'groups', 'state': {'all_on': False, 'any_on': False}, 't': 'event'}

2019-07-11 14:32:52 DEBUG (MainThread) [pydeconz.websocket] Websocket data: {"e":"changed","id":"65520","r":"groups","state":{"all_on":false,"any_on":false},"t":"event"}

2019-07-11 14:32:56 DEBUG (MainThread) [pydeconz.utils] Sending {'data': '{"on": true}'} to http://172.30.32.1:40850/api/AC314636F6/lights/1/state

2019-07-11 14:32:56 DEBUG (MainThread) [pydeconz.utils] HTTP request response: [{'success': {'/lights/1/state/on': True}}]

2019-07-11 14:32:56 DEBUG (MainThread) [pydeconz.websocket] Websocket data: {"e":"changed","id":"1","r":"lights","state":{"alert":null,"on":true,"reachable":true},"t":"event","uniqueid":"00:17:88:01:03:4c:4e:bd-0b"}

2019-07-11 14:32:56 DEBUG (MainThread) [pydeconz] Unsupported event {'e': 'changed', 'id': '65520', 'r': 'groups', 'state': {'all_on': True, 'any_on': True}, 't': 'event'}

2019-07-11 14:32:56 DEBUG (MainThread) [pydeconz.websocket] Websocket data: {"e":"changed","id":"65520","r":"groups","state":{"all_on":true,"any_on":true},"t":"event"}

Anyone else with the same issue? Any ideas on how to fix it? I’d really appreciate any help - this is driving me a bit nuts! Thank you!

Robban · July 11, 2019, 9:10pm

Hi!

Sad to hear you’re having issues. Tried to replicate it with my setup but it worked fine if I understood your steps.

Anwen · July 11, 2019, 11:34pm

Thanks for your reply and for trying to replicate the issue. Do you have a brightness slider in the Phoscon app? And do you know if the debug log line that starts with “Unsupported event” means anything?

I’ve tried deleting the bulb from Deconz and re-adding it, and it seems like it fixes the problem temporarily but then the same thing happens again. Frustrating!

Robban · July 12, 2019, 4:53am

That would be that the group id doesn’t exist or is unknown to hass integration.

In phoscon? I got the brightness slider in hass as well.

If you get it intermittently it is probably an issue in deconz

Anwen · July 12, 2019, 1:05pm

Thanks for your help, Robban. A Hue white bulb is the last thing I expected to have trouble with in Deconz!

Viggen · July 13, 2019, 11:52pm

I am looking into switching from RPi3 to NUC (i5/SSD) running Ubuntu/Docker with Hass.io container + deCONZ and Conbee II.
So far I have tested both the proper marthoc/deconz:latest container, as well as homeassistant/amd64-addon-deconz:latest and imported my Phoscon GW backup.

In both cases, all the lights and switches work fine. I can change the scenes etc, however the moment I enable the integration with Hass.io and pull all of the devices, it becomes very flaky:

switching the lights is very intermittent
quite often there is a very long delay before the light comes on/off
quite often I have to press the switch three of four times for it toggle the light

If I delete the integration in Hass.io, immediately all goes back to normal - works flawlessly without any of the above issues.

The logs are showing the following:

> 14:14:37:628 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:37:628 trigger rule 1 - Rule CALL_SCENE
> 14:14:37:731 0x0000000000000000 error APSDE-DATA.confirm: 0xE1 on task
> 14:14:37:814 0x0017880103F11179 error APSDE-DATA.confirm: 0xE1 on task
> 14:14:38:112 button 4000 initial press
> 14:14:38:114 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:38:291 button 4002 short release
> 14:14:38:293 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:38:293 trigger rule 2 - Rule OFF
> 14:14:39:981 button 1000 initial press
> 14:14:39:983 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:40:127 button 1002 short release
> 14:14:40:130 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:40:130 trigger rule 1 - Rule CALL_SCENE
> 14:14:40:238 0x0000000000000000 error APSDE-DATA.confirm: 0xE1 on task
> 14:14:40:601 button 4000 initial press
> 14:14:40:603 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:40:778 button 4002 short release
> 14:14:40:781 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:40:781 trigger rule 2 - Rule OFF
> 14:14:41:883 button 1000 initial press
> 14:14:41:885 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:42:033 button 1002 short release
> 14:14:42:035 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:42:035 trigger rule 1 - Rule CALL_SCENE
> 14:14:42:270 0x0017880103DBE461 level 254 --> 51
> 14:14:42:384 button 4000 initial press
> 14:14:42:387 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:42:487 0x0017880103DBE461 error APSDE-DATA.confirm: 0xE1 on task
> 14:14:42:491 button 4002 short release
> 14:14:42:494 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:42:494 trigger rule 2 - Rule OFF
> 14:14:43:507 button 1000 initial press
> 14:14:43:510 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:43:550 button 1002 short release
> 14:14:43:553 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:43:553 trigger rule 1 - Rule CALL_SCENE
> 14:14:43:677 0x0000000000000000 error APSDE-DATA.confirm: 0xE1 on task
> 14:14:43:952 button 4000 initial press
> 14:14:43:955 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:44:032 button 4002 short release
> 14:14:44:035 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:44:035 trigger rule 2 - Rule OFF
> 14:14:44:640 button 1000 initial press
> 14:14:44:643 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:44:774 button 1002 short release
> 14:14:44:777 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:44:777 trigger rule 1 - Rule CALL_SCENE
> 14:14:44:873 0x0000000000000000 error APSDE-DATA.confirm: 0xE1 on task
> 14:14:45:141 button 4000 initial press
> 14:14:45:144 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:45:238 button 4002 short release
> 14:14:45:241 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:45:241 trigger rule 2 - Rule OFF
> 14:14:46:008 button 1000 initial press
> 14:14:46:011 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:46:125 button 1002 short release
> 14:14:46:128 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:46:128 trigger rule 1 - Rule CALL_SCENE
> 14:14:46:137 0x0000000000000000 error APSDE-DATA.confirm: 0xD2 on task
> 14:14:46:673 button 4000 initial press
> 14:14:46:676 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:46:801 button 4002 short release
> 14:14:46:804 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:46:804 trigger rule 2 - Rule OFF
> 14:14:47:589 button 1000 initial press
> 14:14:47:592 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:47:618 button 1002 short release
> 14:14:47:621 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:47:621 trigger rule 1 - Rule CALL_SCENE
> 14:14:47:761 0x0000000000000000 error APSDE-DATA.confirm: 0xE1 on task
> 14:14:47:964 button 4000 initial press
> 14:14:47:967 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:48:061 button 4002 short release
> 14:14:48:064 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:48:064 trigger rule 2 - Rule OFF
> 14:14:48:247 0x0000000000000000 error APSDE-DATA.confirm: 0xE1 on task
> 14:14:49:732 button 1000 initial press
> 14:14:49:735 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:49:909 button 1002 short release
> 14:14:49:912 rule event: /sensors/2 state/lastupdated num (0 -> 0)
> 14:14:49:912 trigger rule 1 - Rule CALL_SCENE
> 14:14:51:464 0x0017880103DBE461 onOff 1 --> 0
> 14:14:52:563 0x0017880103F11179 onOff 1 --> 0
> 14:14:57:698 Websocket disconnected 192.168.1.14:51680 (state: 0) 
> 14:14:57:746 Current channel 25
> 14:14:57:754 Device TTL 4685 s flags: 0x7
> 14:14:58:814 New websocket 192.168.1.14:51689 (state: 3) 
> 14:15:01:976 Websocket disconnected 192.168.1.14:51689 (state: 0) 
> 14:15:03:126 New websocket 192.168.1.14:51695 (state: 3) 
> 14:15:03:684 Websocket disconnected 192.168.1.14:51695 (state: 0) 
> 14:15:04:764 New websocket 192.168.1.14:51696 (state: 3) 
> 14:15:12:333 Websocket disconnected 192.168.1.14:51696 (state: 0) 
> 14:15:13:432 New websocket 192.168.1.14:51697 (state: 3) 
> 14:15:13:452 Websocket disconnected 192.168.1.14:51697 (state: 0) 
> 14:15:14:570 New websocket 192.168.1.14:51700 (state: 3) 
> 14:15:57:747 Current channel 25
> 14:15:57:755 Device TTL 4625 s flags: 0x7
> 14:16:06:515 no button handler for: RWL021 ep: 0x02 cl: 0x0001 cmd: 0x0A pl[0]: 021
> 14:16:06:515 ZCL attribute report 0x0017880103CAA8A3 for cluster 0x0001, ep 0x02

It looks like there is a lot of 0x0000000000000000 error APSDE-DATA.confirm: 0xE1 on task errors

What could be causing this?

EDIT:
After reading the following bug report I tired connecting Conbee through an USB extender to eliminate potential RF interference and it seems to be back to normal.
My NUC sits in exactly the same place as RPi3 (currently switched off), so again not sure why there are no issues like that on RPi3. NUC’s WiFi and BT are turned off, but I guess it could be generating more RF noise/interference. It’s strange that this isn’t an issue without the Hass.io integration though…
https://github.com/dresden-elektronik/deconz-rest-plugin/issues/430

xbmcnut · July 25, 2019, 2:48am

Anyone seeing random sensors being added with pairing on Xiaomi Smart Plugs? One plug has no power monitoring and all the others have a rogue sensor.

Secondly, I’m trying to add my first Xiaomi button. I got it to pair once (under the switch panel) but I accidentally deleted it and it won’t pair again. Are they paired as sensors or switches or does it not matter?

Holdestmade · July 25, 2019, 5:09pm

I have just tried to add some old Smartthings sensors. They add OK, in that they appear in HA integration but they are not showing up in the Phoscon app - accessed from the webui in deconz addon. Any reason for this ? All my other Xiaomi sensor are showing fine.
When adding, Phoscon does say “sensor ready” but it is nowhere to be seen in the app.
They do show up in the VNC map

Robban · July 25, 2019, 6:04pm

Historically they have needed to add specific support for the Gui for devices to show up

Holdestmade · July 25, 2019, 6:27pm

OK thanks, any way to delete a node ? I’ve tried in the vnc but it just comes back

Robban · July 25, 2019, 6:28pm

You could use the deconz service in hass, though I don’t have the command in front of me but google deconz Rest API to find out how to unpair a device from deconz

Holdestmade · July 25, 2019, 7:08pm

Thanks, gave it a go but didn’t delete them unfortunately.

theCheek · July 26, 2019, 3:13pm

Anyone have any experiece with Aqara Motion Sensors using Tradfri Smart Plugs as a router/extender? They only want to connect directly to the RaspBee USB.

Light(x) are the Tradfri Smart Plugs, Presence(x) are the Aqara Motion Sensors. 0x0000 is the deCONZ gateway. As you can see all the smart plugs connect to each other and the gateway, but the motion sensors only want to connect to the gateway.