Multisensor (Temp/Hum) stop reporting values

deCONZ General Support
1

Hello community,

have a setup with 5 temp/hum multisensors which worked without problems for years. Since a few weeks all sensors stop reporting new values at the same day, most of them within the same hour.

What I did so far:

  1. Changed the battery of all sensors.
  2. Updated the Gateway to 2.29.1
  3. Updated the ConBee 2 firmware to 26780700
  4. Added an extra router (Sonoff ZBMINIR2)

deconz is running as a Docker container, when I restart the container the sensors are reporting values again. Removing the battery has no special effect when the container is not restarted before.

The three old sensors are _TZ3000_xr3htd96 / TS0201 / Version 1.0.6.

a4:c1:38:e7:d6:c8:39:fa-01-0402 / a4:c1:38:e7:d6:c8:39:fa-01-0405
a4:c1:38:3f:0b:b1:8a:48-01-0402 / a4:c1:38:3f:0b:b1:8a:48-01-0405
a4:c1:38:b0:55:e6:93:45-01-0402 / a4:c1:38:b0:55:e6:93:45-01-0405

The two new sensors are _TZE200_a8sdabtg / TS0601 / Version 2.1.1

a4:c1:38:a9:11:9b:d3:f2-01-0405 / a4:c1:38:a9:11:9b:d3:f2-01-0402
a4:c1:38:60:74:ad:ca:5f-01-0405 / a4:c1:38:60:74:ad:ca:5f-01-0402

Logs for the timeframe when the sensors stopped repoting values can be found here:

Any help would be highly appreciated. :slight_smile:

Thanks and kind regards!

2

Hello, battery level ?
On your log we can see a device make a websocket notification at 20:22:40 and your logs finish at 20h29.
Same result in phoscon ?

3

Hello Smanar,

thanks for your reply!

Batteries are new and have been checked (> 1,4V) with volt-meter and 10 ohm resistor.

Full logs for device a4:c1:38:a9:11:9b:d3:f2 can be found here: Device Logs1 - Pastebin.com

The log shows value updates untill the timestamp “21:22:35:861”. Then only “lastseen” updates untill the deconz-restart at timestamp “09:37:42:267”. The Phoscon UI showed the “lastupdated” timestamp from the message. “Lastseen” updates did not change the timestamp in the UI.

My initial idea was related to the device or some zibee network error. Finally only the restart of the container makes it work again.

Same for sensor a4:c1:38:b0:55:e6:93:45 - Logs are here: Device Logs2 - Pastebin.com

Logs are filtered on device ID from docker logs with settings DEBUG_ERROR=2 and DEBUG_INFO=2.

Full logs since 2024-12-10T20:20:00 until 2024-12-10T23:30:00 can be found here: PrivateBin

4

There is 2 types of websocket notifications, the only important are thoses one that start by “e”:“changed”

And you have 1 at start of your logs

20:22:40:364 Websocket 192.168.5.51:46816 send message: {"e":"changed","id":"25","r":"sensors","state":{"lastupdated":"2024-12-10T19:22:40.362","temperature":2110},"t":"event","uniqueid":"a4:c1:38:a9:11:9b:d3:f2-01-0402"} (ret = 165)

And one at the end

10:23:20:024 Websocket 192.168.5.51:42718 send message: {"e":"changed","id":"25","r":"sensors","state":{"lastupdated":"2024-12-11T09:23:20.023","temperature":2130},"t":"event","uniqueid":"a4:c1:38:a9:11:9b:d3:f2-01-0402"} (ret = 165)

But IDK why the port is not the same ?

5

I’m not aware of how the websockets are used in the communication. I can see different ports and different IP adresses in the logs.

In my setup I’m using the Phoscon Web-GUI, Phoscon Android app and the deCONZ Home Assistant integration.

6

Which deconz version was running when the problem occured first?

7

Something you can try is Using Phoscon/help/API Information/event.
It will open a new websocket connexion just for event.

And BTW when the issue happen, over sensors are working ? Because if it’s that I m thinking, it’s all your websocket connexion that need to be not working.

8

Is it perhaps related to this: Headless deCONZ - no more sensor updates after searching for lights · Issue #7935 · dresden-elektronik/deconz-rest-plugin · GitHub
Or this: Problem with Philips Hue switches no longer working - #6 by Tobimm

9

Thank’s for your ideas!

@ParanoidiordnA
The old deconz version was 2.15.00 and ConBee 2 firmware version 26720700.

Now it is upgraded to deconz version 2.29.1 and firmware 26780700.

@Smanar
That’s a good point, I have a Ikea VALLHORN motion sensor which reports presence (motion) and light level. In my Home Assistant history I can see multiple presence events during the time when the temp/hum sensors did not report values. But the light level values from the motion sensor did also stop when the temp/hum sensors stopped reporting.

@robidog
In my case it was not related to adding new devices to the network.

10

And if you restart deconz, third app probably remake the websocket connexion, and all is reworking.

When it’s broked, try to make a new websocket connexion using Phoscon or another app (On my side I have a browser plugin).
You can found the websocket port used by deconz with http://IP:PORT/api/KEY/config

You can set a fixed port using command line too (–ws-port) but as you are on docker, they can do so much magic on config …

11

Hello Smanar

the effect did not happen again so far. I’ll post again when the situation occours again. Thanks for your help and ideas.