GoControl Z-Wave Thermostat - Fan Initial State

Configuration
1

Is there a way to set the initial state to my z-wave GoControl thermostat so the fan doesn’t go to ‘on low’ upon reboot?

It seems 90% of the time when rebooting and loading the UI back up, the fan turns to ‘on low’ versus ‘auto’.

Is this as simple as setting the initial_state somehow?

My thermostat entities look like this:

image
image969×1134 75.4 KB

I really appreciate any help or direction on this as it’s been bothering me for a while. I can’t imagine this is a good thing for turning the fan on/off so much upon reboots when I’m testing things.

Thanks for any help/guidance on this!

2

Is that what’s happening? I kept finding my fan on low and have yet to track it down. It’s not just on restart (from config option), but actual reboot? Or is on go-control power cycle?

Guess I need to experiment a bit, it is annoying, as I’ve been trying to automate turning the fan on and off based on differences in temps around the house.

3

You could be correct. I guess the odd part is that sometimes it does it and other times does not. The only consistent part is that HA has been rebooted.

I found that after a reboot if I have it up on my computer it usually isn’t turning on but if I reload the site or had it on another tab open or if I load it up on my phone after the reboot that the fan ends up turning on… It’s really odd and frustrating.

I just turn it off right away but can’t figure out why it’s turning back on in the first place.

4

I don’t think I was right. I have not had time to investigate, but for unrelated reasons I had a few power cuts (to the thermostat, not to HA) and it did not reset. Yet Wednesday, for no apparent reason I could see, suddenly the fan turned on.

At this moment I’m not at all sure whether the state is changing from HA requesting it, or from the thermostat just randomly doing it.

Did you make any progress?

PS. The good news is it shows that state (it won’t show the fan is running, but it will show the mode setting). So I guess I could program around it to turn it back off. But I’d like to know where the gremlin arises.

5

So I think I can say that it is the thermostat that is doing it.

Today I noticed it has shifted again. I noticed without 15 minutes of it appearing, and the OZW log was there for a long time before that. I looked and the only event in there that said “fan” was the thermostat reporting the operation mode was fan-only.

I guess that’s not definitive, but i think if the HA software had changed it, it would have appeared in the log.

I’m just going to program around it, i.e. script to turn it back if it gets set.

6

Interesting. I haven’t made any head way with it. I don’t find it happening often enough to really annoy me but just bother me a bit.

It just seems to be a trend that it turns on after rebooting HA. If I reboot, it turns on probably 50% of the time and other times after I reboot and check the app on my phone it for some reason turns on then as well. Once I turn it off manually to ‘Auto’ though it never turns back on at all.

Still wish it could be 100% consistent and not turn on to begin with unless I turn it on myself.

7

I rather forgot about this, then yesterday noticed the fan had been running all day - no power failures, no HA reboots, nothing special. I think I will put a selection on my HA home page for “off”, “auto” and “on”. Off will just force it to off, on to on, and “auto” means I’ll let my node-red decide. I have not yet, but I want to drive the fan based on temperature differential in the house, e.g. if it’s cool enough to not run the AC, but some rooms are hot, run the fan a while. That’s next on my agenda I think. I finally found a override technique I liked to override my daily program.

Finding the hardest thing about HA and programming routines like this is not the programming but finding something that is actually usable in real life, not in front of the screen.

But it’s not helped by gremlins like this fan turning on. THinking I may have bought the wrong thermostat.

1 Like
8

Any solution to this? I have a T6 Honeywell ZWave and experiencing the same issue.

9

None from me. Interesting a different thermostat is doing it. It happened again about 3 days ago after weeks of not doing it. Maybe it’s buried somewhere inside HA.

10

This continues to be one of the few things I can’t get working right in Home Assistant.

It doesn’t do this on each restart, but it does it on many. I looked at the zwave log the last time it did so, and the first time that node (16) showed any fan data was this:

2020-03-26 21:34:12.770 Info, Node016, Value::Set - COMMAND_CLASS_THERMOSTAT_FAN_MODE - Fan Mode - 0 - 1 - On Low
2020-03-26 21:34:12.770 Detail, Node016, Queuing (Send) ThermostatFanModeCmd_Set (Node=16): 0x01, 0x0a, 0x00, 0x13, 0x10, 0x03, 0x44, 0x01, 0x01, 0x25, 0x19, 0x8d
2020-03-26 21:34:12.770 Detail, Node016, Queuing (Send) ThermostatFanModeCmd_Get (Node=16): 0x01, 0x09, 0x00, 0x13, 0x10, 0x02, 0x44, 0x02, 0x25, 0x1a, 0x8e
2020-03-26 21:34:13.015 Info, Node016, Value::Set - COMMAND_CLASS_THERMOSTAT_FAN_MODE - Fan Mode - 0 - 1 - On Low
2020-03-26 21:34:13.015 Detail, Node016, Queuing (Send) ThermostatFanModeCmd_Set (Node=16): 0x01, 0x0a, 0x00, 0x13, 0x10, 0x03, 0x44, 0x01, 0x01, 0x25, 0x1b, 0x8f
2020-03-26 21:34:13.015 Detail, Node016, Queuing (Send) ThermostatFanModeCmd_Get (Node=16): 0x01, 0x09, 0x00, 0x13, 0x10, 0x02, 0x44, 0x02, 0x25, 0x1c, 0x88

I really have not dealt much with zwave, but that sure looks to me like it’s something (presumably home assistant) telling the thermostat to go to fan mode. Maybe it’s just setting something definitional. The next place fan appears is:

2020-03-26 21:35:29.576 Info, Node016, Sending (Send) message (Callback ID=0x19, Expected Reply=0x13) - ThermostatFanModeCmd_Set (Node=16): 0x01, 0x0a, 0x00, 0x13, 0x10, 0x03, 0x44, 0x01, 0x01, 0x25, 0x19, 0x8d
2020-03-26 21:35:29.584 Detail, Node016,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-03-26 21:35:29.584 Detail, Node016,   ZW_SEND_DATA delivered to Z-Wave stack
2020-03-26 21:35:29.616 Detail, Node016,   Received: 0x01, 0x05, 0x00, 0x13, 0x19, 0x00, 0xf0
2020-03-26 21:35:29.616 Detail, Node016,   ZW_SEND_DATA Request with callback ID 0x19 received 
(expected 0x19)

Again, I do not know what that all means, but the end result of this (and a bazillion of other zwave conversations waking up) is that the fan goes from auto to on-low.

I see it on restarting HA. I do not see it always on restarting HA, but frequently.

Note I have zwave on a separate raspberry pi connected via USBIPD, so restarting HA does not restart the zwave network, only whatever querying the integration does.

Anyone else solved this? Is it just this particular thermostat?