Change name device after update HACS repo

[alessandrobenevelli]

Hello, after the last update of the package under HACS the climate.bdr_thermostat entity (created by the previous installation) is no longer available and a new one with the name climate.bdr_circa has been created in its place. it's correct?

[jdschuitemaker]

Do you see an error if you go to Settings -> Devices & Services? For me the device is showing a red box around it that says that it failed to setup. See my issue here https://github.com/freitdav/BDRthermostatHA/issues/30

[alessandrobenevelli]

No error. the entity works correctly but I had to replace it in the various automations instead of the previous one.

[alessandrobenevelli]

After a restart of the home assistant this error is continuously logged

home-assistant | 2023-01-10 23:30:48.816 ERROR (MainThread) [custom_components.bdr_thermostat.climate] {'mode': 'schedule', 'fireplaceModeOn': False, 'roomTemperature': {'value': 21.0, 'unit': '°C', 'min': 0.0, 'max': 50.0}, 'roomTemperatureSetpoint': {'value': 19.0, 'unit': '°C', 'min': 5.0, 'max': 30.0, 'increment': 0.1}, 'nextSwitch': {'time': '05:30', 'dayOffset': 1, 'roomTemperatureSetpoint': {'value': 21.5, 'unit': '°C'}}, 'zoneActivity': 'heating', 'timeProgram': 2}

[jdschuitemaker]

I removed the integration and re-installed it to see if I could replicate what you are seeing. I now have problem my password and it seems it cannot login. I do have a pairing code from my thermostat.

Edit: I can login now, but I am still seeing another problem.

[merkens]

I have the same problem. The entitity name changed after update and now my logs are flooded with this error:

{'mode': 'schedule', 'fireplaceModeOn': False, 'roomTemperature': {'value': 18.0, 'unit': '°C', 'min': -25.0, 'max': 150.0}, 'roomTemperatureSetpoint': {'value': 16.0, 'unit': '°C', 'min': 0.0, 'max': 60.0, 'increment': 0.1}, 'nextSwitch': {'time': '06:00', 'dayOffset': 0, 'roomTemperatureSetpoint': {'value': 19.0, 'unit': '°C'}}, 'zoneActivity': 'heating', 'timeProgram': 1}

[robhuls]

I have the same problem as @merkens and @alessandrobenevelli