Open mike240se opened 4 weeks 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.
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.