-I am seeing very strange behavior with the Honeywell T-6 Pro (TH6320ZW2007/U Z) z-wave. Here is my situation. My church is heated and cooled by residential HVAC systems so I purchased 9 of the T-6’s to replace the existing thermostats so they can be controlled from the office, and we can set the schedule for each day of the week based on normal activities. I upgraded my home system to the C-8 hardware and did a factory reset on my old C-7 and installed it at the church. So far so good. However, there many odd things happening. For example, most of the thermostats are set to auto heat/cool mode, but one will not set to auto even though the device window says it is available. The debug log says the “auto mode is not supported buy this thermostat” Notice the miss-spelling but the others all using the same device driver are in auto mode no problem. There are other documented times when a T-6 does not follow the schedule that is assigned, or if I have two T-6’s using the same scheduler instance only one of them get the change of temperature from the scheduler. Changes made using the dashboard don’t show up on the T-6. There is also a documented case where the device and dashboard showed cooling when the unit was definitely heating. The good news is that the T-6’s do not have any issues controlling the units, but getting the Hubitat control is proving difficult.
Things I have tried: Rebooting hub, power cycling the hub, changing from Honeywell T-6 Pro Z-Wave Thermostat driver to Generic Z-Wave Thermostat driver, restarting the T-6 by removing the power and battery, the hub firmware is up-to-date, and I have run the Z-Ware repair on the hub.
The hub is version C-7 running version 2.4.0.151 and I think the Z-Wave version is up-to-date, the check shows “VersionReport(zWaveLibraryType:7, zWaveProtocolVersion:7, zWaveProtocolSubVersion:18, firmware0Version:7, firmware0SubVersion:18, hardwareVersion:1, firmwareTargets:1, targetVersions:[[target:1, version:7, subVersion:18]])”
Set isu 300 to auto on the offending thermostat... That should do ya
Just curious, are you using this driver?
I have three T6s on this driver and I have no issues with them.
No, I have used the driver that is included, I have not tried this custom driver. I will look into it.
Update on this issue. rlithgow1 you were right I missed setting ISU 300 on this thermostat, and I have moved all of the drivers to the Advanced driver suggested by user2574. But I still have some issues with that driver. I am seeing some errors and some not all of the thermostats don’t respond to the scheduler. The example below the schedule called for the thermostat to be set to 68 but it was still set to 65 minutes after the scheduled time. This was the scheduler screen shot. I did use the scheduler to manually set the temp after taking the shot and the thermostat did respond to the temperature manual change.
2025-03-02 08:13:05.990 AM info Heating Setpoint for Pin Oak/Cottonwood/Prairie: 68.0 from Manual
app:62025-03-02 08:11:33.495 AM info Heating Setpoint for Pin Oak/Cottonwood/Prairie: 70.0 from Manual
app:62025-03-02 07:55:01.207 AM info Thermostat Fan Mode auto from Time Schedule
app:62025-03-02 07:55:00.692 AM info Cooling Setpoint 75.0 from Time Schedule
app:62025-03-02 07:55:00.651 AM info Heating Setpoint 68.0 from Time Schedule
app:62025-03-02 07:55:00.617 AM info Thermostat Mode auto from Time Schedule
dev:62025-03-02 07:57:13.211 AM debug parse:zw device: 32, command: 8106, payload: 27 39 , isMulticast: false
dev:62025-03-02 07:57:12.502 AM debug parse:zw device: 32, command: 7006, payload: 01 01 00 , isMulticast: false
dev:62025-03-02 07:57:10.283 AM debug Got thermostat setpoint report: ThermostatSetpointReport(value:[3, 32])
dev:62025-03-02 07:57:10.280 AM debug parse:zw device: 32, command: 4303, payload: 02 2A 03 20 , isMulticast: false
dev:62025-03-02 07:57:10.166 AM debug Got thermostat setpoint report: ThermostatSetpointReport(value:[2, 138])
dev:62025-03-02 07:57:10.163 AM debug parse:zw device: 32, command: 4303, payload: 01 2A 02 8A , isMulticast: false
dev:62025-03-02 07:57:06.203 AM debug Translated thermostat mode: heat
dev:62025-03-02 07:57:06.202 AM debug Got thermostat mode report: ThermostatModeReport(mode:1)
dev:62025-03-02 07:57:06.200 AM debug parse:zw device: 32, command: 4003, payload: 01 , isMulticast: false
dev:62025-03-02 07:57:05.356 AM debug Translated thermostat mode: heat
dev:62025-03-02 07:57:05.355 AM debug Got thermostat mode report: ThermostatModeReport(mode:1)
dev:62025-03-02 07:57:05.353 AM debug parse:zw device: 32, command: 4003, payload: 01 , isMulticast: false
dev:62025-03-02 07:57:04.502 AM debug Translated fan state: idle
dev:62025-03-02 07:57:04.500 AM debug Got thermostat fan state report: ThermostatFanStateReport(fanOperatingState:0)
dev:62025-03-02 07:57:04.498 AM debug parse:zw device: 32, command: 4503, payload: 00 , isMulticast: false
dev:62025-03-02 07:57:03.648 AM debug Translated fan state: idle
dev:62025-03-02 07:57:03.647 AM debug Got thermostat fan state report: ThermostatFanStateReport(fanOperatingState:0)
dev:62025-03-02 07:57:03.645 AM debug parse:zw device: 32, command: 4503, payload: 00 , isMulticast: false
dev:62025-03-02 07:57:02.081 AM debug Translated fan mode: auto
dev:62025-03-02 07:57:02.080 AM debug Got thermostat fan mode report: ThermostatFanModeReport()
dev:62025-03-02 07:57:02.078 AM debug parse:zw device: 32, command: 4403, payload: 00 , isMulticast: false
dev:62025-03-02 07:57:01.383 AM error
java.lang.NullPointerException: Cannot invoke method toInteger() on null object on line 593 (method parse)
dev:62025-03-02 07:57:01.377 AM debug got temp: 65.0
dev:62025-03-02 07:57:01.375 AM debug parse:zw device: 32, command: 3105, payload: 01 2A 02 8A , isMulticast: false
dev:62025-03-02 07:57:01.300 AM debug got humidity: 28.0
dev:62025-03-02 07:57:01.298 AM debug parse:zw device: 32, command: 3105, payload: 05 22 01 18 , isMulticast: false
dev:62025-03-02 07:57:00.763 AM error
java.lang.NullPointerException: Cannot invoke method toInteger() on null object on line 593 (method parse)
dev:62025-03-02 07:57:00.758 AM debug got temp: 65.0
dev:62025-03-02 07:57:00.756 AM debug parse:zw device: 32, command: 3105, payload: 01 2A 02 8A , isMulticast: false
dev:62025-03-02 07:57:00.745 AM debug got humidity: 28.0
dev:62025-03-02 07:57:00.743 AM debug parse:zw device: 32, command: 3105, payload: 05 22 01 18 , isMulticast: false
dev:62025-03-02 07:57:00.627 AM error
java.lang.NullPointerException: Cannot invoke method toInteger() on null object on line 593 (method parse)
dev:62025-03-02 07:57:00.589 AM debug got temp: 18.5
dev:62025-03-02 07:57:00.586 AM debug parse:zw device: 32, command: 3105, payload: 01 22 00 B9 , isMulticast: false
dev:62025-03-02 07:57:00.122 AM info
Pin Oak/Cottonwood/Prairie battery is 95%
2025-03-02 07:57:00.120 AM debug got battery report: 95
dev:62025-03-02 07:57:00.118 AM debug parse:zw device: 32, command: 8003, payload: 5F , isMulticast: false
dev:62025-03-02 07:55:24.223 AM debug skip:ClockReport(hour:7, minute:55, weekday:1)
dev:62025-03-02 07:55:24.221 AM debug parse:zw device: 32, command: 8106, payload: 27 37 , isMulticast: false
dev:62025-03-02 07:55:24.125 AM debug Translated presence: present
dev:62025-03-02 07:55:24.124 AM debug Got presence report: BasicReport(value:255, targetValue:255, duration:0)
dev:62025-03-02 07:55:24.122 AM debug parse:zw device: 32, command: 2003, payload: FF FF 00 , isMulticast: false
dev:62025-03-02 07:55:01.199 AM debug setting zwave thermostat fan mode 0
dev:62025-03-02 07:55:01.198 AM debug setThermostatFanMode(auto)
dev:62025-03-02 07:55:00.658 AM debug setCoolingSetpoint(75.0) called
dev:62025-03-02 07:55:00.625 AM debug setHeatingSetpoint(68.0) called
dev:62025-03-02 07:55:00.108 AM debug setting zwave thermostat mode 3
dev:62025-03-02 07:55:00.107 AM debug setThermostatMode(auto)
dev:62025-03-02 07:54:44.557 AM debug Translated fan mode: auto
Make sure you click configure on the new driver on each device. That said @thebearmay handles the driver, you might wanna drop a message in the thread. I think @bravenel handles the schedular
