ZHA SNZB-02P unavailable for 6 hours every 6 hours

Configuration Zigbee
, ,
1

Hello,

I’m relatively new to Home Assistant and smart home in general.
I’ve got 3 SNZB-02P Sonoff ZigBee Temperature & Humidity Sensor.
They’ve been working fine for some weeks since installation but recently one of them has started dropping out every 6 hours and stays unavailable for about 6 hours before coming back.

I’ve been searching and trying to find a solution or explanation as to why this is happening but haven’t found anything that provides a solution.

I’ve recently noticed by looking at the Logbook of one of the sensors that’s working and comparing it to the one not working that the events are different.
The one working has this about every hour: “Checkin event was fired”
Whereas the one not working has this at the same time it goes unavailable which is every 6 hours: “Zha Event was fired”

Why is the events different, and is there any way to fix it?
I’ve tried re-pairing the device etc.

This is how the Logbook looks:

HA_SNZB02P_Logbook
HA_SNZB02P_Logbook386×793 42.9 KB

I’m running Home Assistant as a VM on Unraid.
I installed using haos_ova-11.4.qcow2.
I’ve got a 3m USB extension cable connecting the server and the USB dongel which is a ZBDongle-E SONOFF Zigbee 3.0 USB Dongle Plus.
I did not update or make any other changes at the time it started behaving like this.

Thanks in advance!

2

Anyone?

Is there anything else I can look at to see what the issue is?

3

The pattern is very clear, every 6:40 and 18:40 ish it becomes unavailable, and evey 12:40 and 00:40 ish it comes back.

cBJb6S51
cBJb6S511297×272 3.95 KB

4

I am working about 4 years with HA. Did a lot of thing with it.
Added the Lidl Zigbee gateway some weeks ago and a radiator valve SonOff, everything fine.
Now I got a SNZB-02P and have a lot of similar problems. Connection drops, temperature or humidity values need hours to update. Test to move the device from a warm room to a cold room at least3 to 4 degres difference. Hours till update. Distance to Zigbee Coortinator max 10m. Actualy 4 meters.
I know there are some posts to that issue, but they are old for an older Version.

So who has this device running fine and how, or is so bad. I have other SonOff devices working fine.

1 Like
5

After bad experiences with the Sonoff SNZB-03, I don’t buy Sonoff Zigbee sensor any more.

1 Like
6

I’ve got 2 of them working fine it seems, but this one keeps having 6 hours disconnected/unavailable every 6 hours.
The distance isn’t greater than the others, and moving it next to the receiver doesn’t make any difference.

Is there any other logs I can look at to see what’s going on?

7

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.

9

I have not solved it, no.
Checking it how?
Home Assistant says it’s the same as the others, and it’s “Up-to-date”.

The other 2 are still working flawlessly.

11

I believe it’s:
Firmware: 6.10.3.0 build 297

12

Hi Marabon, welcome to the forum!
Have a look at this: Zigbee networks: how to guide for avoiding interference + optimizing using Zigbee Router devices (repeaters/extenders) to get best possible range and coverage