Had not heard about it. Please try the latest version and if still broken file a report here:
My S30 died, and I might have to get an s40 (the dealer does not have any S30 in stock, and I need to get the heat working soon)
Is there any chance this s30 integration will work with the newer s40?
I do not know for sure.
Based on what I’ve ready about it, links below, it seems like an S30 with some enhancements, so I think it’s likely that the integration may just work. It’s also possible the integration needs some adjustments to work, and certainly will need changes to support the new remote temperature sensors the s40 supports. There’s also a chance we cannot make it work via the local connection. I will help as soon as you get it installed and even if it does just work, it’d be good to get some message logs to see what else it has.
Actually it looks like they have a newer version of S30, so it it should not be an issue.
I believe you will want to remove the old connection before creating the new connection. The unique IDs are tied to the controller serial number. If you don’t do this you’ll end up with two sets of entity ids, the new set will have _1 attached to them. This does mean you’ll lose any entity id remapping or friendly names you’ve set. Also remember to give the new S30 the same name as the old one. This is in the prefix of the current entity ids in your system now.
Thanks for the heads up. I’ll make sure to do that. It should be installed today, if everything goes well, so I’ll reconnect HA tonight.
I replaced an s30 just recently. I ended up in a similar situation to what Pete describes. The solution in my case was to restore a recent HA backup and remove the integration prior to configuration of the new s30. I used a new host IP address, but reused the friendly name resulting in all the thermostat cards repopulating without rework.