Michael Schäfer

@MichaelDvP should be same calculation like for rc100h when the product I'd is the same? #590 I have appended a few minutes ago new debug values.

Jep thats why I am wondering why there is no value for those attributes. Strange is that there is no ProductID present from the device. (The count of bus reads...

Like I wrote before it related to the missing tx cable (just connected the rx before...) which fixed the whole connection. After a complete restart of the heating system /...

A missed your first line in the comment. Used the current stable one to catch the changes. Got the first batches with small changes in the values. On what part...

@MichaelDvP with your development build I get the following error `Problem fetching device data (offset is outside the bounds of the DataView)` and the available attributes of the devices are...

That was the problem ;-) Here a bunch of value changes. The concrete value has been read from the display with the corresponding message for the value below. - Hum/dew...

Hm maybe with your experience you can identify something here. It is only possible to - set the heatingcircuit by number to which the module is bound to (probably the...

Just flashed with the dev-build and the device is correctly identified but currently without values. It is also not appearing under customization.  I have watched the related telegrams and...

Your GHA have been skipped so no release available. http://ems-esp.local/api/thermostat ``` { "datetime": "10.08.2022 11:50", "floordry": "off", "dampedoutdoortemp": 20.8, "floordrytemp": 0, "building": "medium", "minexttemp": -14, "damping": "ON", "wwmode": "own_prog", "wwcircmode":...

My fault... Now it seems to be a little bit better. One value present  ``` { "type": "Thermostat", "name": "RC100H", "device id": "0x38", "product id": 200, "version": "40.04", "entities":...