Thanks @kreutzer_peter for your answer so far
Maybe I was not super clear in my post earlier, in the meantime I have search around how to solve my problem and I have found the exact location of my concern inside the addon-on code :
here you can read that Modbus Register (or let’s say Register ranges) are hardcoded
for example from 500 to 536 and from 3500 to 3516
poller.registerPollTask(500, 36, ModbusReadFunctionCode.READ_INPUT_REGISTERS);
systemInformationPoller = poller;
...
poller.registerPollTask(3500, 16, ModbusReadFunctionCode.READ_INPUT_REGISTERS);
energyPoller = poller;
}
This might be enough for most people but with more complex Steibel Heatpump it is sometimes required to have more registers to be pulled.
I also have found here all the Modbus definitions for WPM system, WPM3, WPM3i
For example would like to read and graph :
30588 Raumisttemp-HK2
30589 Raumsolltemp-HK2
30592 Raumisttemp-HK3
30593 Raumsolltemp-HK3
32509 Heizkreispumpe1 Status WPM - Heizkreispumpe 1
32510 Heizkreispumpe2 Status WPM - Heizkreispumpe 2
32511 Heizkreispumpe3 Status WPM - Heizkreispumpe 3
32512 Pufferladepumpe1 Status WPM - Pufferladepumpe 1
32513 Pufferladepumpe2 Status WPM - Pufferladepumpe 2
32521 MischerAufHK2 Status WPM - Mischer HK 2 Auf
32522 MischerZuHK2 Status WPM - Mischer HK 2 Zu
32523 MischerAufHK3 Status WPM - Mischer HK 3 Auf
32524 MischerZuHK2 Status WPM - Mischer HK 3 Zu
I already use a workaround to this issue by adding each channel as a separate Modbus read query and then add the channel, it works.
My question would be how to maintain the Modbus add-on list so that we can all reuse the code regardless of our distinct physical setup.
Maybe a realistic feature would be to add a csv definition as file ?
alternatively make the hardcoded query range bigger so it would pull everything, user can then decide to link channels or not
