Closed mike240se closed 2 months ago
I noticed it was happening more frequently, so I set up an automation to reload it if it is unavailable.
Try something like:
alias: Reload Omnilogic when Unavailable
description: ""
trigger:
- platform: state
entity_id:
- sensor.knight_home_air_temperature
to: unavailable
- platform: time_pattern
minutes: "5"
condition:
- condition: state
entity_id: sensor.knight_home_air_temperature
state: unavailable
action:
- service: homeassistant.reload_config_entry
target:
entity_id: sensor.knight_home_air_temperature
data: {}
mode: single
I noticed it was happening more frequently, so I set up an automation to reload it if it is unavailable.
Try something like:
alias: Reload Omnilogic when Unavailable description: "" trigger: - platform: state entity_id: - sensor.knight_home_air_temperature to: unavailable - platform: time_pattern minutes: "5" condition: - condition: state entity_id: sensor.knight_home_air_temperature state: unavailable action: - service: homeassistant.reload_config_entry target: entity_id: sensor.knight_home_air_temperature data: {} mode: single
Thanks! I was actually thinking about seeing if something like this was possible because it seems to always come back no problem with a reload. I will give this a shot.
Hopefully they arent rate limiting us or something like that, I increased my poll time from 30s to 1m just in case as well.
Seeing the need for reload on my end very often as well. Seems to have happened after the great Windows outages over the summer, and guessing Hayward has possibly made some infrastructure changes that have resulted in the stability of what was previously rock solid.
Whatever it is it is a Hayward Cloud issue. I recommend either trying the local integration that is out there or setting up the "auto-reload" script for when it drops off.
I am not sure what is going on but things went from rock solid stable last year to this year I am having to reload the integration nearly every day.