No access to config folder… as mentionned at the top of this page, what can I do? I found, I manually restart file and samba share component and now I have acces to my files… Strange
btw, should editing an obvious peak in the new statistics editor (which is performed successfully according to the feedback on click) take out the false graph in the energy panel? doesnt happen in my case here:
and renders the rest of the page below it completely empty. Does it take another cycle or so?
I was happy to see that there were ZHA updates in 2022.4.1… My upgrade completed 8 minutes ago and I have yet to have a single one of my Zigbee devices come back online. Still looks like there are issues unfortunately. Previously about 70% of my zigbee devices would eventually come back online over the course of an hour so I’ll see if I can at least get partial functionality back soon.
1 Like
I restarted file editor and samba share manually and now it works.
Thanks i had the same, i only had to reboot the Samba Addon
Unfortunately 2022.4.1 has not fixed my issues. Zigbee devices are either marked offline or unresponsive. Some battery operated sensors seem like are working (motion sensors say clear but don’t report motion) but are not.
Another thing I noticed is that the dashboards are really sluggish but when I look at Glances I don’t see anything out of the ordinary. My HA is running on a proxmox VM with 6 cores of an i7 dedicated to it along with at least 6GB of RAM… which should be way overkill. The usage is 0.5 or less.
2 Likes
If you let it sit for, say, 30 minutes, do you notice some of the items come back online? A majority of my devices will come back on over 30 or so minutes, but response times don’t seem great and not everything comes back. Just trying to see if maybe we have similar issues. Im running on a RPI 4 with 4gb of ram, so quite underpowered compared to your machine, but its been running my 40 zigbee devices without breaking a sweat this entire time.
@GFactor I updated to 2022.4.1 a couple hours ago and while the devices say they are online, they are not working. I still see a lot of delivery errors where it also state something has a BUSY state.
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [34, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xfffd>, 0, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xbb64>, 0, 0, 0, b'\xe4\xf9i\x07\xff\xff.!\x00\x00\x00', 0, 175, 255, 219, 1, 245, 13, -25]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy.zdo] [0xbb64:zdo] ZDO request ZDOCmd.NWK_addr_req: [00:21:2e:ff:ff:07:69:f9, 0, 0]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request with tsn 228 under 144 request id, data: b'e400f96907ffff2e210000000000'
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xbb64>, ep: 0, profile: 0x0000, cluster_id: 0x0000, data: b'e4f96907ffff2e21000000'
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 144, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xBB64 endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\xe4\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 0.5s
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 132, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=20612 endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\xe3\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy.device] [0x5084] Delivery error for seq # 0xe3, on endpoint id 0 cluster 0x8000: Couldn't enqueue send data request: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_confirm (0,)
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] APS data confirm response for request with id 97: e9
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x61 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.NWK address=0x5f72 endpoint=0>, status: 0xe9
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Error while sending 97 req id frame: TXStatus.MAC_NO_ACK
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Trying manual source route: [0]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (32, 97, <DeconzSendDataFlags.RELAYS: 2>, <DeconzAddressEndpoint address_mode=2 address=0x5F72 endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\x94\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0, [0])
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] APS data request response: [2, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, 97]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1)
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [34, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xfffd>, 0, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x6b6a>, 0, 0, 0, b'\x96\xf9i\x07\xff\xff.!\x00\x00\x00', 0, 175, 255, 221, 1, 245, 13, -55]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy.zdo] [0x6b6a:zdo] ZDO request ZDOCmd.NWK_addr_req: [00:21:2e:ff:ff:07:69:f9, 0, 0]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy.util] Duplicate 150 TSN
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x6b6a>, ep: 0, profile: 0x0000, cluster_id: 0x0000, data: b'96f96907ffff2e21000000'
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_confirm (0,)
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] APS data confirm response for request with id 95: e9
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x5f 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.NWK address=0xbb64 endpoint=0>, status: 0xe9
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Error while sending 95 req id frame: TXStatus.MAC_NO_ACK
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Trying manual source route: [0]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (32, 95, <DeconzSendDataFlags.RELAYS: 2>, <DeconzAddressEndpoint address_mode=2 address=0xBB64 endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\xdb\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0, [0])
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] APS data request response: [2, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, 95]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 137, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xB819 endpoint=1>, 260, 2820, 1, b'\x00\x88\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.5s
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 139, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x3B92 endpoint=1>, 260, 2820, 1, b'\x00\x8a\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.5s
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1)
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [34, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xfffd>, 0, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x5f72>, 0, 0, 0, b'\x97\xf9i\x07\xff\xff.!\x00\x00\x00', 0, 175, 255, 214, 1, 245, 13, -69]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy.zdo] [0x5f72:zdo] ZDO request ZDOCmd.NWK_addr_req: [00:21:2e:ff:ff:07:69:f9, 0, 0]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request with tsn 151 under 145 request id, data: b'9700f96907ffff2e210000000000'
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x5f72>, ep: 0, profile: 0x0000, cluster_id: 0x0000, data: b'97f96907ffff2e21000000'
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 145, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x5F72 endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\x97\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 0.5s
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 141, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xAFEC endpoint=1>, 260, 2820, 1, b'\x00\x8c\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.5s
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 142, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x459F endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\xd6\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.5s
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0]
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_confirm (0,)
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] APS data confirm response for request with id 120: 00
2022-04-08 09:57:09 DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x78 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.NWK address=0xa244 endpoint=0>, status: 0x00
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 144, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xBB64 endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\xe4\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0]
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] APS data request response: [2, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 38>, 144]
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_confirm (0,)
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] APS data confirm response for request with id 131: 00
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x83 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.NWK address=0x6b6a endpoint=0>, status: 0x00
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 133, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x0298 endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\x92\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] APS data request response: [2, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, 133]
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0]
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_confirm (0,)
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] APS data confirm response for request with id 143: e1
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x8f 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.NWK address=0x243f endpoint=0>, status: 0xe1
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Error while sending 143 req id frame: TXStatus.MAC_CHANNEL_ACCESS_FAILURE
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Trying manual source route: [0]
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (32, 143, <DeconzSendDataFlags.RELAYS: 2>, <DeconzAddressEndpoint address_mode=2 address=0x243F endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\x9d\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0, [0])
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] APS data request response: [2, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, 143]
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 134, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x243F endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\x9c\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy.device] [0x243f] Delivery error for seq # 0x9c, on endpoint id 0 cluster 0x8000: Couldn't enqueue send data request: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 145, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x5F72 endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\x97\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.0s
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 135, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x3FB7 endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\xf8\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:10 DEBUG (MainThread) [zigpy.device] [0x3fb7] Delivery error for seq # 0xf8, on endpoint id 0 cluster 0x8000: Couldn't enqueue send data request: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 137, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xB819 endpoint=1>, 260, 2820, 1, b'\x00\x88\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy.device] [0xb819] Delivery error for seq # 0x88, on endpoint id 1 cluster 0x0b04: Couldn't enqueue send data request: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:11 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0xB819:1:0x0b04]: failed to get attributes '['active_power', 'apparent_power', 'rms_current', 'rms_voltage']' on 'electrical_measurement' cluster: [0xb819:1:0x0b04]: Message send failure
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 139, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x3B92 endpoint=1>, 260, 2820, 1, b'\x00\x8a\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy.device] [0x3b92] Delivery error for seq # 0x8a, on endpoint id 1 cluster 0x0b04: Couldn't enqueue send data request: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:11 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x3B92:1:0x0b04]: failed to get attributes '['active_power', 'apparent_power', 'rms_current', 'rms_voltage']' on 'electrical_measurement' cluster: [0x3b92:1:0x0b04]: Message send failure
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 145, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x5F72 endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\x97\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.5s
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 141, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xAFEC endpoint=1>, 260, 2820, 1, b'\x00\x8c\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy.device] [0xafec] Delivery error for seq # 0x8c, on endpoint id 1 cluster 0x0b04: Couldn't enqueue send data request: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:11 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0xAFEC:1:0x0b04]: failed to get attributes '['active_power', 'apparent_power', 'rms_current', 'rms_voltage']' on 'electrical_measurement' cluster: [0xafec:1:0x0b04]: Message send failure
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 142, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x459F endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\xd6\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-08 09:57:11 DEBUG (MainThread) [zigpy.device] [0x459f] Delivery error for seq # 0xd6, on endpoint id 0 cluster 0x8000: Couldn't enqueue send data request: Command.aps_data_request, status: Status.BUSY
1 Like
searching why the one icon mdi: track-light-off I would have liked to add didnt show up, I tried to load the link in the release note for the beautiful new icons at Material Design Icons
Cant open that in Safari, while it opens in a flash in Chrome. Anyone else seeing that too?
that website is really difficult to follow release changes btw. always lose my way there. Finally arrived at Material Design Icons to see it being released in #6337, but clicking that renders a 404… o well.
First link above works fine in firefox
#6337 renders 404, in second link
… thou right track-light-off don’t exist in first link
Try this:
https://dev.materialdesignicons.com/icon/track-light-off
…or go to https://materialdesignicons.com/ click on search, type " track-light-off " hit enter, then click on the downerrow TAG(to the right), then you see the Icon to the left, abit down , click it “import” …thou yes, not in HA Currently, seems like they officially, are versions from Dev-v 6.6.96
I’m still confused as well, when now it is said, that the built-in SQLite is restore-tested (as asked above as well), because, e.g. here Lots of problems after restoring snapshot. What to do?. Further same topics here and in a lot of other topics in the community.
both Tom, and Pedro told us there, that “Unfortunately the database rarely survives a restore”, what is seen behavior locally as well. Here it didn’t survive a single restore and every time the history and long term data was lost in the past, what is not the end of the world, but still a pity.
1 Like
There has been sweeping changes to the database management in recent releases, taking past comments out of context and applying them to current conversations to spark an argument is not suggested.
3 Likes
If you don’t use the default_config, you’ll need to add it to your config (that’s what worked for me).
1 Like
“not suggested” is not fair. How should we know, that the backup/restore is that much improved without asking and referencing - if not listed or described anywhere (as far as I read)?
So from past comments, where you or Tom said, that it is technical not and never possible to improve or fix the past behavior with SQLite, it was now indeed possible after all and the db will survive the restore now? This would be of course a great news! 
I would take Frencks word over mine when it comes to the SQLLite database in home assistant. I personally won’t use it for all the reasons I’ve highlighted in the past.
I no longer see the error during startup after updating to HAC 2022.4.1
1 Like
Yes same here 
… thou still a-lot errors caused by a Custom integration, reported at it’s git-hub-reposetory
But that’s just it isn’t it? We all moved over because of those reasons. But if they’re no longer real cause for worries, we needn’t stay and could migrate back.
We just don’t know the if’s and when’s.
I am echoing your comments / questions. I have no idea what a long time HA user should do? Mariadb works. We have been advised in the past not to use the built in DB. Now we are advised to switch back? No one is explaining the trade offs or how to switch back without losing all the data.
I’m not going to switch back. No point unless something is deprecated, which it isn’t.
1 Like