2022.4: Groups! Groups! Groups!

phasemd · April 7, 2022, 4:42pm

I really would like to see this change reverted or at least made optional.

This is a breaking change for all Sonos users not using Spotify or a local music library.

peca89 · April 7, 2022, 4:45pm

OK, I have given it another try. It has (mostly) succeded now without apparent change.

I say “mostly” because gree integration still does not work:

....
File "/config/custom_components/gree/climate.py", line 29, in <module>
    from homeassistant.components.fan import SPEED_HIGH, SPEED_LOW, SPEED_MEDIUM
ImportError: cannot import name 'SPEED_HIGH' from 'homeassistant.components.fan' (/usr/src/homeassistant/homeassistant/components/fan/__init__.py)

This appears to be removed in this commit
https://github.com/home-assistant/core/commit/7fbe1dbc99b7cdf503820d2d0356090766ae1f7e

I have no idea what this means nor is it HA or custom integration issue. Anyway, gree does not work anymore. Trouble is, it also prevents restarts:

The system cannot restart because the configuration is not valid: Platform error climate.gree - cannot import name 'SPEED_HIGH' from 'homeassistant.components.fan' (/usr/src/homeassistant/homeassistant/components/fan/__init__.py)

And since the issue is with fan component, this might be the reason why tuya integration also complains…

hazio · April 7, 2022, 5:13pm

What is better Hue groups, or Groups via UI?

micque · April 7, 2022, 5:39pm

My system Rpi 4 - 4g has been running at 3-4% of the processor bandwidth. As of the 2022.04 update, while the base level is still 3-4%, I’m now seeing a spike to 10-12% every 5 minutes that appears to correspond to the supervisor.store.git activity. Is this to be expected? Seems like a lot of effort to check on something that changes infrequently.

Recte · April 7, 2022, 5:56pm

