Vivint Thermostat seems to be setting itself?

🛎️ Get Help
21

I'm sure you checked this, but are all thermostats on the same firmware version?

Are you setting the temperature on the thermostat itself, or setting it through Hubitat?

I was going to try tonight swapping with new batteries and then by setting both thermostats physically and monitor for any issues. Sounds like you have a more foolproof method with the zwave sniffer.

I almost never set the temperature at the thermostat itself, I use a tablet/phone/alexa.

22

Haven't checked. I should though.

I've done both. Seemed to happen either way, but I'll try to do it both ways again to be sure.

1 Like
23

I read that firmware is updated automatically by the smart panel, if they are different, I don't know if we could get a firmware to update manually.

My hope is the 2 that you have that are not having the issue are on a newer firmware.

24

Yeah, that could be a pickle if it needs a firmware update. :confused:

If that happens I may need to just build my own thermostats, a la:

2 Likes
25

@JasonJoel Is there anyway we can modify the driver to tell the difference between physically changing the setpoint vs setting it via Hubitat? I know in the logs they both show the same currently.

26

Yes, I could set a state when the set happens from the thermostat, and reset it when the report comes in. That is the same way we handle physical vs digital presses on switches/dimmers. I'll do that if I get a minute.

I can tell you for sure that the "rogue" changes are not going through the normal driver "set" code though - as I started logging that on day 1. That code isn't triggered when the setpoint changes randomly so the "rogue" changes would always show as being from the thermostat.

EDIT: My dev thermostat just changed SP again. Hopefully I'll have the sniffer logs when I get home (assuming the PC didn't go to sleep or something stupid). I can also confirm that it changed to the last SP I physically set the thermostat to.

27

Fingers crossed we get something. Thanks for all your work on this @JasonJoel

28

OK.

  • The change didn't happen from an external command (aka from the hub).
  • There were no obvious zwave issues (dropouts, CRC errors, retransmits, etc) at the time the thermostat changed setpoint.
  • All 5 of my thermostats are the same versions:
    • V0.34
    • Z11.27

So still a bit of a mystery, but appears to be a device issue. :frowning:

1 Like
29
  • Version 1.9 - 09/22/2020 Added digital/physical type to setpoint change events
1 Like
30

Well what the hell. Lol

I checked and mine are the same versions.

31

My downstairs thermostat has been changing on a daily basis and it's starting to get a bit frustrating, trying to think of a way that I can only approve it changing set points but not coming up with any ideas...

I did forget to swap out the batteries so I did that and bent the connectors a bit more.

32

Just an update since my last post, changing the batteries and bending the contacts, it hasn't happened once.

1 Like
33

I have about a dozen of these thermostats that I bought on ebay, and I can reliably get them to "reset" themselves:

  1. Set a set-point manually on the thermostat (eg. Heat @ 70)
  2. Set a set-point through Z-Wave (eg. Heat @ 69)

After about a day the thermostat will reset to what you manually set (Heat @ 70). This happens with all combinations of power (C-Wire only, C-Wire + battery, battery only).

I ended up buying a Vivint control panel to check if the thermostats behave the same way when you set the temperature through the Vivint hub, and the good news is that they don't. When the Vivint hub sets the temperature, the temperature stays set.... (and it's not something that the hub constantly sets because I've unplugged and powered off the hub after setting the thermostat temperature).

I've run a zniffer with the Vivint hub (uploaded here: https://filebin.net/tks6xa7r94iy7hjb/vivint.zlf?t=pgfu4wlz) but it doesn't seem to be doing anything too special...

Will try to replicate exactly what the hub does, and see how the thermostat behaves...

2 Likes
34

Awesome @srs. I did start to see the thermostats change back again after some time, if I happened to set the thermostat lower one day. I've noticed that if I take the thermostat off the wall and take out the batteries - effectively power cycling the device, then I don't have issues. So it seems like they almost store a set point in their memory and a Z-wave command only temporarily changes the setpoint.

Looking forward to what if anything you can find from the logging.

1 Like