Found this while debug logging while it went unavailable, but I’m not sure what I’m looking at:
2024-03-22 16:05:56.822 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x70BC](SNZB-02P): Attempting to checkin with device - missed checkins: 2
2024-03-22 16:05:56.823 DEBUG (MainThread) [zigpy.zcl] [0x70BC:1:0x0000] Sending request header: ZCLHeader(frame_control=FrameControl<0x00>(frame_type=<FrameType.GLOBAL_COMMAND: 0>, is_manufacturer_specific=False, direction=<Direction.Client_to_Server: 0>, disable_default_response=0, reserved=0, *is_cluster=False, *is_general=True), tsn=66, command_id=<GeneralCommand.Read_Attributes: 0>, *direction=<Direction.Client_to_Server: 0>)
2024-03-22 16:05:56.823 DEBUG (MainThread) [zigpy.zcl] [0x70BC:1:0x0000] Sending request: Read_Attributes(attribute_ids=[4])
2024-03-22 16:05:56.823 DEBUG (MainThread) [zigpy.device] [0x70bc] Extending timeout for 0x42 request
2024-03-22 16:05:56.823 DEBUG (MainThread) [bellows.zigbee.application] Sending packet ZigbeePacket(timestamp=datetime.datetime(2024, 3, 22, 15, 5, 56, 823329, tzinfo=datetime.timezone.utc), src=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x0000), src_ep=1, dst=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x70BC), dst_ep=1, source_route=None, extended_timeout=True, tsn=66, profile_id=260, cluster_id=0, data=Serialized[b'\x00B\x00\x04\x00'], tx_options=<TransmitOptions.NONE: 0>, radius=0, non_member_radius=0, lqi=None, rssi=None)
2024-03-22 16:05:56.823 DEBUG (MainThread) [bellows.ezsp.protocol] Send command setExtendedTimeout: (04:87:27:ff:fe:b3:23:1f, True)
2024-03-22 16:05:56.823 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'21d321a92a2a0a91ea6ab5022d51930be97e'
2024-03-22 16:05:56.829 DEBUG (bellows.thread_0) [bellows.uart] Data frame: b'13d3a1a92a2ad08e7e'
2024-03-22 16:05:56.829 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'82503a7e'
2024-03-22 16:05:56.829 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received setExtendedTimeout: []
2024-03-22 16:05:56.829 DEBUG (MainThread) [bellows.ezsp.protocol] Send command sendUnicast: (<EmberOutgoingMessageType.OUTGOING_DIRECT: 0>, 0x70bc, EmberApsFrame(profileId=260, clusterId=0, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_RETRY|APS_OPTION_ENABLE_ROUTE_DISCOVERY: 320>, groupId=0, sequence=66), 71, b'\x00B\x00\x04\x00')
I’ve also noticed that even during the 6 hours the device is “available” the data doesn’t change.
The temperature should be moving up and down every x minutes, like the other sensors, but the one with the issues is stuck with the same value for the entire 6 hours until it goes offline again. Then it has a new value when it comes back, and sticks with it until to goes offline again.