cfoos1
July 15, 2025, 10:55pm
1
I got a bunch of ZSE44 sensors and when trying to calibrate them found that they have 1-1.5 degree F jitter. The image is a sample of one of them. This is in a room with a steady temp. After several days of back and forth with support the only solution they could provide is that I should set the sensor to only report on 2 degree changes.
This is a different time period and the green line is a Third Reality sensor correctly reporting the room getting cooler. The other lines are all ZSE44's with the latest firmware.
They finally gave me a return label saying the sensors apparently don't meet my use case and it warns there will be a 30% restocking fee.
Best I can tell there is actually a bug in the firmware since the zwave radio logs show the devices re-broadcasting messages several times with ~4min delays.
3 Likes
It looks like the Third Reality just reports less often, with fewer data points. What is the difference in the number of data points on that graph between 3rd Reality and ZSE44s?
I don't think you can claim that. What is keeping it "steady"? How do you know that the temperature around the sensor is not actually fluctuating? Rooms temps are not consistent in all areas of the room, and any movement will move air around. Any heating or cooling will cycle on and off and will show in the temp readings, often showing 1-1.5 degree changes, at least.
If a sensor does not report as often, you will not see the spikes, you see only the general drop.
4 Likes
cfoos1
July 16, 2025, 1:00am
3
I have an inverter heat pump that keeps the temp within 1 degree most times. The Third Reality sensor reports on 0.2F change. I also have a NIST traceable thermometer I used to check it. On top of that I have a weather station thermometer in the same room, and I did leave them in a cooler overnight to buffer against any changes overnight but they did the same thing.
I can tell you for a fact that the room temp does not go from 72.4, to exactly 74, back down to 72.4 then back up to exactly 74 several times every 5 minutes. I do still have one ZSE44 that is not boxed up so I'll warm it and the other one up and put them back in the room to get that data graphed.
cfoos1
July 16, 2025, 1:34am
4
This is after putting both sensors in a cooler and adding a measuring cup half full of hot water. Each dot is a report from the sensor and the ZSE44 is the yellow one.
cfoos1
July 16, 2025, 2:04am
5
And this is after it leveled off and the cooler started to cool off inside. AKA, should not be any increases in temp at all since the cooler is in a 70 degree room.
Slate
July 16, 2025, 3:35am
7
What driver are you using?
cfoos1
July 16, 2025, 10:56am
8
On a side note, thanks for reminding me, lol:
cfoos1
July 16, 2025, 3:12pm
10
I was going to copy over some logs I provided Zooz, but it appears I have been denied further access to their ticket system.
Doesn't matter, I replied mostly by email and can get new logs. Does anyone know what the serial section of the zwave logs is for? It seems like the serial is supposed to change each time for a new message but the sensor is re-sending old ones on a loop.
I tried to add a txt file for a log but that is denied so I'll just add some lines unless there is a preferred way to add a wall of text.
2025-07-16 06:27:25.383 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 70.8
2025-07-16 06:27:25.381 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 71.1 => 70.8 [Endpoint 0]
2025-07-16 06:27:25.379 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:27:25.377 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:27:25.376 AM|SERIAL « 0x011400a80000010036063105012a02c400bd007f7f16 (22 bytes)
2025-07-16 06:27:09.143 AM|DRIVER all queues idle
2025-07-16 06:27:09.140 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -96 dBm - channel 1: -98 dBm - channel 2: -98 dBm - channel 3: -93 dBm
2025-07-16 06:27:09.139 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:27:09.138 AM|SERIAL « 0x0107013ba09e9ea3c1 (9 bytes)
2025-07-16 06:27:09.135 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:27:09.133 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:27:09.132 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:27:09.129 AM|DRIVER one or more queues busy
2025-07-16 06:26:55.266 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 71.1
2025-07-16 06:26:55.264 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 70.4 => 71.1 [Endpoint 0]
2025-07-16 06:26:55.263 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:26:55.260 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:26:55.258 AM|SERIAL « 0x011400a80000010036063105012a02c700bd007f7f15 (22 bytes)
2025-07-16 06:26:39.143 AM|DRIVER all queues idle
2025-07-16 06:26:39.141 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -96 dBm - channel 1: -97 dBm - channel 2: -97 dBm - channel 3: -92 dBm
2025-07-16 06:26:39.139 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:26:39.138 AM|SERIAL « 0x0107013ba09f9fa4c6 (9 bytes)
2025-07-16 06:26:39.134 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:26:39.133 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:26:39.131 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:26:39.129 AM|DRIVER one or more queues busy
2025-07-16 06:26:25.148 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 70.4
2025-07-16 06:26:25.146 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 71.1 => 70.4 [Endpoint 0]
2025-07-16 06:26:25.144 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:26:25.142 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:26:25.140 AM|SERIAL « 0x011400a80000010036063105012a02c000bd007f7f12 (22 bytes)
2025-07-16 06:26:09.141 AM|DRIVER all queues idle
2025-07-16 06:26:09.138 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -93 dBm - channel 1: -94 dBm - channel 2: -94 dBm - channel 3: -89 dBm
2025-07-16 06:26:09.137 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:26:09.135 AM|SERIAL « 0x0107013ba3a2a2a7c6 (9 bytes)
2025-07-16 06:26:09.133 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:26:09.131 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:26:09.130 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:26:09.128 AM|DRIVER one or more queues busy
2025-07-16 06:25:39.180 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:25:39.180 AM|SERIAL « 0x0107013ba0a0a0a4c6 (9 bytes)
2025-07-16 06:25:39.179 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:25:39.178 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:25:39.131 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:25:39.128 AM|DRIVER one or more queues busy
2025-07-16 06:25:09.142 AM|DRIVER all queues idle
2025-07-16 06:25:09.140 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -98 dBm - channel 1: -99 dBm - channel 2: -99 dBm - channel 3: -95 dBm
2025-07-16 06:25:09.138 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:25:09.137 AM|SERIAL « 0x0107013b9e9d9da1fd (9 bytes)
2025-07-16 06:25:09.136 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:25:09.132 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:25:09.130 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:25:09.128 AM|DRIVER one or more queues busy
2025-07-16 06:24:54.794 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 71.1
2025-07-16 06:24:54.792 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 70.6 => 71.1 [Endpoint 0]
2025-07-16 06:24:54.791 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:24:54.788 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:24:54.787 AM|SERIAL « 0x011400a80000010036063105012a02c700bd007f7f15 (22 bytes)
2025-07-16 06:24:39.142 AM|DRIVER all queues idle
2025-07-16 06:24:39.139 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -98 dBm - channel 1: -99 dBm - channel 2: -99 dBm - channel 3: -95 dBm
2025-07-16 06:24:39.139 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:24:39.137 AM|SERIAL « 0x0107013b9e9d9da1fd (9 bytes)
2025-07-16 06:24:39.135 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:24:39.131 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:24:39.130 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:24:39.128 AM|DRIVER one or more queues busy
2025-07-16 06:24:34.984 AM|DRIVER « [Node 022] [REQ] [BridgeApplicationCommand] - │ RSSI: -75 dBm - └─[Security2CCMessageEncapsulation] - │ sequence number: 191 - │ security class: S2_Authenticated - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 69.2
2025-07-16 06:24:34.982 AM|CNTRLR [Node 022] [~] [Multilevel Sensor] Air temperature: 70.3 => 69.2 [Endpoint 0]
2025-07-16 06:24:34.981 AM|CNTRLR [Node 022] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:24:34.980 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:24:34.979 AM|SERIAL « 0x012000a80000010016129f03bf00eb632050e314743d13dfb32a9d4500b5007f7 (34 bytes) - f2f
2025-07-16 06:24:24.676 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 70.6
2025-07-16 06:24:24.674 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 70.4 => 70.6 [Endpoint 0]
2025-07-16 06:24:24.673 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:24:24.671 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:24:24.669 AM|SERIAL « 0x011400a80000010036063105012a02c200bd007f7f10 (22 bytes)
2025-07-16 06:24:09.140 AM|DRIVER all queues idle
2025-07-16 06:24:09.137 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -98 dBm - channel 1: -100 dBm - channel 2: -100 dBm - channel 3: -95 dBm
2025-07-16 06:24:09.136 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:24:09.134 AM|SERIAL « 0x0107013b9e9c9ca1fd (9 bytes)
2025-07-16 06:24:09.132 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:24:09.131 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:24:09.129 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:24:09.127 AM|DRIVER one or more queues busy
2025-07-16 06:23:54.578 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 70.4
2025-07-16 06:23:54.578 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 70.9 => 70.4 [Endpoint 0]
2025-07-16 06:23:54.577 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:23:54.576 AM|SERIAL « 0x011400a80000010036063105012a02c000bd007f7f12 (22 bytes)
2025-07-16 06:23:39.141 AM|DRIVER all queues idle
2025-07-16 06:23:39.138 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -96 dBm - channel 1: -95 dBm - channel 2: -95 dBm - channel 3: -90 dBm
2025-07-16 06:23:39.138 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:23:39.136 AM|SERIAL « 0x0107013ba0a1a1a6c4 (9 bytes)
2025-07-16 06:23:39.134 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:23:39.132 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:23:39.131 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:23:39.127 AM|DRIVER one or more queues busy
2025-07-16 06:23:09.139 AM|DRIVER all queues idle
2025-07-16 06:23:09.136 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -96 dBm - channel 1: -96 dBm - channel 2: -96 dBm - channel 3: -93 dBm
2025-07-16 06:23:09.134 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:23:09.133 AM|SERIAL « 0x0107013ba0a0a0a3c1 (9 bytes)
2025-07-16 06:23:09.131 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:23:09.129 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:23:09.129 AM|DRIVER one or more queues busy
2025-07-16 06:23:06.691 AM|DRIVER « [Node 012] [REQ] [BridgeApplicationCommand] - │ RSSI: -75 dBm - └─[MeterCCReport] - meter type: Electric - scale: W - rate type: Consumed - value: 0 - time delta: 0 seconds
2025-07-16 06:23:06.689 AM|CNTRLR [Node 012] [~] [Meter] value[66049]: 0 => 0 [Endpoint 0]
2025-07-16 06:23:06.688 AM|CNTRLR [Node 012] [Meter] value[66049]: metadata updated [Endpoint 0]
2025-07-16 06:23:06.685 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:23:06.684 AM|SERIAL « 0x011800a8000001000c0a3202217400000000000000b5007f7f98 (26 bytes)
2025-07-16 06:23:06.594 AM|DRIVER « [Node 012] [REQ] [BridgeApplicationCommand] - │ RSSI: -75 dBm - └─[MeterCCReport] - meter type: Electric - scale: kWh - rate type: Consumed - value: 397.932 - time delta: 3600 seconds - prev. value: 397.932
2025-07-16 06:23:06.593 AM|CNTRLR [Node 012] [~] [Meter] value[65537]: 397.932 => 397.932 [Endpoint 0]
2025-07-16 06:23:06.591 AM|CNTRLR [Node 012] [Meter] value[65537]: metadata updated [Endpoint 0]
2025-07-16 06:23:06.589 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:23:06.588 AM|SERIAL « 0x011c00a8000001000c0e320221640006126c0e100006126c00b5007f7f96 (30 bytes)
2025-07-16 06:23:06.491 AM|DRIVER « [Node 012] [REQ] [BridgeApplicationCommand] - │ RSSI: -75 dBm - └─[MeterCCReport] - meter type: Electric - scale: A - rate type: Consumed - value: 0 - time delta: 0 seconds
2025-07-16 06:23:06.489 AM|CNTRLR [Node 012] [~] [Meter] value[66817]: 0 => 0 [Endpoint 0]
2025-07-16 06:23:06.488 AM|CNTRLR [Node 012] [Meter] value[66817]: metadata updated [Endpoint 0]
2025-07-16 06:23:06.485 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:23:06.484 AM|SERIAL « 0x011800a8000001000c0a3202a16c00000000000000b5007f7f00 (26 bytes)
2025-07-16 06:23:06.394 AM|DRIVER « [Node 012] [REQ] [BridgeApplicationCommand] - │ RSSI: -75 dBm - └─[MeterCCReport] - meter type: Electric - scale: V - rate type: Consumed - value: 123.257 - time delta: 0 seconds
2025-07-16 06:23:06.392 AM|CNTRLR [Node 012] [~] [Meter] value[66561]: 123.577 => 123.257 [Endpoint 0]
2025-07-16 06:23:06.390 AM|CNTRLR [Node 012] [Meter] value[66561]: metadata updated [Endpoint 0]
2025-07-16 06:23:06.387 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:23:06.385 AM|SERIAL « 0x011800a8000001000c0a3202a1640001e179000000b5007f7f91 (26 bytes)
2025-07-16 06:22:54.324 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 70.9
2025-07-16 06:22:54.322 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 71.1 => 70.9 [Endpoint 0]
2025-07-16 06:22:54.321 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:22:54.318 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:22:54.317 AM|SERIAL « 0x011400a80000010036063105012a02c500bd007f7f17 (22 bytes)
2025-07-16 06:22:39.140 AM|DRIVER all queues idle
2025-07-16 06:22:39.137 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -95 dBm - channel 1: -97 dBm - channel 2: -97 dBm - channel 3: -93 dBm
2025-07-16 06:22:39.135 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:22:39.132 AM|SERIAL « 0x0107013ba19f9fa3c0 (9 bytes)
2025-07-16 06:22:39.131 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:22:39.128 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:22:39.127 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:22:39.125 AM|DRIVER one or more queues busy
2025-07-16 06:22:09.139 AM|DRIVER all queues idle
2025-07-16 06:22:09.136 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -98 dBm - channel 1: -98 dBm - channel 2: -98 dBm - channel 3: -93 dBm
2025-07-16 06:22:09.134 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:22:09.133 AM|SERIAL « 0x0107013b9e9e9ea3ff (9 bytes)
2025-07-16 06:22:09.130 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:22:09.127 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:22:09.126 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:22:09.124 AM|DRIVER one or more queues busy
2025-07-16 06:21:54.091 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 71.1
2025-07-16 06:21:54.090 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 70.9 => 71.1 [Endpoint 0]
2025-07-16 06:21:54.089 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:21:54.086 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:21:54.084 AM|SERIAL « 0x011400a80000010036063105012a02c700bd007f7f15 (22 bytes)
2025-07-16 06:21:39.137 AM|DRIVER all queues idle
2025-07-16 06:21:39.135 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -96 dBm - channel 1: -98 dBm - channel 2: -98 dBm - channel 3: -94 dBm
2025-07-16 06:21:39.134 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:21:39.133 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:21:39.126 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:21:39.123 AM|DRIVER one or more queues busy
2025-07-16 06:21:23.976 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 70.9
2025-07-16 06:21:23.975 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 71.1 => 70.9 [Endpoint 0]
2025-07-16 06:21:23.972 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:21:23.970 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:21:23.969 AM|SERIAL « 0x011400a80000010036063105012a02c500bd007f7f17 (22 bytes)
2025-07-16 06:21:09.135 AM|DRIVER all queues idle
2025-07-16 06:21:09.133 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -97 dBm - channel 1: -98 dBm - channel 2: -98 dBm - channel 3: -92 dBm
2025-07-16 06:21:09.132 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:21:09.130 AM|SERIAL « 0x0107013b9f9e9ea4f9 (9 bytes)
2025-07-16 06:21:09.128 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:21:09.126 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:21:09.125 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:21:09.122 AM|DRIVER one or more queues busy
2025-07-16 06:20:39.137 AM|DRIVER all queues idle
2025-07-16 06:20:39.132 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -98 dBm - channel 1: -97 dBm - channel 2: -97 dBm - channel 3: -95 dBm
2025-07-16 06:20:39.131 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:20:39.130 AM|SERIAL « 0x0107013b9e9f9fa1fd (9 bytes)
2025-07-16 06:20:39.128 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:20:39.126 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:20:39.124 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:20:39.121 AM|DRIVER one or more queues busy
2025-07-16 06:20:23.741 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 71.1
2025-07-16 06:20:23.740 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 70.9 => 71.1 [Endpoint 0]
2025-07-16 06:20:23.738 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:20:23.736 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:20:23.734 AM|SERIAL « 0x011400a80000010036063105012a02c700bd007f7f15 (22 bytes)
2025-07-16 06:20:09.133 AM|DRIVER all queues idle
2025-07-16 06:20:09.131 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -97 dBm - channel 1: -98 dBm - channel 2: -98 dBm - channel 3: -94 dBm
2025-07-16 06:20:09.129 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:20:09.129 AM|SERIAL « 0x0107013b9f9e9ea2ff (9 bytes)
2025-07-16 06:20:09.126 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:20:09.125 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:20:09.121 AM|DRIVER one or more queues busy
2025-07-16 06:19:53.626 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 70.9
2025-07-16 06:19:53.624 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 71.1 => 70.9 [Endpoint 0]
2025-07-16 06:19:53.623 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:19:53.620 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:19:53.619 AM|SERIAL « 0x011400a80000010036063105012a02c500bd007f7f17 (22 bytes)
2025-07-16 06:19:39.133 AM|DRIVER all queues idle
2025-07-16 06:19:39.131 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -95 dBm - channel 1: -98 dBm - channel 2: -98 dBm - channel 3: -94 dBm
2025-07-16 06:19:39.129 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:19:39.128 AM|SERIAL « 0x0107013ba19e9ea2c1 (9 bytes)
2025-07-16 06:19:39.126 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:19:39.124 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:19:39.123 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:19:39.121 AM|DRIVER one or more queues busy
2025-07-16 06:19:23.511 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 71.1
2025-07-16 06:19:23.510 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 70.4 => 71.1 [Endpoint 0]
2025-07-16 06:19:23.508 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:19:23.504 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:19:23.502 AM|SERIAL « 0x011400a80000010036063105012a02c700bd007f7f15 (22 bytes)
2025-07-16 06:19:09.135 AM|DRIVER all queues idle
2025-07-16 06:19:09.132 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -96 dBm - channel 1: -97 dBm - channel 2: -97 dBm - channel 3: -94 dBm
2025-07-16 06:19:09.130 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:19:09.129 AM|SERIAL « 0x0107013ba09f9fa2c0 (9 bytes)
2025-07-16 06:19:09.127 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:19:09.124 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:19:09.123 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:19:09.119 AM|DRIVER one or more queues busy
2025-07-16 06:18:53.393 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 70.4
2025-07-16 06:18:53.391 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 70.6 => 70.4 [Endpoint 0]
2025-07-16 06:18:53.390 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:18:53.387 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:18:53.386 AM|SERIAL « 0x011400a80000010036063105012a02c000bd007f7f12 (22 bytes)
2025-07-16 06:18:39.130 AM|DRIVER all queues idle
2025-07-16 06:18:39.127 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -97 dBm - channel 1: -96 dBm - channel 2: -96 dBm - channel 3: -92 dBm
2025-07-16 06:18:39.126 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:18:39.125 AM|SERIAL « 0x0107013b9fa0a0a4f9 (9 bytes)
2025-07-16 06:18:39.123 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:18:39.120 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:18:39.120 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:18:39.117 AM|DRIVER one or more queues busy
2025-07-16 06:18:09.130 AM|DRIVER all queues idle
2025-07-16 06:18:09.127 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -99 dBm - channel 1: -98 dBm - channel 2: -98 dBm - channel 3: -95 dBm
2025-07-16 06:18:09.126 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:18:09.125 AM|SERIAL « 0x0107013b9d9e9ea1fe (9 bytes)
2025-07-16 06:18:09.122 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:18:09.120 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:18:09.119 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:18:09.116 AM|DRIVER one or more queues busy
2025-07-16 06:17:53.163 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 70.6
2025-07-16 06:17:53.161 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 70.4 => 70.6 [Endpoint 0]
2025-07-16 06:17:53.159 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:17:53.157 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:17:53.155 AM|SERIAL « 0x011400a80000010036063105012a02c200bd007f7f10 (22 bytes)
2025-07-16 06:17:39.128 AM|DRIVER all queues idle
2025-07-16 06:17:39.126 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -98 dBm - channel 1: -99 dBm - channel 2: -99 dBm - channel 3: -94 dBm
2025-07-16 06:17:39.124 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:17:39.123 AM|SERIAL « 0x0107013b9e9d9da2fe (9 bytes)
2025-07-16 06:17:39.121 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:17:39.118 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:17:39.118 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:17:39.115 AM|DRIVER one or more queues busy
2025-07-16 06:17:09.128 AM|DRIVER all queues idle
2025-07-16 06:17:09.126 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -96 dBm - channel 1: -98 dBm - channel 2: -98 dBm - channel 3: -93 dBm
2025-07-16 06:17:09.124 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:17:09.123 AM|SERIAL « 0x0107013ba09e9ea3c1 (9 bytes)
2025-07-16 06:17:09.121 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:17:09.119 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:17:09.118 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:17:09.116 AM|DRIVER one or more queues busy
2025-07-16 06:16:52.928 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 70.4
2025-07-16 06:16:52.927 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 71.1 => 70.4 [Endpoint 0]
2025-07-16 06:16:52.925 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:16:52.921 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:16:52.919 AM|SERIAL « 0x011400a80000010036063105012a02c000bd007f7f12 (22 bytes)
2025-07-16 06:16:39.130 AM|DRIVER all queues idle
2025-07-16 06:16:39.126 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -95 dBm - channel 1: -97 dBm - channel 2: -97 dBm - channel 3: -92 dBm
2025-07-16 06:16:39.125 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:16:39.124 AM|SERIAL « 0x0107013ba19f9fa4c7 (9 bytes)
2025-07-16 06:16:39.122 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:16:39.119 AM|DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-16 06:16:39.119 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:16:39.116 AM|DRIVER one or more queues busy
2025-07-16 06:16:22.808 AM|DRIVER « [Node 054] [REQ] [BridgeApplicationCommand] - │ RSSI: -67 dBm - └─[MultilevelSensorCCReport] - sensor type: Air temperature - scale: Fahrenheit - value: 71.1
2025-07-16 06:16:22.806 AM|CNTRLR [Node 054] [~] [Multilevel Sensor] Air temperature: 70.4 => 71.1 [Endpoint 0]
2025-07-16 06:16:22.805 AM|CNTRLR [Node 054] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2025-07-16 06:16:22.802 AM|SERIAL » [ACK] (0x06)
2025-07-16 06:16:22.801 AM|SERIAL « 0x011400a80000010036063105012a02c700bd007f7f15 (22 bytes)
2025-07-16 06:16:09.128 AM|DRIVER all queues idle
2025-07-16 06:16:09.127 AM|DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -97 dBm - channel 1: -98 dBm - channel 2: -98 dBm - channel 3: -94 dBm
2025-07-16 06:16:09.126 AM|SERIAL « [ACK] (0x06)
2025-07-16 06:16:09.118 AM|SERIAL » 0x0103003bc7 (5 bytes)
2025-07-16 06:16:09.116 AM|DRIVER one or more queues busy
Best I can tell this is the sensor sending this report on a loop, along with other ones and that is what is causing the reported temp to jump up and down.
Use preformatted text blocks (I fixed it for you)
You are using Zwave JS...
I could be the sensor or it could be an issue with ZWJS, hard to tell without analyzing a bunch of the zwave logs.
Just in brief testing I did on my test hub with some switches I was getting all sort of duplicate and bogus messages. Switch back to Legacy ZIP and problems go away. I reported it and have been waiting for a fix to test further.
2 Likes
tohm
July 16, 2025, 3:22pm
12
Yup... I've been using one of these ZSE44 sensors in Hubitat for a couple of years now... I attached to the side of my clothes dryer... along with 2 other sensors in the room...it's part of my home kiosk dashboard to show if the dryer is on and reminds me if I left clothes in the dryer after it finished... When I created the rule, I had to make accommodations for some serious false heat fluctuations... Randomly the sensor would report temperatures way above 500 degrees for very short periods of time. I was going to replace the sensor, but this rule fix has done a good job so i never replaced it. I don't' think you can count on this sensor being part of an HVAC system or anything critical.
cfoos1
July 16, 2025, 3:34pm
13
I did try Zwave JS to get the logs, but also tested on the old zwave, and also removed the sensor and moved it to my C7 hub using US instead of US-LR. So I have reproduced with new and old zwave on C8 and C7 with both US bands.
I'll modify my old post to add the full logs instead of the snippets. There are several that repeat like that and these sensors are the only ones that do it. Each time it is logged to the device.
cfoos1
July 16, 2025, 3:39pm
14
Honestly I would be fine with it if they said that the temp report was +- 1.5 degree and I would have not bought them, but on their site they say to use it to control AC.
I would still have bought one more, just not as many as I did. I was testing it and the other sensor to turn on bathroom fans based on humidity and it works great for that. I just never looked at the temp accuracy before buying more.....
1 Like
tohm
July 16, 2025, 3:48pm
15
+-1.5 degrees? In my case, it would jump to 500 even 1000 degrees... but for very short periods of time. I like ZooZ products overall and I have many, but I'll never get another ZSE44 again.
1 Like
cfoos1
July 16, 2025, 3:53pm
16
If you look at the first image in the post. That one sensor was jumping between less than 72.5 and back to exactly 74 with as little as a min between them at times. I think the lower values were the correct ones and everything above just old readings getting resent on a loop.
cfoos1
July 16, 2025, 3:56pm
17
@jtp10181 Does your driver have access to a message number or serial? Something that should be unique per temp report that could allow the driver to discard repeated messages.
The device spamming old messages would still nuke the battery, but discarding repeats should make them usable at least.
cfoos1:
I did try Zwave JS to get the logs, but also tested on the old zwave, and also removed the sensor and moved it to my C7 hub using US instead of US-LR. So I have reproduced with new and old zwave on C8 and C7 with both US bands.
Well that eliminates ZWJS as the issue then, it could just be the sensor. I only have one on Hubitat old one and its set to 2 deg threshold and in my garage. My chart looks pretty stable.
I do have a new model paired to SmartThings (test device) but the chart is not great on there. I can see the history though, looks pretty stable. The sensor is just sitting on my desk with the cover off. Its set to a threshold of 1 deg.
This is the command class the reports come in as, looks like Hubitat is not passing a sequence or anything like that over to the driver.
I would be curious to see what all your temp related settings are set to?
cfoos1
July 16, 2025, 4:20pm
19
Right now I have it set to 3 to see if there is a point that it stabilizes or if you just need to increase past the reading fluctuations.
The I2c sensor specs say +/- 0.2 C, so I started to wonder if the sensor has jitter in its reported value and setting the device too low is causing interrupts resulting in the device not knowing messages were received causing a cache and resend loop.
The ZSE44 advanced settings for the 800 version does say it can be set to 0.1, but maybe they did not fully test that and the device firmware can't handle it.
I say this since setting to report on 0.2 still fluctuated a lot, but since setting it to report on 0.3 it seems stable. The device warmed up when I touched it to wake it, but it is now reporting the cooldown in 0.3+ increments without spikes to old readings.
Oh yeah, I would not really go below 0.5 myself on any temp sensor.
