DeConz lost connection after Homebridge action

[AntiHeld889]

Hello at first sorry for my bad english.

Issuses:

I have create an action in Homebridge "leave home" with 21 Devices (bulbs) which working over Deconz and Homebridge-hue Plugin. If I start these action DeConz is crashing and can't reconnect to the network. After I restart the program it shows me Firmware update (but all Firmwares are up to date) when it is finished, Deconz is working again.

[ebaauw]

I have create an action in Homebridge "leave home" with 21 Devices (bulbs) which working over Deconz and Homebridge-hue Plugin

I assume you mean the Leave Home scene in HomeKit?

If I start these action DeConz is crashing

deCONZ shouldn't crash by anything done by homebridge-hue (or any app using the deCONZ REST API). Does this happen every time you activate the HomeKit scene, or did this happen only once?

If it happens every time, could you:

• Start deCONZ manually, capture its output;
• Run homebridge -D manually, capture its output (see Troubleshooting in homebridge-hue README);
• Reproduce the crash;
• Post the outputs of deCONZ and homebridge here?

If I start these action DeConz is crashing and can't reconnect to the network. After I restart the program it shows me Firmware update

I assume you mean the RaspBee won't connect to the ZigBee network? I've experienced this once - as if the RaspBee was zapped completely and needed to be re-initialised, starting with flashing the firmware. I haven't been able to reproduce this, however. I suspect it might be related to the RaspBerry Pi producing too much heat (see issue #147). What other programmes are you running on your Raspberry Pi?

[AntiHeld889]

I assume you mean the Leave Home scene in HomeKit?

Yes I mean the Leave Home scene in HomeKit.

deCONZ shouldn't crash by anything done by homebridge-hue (or any app using the deCONZ REST API). Does this happen every time you activate the HomeKit scene, or did this happen only once?

Yes every time I tested the scene Deconz lost the connection Homebridge runs normally after that I don't think that RaspBee lost connection by anything done by homebridge-hue. But perhaps because there are too many devices or commands at once?

