@ncortines wrote:
Hi,
I have a Generic Thermostat that triggers a MQTT Switch to open/close the valve of a water heater:
- platform: mqtt name: "heater_bedroom" state_topic: "bedroom/relay/state" command_topic: "bedroom/relay/set" payload_on: 1 payload_off: 0 state_on: "1" state_off: "0" retain: true - platform: generic_thermostat name: thermostat_bedroom heater: switch.heater_bedroom target_sensor: sensor.temperature_xiaomi_air_1 min_temp: 16 max_temp: 26 ac_mode: False target_temp: 20.5 cold_tolerance: 0.1 hot_tolerance: 0.1 min_cycle_duration: seconds: 5 keep_alive: minutes: 3 initial_operation_mode: "auto" away_temp: 16
I also have an automation that triggers the central heating boiler whenever 1 or more heater switches are open:
- id: enable_boiler alias: Enable Boiler trigger: - platform: state entity_id: - group.all_heaters to: 'on' from: 'off' action: - service: switch.turn_on data: entity_id: - switch.boiler
This configuration works pretty well (I’ve been using it for the whole season without glitches) until, for whatever the reason, one of the heater’s MQTT Switches disconnects.
If one of the heater’s MQTT Switches disconnects while the State was “ON”, it remains “ON”, and my Boiler keeps heating even though the heater’s MQTT Switch now is closed, because those are Normally Closed valves.
So basically, the ideal solution for me would be a MQTT Switch that changes state to “OFF” when the connection to the client is lost.
What could be a solution for my problem?
Thanks!
Juan
Posts: 8
Participants: 4