Zen Thermostat driver broken in 2.3.4.x

Can you see if you can replicate the issue I mentioned above.

Start with Thermostat Mode = Off Fan Mode On

Turn Fan Mode from On to Auto and see if that also changes Themostat Mode from Off to Auto.

I'm seeing this from the driver page itself along with the dashboard mentioned above.

Please go through that process using the driver and post the live debug logs, be sure any apps that use the thermostat are paused...

Both Thermostat Mode Off and Fan Auto (off)

Then Turning Fan to On

Switch Fan back to Auto (off) this happens

1 Like

interesting, this isn't a driver issue, the device itself is doing this.
you can see the 4th line from last in the log where the thermostat is returning a value of 01 which is auto...
This is a device firmware bug.

That seems logical as it did the same thing when trying to use the Generic Zigbee Thermostat driver as well.

Thanks for the info, you would happen to know if there is a zen thermostat firmware update that can be pushed through the zigbee firware updater?

we don't have one, we'll upload it if they provide one to us.

2 Likes

Thread from ST forum - there was an update in 2019, at least, doesn't sound like it would address the issues discussed here.

Instructions to update (assuming you have access to a ST hub). I had these in some notes I'd saved, no idea if below works or not...

Aha! Discovered the instructions were from @dJOS - so we know he's already applied the update. His post here:

  1. Take your Zen off the wall, wake up the screen if it isnt already on.
  2. Press the network button 10 times to remove it from your HE Zigbee network - this is only done on the device, your HE device won't be removed unless you run that process on the HE (so dont).
  3. On your SmartThings app, select add a device and pick the Zen Thermostat
  4. Press the network button 5 times to add it to your SmartThings
  5. follow the instruction HERE to check your Device FW version
    a. Take your Zen off the mount
    b. Select "prefs"
    c. Scroll right to "info" and the first item when you scroll down is your current FW version.
  6. pull the batteries out of your Zen for a minute
  7. Wait for up to 10 mins and it should auto-update - you'll know it's doing this as a symbol will start randomly flashing around the screen. It's done when the display goes back to showing "prefs".
  8. make sure the Zen is responding in the ST app then power down your ST HUB
  9. Press the network button 10 times to remove it from SmartThings
  10. On your Hubitat Hub, go to discover Zigbee new device and start the discovery process
  11. Press the network button 5 times to re-add it to your Hubitat - you'll see it say something along the lines of "found an existing device". This means you succeeded!
3 Likes

Thanks for that, I don't have access to smartthings.

I had to drag out my old ST v2 hub to update mine last year - AFAIK there havent been any updates since.

2nd hand v2 Hubs are usually cheap on FleaBay.

I can't remember - any regrets about the FW update?

Nope, it was a significant improvement.

1 Like

Appreciate the tip but I don't throw good money after bad products, I've been working around this issue for awhile now with using delay, refresh, and off commands in my node red flows to compensate for the issue. It's the only issue I've noticed with the thermostat and it's not that big of an issue needing an immediate hassle free solution.

I've contacted the company and asked them for a firmware update for this issue and to send it to Hubitat so they can push the update to their users via zigbee updater. If they respond great if not, no big deal for me.

I’m wondering if my issues are caused by Rule Machine - I’m seeing massive lag in thermostat related rules.

Only issue is I can’t mail it down to anything specific. I made sure my triggers between rules can’t overlap and that made a small improvement.

It’s just weird tho as I hasn’t touched these rules in over a year before moving them from legacy to RM 5.1.

@waynespringer79 - I also just emailed them to see about getting the firmware. I have a decommissioned ST hub, so I’ll take that route if I need to. I actually haven’t had any issues with my Zen, but just in case. And I just ordered another one because I’ve been having issues with one of my NoControl thermostats that I’ve had since my ST days. I’ve had my Zen for over a year now, and it’s been solid with the exception of it showing a “pending heat” status instead of “heating.”

@dJOS - When you have a minute, do you mind sharing your Zen device info? Below is mine. I’m wondering if this indicates the Zigbee version. Also, does the new firmware solve the “pending heat” issue?

Sure, here you go:

Btw, with the most recent 2 updates, this issue has gone away for me.

Nope, it's always "pending heat" for my downstairs ducted gas system and Zen support has been less than helpful - they blame Hubitat's driver.

I wonder if anyone has been able to successfully update recently. I bought another 2 Zen thermostats to replace some older Z-wave devices that were giving me problems. They came with older firmware. I've been trying to get them to update using my SmartThings hub to no avail. Pulled the batteries a few times over the course of a few days with them on SmartTh!ngs. Even clicked the update firmware button in the device information. But nothing.

Mine updated from the ST hub, but IIRC they had to sit on the hub for a few days after I hit the update FW option. I think it took maybe ~ 1-2 days.

1 Like

Thanks. I commented too soon. Just checked again, and after about 2 days, it finally updated. On to the next one.

2 Likes

+1 for a firmware update without ST. I got a Zen off Amazon about 2 weeks ago and it came with FW v. 2.31.

My issue is that the device doesn't refresh on its own regularly so the hub never knows what it is doing. I wrote an RM to refresh every 2 minutes so a ceiling fan can work with it together, but this seems clunky to me. The code necessitates a while/repeat loop and it is all hub-side processing.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.