Homebridge:
[2017-8-29 14:31:01] [RaspBee] deCONZ-GW: hue bridge request #69: ok
[2017-8-29 14:31:01] [RaspBee] deCONZ-GW: hue bridge request #70: ok
[2017-8-29 14:31:03] [RaspBee] deCONZ-GW: hue bridge request #71: get /config
[2017-8-29 14:31:03] [RaspBee] deCONZ-GW: hue bridge request #71: ok
[2017-8-29 14:31:03] [RaspBee] deCONZ-GW: hue bridge request #72: get /sensors
[2017-8-29 14:31:03] [RaspBee] deCONZ-GW: hue bridge request #72: ok
[2017-8-29 14:31:03] [RaspBee] deCONZ-GW: hue bridge request #73: get /lights
[2017-8-29 14:31:03] [RaspBee] deCONZ-GW: hue bridge request #73: ok
[2017-8-29 14:31:08] [RaspBee] deCONZ-GW: hue bridge request #74: get /config
[2017-8-29 14:31:08] [RaspBee] deCONZ-GW: hue bridge request #74: ok
[2017-8-29 14:31:08] [RaspBee] deCONZ-GW: hue bridge request #75: get /sensors
[2017-8-29 14:31:08] [RaspBee] deCONZ-GW: hue bridge request #75: ok
[2017-8-29 14:31:08] [RaspBee] deCONZ-GW: hue bridge request #76: get /lights
[2017-8-29 14:31:08] [RaspBee] deCONZ-GW: hue bridge request #76: ok
[2017-8-29 14:31:11] [Harmony Hub] debug Refreshing current activity
[2017-8-29 14:31:13] [RaspBee] deCONZ-GW: hue bridge request #77: get /config
[2017-8-29 14:31:13] [RaspBee] deCONZ-GW: hue bridge request #77: ok
[2017-8-29 14:31:13] [RaspBee] deCONZ-GW: hue bridge request #78: get /sensors
[2017-8-29 14:31:13] [RaspBee] deCONZ-GW: hue bridge request #78: ok
[2017-8-29 14:31:13] [RaspBee] deCONZ-GW: hue bridge request #79: get /lights
[2017-8-29 14:31:13] [RaspBee] deCONZ-GW: hue bridge request #79: ok
[2017-8-29 14:31:18] [RaspBee] deCONZ-GW: hue bridge request #80: get /config
[2017-8-29 14:31:18] [RaspBee] deCONZ-GW: hue bridge request #80: ok
[2017-8-29 14:31:18] [RaspBee] deCONZ-GW: hue bridge request #81: get /sensors
[2017-8-29 14:31:18] [RaspBee] deCONZ-GW: hue bridge request #81: ok
[2017-8-29 14:31:18] [RaspBee] deCONZ-GW: hue bridge request #82: get /lights
[2017-8-29 14:31:18] [RaspBee] deCONZ-GW: hue bridge request #82: ok
[2017-8-29 14:31:20] [RaspBee] Komodenspot 1: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Couchspot 2: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [Harmony Hub] Queue activity to -1
[2017-8-29 14:31:20] [Harmony Hub] Set activity to -1
[2017-8-29 14:31:20] [RaspBee] Komodenspot 2: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Komodenspot 3: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Nachttisch 2: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Nachttisch 1: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Kugel: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Couchspot 4: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Couchspot 1: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Gadrobenspot: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Flurspot 4: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Flurspot 1: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [IronMan] Turning IronMan off
[2017-8-29 14:31:20] [RaspBee] Light 2: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Gadrobe: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Flurspot 2: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Flurspot 3: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Couchspot 3: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Deckenlampe: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] Schlafzimmer Deckenlampe: homekit power changed from 1 to 0
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #83: put /lights/14/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #84: put /lights/7/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #85: put /lights/13/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #86: put /lights/12/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #87: put /lights/5/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #88: put /lights/6/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #89: put /lights/4/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #90: put /lights/10/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #91: put /lights/8/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #92: put /lights/11/state {"on":false}
[2017-8-29 14:31:20] [Denon AVR] denon avr powered false
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #83: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #93: put /lights/19/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #84: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #94: put /lights/16/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #86: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #95: put /lights/2/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #85: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #96: put /lights/3/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #88: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #97: put /lights/17/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #90: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #98: put /lights/18/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #92: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #99: put /lights/9/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #87: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #100: put /lights/15/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #91: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #101: put /lights/1/state {"on":false}
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #89: ok
[2017-8-29 14:31:20] [RaspBee] Flurspot 4: event: light on changed from true to false
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #93: ok
[2017-8-29 14:31:20] [RaspBee] Flurspot 1: event: light on changed from true to false
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #94: ok
[2017-8-29 14:31:20] [Harmony Hub] Finished setting activity to -1
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #95: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #96: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #98: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #97: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #99: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #101: ok
[2017-8-29 14:31:20] [RaspBee] deCONZ-GW: hue bridge request #100: ok
[2017-8-29 14:31:21] [IronMan] Sent code: 3167536, pin: 0, pulseLength: 180

[2017-8-29 14:31:23] [RaspBee] deCONZ-GW: hue bridge request #102: get /config
[2017-8-29 14:31:23] [RaspBee] deCONZ-GW: hue bridge request #102: ok
[2017-8-29 14:31:23] [RaspBee] deCONZ-GW: hue bridge request #103: get /sensors
[2017-8-29 14:31:23] [RaspBee] deCONZ-GW: hue bridge request #103: ok
[2017-8-29 14:31:23] [RaspBee] deCONZ-GW: hue bridge request #104: get /lights
[2017-8-29 14:31:23] [RaspBee] deCONZ-GW: hue bridge request #104: ok
[2017-8-29 14:31:28] [RaspBee] deCONZ-GW: hue bridge request #105: get /config
[2017-8-29 14:31:28] [RaspBee] deCONZ-GW: hue bridge request #105: ok
[2017-8-29 14:31:28] [RaspBee] deCONZ-GW: hue bridge request #106: get /sensors
[2017-8-29 14:31:28] [RaspBee] deCONZ-GW: hue bridge request #106: ok
[2017-8-29 14:31:28] [RaspBee] deCONZ-GW: hue bridge request #107: get /lights
[2017-8-29 14:31:28] [RaspBee] deCONZ-GW: hue bridge request #107: ok
[2017-8-29 14:31:28] [RaspBee] Schlafzimmer Deckenlampe: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Schlafzimmer Deckenlampe: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Light 2: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Light 2: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Gadrobe: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Gadrobe: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Kugel: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Kugel: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Nachttisch 2: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Nachttisch 2: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Nachttisch 1: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Nachttisch 1: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Couchspot 2: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Couchspot 2: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Couchspot 1: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Couchspot 1: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Couchspot 3: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Couchspot 3: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Couchspot 4: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Couchspot 4: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Gadrobenspot: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Gadrobenspot: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Komodenspot 3: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Komodenspot 3: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Komodenspot 2: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Komodenspot 2: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Komodenspot 1: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Komodenspot 1: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Deckenlampe: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Deckenlampe: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Flurspot 1: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Flurspot 1: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Flurspot 2: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Flurspot 2: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Flurspot 3: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Flurspot 3: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Flurspot 4: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Flurspot 4: set homekit status fault from 0 to 1
[2017-8-29 14:31:28] [RaspBee] Spiegellampe: light reachable changed from true to false
[2017-8-29 14:31:28] [RaspBee] Spiegellampe: set homekit status fault from 0 to 1
[2017-8-29 14:31:31] [Harmony Hub] debug Refreshing current activity
[2017-8-29 14:31:33] [RaspBee] deCONZ-GW: hue bridge request #108: get /config
[2017-8-29 14:31:33] [RaspBee] deCONZ-GW: hue bridge request #108: ok
[2017-8-29 14:31:33] [RaspBee] deCONZ-GW: hue bridge request #109: get /sensors
[2017-8-29 14:31:33] [RaspBee] deCONZ-GW: hue bridge request #109: ok
…

