Major flaw in latest thermostat firmware 1.2.5 - It takes 2-3+ attempts to make any changes

Home
, ,
1

When selecting ANY action (on, off, temperature adjustment, heat, cool, auto, ANYTHING) the very first request does not hold, and the system is kicked back to its previous state.

For example. If the system is off, and I turn the heat on, it will revert back to off…which is causing my compressor to briefly kick on.

OR

If the heat is on 73, and I increase it to 74, it will display 74 with the orange screen for about two seconds, and then immediately kick back to 73 and shut the system off - again causing my compressor to short cycle. Same for turning the system off or on. Or cooling temperature adjustments. If I make any change in the app, that change is displayed for literally one second, and then it kicks back to whatever the previous state was. This is short cycling my system!!!

This is a massive bug and needs to be addressed IMMEDIATELY. I have had these tstats for over a year, and this has never happened. Sometimes in the past if you didn’t stay on the screen long enough after making a change, it wouldn’t accept it (mainly with temp adjustments) but this is an entirely different issue.

Every single action is like this, it does not matter what I am asking the thermostat to do - it will accept the change for about a second or two, and then kick back to its previous state.

The problem is that my HVAC system is accepting the first request, but then when the app kicks that request out, my system immediately shuts off (or on) as a result. I have to wait on the screen, and make the appropriate change again after a few seconds. This is causing my system to short cycle.

Thermostats went from the recent alpha firmware to 1.2.5

iOS app version 2.36.0.14

See attached videos if this doesn’t make sense:



2

I will verify but seem to recall the same issue. Please submit a log so Wyze can look into this. I will try to reproduce and submit a log as well.

3

On the previous firmware versions, you simply had to wait on the screen after making a temperature change, otherwise it wouldn’t register. It doesn’t matter what you do now though, I am sometimes having to make the same request three times in a row for it to stick. Really strange that this hasn’t been reported at all. This isn’t just once in a while, it’s been every single time since the new firmware rolled out.

4

I to am having this same issue. read this here and checked. my Tstat is doing the exact same thing. on firmware version 1.2.5

6

Can you all please submit logs of this so Wyze can correct it.

@WyzeJasonJ , just want you to be aware of the issue with 1.2.5. I will submit a log once I have time to reproduce it.

8

I’ve had this same issue for many revisions of firmware. However, the difference is mine is random in sometimes it works fine and maybe 25% of the time does this. When it does do it, it doesn’t always work on the 2nd try. I’ve also just let it sit and sometimes it will actually go to the change that I made but not always. Finally, mine won’t actually turn the HVAC on until the change sticks. I’m currently running 1.2.1. Next time it does it I will submit log.

9

I just want to make sure we are talking about the same issue. I know that typically, when you first initiate a temp change, it will not ‘stick’ unless you stay on that screen for a few seconds.

The issue I am seeing now after this latest fw update, is that even when turning the thermostat ON or OFF, it will literally revert back to its previous state first. Forcing me to tap the button again a second, or third time.

Same happens when switching from heat to cool, or tapping any of the buttons. This happens from Mac OSX, the iPhone, iPad, every device. Whatever button I tap on, it will revert back to whatever state it was in previously.

I’ve attached another video example. Just now when taking this video, I literally had to request the temperature change THREE times. Meanwhile, my HVAC kicked on during the first attempt. This is insane:

10

Yep, same issue here except my HVAC doesn’t kick on until the change “sticks” and it doesn’t have this behavior all the time and seems to be random when it decides to do it. Again, I’m still running 1.2.1. I have 2 thermostats for 2 zones and they both have this behavior. I was able to get one to do it last night so I did submit a log.

11

Happened to me too. And when you circle to the temperature and click on the top blank space above the number it resets too.

12

Today it seems like I need to make the selection at least three times. Trying to change the temperature is such a task now. Or doing ANYTHING! This is INSANE. Wyze, PLEASE!!! Fix this !!!

14

Agree, major bug in 1.25 latest fw. AC is kicking in every few minutes. This is bad for compressor. I deleted and reset the device multiple times. Same results. I deleted the device from android app. Now is working normally in manual mode. Also when online the temperature was out of wack. VERY BAD FIRMWARE. WYZE PLEASE FIX THIS.

15

Done! Thanks !

16

Same here.

Since this firmware, my furnace fan was switching back and forth frequently until eventually it locked it into a permanent on state. The temperature would randomly be 57F or some other value instead of honoring schedule and temperature preferences too when I’d go into the app. I also experienced the delay/retry issues of values not being set.

This firmware is breaking homes whether it be the direct hardware or causing homes that are unattended to dip below or above intended temperatures (think freezing water lines or to a more extreme level - loss of life). This needs to be fixed ASAP. This isn’t a vote to fix it issue. At the minimum, an advisory needs to be sent out for liability purposes. I don’t expect Wyze to be covering any repair bills related, but I’m sure there will be some that do.

17

Last night the thermostat start kicking in the AC every 5 min or so. Temperature reading was out of wack. I believe that since WYSE sensor introduction and firmware updates the T-Stat thinks that he has sensors all around even if you do not have any. The code in FW is somehow out of wack with temperature reading and sensor averaging etc. I believe people are unaware about this and they will have damaged AC/Furnace soon.

WYSE PLEASE REVERT BACK TO 1.2.1 AND LET PEOPLE HAVE OPTION FOR A FW WITH OR WITHOUT SENSORS.

I REMOVED THE WYSE THERMOSTAT AND DUG OUT MY OLD DUMB THERMOSTAT. NOW IS BACK TO NORMAL

18

The newest beta app seams to have fixed this issue for me. Will keep testing to see longterm. But so far everytime ive changed the temp it has worked like its supposed to.

19

How about the skewed temperature reading being out of whack and short heating/cooling cycles? This is a big concern. Other people experience T-stat overheating and messing up the temperature reading. I still believe that the sensor introduction messed up the thermostat.

20

Same issue here

21

I have not experienced the short cycling or the unit overheating. Yet. But time will tell if it starts to act up. But latest beta app seams to have fixed the ability to chang temp setting issue.

Also I only have stand alone T-stat no extra room sensors. so that may change how mine is acting.

23

Same. I stopped experiencing it since I gave up hope for a timely update and switched to a different thermostat. We already hit below freezing here and haven’t had much in the form of official messaging so it should be no surprise.

24

Still the temperature showing is out of whack. I do temperature correction and still is randomly thinks is different. Is cycling the AC at 2-5 minutes interval. This is crazy. It worked very well until 1.2.5 The T-stat is at 90F temperature (housing). It seems to hot for a T-stat to function properly.
I am in balanced mode. Wyze should tell me (us) what is the best setup so the AC so it will not cycle so often. I give this another week before I throw it in the garbage. Very angry and pissed of customer after I believed in Wyze and stupid me got 3 T-Stats