Waiting for this one (Amcrest and Dahua Cameras become unavailable · Issue #68244 · home-assistant/core · GitHub) to be solved before I will upgrade, but the Sonos change isn’t a thing to look forward to.

I use this Selecting between multiple sources with a button - #2 by Recte and am wondering if anyone knows if there is still a list in the attributes (or anywhere else) that I can use as an array.

fixxser · April 7, 2022, 6:29pm

I had to revert back to my 2022.3.8 version. The 2022.4 broke my media playing scripts. It kept saying the pause, play functions is not supported. Even after “Host” reboots.

2022.3.8 is working perfect for me.

aruffell · April 7, 2022, 6:57pm

I enabled ZHA debug logs to see why my ZHA network is down since upgrading to 2022.4. I see errors and “Status.BUSY” but I can’t make sense of it. I power cycled the devices that are associated with an error (but I am about to cut power to the house again to be sure).

The log is very active and I can’t add back a switch I deleted, and the logs the app shows me move to fast and have lots of gibberish so they are not helping me understand what is wrong. It just seems like there is an excess of traffic due to something that happened with or after the update. Downgrading breaks a lot of other things but ZHA calms down and works a little, upgrading back to 2022.4 fixes multiple other issues that came up downgrading but renders my ZHA network inoperable.

2022-04-07 13:51:32 DEBUG (MainThread) [zigpy.zcl] [0x5F72:1:0x0b04] Sending request header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.GLOBAL_COMMAND: 0>, is_manufacturer_specific=False, is_reply=0, disable_default_response=0, reserved=0, *is_cluster=False, *is_general=True), tsn=189, command_id=<GeneralCommand.Read_Attributes: 0>, *is_reply=False)
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy.zcl] [0x5F72:1:0x0b04] Sending request: Read_Attributes(attribute_ids=[1291, 1295, 1288, 1285])
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request with tsn 189 under 190 request id, data: b'00bd000b050f0508050505'
2022-04-07 13:51:32 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0xBB64:1:0x0b04]: async_update
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy.zcl] [0xBB64:1:0x0b04] Sending request header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.GLOBAL_COMMAND: 0>, is_manufacturer_specific=False, is_reply=0, disable_default_response=0, reserved=0, *is_cluster=False, *is_general=True), tsn=191, command_id=<GeneralCommand.Read_Attributes: 0>, *is_reply=False)
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy.zcl] [0xBB64:1:0x0b04] Sending request: Read_Attributes(attribute_ids=[1291, 1295, 1288, 1285])
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request with tsn 191 under 192 request id, data: b'00bf000b050f0508050505'
2022-04-07 13:51:32 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0xD1AA:1:0x0b04]: async_update
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy.zcl] [0xD1AA:1:0x0b04] Sending request header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.GLOBAL_COMMAND: 0>, is_manufacturer_specific=False, is_reply=0, disable_default_response=0, reserved=0, *is_cluster=False, *is_general=True), tsn=193, command_id=<GeneralCommand.Read_Attributes: 0>, *is_reply=False)
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy.zcl] [0xD1AA:1:0x0b04] Sending request: Read_Attributes(attribute_ids=[1291, 1295, 1288, 1285])
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request with tsn 193 under 194 request id, data: b'00c1000b050f0508050505'
2022-04-07 13:51:32 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x3A1C:1:0x0b04]: async_update
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy.zcl] [0x3A1C:1:0x0b04] Sending request header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.GLOBAL_COMMAND: 0>, is_manufacturer_specific=False, is_reply=0, disable_default_response=0, reserved=0, *is_cluster=False, *is_general=True), tsn=195, command_id=<GeneralCommand.Read_Attributes: 0>, *is_reply=False)
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy.zcl] [0x3A1C:1:0x0b04] Sending request: Read_Attributes(attribute_ids=[1291, 1295, 1288, 1285])
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request with tsn 195 under 196 request id, data: b'00c3000b050f0508050505'
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 0.5s
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 190, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x5F72 endpoint=1>, 260, 2820, 1, b'\x00\xbd\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 0.5s
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 192, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xBB64 endpoint=1>, 260, 2820, 1, b'\x00\xbf\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 0.5s
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 194, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xD1AA endpoint=1>, 260, 2820, 1, b'\x00\xc1\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 0.5s
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 196, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x3A1C endpoint=1>, 260, 2820, 1, b'\x00\xc3\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:32 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 0.5s
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 186, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x6037 endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\xc8\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.0s
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 188, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x6037 endpoint=1>, 260, 2820, 1, b'\x00\xbb\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.0s
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 190, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x5F72 endpoint=1>, 260, 2820, 1, b'\x00\xbd\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.0s
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 192, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xBB64 endpoint=1>, 260, 2820, 1, b'\x00\xbf\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.0s
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 194, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xD1AA endpoint=1>, 260, 2820, 1, b'\x00\xc1\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.0s
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 196, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x3A1C endpoint=1>, 260, 2820, 1, b'\x00\xc3\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.0s
2022-04-07 13:51:33 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.processor_use_percent, old_state=<state sensor.processor_use_percent=7; state_class=measurement, unit_of_measurement=%, icon=mdi:cpu-64-bit, friendly_name=Processor use @ 2022-04-07T13:51:03.681125-05:00>, new_state=<state sensor.processor_use_percent=4; state_class=measurement, unit_of_measurement=%, icon=mdi:cpu-64-bit, friendly_name=Processor use @ 2022-04-07T13:51:33.682051-05:00>>
2022-04-07 13:51:33 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.memory_use, old_state=<state sensor.memory_use=2154.8; state_class=measurement, unit_of_measurement=MiB, icon=mdi:memory, friendly_name=Memory use @ 2022-04-07T13:51:18.681294-05:00>, new_state=<state sensor.memory_use=2090.2; state_class=measurement, unit_of_measurement=MiB, icon=mdi:memory, friendly_name=Memory use @ 2022-04-07T13:51:33.682291-05:00>>
2022-04-07 13:51:33 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.memory_free, old_state=<state sensor.memory_free=3779.3; state_class=measurement, unit_of_measurement=MiB, icon=mdi:memory, friendly_name=Memory free @ 2022-04-07T13:51:18.681559-05:00>, new_state=<state sensor.memory_free=3843.8; state_class=measurement, unit_of_measurement=MiB, icon=mdi:memory, friendly_name=Memory free @ 2022-04-07T13:51:33.682450-05:00>>
2022-04-07 13:51:33 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.memory_use_percent, old_state=<state sensor.memory_use_percent=36.3; state_class=measurement, unit_of_measurement=%, icon=mdi:memory, friendly_name=Memory use (percent) @ 2022-04-07T13:51:18.681706-05:00>, new_state=<state sensor.memory_use_percent=35.2; state_class=measurement, unit_of_measurement=%, icon=mdi:memory, friendly_name=Memory use (percent) @ 2022-04-07T13:51:33.682586-05:00>>
2022-04-07 13:51:33 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.network_throughput_in_enp0s18, old_state=<state sensor.network_throughput_in_enp0s18=5.403; state_class=measurement, unit_of_measurement=MB/s, icon=mdi:server-network, friendly_name=Network throughput in enp0s18 @ 2022-04-07T13:51:18.681983-05:00>, new_state=<state sensor.network_throughput_in_enp0s18=5.712; state_class=measurement, unit_of_measurement=MB/s, icon=mdi:server-network, friendly_name=Network throughput in enp0s18 @ 2022-04-07T13:51:33.682827-05:00>>
2022-04-07 13:51:33 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.network_throughput_out_enp0s18, old_state=<state sensor.network_throughput_out_enp0s18=4.217; state_class=measurement, unit_of_measurement=MB/s, icon=mdi:server-network, friendly_name=Network throughput out enp0s18 @ 2022-04-07T13:51:18.682126-05:00>, new_state=<state sensor.network_throughput_out_enp0s18=0.107; state_class=measurement, unit_of_measurement=MB/s, icon=mdi:server-network, friendly_name=Network throughput out enp0s18 @ 2022-04-07T13:51:33.682963-05:00>>
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0]
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1)
2022-04-07 13:51:33 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=0x6037>, 0, 0, 0, b'\xc9\xf9i\x07\xff\xff.!\x00\x00\x00', 0, 175, 255, 93, 192, 223, 13, -70]
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy.zdo] [0x6037:zdo] ZDO request ZDOCmd.NWK_addr_req: [00:21:2e:ff:ff:07:69:f9, 0, 0]
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request with tsn 201 under 197 request id, data: b'c900f96907ffff2e210000000000'
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x6037>, ep: 0, profile: 0x0000, cluster_id: 0x0000, data: b'c9f96907ffff2e21000000'
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 197, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x6037 endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\xc9\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:33 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 0.5s
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 186, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x6037 endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\xc8\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.5s
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 188, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x6037 endpoint=1>, 260, 2820, 1, b'\x00\xbb\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.5s
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 190, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x5F72 endpoint=1>, 260, 2820, 1, b'\x00\xbd\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.5s
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 192, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xBB64 endpoint=1>, 260, 2820, 1, b'\x00\xbf\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.5s
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 194, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xD1AA endpoint=1>, 260, 2820, 1, b'\x00\xc1\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.5s
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (26, 196, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x3A1C endpoint=1>, 260, 2820, 1, b'\x00\xc3\x00\x0b\x05\x0f\x05\x08\x05\x05\x05', <DeconzTransmitOptions.USE_APS_ACKS|USE_NWK_KEY_SECURITY: 6>, 0)
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.5s
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0]
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1)
2022-04-07 13:51:34 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=0xafec>, 0, 0, 0, b'\xb4\xf9i\x07\xff\xff.!\x00\x00\x00', 0, 175, 255, 138, 192, 223, 13, -73]
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy.zdo] [0xafec:zdo] ZDO request ZDOCmd.NWK_addr_req: [00:21:2e:ff:ff:07:69:f9, 0, 0]
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request with tsn 180 under 198 request id, data: b'b400f96907ffff2e210000000000'
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xafec>, ep: 0, profile: 0x0000, cluster_id: 0x0000, data: b'b4f96907ffff2e21000000'
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 198, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xAFEC endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\xb4\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 0.5s
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 197, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0x6037 endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\xc9\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_request' failure: Command.aps_data_request, status: Status.BUSY
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] retrying 'aps_data_request' in 1.0s
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0]
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_confirm (0,)
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] APS data confirm response for request with id 152: a7
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x98 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.NWK address=0x3a1c endpoint=0>, status: 0xa7
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Error while sending 152 req id frame: TXStatus.APS_NO_ACK
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy.device] [0x3a1c] Delivery error for seq # 0xd2, on endpoint id 0 cluster 0x8000: message send failure
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (29, 198, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=0xAFEC endpoint=0>, 0, <ZDOCmd.NWK_addr_rsp: 0x8000>, 0, b'\xb4\x00\xf9i\x07\xff\xff.!\x00\x00\x00\x00\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-04-07 13:51:34 DEBUG (MainThread) [zigpy_deconz.api] APS data request response: [2, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, 198]

frenck · April 7, 2022, 7:11pm

Have you reported and documented the issue you ran into so it can be looked at and get fixed? Or did you just frustrate yourself and worked around it leading up to this response? Don’t get me wrong, but if you have to, chances are you will run into it again, and become frustrated again.

And simply put: If you can run into, someone else can too.

Sorry to hear you feel that way. Although more often those frustrations from regulars that provide such a response if often created by the lack of reading of the commenter, or, having to repeat the same thing over and over again. Often not personal, but I see how it sometimes can be felt aggressive. Honestly, we are not the best at spoonfeeding in general (That is not meant as a negative comment towards either commenters or responders, it’s more an observation)

I may ask dumb questions at times, or seek help on stuff that is documented somewhere I am unaware of. I sometimes likely don’t even know what to search for, etc…

There is nothing wrong with that. We all had to learn. I still learn every day. Both in the profession as a developer and even as a Home Assistant user. Makes me feel humble at times, which is kinda nice at times. I personal don’t see that as a blocker, but a fun thing!

From my personal experience, if I am stuck, and can’t figure it out. I lay down what I want to solve, how I tried to solve it and which resources I tried to look for an answer to already. This helps someone understand my context.

A response I often get from the Home Assitant community: “Yeah but you are Frenck, people will help you”. Sure, fair, but outside of this community I’m also just Frenck, and need help there at times too.

This is not meant unfriendly, but one is more likely to help someone if they showed they tried and they understand how they can be of help.

Loving it!

We all do!

pbvdven · April 7, 2022, 7:25pm

what issues did you got downgrading im also having similar issues with ZHA on 2022.4 devices wont repair even if you fully deleted them after few trys the get found but stuck on initiallizing or something but downgrading to 2022.3.8 fixed all of that and i had no issues downgrading. there is also a problem with some zigbee devices on ZHA 2022.4.0 like ikea remote and xaomi button but still moving back solves all these issues for now. i have read lot of people with similar issues some have fixed it updating the zigpy qurk some deleted some dev/lib folder but for some that wont fix it and they restored back to 2022.3.8 for now so i think moving back is your best option for now

nickrout · April 7, 2022, 7:26pm

I am neither a fanboy nor a developer. The complaint was that an error wasn’t caught in testing. I suggested the user join beta so more eyes on.

How is that arrogant?

arganto · April 7, 2022, 7:29pm

I got told, that e.g. loosing the history db including long term data, etc. after most of restores is known behavior and will not be fixed. You will find a lot of topics around this here.

frenck · April 7, 2022, 7:31pm

How would that improve things?

aruffell · April 7, 2022, 7:33pm

I have not reported the issue on GitHub as I did not know what to report, other than post 2022.4 update ZHA is no longer working. I got some logs out of the system just an hour or so ago.

I have reported issues I can define more accurately multiple times.

I totally get it, but if one doesn’t even know the topic is covered somewhere, or doesn’t know what to search to find it, then what fault do we have? It is not easy to find answers and believe me I spend more time than I can afford doing my own research trying to fix stuff.

Agreed. By the time I am ready to give up and resort to asking, I am unable to provide accurate steps of all the things I tried. If I were an expert, I would have a logical process that I can detail, but I am not and it often feels like trying new paths in a completely dark maze… Hindsight, I should always take notes of what I try.

Agreed. I really need to take notes so I stand a chance to relay what I tried and give others an opportunity to mock my clueless attempts

On another note, I’ll take the opportunity to thank you for all you do for HA. It is very much appreciated!

frenck · April 7, 2022, 7:37pm

I’ve seen some more reports on that, which you could follow, read, and, if you have additional info, maybe provide to help resolve those issues.

Here is a list of open issues for ZHA currently: https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A"integration%3A+zha"

(You can find those using the “View known issues” link in the docs, and on the integration dashboard of your instance).

nickrout · April 7, 2022, 7:41pm

And on the info page in HA.

aruffell · April 7, 2022, 7:50pm

Downgrading to 2022.3.8 resulted in:
(list may not be complete)

Various integrations were reported as not starting (they were all default stuff such as recorder, logger, default_config, etc.).
Most Zigbee devices worked better, but 20-30 devices were having issues (unavailable, super slow or unresponsive)
Cards like the History card said the history something was disabled
Node Red was getting stuck loading at 60/130
I lost access via Samba to Config and Backups
Studio Code Server also lost access to YAML files
Many NR automations not working

I tried at least a couple different backups.

I restored to the backup I took before downgrading. Everything seems to be working now EXCEPT for all my Zigbee devices. I can’t control them… I have a view I created using a single custom:zha-network-card which shows me my 90 devices. It only shows 2 battery powered zigbee devices as offline, along with my ConBee II zigbee controller. Slowly the LQI/RSSI values are populating back. It seems to me that when things work well, values are populated for all the devices.

EDIT: as for the suggested workaround (Installing a newer version of ZHA sw), I haven’t figured out how to do it yet.

arganto · April 7, 2022, 7:55pm

Didn’t understand the question. A working restore of a backup including esp. long term statistics is for me a more than common “feature” and would improve a lot of things. Without this, the HA backup-restore is not comparable with other restores. Esp. with all the new and growing statistics data, it is a pity, that you loose you complete data, if you have to restore a backup for whatever reasons.

spacegaier · April 7, 2022, 8:08pm

You can. Click on the group and press “Configure State”. The button label is not ideal IMHO, but you will then get a dialog where you can change the entities.

frenck · April 7, 2022, 8:08pm

Not sure which part you are referring to specifically.,

Agreed!

We do tests backups, and lots of people use them with success. Looking up above, the question becomes, why don’t they work for some? That is a bug, not intentionally. Such cases need research and debugging to find out why that is. If such a case if found, we can add tests to ensure such issues never happen again.

frenck · April 7, 2022, 8:09pm

Yeah… that is not a permanent thing (we hope). We are not completely happy with that. But… it’s a start!