Doconz
14:31:01:821 APS-DATA.request id: 42, addrmode: 0x03, addr: 0x000b57fffe269075, profile: 0x0104, cluster: 0x0006, ep: 0x01 queue: 2 len: 5
14:31:01:932 APS-DATA.confirm id: 39, status: 0x00 SUCCESS
14:31:01:932 APS-DATA.confirm request id: 39 -> erase from queue
14:31:01:946 APS-DATA.confirm id: 42, status: 0x00 SUCCESS
14:31:01:946 APS-DATA.confirm request id: 42 -> erase from queue
14:31:05:262 APS-DATA.request id: 86, addrmode: 0x02, addr: 0xfe41, profile: 0x0000, cluster: 0x0031, ep: 0x00 queue: 1 len: 2
14:31:05:343 APS-DATA.confirm id: 86, status: 0x00 SUCCESS
14:31:05:343 APS-DATA.confirm request id: 86 -> confirmed, timeout 10000
14:31:05:429 APS-DATA.indication srcAddr: 0x000b57fffe269075, dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 175, rssi: -69
14:31:05:430 APS-DATA.request id: 86 erase from queue
14:31:05:742 APS-DATA.request id: 95, addrmode: 0x02, addr: 0xfe41, profile: 0x0000, cluster: 0x0031, ep: 0x00 queue: 1 len: 2
14:31:05:826 APS-DATA.confirm id: 95, status: 0x00 SUCCESS
14:31:05:826 APS-DATA.confirm request id: 95 -> confirmed, timeout 10000
14:31:05:908 APS-DATA.indication srcAddr: 0x000b57fffe269075, dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 175, rssi: -69
14:31:05:908 APS-DATA.request id: 95 erase from queue
14:31:06:222 APS-DATA.request id: 103, addrmode: 0x02, addr: 0xfe41, profile: 0x0000, cluster: 0x0031, ep: 0x00 queue: 1 len: 2
14:31:06:300 APS-DATA.confirm id: 103, status: 0x00 SUCCESS
14:31:06:300 APS-DATA.confirm request id: 103 -> confirmed, timeout 10000
14:31:06:373 APS-DATA.indication srcAddr: 0x000b57fffe269075, dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 175, rssi: -69
14:31:06:373 APS-DATA.request id: 103 erase from queue
14:31:06:702 APS-DATA.request id: 110, addrmode: 0x02, addr: 0xfe41, profile: 0x0000, cluster: 0x0031, ep: 0x00 queue: 1 len: 2
14:31:06:785 APS-DATA.confirm id: 110, status: 0x00 SUCCESS
14:31:06:785 APS-DATA.confirm request id: 110 -> confirmed, timeout 10000
14:31:06:856 APS-DATA.indication srcAddr: 0x000b57fffe269075, dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 175, rssi: -69
14:31:06:856 APS-DATA.request id: 110 erase from queue
14:31:07:183 APS-DATA.request id: 120, addrmode: 0x02, addr: 0xfe41, profile: 0x0000, cluster: 0x0031, ep: 0x00 queue: 1 len: 2
14:31:07:261 APS-DATA.confirm id: 120, status: 0x00 SUCCESS
14:31:07:261 APS-DATA.confirm request id: 120 -> confirmed, timeout 10000
14:31:07:343 APS-DATA.indication srcAddr: 0x000b57fffe269075, dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 175, rssi: -69
14:31:07:343 APS-DATA.request id: 120 erase from queue
14:31:07:663 APS-DATA.request id: 125, addrmode: 0x02, addr: 0xfe41, profile: 0x0000, cluster: 0x0031, ep: 0x00 queue: 1 len: 2
14:31:07:745 APS-DATA.confirm id: 125, status: 0x00 SUCCESS
14:31:07:745 APS-DATA.confirm request id: 125 -> confirmed, timeout 10000
14:31:07:802 APS-DATA.indication srcAddr: 0x000b57fffe269075, dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 167, rssi: -70
14:31:07:803 APS-DATA.request id: 125 erase from queue
14:31:10:125 APS-DATA.indication srcAddr: 0x000b57fffe1523b3, dstAddrMode: 2, profile: 0x0104, cluster: 0x0008, lqi: 191, rssi: -67
14:31:10:126 APS-DATA.request id: 158, addrmode: 0x03, addr: 0x000b57fffe1523b3, profile: 0x0104, cluster: 0x0008, ep: 0x01 queue: 1 len: 5
14:31:10:195 APS-DATA.confirm id: 158, status: 0x00 SUCCESS
14:31:10:195 APS-DATA.confirm request id: 158 -> erase from queue
14:31:11:354 APS-DATA.confirm id: 107, status: 0xA7 NO_ACK
14:31:11:649 APS-DATA.indication srcAddr: 0x000b57fffe4bba29, dstAddrMode: 2, profile: 0x0104, cluster: 0x0008, lqi: 231, rssi: -62
14:31:11:649 APS-DATA.request id: 181, addrmode: 0x03, addr: 0x000b57fffe4bba29, profile: 0x0104, cluster: 0x0008, ep: 0x01 queue: 0 len: 5
14:31:11:668 APS-DATA.indication srcAddr: 0x000b57fffe4bba29, dstAddrMode: 2, profile: 0x0104, cluster: 0x0300, lqi: 231, rssi: -62
14:31:11:668 APS-DATA.request id: 185, addrmode: 0x03, addr: 0x000b57fffe4bba29, profile: 0x0104, cluster: 0x0300, ep: 0x01 queue: 1 len: 5
14:31:11:776 APS-DATA.confirm id: 181, status: 0x00 SUCCESS
14:31:11:776 APS-DATA.confirm request id: 181 -> erase from queue
14:31:11:789 APS-DATA.confirm id: 185, status: 0x00 SUCCESS
14:31:11:789 APS-DATA.confirm request id: 185 -> erase from queue
14:31:12:943 APS-DATA.request id: 203, addrmode: 0x02, addr: 0xa6f4, profile: 0x0000, cluster: 0x0031, ep: 0x00 queue: 0 len: 2
14:31:13:035 APS-DATA.confirm id: 203, status: 0x00 SUCCESS
14:31:13:035 APS-DATA.confirm request id: 203 -> confirmed, timeout 10000
14:31:13:066 APS-DATA.indication srcAddr: 0x00158d0001a6d215, dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -58
14:31:13:067 APS-DATA.request id: 203 erase from queue
14:31:13:423 APS-DATA.request id: 210, addrmode: 0x02, addr: 0xa6f4, profile: 0x0000, cluster: 0x0031, ep: 0x00 queue: 0 len: 2
14:31:13:515 APS-DATA.confirm id: 210, status: 0x00 SUCCESS
14:31:13:515 APS-DATA.confirm request id: 210 -> confirmed, timeout 10000
14:31:13:548 APS-DATA.indication srcAddr: 0x00158d0001a6d215, dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -58
14:31:13:548 APS-DATA.request id: 210 erase from queue
14:31:13:902 APS-DATA.request id: 220, addrmode: 0x02, addr: 0xa6f4, profile: 0x0000, cluster: 0x0031, ep: 0x00 queue: 0 len: 2
14:31:13:980 APS-DATA.confirm id: 220, status: 0x00 SUCCESS
14:31:13:980 APS-DATA.confirm request id: 220 -> confirmed, timeout 10000
14:31:14:028 APS-DATA.indication srcAddr: 0x00158d0001a6d215, dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -58
14:31:14:029 APS-DATA.request id: 220 erase from queue
14:31:14:383 APS-DATA.request id: 226, addrmode: 0x02, addr: 0xa6f4, profile: 0x0000, cluster: 0x0031, ep: 0x00 queue: 0 len: 2
14:31:14:471 APS-DATA.confirm id: 226, status: 0x00 SUCCESS
14:31:14:471 APS-DATA.confirm request id: 226 -> confirmed, timeout 10000
14:31:14:507 APS-DATA.indication srcAddr: 0x00158d0001a6d215, dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -58
14:31:14:508 APS-DATA.request id: 226 erase from queue
14:31:14:863 APS-DATA.request id: 236, addrmode: 0x02, addr: 0xa6f4, profile: 0x0000, cluster: 0x0031, ep: 0x00 queue: 0 len: 2
14:31:14:952 APS-DATA.confirm id: 236, status: 0x00 SUCCESS
14:31:14:952 APS-DATA.confirm request id: 236 -> confirmed, timeout 10000
14:31:14:000 APS-DATA.indication srcAddr: 0x00158d0001a6d215, dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -58
14:31:15:000 APS-DATA.request id: 236 erase from queue
14:31:15:121 APS-DATA.indication srcAddr: 0x00158d0001a1ee43, dstAddrMode: 2, profile: 0x0104, cluster: 0x0000, lqi: 239, rssi: -61
14:31:15:342 APS-DATA.request id: 246, addrmode: 0x02, addr: 0xa6f4, profile: 0x0000, cluster: 0x0031, ep: 0x00 queue: 0 len: 2
14:31:15:414 APS-DATA.confirm id: 246, status: 0x00 SUCCESS
14:31:15:414 APS-DATA.confirm request id: 246 -> confirmed, timeout 10000
14:31:15:462 APS-DATA.indication srcAddr: 0x00158d0001a6d215, dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 255, rssi: -58
14:31:15:462 APS-DATA.request id: 246 erase from queue
14:31:20:623 APS-DATA.request id: 57, addrmode: 0x02, addr: 0xaa77, profile: 0x0000, cluster: 0x0031, ep: 0x00 queue: 0 len: 2
14:31:20:715 APS-DATA.confirm id: 57, status: 0x00 SUCCESS
14:31:20:715 APS-DATA.confirm request id: 57 -> confirmed, timeout 10000
14:31:20:788 APS-DATA.request id: 61, addrmode: 0x03, addr: 0x000b57fffe273804, profile: 0x0104, cluster: 0x0006, ep: 0x01 queue: 1 len: 3
14:31:20:790 APS-DATA.request id: 62, addrmode: 0x03, addr: 0x000b57fffe268e1b, profile: 0x0104, cluster: 0x0006, ep: 0x01 queue: 2 len: 3
14:31:20:793 APS-DATA.request id: 63, addrmode: 0x03, addr: 0x000b57fffe269075, profile: 0x0104, cluster: 0x0006, ep: 0x01 queue: 3 len: 3
14:31:20:797 APS-DATA.request id: 64, addrmode: 0x03, addr: 0x000b57fffe266b74, profile: 0x0104, cluster: 0x0006, ep: 0x01 queue: 4 len: 3
14:31:20:800 APS-DATA.request id: 65, addrmode: 0x03, addr: 0x000b57fffe127d35, profile: 0x0104, cluster: 0x0006, ep: 0x01 queue: 5 len: 3
14:31:27:508 APS-DATA.request id: 61, status: 0x05 giveup
14:31:27:508 APS-DATA.request id: 61, set state: 0x06
14:31:27:508 emit artificial APSDE-DATA.confirm id: 61
14:31:27:509 APS-DATA.request id: 66, addrmode: 0x03, addr: 0x000b57fffe0d892f, profile: 0x0104, cluster: 0x0006, ep: 0x01 queue: 6 len: 3
14:31:27:513 APS-DATA.request id: 134, addrmode: 0x02, addr: 0xfffd, profile: 0x0000, cluster: 0x0013, ep: 0x00 queue: 7 len: 15
14:31:27:590 aps request id: 57 finished, erase from queue
14:31:27:662 aps request id: 61 finished, erase from queue
14:31:27:662 emit artificial APSDE-DATA.confirm id: 61
14:31:27:742 aps request id: 62 finished, erase from queue
14:31:27:742 emit artificial APSDE-DATA.confirm id: 62
14:31:27:822 aps request id: 63 finished, erase from queue
14:31:27:822 emit artificial APSDE-DATA.confirm id: 63
14:31:27:902 aps request id: 64 finished, erase from queue
14:31:27:902 emit artificial APSDE-DATA.confirm id: 64
14:31:27:982 aps request id: 65 finished, erase from queue
14:31:27:983 emit artificial APSDE-DATA.confirm id: 65
14:31:28:065 aps request id: 66 finished, erase from queue
14:31:28:066 emit artificial APSDE-DATA.confirm id: 66
14:33:23:507 APS-DATA.request id: 18, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 queue: 0 len: 3
14:33:23:582 aps request id: 18 timeout
14:33:23:582 aps request id: 18 erase from queue
14:33:23:582 emit artificial APSDE-DATA.confirm id: 18
14:33:37:506 APS-DATA.request id: 66, addrmode: 0x03, addr: 0x00212effff014355, profile: 0x0104, cluster: 0x0019, ep: 0x0A queue: 0 len: 5
14:33:37:582 aps request id: 66 finished, erase from queue
14:33:37:583 emit artificial APSDE-DATA.confirm id: 66
14:34:56:507 APS-DATA.request id: 79, addrmode: 0x03, addr: 0x00212effff014355, profile: 0x0104, cluster: 0x0019, ep: 0x0A queue: 0 len: 5
14:34:56:542 aps request id: 79 finished, erase from queue
14:34:56:542 emit artificial APSDE-DATA.confirm id: 79
14:36:04:507 APS-DATA.request id: 54, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 queue: 0 len: 3
14:36:04:542 aps request id: 54 timeout
14:36:04:542 aps request id: 54 erase from queue
14:36:04:542 emit artificial APSDE-DATA.confirm id: 54
14:36:15:507 APS-DATA.request id: 93, addrmode: 0x03, addr: 0x00212effff014355, profile: 0x0104, cluster: 0x0019, ep: 0x0A queue: 0 len: 5
14:36:15:582 aps request id: 93 finished, erase from queue
14:36:15:582 emit artificial APSDE-DATA.confirm id: 93

