Hi Stefan,
I am using the OTThing V2.46 firmware with a Westen Boyler Digit+ boiler.
I have identified a major issue regarding Domestic Hot Water (DHW) management.
The Problem:
As soon as the OTThing connects to the OpenTherm bus as a Master, the boiler disables its internal DHW storage tank management. It seems the boiler expects a specific configuration handshake, but because it doesn't receive proper confirmation refuses to fire for DHW.
If I switch the OTThing to Bypass, the boiler starts the DHW procedure.
Naming inconsistency:
I found that naming of DHW mixes and dhw and dwh are mixed throughout the codebase and MQTT entities
Proposed Solutions:
Fix naming:
correcting dwh/dhw variables maybe could solve some hidden issues
Feature Request:
Could you implement an option in the "Setup" menu to "Disable DHW control" (but not the function, just the control)?
The goal would be to allow the OTThing to act as a Master for CH (Central Heating) ONLY, while delegating full DHW management back to the boiler's internal logic and it doesn't disabling the DHW itself.
In this mode, the OTThing should simply report the boiler's internal DHW temperature without trying to command the DHW state and allowing the SetTemp modification.
This would allow the boiler to operate autonomously for hot water while the OTThing handles the heating circuit perfectly.
Thank you for your hard work on this project! I'm glad I found your solution!
ps.: Of course, it would be best if DWH could be controlled via OTThing, but I don't know if it would work universally for everyone, which it might for me.
otthing_CF3900_config.json
otthing_CF3900_log.txt
otthing_CF3900_ot_items.json
otthing_CF3900_status.json
Hi Stefan,
I am using the OTThing V2.46 firmware with a Westen Boyler Digit+ boiler.
I have identified a major issue regarding Domestic Hot Water (DHW) management.
The Problem:
As soon as the OTThing connects to the OpenTherm bus as a Master, the boiler disables its internal DHW storage tank management. It seems the boiler expects a specific configuration handshake, but because it doesn't receive proper confirmation refuses to fire for DHW.
If I switch the OTThing to Bypass, the boiler starts the DHW procedure.
Naming inconsistency:
I found that naming of DHW mixes and dhw and dwh are mixed throughout the codebase and MQTT entities
Proposed Solutions:
Fix naming:
correcting dwh/dhw variables maybe could solve some hidden issues
Feature Request:
Could you implement an option in the "Setup" menu to "Disable DHW control" (but not the function, just the control)?
The goal would be to allow the OTThing to act as a Master for CH (Central Heating) ONLY, while delegating full DHW management back to the boiler's internal logic and it doesn't disabling the DHW itself.
In this mode, the OTThing should simply report the boiler's internal DHW temperature without trying to command the DHW state and allowing the SetTemp modification.
This would allow the boiler to operate autonomously for hot water while the OTThing handles the heating circuit perfectly.
Thank you for your hard work on this project! I'm glad I found your solution!
ps.: Of course, it would be best if DWH could be controlled via OTThing, but I don't know if it would work universally for everyone, which it might for me.
otthing_CF3900_config.json
otthing_CF3900_log.txt
otthing_CF3900_ot_items.json
otthing_CF3900_status.json