Secure SRT321 thermostat no longer showing as a thermostat

I have been using a Secure SRT321 thermostat and boiler actuator and the thermostat stopped showing as a thermostat. I removed the device cleanly, factory reset it and added it back to see if it recognises it as a thermostat again, but no joy. The device reports temperature as a sensor, but HA no longer can add it as a thermostat.

The device was working fine for 6 months and then stopped showing as a thermostat, before deciding to remove it and re-add as a new device.

I’m stuck trying to get it to act as a remote climate control device now.

Any help really appreciated.

Some solutions are explained in the comments.

Here as well. https://github.com/home-assistant/home-assistant/issues/29844

Thanks, I’ll check it out

I checked and there is no specific fix for it, just some varying workarounds that don’t work. Making breaking changes to climate control devices in the winter seems like sloppy coding and quality control to me.

The proposed fix is confirmed working, so you must have missed something. One workaround is to modify the XML file, make sure HA is stopped before doing that. The other is to download the bug fix and apply it as as custom component. When doing that, you must copy the entire zwave directory.

Making breaking changes to climate control devices in the winter seems like sloppy coding and quality control to me.

Yes, it sucks, but the climate change was listed in the breaking changes of the release notes, so it’s always good to be wary if you are using a component with a breaking change. Unfortunately it broke things in unanticipated ways, that happens. :man_shrugging: You still have the choice of rolling back to 0.102.

Here are the instructions on how to install the bug fix. Did you try this already?

  1. Download the file https://github.com/oandrew/home-assistant/archive/zwave-thermostat-non-specific.zip
  2. Extract the homeassistant/components/zwave directory into your /config/custom_components directory. See instructions.
  3. Restart HA. Verify there is a climate component.

If you can confirm it works, I can submit a PR in place of the original author so the fix is in the next release or perhaps a patch.

Thanks, I’ll try this. I was editing the xml file, but I missed one thing in there. So i’m just seeing if the “specific=4” solves it.

Thank you for your help, if the specific=4 doesn’t work, I’ll try te bug fix.

Just tried it, it works. I updated to 0.103.6 and the climate device is still there.

Hi,
I realise this is a few months old but does anyone know whether this fix is going to be rolled out in an update? I’ve just installed HA for the first time (so much better than smartthings!!!) and this is my only problem. I’m sure I can work out fixing the xml or implementing the bug fix but as I don’t need to worry about it until we can go out again and the weather also gets colder I thought I’d check.

Hi Tom,

I made the changes recommend, but my thermostat as never worked correctly in Home Assistant since. It kind of works, but whenever I restart home assistant it turns on the heating, even if the temperature is above the set temperature. I kind of gave up with it.

Cheers, mine doesn’t even show the setpoint it just shows the current temperature… It’d be nice to fix before winter but definitely not a deal breaker.