A while ago I migrated all my Stiebel Eltron Heatpump Things to the “modbus:stiebeleltron-heatpump-allwpm” Thing. Before I used some manual Modbus Pollers in combination with “modbus:heatpump:”.
Basically everything is working with the “allwpm”, except of “Operating Mode”. It is reading the value correctly, but is not able to set a value to a different mode.
For this single configuration I’m still using the “old” modbus:heatpump, where I’m still able to change the Operating Mode. But I want to get rid of this one
Anyone also have this issue with “modbus:stiebeleltron-heatpump-allwpm” and Operating Mode?
Unfortunatelly I cannot find anything in the modbus logs, even when using debug.
ran into something like this on allwpm too. reads look fine, writes to operating mode just vanish. in my experience that channel is mapped to a different register or write type than the old heatpump thing, so the item might still be bound to a read-only or wrong transformation. id probably compare the channel config on both things side by side, and try a Number item with autoupdate=false. debug logs staying quiet is pretty typical for a no-op write.
yeah mainui is kinda empty for modbus channels. you can still peek the thing json though: http://<oh>:8080/rest/things/<thingUID>
and dig channels / configuration on the operating-mode channel for both the allwpm thing and the old heatpump one. or in karaf openhab:things show <uid>.
useful bit is usually writeType / address / valuetype differing between the two. if the allwpm channel basically has no write params thatd explain a silent no-op.
I used a rule to make sure the command sends an integer and not a string number.
Like this it is working. It seems I have to adjust my MainUI page or set metadata using “command options” or something like this.
Update
It is even not working via a rule. I tested it again and it didn’t work. Probably I did a mistake with the first test.
