I created sql sensor to pick up my electricity data and solar cost. However, there has been a lot of confusion re scan_interval via YAML and in UI and some suggested to use automation if you don’t want 60 seconds polling.
So here is what is happening to me.
YAML SQL(can’t update) via homeassistant.update_entity so I then moved to preferred SQL UI, disabled polling and then tried homeassistant.update_entity both via automation and Dev tool, not working. However, I managed to make it work using homeassistant.reload_config_entry
The question is what’s the use of SQL UI if it is no good. You can’t set scan_internal and can’t trigger it via homeassistant.update_entity .(at least not for me).
The other issue I’ve is why am I not able to force update it via homeassistant.update_entity . but via `homeassistant.reload_config_entry’. Is the reload option not recommended ?, and if not then what are my options.
The following is working for me:
alias: Refresh SQL costs
description: Update SQL sensors
triggers:
- trigger: time_pattern
hours: /2
- at: "00:05:00"
trigger: time
- event: start
trigger: homeassistant
actions:
- action: homeassistant.reload_config_entry
metadata: {}
data: {}
target:
entity_id:
- sensor.sql_cost_base_today
- sensor.sql_cost_shoulder_today
- sensor.sql_cost_peak_today
- sensor.sql_cost_fixed_today
- sensor.sql_comp_tier1_today
- sensor.sql_comp_tier2_today
enabled: true
mode: single