[ebaauw]

But perhaps because there are too many devices or commands at once?

Looking at the homebridge log, you see that HomeKit switches off 19 lights in bulk when activating the scene at 14:31:20. By design, homebridge-hue throttles the corresponding requests to turn off each light, issuing the first 10 requests to deCONZ immediately, and the remaining 9 only after deCONZ has returned a response for a previous request (so it never has more than 10 outstanding requests with deCONZ).
You can tweak the number of outstanding requests by setting parallelRequests in config.json (see https://github.com/ebaauw/homebridge-hue/wiki/Configuration), but I'm afraid that won't help (as deCONZ returns responses for all 19 requests in the same second anyways).

Somehow, deCONZ sets state.reachable to false for 20 lights, shortly after this action (presumably because the RaspBee has lost the connection to the ZigBee network?). homebridge-hue detects this when polling deCONZ at 14:31:28. I think you're running an older version of homebridge-hue that doesn't yet use the websocket notifications? This is logged at the beginning of the homebridge output, along with the types of lights you have.

From the deCONZ log, you see it handles the first 5 requests (61-65) to the lights to turn off (cluster 0x0006) at 14:31:20. After 7 seconds it gives up on the first request 61, and handles the next (66), but no sign of the remaining requests...

14:31:27:508 APS-DATA.request id: 61, status: 0x05 giveup
14:31:27:508 APS-DATA.request id: 61, set state: 0x06

I'm afraid this is an issue with deCONZ, beyond my understanding, but it doesn't seem like it's trying to handle too many requests simultaneously. Hopefully @manup can shed a light on this. What version of deCONZ and RaspBee firmware are you running (see Help|About in the deCONZ GUI)?

[AntiHeld889]

I have used the last version of homebridge-hue (0.5.24) now 0.5.25.
I have test it with "parallelRequests": 3 but same Problem

Deconz: 2.04.69
Firmeware: 0x26160500

After it lost the connection to the Zigbee network it's trying to reconnect but i need to restart the programm. If I restart the programm it shows me at Help/About Firmware Version unknown. Then its starts flashing and is working again

[AntiHeld889]

Error found another plugin was still active for a 433mhz transmitter which on pin 17 then caused the error.

Very stupid of me!