Your goal here should be getting all the entity_ids to have the same starting portion. Then when they are all the same, rename the device and regenerate. This should work as long as the integration doesn’t do anything stupid with the entity name
1 Like
Sure, I agree…the main starting portion should be main_floor, which is why I am a little confused why the main_foor swap to main_floor does not also adjust the main_foor_wt_env, since there is a shared common prefix of main_foor. Ideally I would not remove the _wt_env portion (it’s not even something I added, it is there by default), as that is a specific indicator in this case of weather/environment…all of those sensors are for things that are external to the house.
Sounds like the integration is doing funky things with the entity name then
1 Like
Are those entities belonging to different Devices ? , so it’s not a matter of a specific Device which behave “spooky”
1 Like
That’s what I am thinking, unfortunately.
No, they all belong to 1 device. The integration itself creates 4 devices per thermostat, and those 4 devices have, respectively, 23, 0, 1, and 6 entities. Everything shown above has been from the 1 device that owns 23 entities and are separate from the other 3 devices and its entities.
1 thermostat (Device 1), which the integrations create 4 Devices for, sounds advanced/complicated to me, and did you Rested/Rebooted this (Device 1) ?
1 Like
- Thermostat
- Air Handler
- Heat Pump
- Climate Zone (this is a single zone unit, but if I had multiple zones then presumably it would have a device per zone)
And yes, I rebooted the device directly as well
hmmmm, yeah it looks like a “complicated integration”
- If using a local connection and you have more than one S30 in your local network, please use a different app_id for each instance (e.g. homeassistant_1, homeassistant_2). If using a Cloud Connection DO NOT change the default app_id.
- If you are running more than 1 Home Assistant communicating to cloud or locally - you MUST use a different app_id for each instance - Detailed Configuration
Set the Name for the system. This name will be appended as the prefix for all the entities that get created, so you want something descriptive using only alphanumeric character; but not too long as it’ll be in all the entity names. To set this, go into the panel, select settings and look for the Name field.
1 Like
Yeah, I already checked that one and confirmed it is appropriately named 
And this Thermostat is a WIFI device, which is also Named “something” ?
In Your Router and mobile APP
" Most, will use the Local Connection. Local connections are faster and more reliable than Cloud Connections. To have this work requires that the S30 has a static IP address (DHCP lease), consult your router documentation for how to configure this. "
Anyways, im done reading , Turn everything off, clean out HA ( well, can’t bc of some obscure Retain-policy ), Tomorrow or the weekend, start your Climate-Unit again start from fresh, Name it add it to your internet/app (Cloud-Connected) i assume you had initially then install the integration again, Local or Cloud
Or just start renaming the entities 1 by 1 
1 Like
I’ve been wondering why regenerating skips the disabled entities. Is there something that prohibits renaming entities marked disabled?
It’s just that you end up with inconstantly named entities if you later enable the entities.
Im more concerned about “Disabled” Devices/Entities from a “Native Integration” which one can’t enable, Nor Delete, i’ve been Remodeling my HA lately (switching integrations etc), and have bunch of devices/entities (in disabled state), which i can’t enable, nor delete/edit (because i’ve deleted the integrations) I have soon more disabled devices/entities than Enabled now 
