Broken in hub version 2.3.0.124: Advanced Honeywell T6 Pro Thermostat

Soft reset is a good idea to ensure completely clean database. I don't think a 20m wait is required on the power down, tho, more like 30-60s should be sufficient. :slight_smile:

Here are some screens showing the soft reset process...

Choose the Restore from Backup? link at the bottom of the screen below and choose the backup file you just created:

i did this procedure about 4 days ago but happy to do it again now ty

2 Likes

It won't hurt, and will ensure all the mess is cleaned out of your system that could have accumulated.

i didn't think it would hurt either but...

A full z-wave repair is not usually recommended. Try repairing just those three nodes.

2 Likes

Oops, yes, I missed that a full repair was recommended/intended, sorry, reading too quickly. Z-Wave repairs are generally recommended on a per-device basis only where there are issues. That Zooz may also still be causing you problems...can be a troublesome device.

The good news is that @aaiyar can be at your door in just a few hours if you need any additional help. He's just that nice a guy. :wink:

2 Likes

haha. well power cycling again and waiting about 30 minutes seems to let everything come back to the z-wave network fine

2 Likes

I only recommended it for the once because of all the ghosts he had going.

2 Likes

for some reason my energy meter reports about 100x zwave log messages per minute. that's why i am not super concerned about the 1-3x made by my non-quiescent polling T6 approach. anybody know how i can reduce this massive volume?

aeotec home energy meter2022-01-11 17:33:08.380 seqNo: 198, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:08.080 seqNo: 197, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:07.780 seqNo: 196, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:07.479 seqNo: 195, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:07.179 seqNo: 194, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:06.878 seqNo: 193, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:06.578 seqNo: 192, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:06.278 seqNo: 191, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:05.977 seqNo: 190, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
Advanced Honeywell T6 Pro Thermostat2022-01-11 17:33:05.778 seqNo: 189, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0
Advanced Honeywell T6 Pro Thermostat2022-01-11 17:33:05.777 seqNo: 188, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0
aeotec home energy meter2022-01-11 17:33:05.677 seqNo: 187, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:05.376 seqNo: 186, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:05.076 seqNo: 185, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:04.775 seqNo: 184, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:04.475 seqNo: 183, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:04.175 seqNo: 182, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:03.874 seqNo: 181, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:03.574 seqNo: 180, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:03.273 seqNo: 179, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
aeotec home energy meter2022-01-11 17:33:02.973 seqNo: 178, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
Advanced Honeywell T6 Pro Thermostat2022-01-11 17:33:02.674 seqNo: 177, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0
aeotec home energy meter2022-01-11 17:33:02.672 seqNo: 176, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
Advanced Honeywell T6 Pro Thermostat2022-01-11 17:33:02.373 seqNo: 175, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0
aeotec home energy meter2022-01-11 17:33:02.372 seqNo: 174, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
Advanced Honeywell T6 Pro Thermostat2022-01-11 17:33:02.073 seqNo: 173, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0
aeotec home energy meter2022-01-11 17:33:02.071 seqNo: 172, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
Advanced Honeywell T6 Pro Thermostat2022-01-11 17:33:01.772 seqNo: 171, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0
aeotec home energy meter2022-01-11 17:33:01.771 seqNo: 170, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
Advanced Honeywell T6 Pro Thermostat2022-01-11 17:33:01.472 seqNo: 169, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0
aeotec home energy meter2022-01-11 17:33:01.471 seqNo: 168, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
Advanced Honeywell T6 Pro Thermostat2022-01-11 17:33:01.171 seqNo: 167, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0
aeotec home energy meter2022-01-11 17:33:01.170 seqNo: 166, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
Advanced Honeywell T6 Pro Thermostat2022-01-11 17:33:01.071 seqNo: 165, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0
Advanced Honeywell T6 Pro Thermostat2022-01-11 17:33:01.070 seqNo: 164, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0
Advanced Honeywell T6 Pro Thermostat2022-01-11 17:33:00.871 seqNo: 163, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0
aeotec home energy meter2022-01-11 17:33:00.869 seqNo: 162, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown
Advanced Honeywell T6 Pro Thermostat2022-01-11 17:33:00.771 seqNo: 161, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0
Advanced Honeywell T6 Pro Thermostat2022-01-11 17:33:00.769 seqNo: 160, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0
Advanced Honeywell T6 Pro Thermostat2022-01-11 17:33:00.570 seqNo: 159, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0

You should be able to turn that down in the driver

another question: i see in my motion sensor logs my motion sensor is definitely catching me active moving as i walk near the living room in the last half hour:

motion	active		motion set to active	DEVICE		2022-01-11 05:54:10.994 PM PST
motion	inactive		motion set to inactive	DEVICE		2022-01-11 05:54:07.462 PM PST
motion	active		motion set to active	DEVICE		2022-01-11 05:53:22.193 PM PST
motion	inactive		motion set to inactive	DEVICE		2022-01-11 05:38:16.488 PM PST
motion	active		motion set to active	DEVICE		2022-01-11 05:38:07.075 PM PST

i have a super-simple rule that is supposed to (and often does) set noMotionMin global variable to 0 whenever motion is detected.

how is noMotionMin 188?

it's still going up as i write this!

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:27:00.464 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 195

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:26:00.192 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 194

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:25:00.181 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 193

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:24:00.194 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 192

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:23:00.196 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 191

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:22:00.205 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 190

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:21:00.177 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 189

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:20:00.292 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 188

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:19:00.201 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 187

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:18:00.190 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 186

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:17:00.174 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 185

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:16:00.177 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 184

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:15:00.200 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 183

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:14:00.199 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 182

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:13:00.175 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 181

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:12:00.188 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 180

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:11:00.183 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 179

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:10:00.195 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 178

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:09:00.175 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 177

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:08:00.172 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 176

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:07:00.176 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 175

[dev:47](http://hubitat/logs#pastdev47)2022-01-11 06:06:00.183 pm [info](http://hubitat/device/edit/47)noMotionMin variable is 174

I can't reproduce what you have observed. My rule and log are appended.

I suggest recreating your rule. If the issue persists, then start a new thread under Rule Machine, because this is quite distinct from the title of this thread (so the right people might not see it).