Junkers ISM 2 Module not recognized

[knopfsocke]

Is your feature request related to a problem? Please describe.
EMS-ESP32 discoverd two unknow devices. One of them has to be the ISM 2 I use to control the components of my solar system together with the FW 200 controller.

The ISM 2 module is connected as follows:

R1 = solar circuit pump for 1st collector array (SP)
R6 = valve return increase (DWU1)
NTC1 = collector temperature sensor 1st field (T1)
NTC2 = Bottom storage tank temperature sensor on the heating water side (solar storage tank T2)
NTC3 = center heating water-side cylinder temperature sensor (solar cylinder T3)
NTC6 = heating network return temperature sensor (T4)

"Devices": [
{
"type": "Boiler",
"name": "Junkers GBx72/Trendline/Cerapur/Greenstar Si/27i (DeviceID:0x08 ProductID:123, Version:06.02)",
"handlers": "0x10 0x11 0xC2 0x14 0x15 0x1C 0x18 0x19 0x1A 0x35 0x16 0x33 0x34 0x26 0x2A 0xD1 0xE3 0xE4 0xE5 0xE6 0xE9 0xEA"
},
{
"type": "Thermostat",
"name": "Junkers FW200 (DeviceID:0x10 ProductID:106, Version:12.14)",
"handlers": "0xA3 0x06 0xA2 0x12 0x16F 0x170 0x171 0x172 0x165 0x166 0x167 0x168"
},
{
"type": "Mixer",
"name": "Junkers IPM (DeviceID:0x20 ProductID:102, Version:20.08)",
"handlers": "0x10C 0x11E"
},
{
"type": "Mixer",
"name": "Junkers IPM (DeviceID:0x21 ProductID:102, Version:20.08)",
"handlers": "0x10C 0x11E"
},
{
"type": "Controller",
"name": "Controller (DeviceID:0x09, ProductID:152, Version:02.08)"
},
{
"type": "Unknown",
"name": "Junkers unknown (DeviceID:0x30 ProductID:103, Version:23.04)"
},
{
"type": "Unknown",
"name": "Junkers unknown (DeviceID:0x41 ProductID:100, Version:20.08)"
}
]
}

[MichaelDvP]

Please use log level all in system->system log and wait more than a minute, then download the log and attach it here (drag&drop).
If ISM2 is mostly compatible with ISM1 it's a simple add of product id 103 to database. But i think there are some extras in ISM2.
For Device-ID 0x41 i have no idea what it doing. Norbers list says powermodule for heatingcircuit hc10, but we have a 0x40 as rf temperature sensor, maybe something like that?

[knopfsocke]

Here the requested log file: log.txt

Nobert added in his latest version also 0x40 and 0x41 see here and here
so it looks like that 0x41 is the IPM2 Module and not 0x30?

[MichaelDvP]

Thanks, It s telegram 0x103 like ISM1 and in addition telegram 0x104. 0x104 has two temperatures (offset 0 and 2) and the valve state (offset 16/17).

The 0x41module is something with warm water, sending telegram 0x34 with setpoint (55°C) and measured temperature (54,9°C): Unknown(0x41) -> All(0x00), UBAMonitorWW(0x34), data: 37 02 25 02 25 00 00 00 00
and sometimes sending commands in 0x1E to the boiler Unknown(0x41) -> Boiler(0x08), ?(0x1E), data: 02 1D
The boiler broadcasts only that it has no warm water system: Boiler(0x08) -> All(0x00), UBAMonitorWW(0x34), data: 00 (offset 8)
@proddy Should we add a own class or register as generic type module? For a first test i think i'll add it to generic first and push to my github. I do not see a setting telegram for the warm water.

@knopfsocke Please check here, after update you'll need to refresh page in browser. Please post system info and http://ems-esp.local/api/solar and http://ems-esp.local/api/generic

[MichaelDvP]

Hmm, then better add the 0x41 to solar ISM2-Dhw? Can you make a log while changing the dhw-setpoint on the thermostat to fetch the command for this module?

[knopfsocke]

Thanks, you're fast 👍

I tested with Development Build v3.4.0b10

Requested API Results
system.txt
solar.txt
generic.txt

Screenshots with more visual results

The solar values looking very good 🥇

my observations
In the Screenshot you can see that the temperature value is a little different from the current external/internal temperature (54,7°C) and the requested set temperature (55°C). I activated the system log again and changed in the FW200 the warm water program settings the target temperature from 55°C to 59°C, that changed the DHW set temperature in the ems-esp ui. The external/internal temperature goes very slowly down. At a certain point, the heater and pump switches on to charge the hot water storage tank, and then the temperature rises again. Evereything is hopefully in the log file: log2.txt

I found another little thing in the new ui settings, i will create an extra github issue for that.

[proddy]

@proddy Should we add a own class or register as generic type module? For a first test i think i'll add it to generic first and push to my github. I do not see a setting telegram for the warm water

@MichaelDvP and new class would be nice, but agree test under generic first

[MichaelDvP]

I've added the missing ISM2 values.
We have SM100 dhw in solar class, because the SM100 does not have a own product-id for the dhw, only uses a different device-id. So i moved the ISM-dhw also to solar class, consitent with the SM100 dhw. In the log i've found the Seltemp-setting in telegram 0x35 (like boilers) and added the setting command.
@knopfsocke please update and check again (same link as before).

[knopfsocke]

Thank you @MichaelDvP , here are the new test results:

API Results
system.txt
solar.txt
generic.txt

Log Files

1. I tried to change the temperature from 55°C to 57°C in ems-esp web UI. Doesn't work: log-setDHWTemperature-UI.txt
2. I sucessfully changed the temperature again with FW200: log-setDHWTemperature-FW200.txt

UI Screenshot

[knopfsocke]

Update: With the latest build from @MichaelDvP, the MQTT Solar content changed. For example I don't get values for collectorTemp, tankBottomTemp, solarPump, ...

[MichaelDvP]

Oh, yes, the solar mqtt need a change to support multiple modules (like mixers). I'll update..
The change from webui i can not find in the log, there is nothing sent.

[knopfsocke]

The change from webui i can not find in the log, there is nothing sent.

Strange, I can try again. If you plan another update, i will wait for that.

[knopfsocke]

I found the problem, maybe :-)

In the settings the value is marked as read-only, but the pencil symbol in the dashboard is still visible. I can enter a new value, but no error message appeared in the UI. I suggest to gray out the symbol in the dashboard if the attribute is marked as read-only.

[proddy]

if an entity is forced to be read-only in the Customization screen then there will be no light blue Pencil icon next to the entity name in the Dashboard. If you're seeing something different then we have a bug somewhere