[Resurrected] Advanced Honeywell T6 Pro Z-Wave Thermostat Driver

Custom Apps and Drivers
284

I'm having a problem with setting the time on my T6 Pros. I have six of them for various zone and they were working just fine. When we switched to DST they changed correctly. Then I upgraded from a C-7 to a C-8. I didn't notice any problems.

A week or so ago I did some maintenance on the heating system and they were off most of an hour. After they powered up and I cleared the "set the date" alert I tried syncing the clock w/o luck. Some of them also lost their set points. The Hubitat values were correct, so it was just a matter of hitting Configure. But time sync did not work. I tried various things, but did not save any logs as I was busy.

Last night we had a 12 hour power failure. So before I start messing with them, what's the recommended procedure to get them configured and time in sync after a power loss?

I suppose that now that they are in the network as repeaters I can put batteries in them. That's allot of batteries...

Thanks.

Jeff

285

Thermostat should automatically sync with the Hub’s time, but there is a Sync Clock button on the device page.

286

I tried that, with and w/o doing a configure first with no luck.

I turned on debug logging and see a syncClock job pending:

syncClock	2023-04-03 00:32:23 EDT		PENDING	23 32 0/3 * * ?

I then hit syncClock and see no new debug logs, or a change in the schedule job.

The same when I hit configure. No debug long or change in the scheduled jobs.

The only logs I see are from when I turned on debugging:

dev:1352023-04-02 21:36:08.023debugParameterNumber: 43, Size: 1, Value: 0
dev:1352023-04-02 21:36:08.022debugParameterNumber: 42, Size: 1, Value: 0
dev:1352023-04-02 21:36:08.020debugParameterNumber: 41, Size: 1, Value: 1
dev:1352023-04-02 21:36:08.018debugParameterNumber: 40, Size: 1, Value: 0
dev:1352023-04-02 21:36:08.017debugParameterNumber: 39, Size: 1, Value: 1
dev:1352023-04-02 21:36:08.015debugParameterNumber: 38, Size: 1, Value: 0
dev:1352023-04-02 21:36:08.014debugParameterNumber: 37, Size: 1, Value: 0
dev:1352023-04-02 21:36:08.012debugParameterNumber: 36, Size: 1, Value: 0
dev:1352023-04-02 21:36:08.006debugParameterNumber: 35, Size: 1, Value: 0
dev:1352023-04-02 21:36:08.004debugParameterNumber: 34, Size: 1, Value: 0
dev:1352023-04-02 21:36:08.002debugParameterNumber: 33, Size: 1, Value: 0
dev:1352023-04-02 21:36:08.001debugParameterNumber: 32, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.999debugParameterNumber: 31, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.997debugParameterNumber: 30, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.996debugParameterNumber: 29, Size: 1, Value: 68
dev:1352023-04-02 21:36:07.994debugParameterNumber: 28, Size: 1, Value: 50
dev:1352023-04-02 21:36:07.993debugParameterNumber: 27, Size: 1, Value: 1
dev:1352023-04-02 21:36:07.991debugParameterNumber: 26, Size: 1, Value: 5
dev:1352023-04-02 21:36:07.989debugParameterNumber: 25, Size: 1, Value: 9
dev:1352023-04-02 21:36:07.988debugParameterNumber: 24, Size: 1, Value: 9
dev:1352023-04-02 21:36:07.986debugParameterNumber: 23, Size: 1, Value: 3
dev:1352023-04-02 21:36:07.984debugParameterNumber: 22, Size: 1, Value: 3
dev:1352023-04-02 21:36:07.983debugParameterNumber: 21, Size: 1, Value: 3
dev:1352023-04-02 21:36:07.981debugParameterNumber: 20, Size: 1, Value: 3
dev:1352023-04-02 21:36:07.980debugParameterNumber: 19, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.978debugParameterNumber: 18, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.976debugParameterNumber: 17, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.964debugParameterNumber: 16, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.961debugParameterNumber: 15, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.960debugParameterNumber: 14, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.958debugParameterNumber: 13, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.956debugParameterNumber: 12, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.954debugParameterNumber: 11, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.953debugParameterNumber: 10, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.951debugParameterNumber: 9, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.949debugParameterNumber: 8, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.948debugParameterNumber: 7, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.946debugParameterNumber: 6, Size: 1, Value: 1
dev:1352023-04-02 21:36:07.944debugParameterNumber: 5, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.943debugParameterNumber: 4, Size: 1, Value: 3
dev:1352023-04-02 21:36:07.941debugParameterNumber: 3, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.939debugParameterNumber: 2, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.924debugParameterNumber: 1, Size: 1, Value: 0
dev:1352023-04-02 21:36:07.836warndebug logging is: true
dev:1352023-04-02 21:36:07.835infoupdated...

Since switching to the C-8 most devices, including the thermostats, are connected directly to the hub.

Any ideas?

287

There isn’t any logging in that method just sends the updated time to the thermostat.

288

The T6 isn't smart enough to have a dynamic Balance Point that adjusts based on the heating Set Point, so I use this Advanced driver (via Rule Machine) to lower the Balance Point a calculated amount when I lower the Set Point. I need access to ISU#355 Balance Point (Compressor Lockout) to do that. (I added a BalancePoint command to the driver for RuleMachine to use.)

289

Anybody know if this thermostat is compatible with a duel fuel set-up. Specifically a Heat Pump and a Gas Furnace. If so, any resources on how to set this up. Thanks.

290

Yes.... It can do both together... Manual shows wiring.

1 Like
291

Will this driver work with my WiFi T6s ? Model# TH6320WF2003
Thanks,

292

No. It’s for the 500 and 700 series zwave T6 thermostats.

1 Like
293

Thanks for quick answer !

1 Like
294

I just installed 2 T6 Pro z-wave thermostats last night and switched to this driver earlier this morning. I see this in the logs for both thermostats:

image
image943×36 5.62 KB

Any ideas?

295

Looks like it isn't seeing a value for Temperature Scale. If you click on Save Preferences does the error go away?

1 Like
297

It looks like the save preferences may have fixed the error.

I will continue to monitor.

1 Like
298

Installed this Advanced T6 driver a few weeks ago with logging turned on but the only events showing up in Past Logs is the Battery Level !

What have I missed ?

299

Did you hit configure on the device page after you changed to it?

300

Yes. I did at time of install and have just hit Condigure again, but nothing other than Battery level is being logged. All app functions and automations are working fine.

Logging stopped when I switched from Generic Z-wave driver to the Advanced T6.

301

Definitely strange. I'm sure @thebearmay has an answer for this.

302

Might try hitting Save Preferences - should force a parameter update to the thermostat which normally will wake it up (sometimes takes 5-10 minutes after that to fully respond).

1 Like
303

Thank you, Tried that a few times without success, Have checked Past Logs and there's been no logging since I switched to the Advanced T6 drive back on 25 April.

I switched back to the Generic ZW+ driver and logging immediately starts up again ! Went back to the Advanced T6 and it stops (only Battery Level being reported).

Not sure what else I can do or why logging not working in my case ?

304

Try re pairing it again, that may do it... That said if it helps here is all my current settings in case you spot something.

image
image3378×1374 333 KB

image
image3457×1594 280 KB

image
image3477×1615 283 KB