After Update from 3.6.2 to 3.6.3 some entities are not available in HA any more

[DoubleYou2]

PROBLEM DESCRIPTION

RC310 / Buderus GB125 / EMS-ESP V3.6.3 and HA latest version:

After updating from V3.6.2 (or from 3.6.3-dev6c) some entities are not available in home assistant (HA) any more.
Some entities are incomplete (regarding attributes) and unavailable also.

Here is an example for climate.thermostat_hc1.

This screenshot shows state of entity climate.thermostat_hc1 with V3.6.3-dev6c (similar to V3.6.2):

This screenshot shows state of entity climate.thermostat_hc1 with V3.6.3 :

From my (user) perspective this issue is not caused by home assistant. Replacing firmware 3.6.3 (released version) with 3.6.2 or 3.6.3-dev6c immediately solves this issue. Regarding release notes for V3.6.3 I don't think this issue has to do with breaking changes, or does it?

[proddy]

Do you see the values in the EMS-ESP web dashboard? Are there errors in the log of EMS-ESP or HA? Do they come back after a restart?

[MichaelDvP]

Same issue as #1440, i've made a fix, but no feedback yet.

[DoubleYou2]

Yes, I see all values in the EMS-ESP dashboard.
Yes, due to missing entities and attributes, HA log is full of error-messages (because my scripts try to access these attributes).
Restart of HA or EMS-ESP do not change situation.

Is there already a fix for test available?

[proddy]

I'm still thinking of what could have caused this. Do you see anything interesting in HA->devices->mqtt ?

And no fix yet as I'm still on a bus on my way home. We're not google !

[DoubleYou2]

Thanks for your support.
In HA-> devices -> MQTT there is a red exclamation mark regarding climate.thermostat_hc1 stating "unavailable", but nothing really special.

My question regarding an available fix is because of MichaelDvP comment on a similar issue he is working on...

[MichaelDvP]

'm still thinking of what could have caused this.

The hc->mode is not set because in this line the if is wrong

EMS-ESP32/src/devices/thermostat.cpp

Line 1030 in ec85a7e

if (telegram->read_value(mode, 0)) {

A second bug is that i have missed the to adapt the setting here:

EMS-ESP32/src/devices/thermostat.cpp

Line 2601 in ec85a7e

hc->mode = set_mode_value ? 1 : 0;

The fix is MichaelDvP@aed4596
and now confirmed working in #1440.

@DoubleYou2 Please also test https://github.com/MichaelDvP/EMS-ESP32/releases/tag/latest, i think this wll fix the bug.

[proddy]

@DoubleYou2 if you can try that build and let us know - then I'll do a patch

[DoubleYou2]

OK. I checked the new build v3.6.4.-dev_0 and my reported problem is fixed!
I guess there will be a patch based on v3.6.3 ?

Thanks for your incredible fast support.

Another question which has nothing to do with update to v3.6.3:
There are other entities which are not available (which I don't use, so I don't care) even in earlier versions like 3.6.2 (?):

• sensor.ems_espheizung_shower_duration
• sensor.boiler_dhw_energy_dhw
• sensor.thermostat_hc1_heatpump_operating_state
• sensor.ems_esp_shower_duration
• sensor.ems_esp_shower_timestamp

Are these entities not supported any more?

[proddy]

thanks, we'll work on the patch.

Regarding those other entities, the shower ones are still there but will only show in HA after the first shower. hpoperatingstate is still there so maybe it's waiting on a value to come in. dhw_energy_dhw was renamed because of the duplicate dwh (there was a GH issue for this). Not sure what it's renamed to now, perhaps total energy warm supplied. In general it's best to look at the shortnames and not the full translated names which helps us locate the actual entity. And another good practice is when upgrading versions delete any old HA dashboards/cards and re-add them directly from HA->Devices&Service->MQTT

[DoubleYou2]

... ok. Thanks...