Update: Honeywell T6 Not Updating

Configuration
1

The previous discussion was helpful but I was all over the place with trouble shooting.

I narrowed it down to when the app is open on my iphone and I touch the physical panel and turn on the heat, the app updates correctly and it shows it’s heating.

If the app has been swiped closed and I turn the heat on at the physical panel and then open the app, it shows heating but also off as in the picture in the previous post.

That seems to be a Home Assistant issue with not communicating when it opens.

Anyone know how that can be addressed in Github?

2

I mean, it’s like you have to wait a couple of minutes for it to report in, that’s my guess…

3

What happens if you swipe down on the Companion App screen to reload it? Will it display correctly then?

In my case, when I move from wifi to cell it doesn’t always update right away and I have to swipe down to reload.

That’s why the logs are critical:

Problem: push button on T6 and doesn’t update on the iPhone
Ok: but there are a lot of steps in between:

  1. Is the T6 sending data to z-wave js? (z-wave js logs)
  2. Is z-wave js noting the state change? (z-wave js logs, zui logs, HA z-wave debug logs)
  3. Is z-wave and HA communicating? (zui logs and HA z-wave debug logs)
  4. Is HA reporting the state change: (debug logs again)
  5. Is HA web app showing the new state but not the Companion App?
1 Like
4

I think I have done this. I have to get this submitted to github.

5

As you have seen, github issues are not really a place to ask for general help debugging.

6

@AlCalzone told me to create a new conversation.

AlCalzone left a comment (zwave-js/zwave-js#5354)

Please create a new discussion here

7

That’s because you posted to an unrelated and closed issue. Where he told you to post is the discussions for z-wave js, so that has nothing to do with your iPhone companion app not updating unless you can show it’s happening in z-wave js.

If you saw in the z-wave js logs, for example, that z-wave js is consistently reporting an error when you push the T6 mode button then that might be a good place to ask. That’s why I was trying to get you to follow the logs so you know where to ask for more help.

I don’t know what’s happening in your situation. You showed me logs of the T6 and thus z-wave js updating HA:

2026-02-16 17:27:11.275 CNTRLR   [Node 010] [~] [Thermostat Mode] mode: 0 => 1                     [Endpoint 0]
2026-02-16 17:27:11.281 DEBUG (MainThread) [zwave_js_server] Received message:
WSMessage(type=<WSMsgType.TEXT: 1>, data='{"type":"event","event":{"source":"node","event":"value updated","nodeId":10,"args":{"commandClassName":"Thermostat Mode","commandClass":64,"endpoint":0,"property":"mode","newValue":1,"prevValue":0,"propertyName":"mode"}}}', extra='')

2026-02-16 17:27:11.282 DEBUG (MainThread) [homeassistant.components.zwave_js] [climate.t6_pro_z_wave_programmable_thermostat_with_smartstart] Value mode/None changed to: 1
2026-02-16 17:27:11.284 DEBUG (MainThread) [zwave_js_server.server] 2026-02-16 17:27:11.277:
2026-02-16 17:27:11.277 DRIVER « [Node 010] [REQ] [BridgeApplicationCommand]
                                 │ RSSI: -72 dBm
                                 └─[ThermostatModeCCReport]
                                     mode: Heat

If it isn’t consistantly doing that, and z-wave js is showing and error when it doesn’t (or not showing anything at all) then I’d be wondering if it was the T6 itself.

8

I don’t want to jinx myself but the updates to HA over the last two weeks, zwave js combined with zwave js ui and the firmware update to ZWA-2 seems to have solved my mode update issue.