opentherm_gw: Create set_ch_enable_bit service or call it automatically when calling set_control_setpoint

[wavemaking]

Home Assistant release with the issue: 0.94.3 and earlier

Operating environment (Hass.io/Docker/Windows/etc.): Installed using pip on Ubuntu

Component/platform: https://www.home-assistant.io/components/opentherm_gw/

Description of problem: At present, the pyotgw function set_ch_enable_bit is not made available as a service. My Intergas kettle does not automatically start pumping when I call set_control_setpoint. Thus, it would be very useful to either allow calling the service set_ch_enable_bit manually, or to call it automaticall when calling set_control_setpoint.

Problem-relevant configuration.yaml entries:

opentherm_gw:
  device: socket://192.168.71.103:6638
  climate:
    name: 'Salon Wall Thermostat' 
  monitored_variables:
    - otgw_mode
    - room_setpoint
    - room_setpoint_ovrd
    - room_temp
    - master_ch_enabled
    - master_dhw_enabled
    - relative_mod_level
    - control_setpoint
    - ch_water_temp
    - max_ch_setpoint
    - dhw_temp
    - dhw_setpoint
    - ch_pump_starts
    - ch_pump_hours
    - dhw_flow_rate
    - dhw_pump_starts
    - dhw_pump_hours
    - burner_starts
    - burner_hours

[mvn23]

According to the OpenTherm Gateway Serial Commands docs, especially the description of the CS and CH commands, this bit is set automatically by the OpenTherm Gateway. Support on the boiler should not be required to enable this bit. You can add slave_ch_active to your monitored_variables to see if your boiler picks this up. Either way, this is not a bug in Home Assistant itself as it should be handled automatically by the device. If you believe this is a bug in the way the OpenTherm Gateway is handled, then please file a bug with the pyotgw library, which is what is used to control the gateway.

[notrix]

What about turning off set_ch_enable_bit ? Is it possible to stop pumping (temperature satisfied) any other way?

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[notrix]

Well I would not call this feature request as stale. Still waiting it to be implemented.

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.