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.