The scan_interval is seconds - not minutes. Once a minute however would likely cause you to be blocked.
My recommendation (and my own approach) is to set the scan interval really high (I use 604800) and use an update of device_tracker.mi9 to trigger an update of the travel sensor, but only when not at home. Something like this
automation:
- initial_state: 'on'
alias: 'mi9 on the move'
- platform: state
entity_id: device_tracker.mi9
condition:
- condition: template
value_template: "{{ not is_state('device_tracker.mi9','home') }}"
action:
- service: homeassistant.update_entity
entity_id: sensor.travel_back_home
That way you’re only updating the travel time when it matters.
Wow !!! great answer
I do what you posted here
and get this error :
Configuration validation
Validate your configuration if you recently made some changes to your configuration and want to make sure that it is all valid
Configuration invalidCHECK CONFIG
Invalid config for [automation]: [platform] is an invalid option for [automation]. Check: automation->platform. (See /config/configuration.yaml, line 167). Please check the docs at https://home-assistant.io/integrations/automation/
If you trigger the entity like that, does that not count against the waze api call limits ? If my wife would be traveling for an hour, would that not cause a lot of updates?
also scan_interval i can’t seem to configure in the gui anymore, i guess that got removed.