Hi Peter, nice to hear you are still using this binding! I still use it too, most of the time without thinking about it since it never causes any issues.
Thanks for the suggestion. It would be relatively easy to add the fault indication flag. And with a little more effort it would also be possible to get details from the boiler as to what kind of fault has occured (as long as the boiler supports it).
However, since I am still busy renovating my house… these things always take way more time than expected … I won’t be able to work on implementing this feature until the Christmas holidays.
Got the esp working with ESP-link. Showing the everything from the thermostat and boiler. However, the binding 0.8.0 does not allow me to configure anything in PaperUI. It just shows the binding, but no channels, no configuration etc. Do I miss something?
@PGustias thanks for the detailed screenshot, this really helps me in mapping the data sent through opentherm to the binding.
@JdeJong you should be able to configure the IP address to connect to the OTGW device. After that, a complete list of channels should be available in openHAB which also shows up in PaperUI. The sources are currently not available on Github, because the structure of the openHAB sources has changed quite a bit and I haven’t had the time to adjust the sources of the binding to match the new structure. Is there anything in particular you are interested in regarding the sources of the binding?
The thing is, that the bindings in the upstream repo from openhab were moved from /addons/binding to /bundles, and with it of course also the build scripts etc. So I ran into a lot of issues when creating a pull request.
Unfortunately documentation (both openhab and eclipse smarthome) is now out of date or contain broken links to examples of how to get things working… so if you can help me out by explaining how the new forlder structure works or how to migrate the binding from the old to the new structure… that would be very helpful
Your question is more related to the OpenTherm gateway device itself than the binding. The OTGW website indeed states that for temporary override (TT) and constant override (TC) a value of 0 cancels the override. But I have never tested this myself.
Please let me know if it works, if not I have to look into it.
Tested today. The override for DHW works and can be removed by setting it to 0.
What doesn’t work is the override for the room temperature. But it’s not related to removing the override, it just won’t take the override at all.
It always shows the temperature of the thermostat.
I also checked the log and there only the setpoints of the thermostat is returned.
One thing that is important to know: I have two different heating circuits, one for floor heating and one for radiators in the 1st floor. Within the thermostat I can set two different setpoints. Only one is shown in the plugin.
Do I have to change anything to be able to set both setpoints through the gateway? Or at least one of the setpoints?
I am not sure how it would work with two circuits… but if the boiler has two room setpoints, that might explain why the constant or temporary room setpoint override doesn’t work. With this binding though, I am limited to the features of the OTGW device. And as far as I know, it doesn’t support overriding two separate room setpoints. At least, not with the standard firmware.
If you check the OTGW site with the link I provided earlier, you will see all the commands the OTGW device supports. Some commands are mapped to channels, like temporary and constant override, but any command not mapped to a channel can always be set through the generic “Send command” channel of the binding.
Please check if you can get the setup working with just the OTGW device and OTmonitor or telnet or something… to find out whether the issue is with the binding or the hardware.