[Junkers Cerapur Compact] Missing 0x22 telegram interpreter about ems-esp32

[proddy]

Thanks. Could you try creating custom entities for these to validate they work and then send us the screenshots so we can add the code?

https://emsesp.github.io/docs/Troubleshooting/#im-missing-certain-data-from-an-ems-device

[bszczepanik]

Sure! I will do my best. I need some time for reverse engineering. I will let you know here if I have some results.

[bszczepanik]

Any hint how to create custom entities with that kind of telegram?

[proddy]

The approach to adding entities to EMS-ESP is

• first determine what information you need. If you don't know, you probably don't need it
• Use the EMS device (boiler, thermostat, etc) to make the change manually whilst recording the telegrams
• Identify the telegram type and offset for the data point
• create a custom entity to validate
• report it to the dev team via GitHub

This is also documented in the wiki.

So, this 0x22 telegram - what is it and why do you need it?

[bszczepanik]

I understand, but here I see different problem. In 0x22 telegram I got two (or many) different variables.

In the telegrams below, I've got information that I want, comfort/eco mode for DHW. Variable type is BOOL. I see it in the last byte. (01 -> 00).

000+00:18:55.361 T 686: [emsesp] boiler(0x08) -B-> All(0x00), ?(0x22), data: 01 37 45 01 00 01
000+00:19:20.367 T 700: [emsesp] boiler(0x08) -B-> All(0x00), ?(0x22), data: 01 37 45 01 00 00

For reverese engineering tests, I changed other variable on the boiler (some delay time for DHW, integer variable) and I've got this telegrams with data on the last position (03 -> 01):

000+00:18:08.351 T 667: [emsesp] boiler(0x08) -B-> All(0x00), ?(0x22), data: 01 33 46 01 00 03
000+00:18:32.138 T 675: [emsesp] boiler(0x08) -B-> All(0x00), ?(0x22), data: 01 33 46 01 00 01

As I see in documentation, Message ID is inside a telegram, I think it is byte 2 (position 3). 0x45 in the first example, 0x46 in the second.

The point is, How can I define custiom entity, if I have the same telegram number for more than one data point.

[proddy]

you can create as many custom entities as you want for the same telegram. If you make them read only its harmless so you can just play around until you get the right results back.

For DHW comfort (hot/eco/intelligent etc) should already be reported (called wwComfort) in the 0x33 or 0xEA telegrams. Are you not seeing it?

[MichaelDvP]

I changed other variable on the boiler

If you specify what exactly you have changed with what values. maybe we can help.

Message ID is inside a telegram, I think it is byte 2

Device-id is 0x08 for boiler, Type-id is 0x22, offset starts with 0 for first byte, read the last byte is offset 5.

[bszczepanik]

Ok I found that comfort/eco mode of DHW for my boiler is already configured. But there is no reaction from the boiler to changes in parameters.

000+00:18:34.574 I 593: [command] Calling command 'boiler/wwactivated' (activated) with value on
000+00:18:34.660 N 594: [emsesp] Me(0x0B) -W-> boiler(0x08), UBAParameterWW(0x33), data: FF (offset 1)
000+00:18:34.727 N 595: [emsesp] boiler(0x08) -B-> All(0x00), UBAParameterWW(0x33), data: 08 00 30 00 00 00 00 02 4B 00 FF FF

If I change this manually on the boiler I see change:

000+00:21:13.104 N 612: [emsesp] boiler(0x08) -B-> All(0x00), UBAParameterWW(0x33), data: 08 FF 30 00 00 00 00 02 4B 00 FF FF

How can I turn on possibility to change this parameter?

[bszczepanik]

Maybe that problem is because the boiler wait for command from exact Device ID. I know that my boiler works with CR100 controller. I found a list of device IDs where this controller is:

Can I change here BUS ID for any custom? I would try 0x10 and 0x18

[proddy]

you could export the settings (emsesp_settings.json) modify "Settings" "ems_bus_id" with the new value to 16 (0x10), save, and import it back. It's a hack but see if it works.