No "feedback" from T6 Pro thermostat??

[gduprey]

Howdy,

In the process of upgrading my ZWave thermostats from older Honeywell zwave units to newer honeywell T6 Pro zwave units.  Much nicer looking unit and supports things like humidity and clock setting the older ones would not. 

One problem I'm seeing is that when in the admin console and issuing any command (switch to heat mode, turn fan on, change set point, etc), the admin UI doesn't reflect the change until I do an explicit poll via "Query".  I'm confirming via the REST interface this is not a phantom UI thing - the actual various state/status values for the thermostat device in the ISY does not change after a command.

The commands do work (again, a query confirms it was well as real world actions).  And I do get status messages when the thermostat kicks into heating or cooling action, so it is receiving data.  I've unpaired and re-paired the unit.  I actually have two of these and both act the same (trying to rule out a defect with one).  No obvious errors/problems in the device communication logs.

My old honeywell units (and even my old RCS units) all properly updated their ISY/console "state" after being sent a command.

Has anyone had experience with this thermostat or anything similar?  Is there some setting that causing the ISY to reflect the changes?  Or a known reason why it won't?

I'd really hate to have to change a ton of code to followup every command with a query.

Thanks!

Gerry

[wmcneil]

I have a Zwave T6 Pro that I installed a couple months ago. While there can be a few seconds lag between changing a value in the Admin Console and the displayed status correspondingly updating, I have not had the problem you describe. I am running 5.0.16C

Have you checked the event viewer, to see if the thermostat is communicating well with the ISY?

 

[gduprey]

Thanks for replying.  It's definitely communicating.  I can see, for example, when I switch the thermostat into Heat mode via the admin console or REST interface, even though the admin console shows no change (and no node update via the WebSockets subcription), the face of the thermostat changes.  Also, when the thermostat calls for heat, I get a status update and even the admin console switches and shows it saying "Heating".  So I'm transmitting OK and receiving events OK, just no status feedback from the ISY on commands.

That said, I was briefly on 5.0.16C last weekend and while that was a roiling disaster of biblical proportions, I did notice that it did seem to correctly reflect commands on the admin console.  So I'm guessing there is something slightly different about the tstat and the ISY 4.7.3 firmware doesn't quite handle it, but 5.x does (my REST based programs matched  what I saw in the admin UI, so I'm confident that its not just an admin console/UI problem).

I'm going to make another stab at 5.0.16C this weekend and hope like heck it takes.  If so, I suspect this will resolve this issue.

Gerry

[lilyoyo1]

46 minutes ago, gduprey said:

Thanks for replying.  It's definitely communicating.  I can see, for example, when I switch the thermostat into Heat mode via the admin console or REST interface, even though the admin console shows no change (and no node update via the WebSockets subcription), the face of the thermostat changes.  Also, when the thermostat calls for heat, I get a status update and even the admin console switches and shows it saying "Heating".  So I'm transmitting OK and receiving events OK, just no status feedback from the ISY on commands.

That said, I was briefly on 5.0.16C last weekend and while that was a roiling disaster of biblical proportions, I did notice that it did seem to correctly reflect commands on the admin console.  So I'm guessing there is something slightly different about the tstat and the ISY 4.7.3 firmware doesn't quite handle it, but 5.x does (my REST based programs matched  what I saw in the admin UI, so I'm confident that its not just an admin console/UI problem).

I'm going to make another stab at 5.0.16C this weekend and hope like heck it takes.  If so, I suspect this will resolve this issue.

Gerry

4.7.3 only has basic zwave control not multi channel which may be what your issue is.