You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to have a delay option in (certain?) automation's.
My setup
WARP2 Pro with NFC auth (and OCPP)
evcc which consumes NFC tag IDs to determine the EV connected
iobroker
larger roof solar installation
My use case
After a car was connected simulate a NFC tag after X seconds or minutes. Background is convenience when charging our EV so nobody has to present an NFC tag to the box. Just connect and leave.
The time delay is to allow me to present a different tag I use to charge guest vehicles.
I differentiate the vehicles in my charger and evcc (via tag id). evcc gives nice percentage values of how much electricity came from my roof and how much the charge costs.
I haven't thought or looked into the other automation options and thus can't say if a delay option would make sense there too.
The text was updated successfully, but these errors were encountered:
Add "delay" to automation/config array members (default 0), then check for the delay in Automation::trigger() and schedule a task if it is not 0. This should automagically work for all types of triggers and actions, but we should probably block the trigger until the delay is elapsed to make sure we don't spam tasks.
I'd like to have a delay option in (certain?) automation's.
My setup
My use case
After a car was connected simulate a NFC tag after X seconds or minutes. Background is convenience when charging our EV so nobody has to present an NFC tag to the box. Just connect and leave.
The time delay is to allow me to present a different tag I use to charge guest vehicles.
I differentiate the vehicles in my charger and evcc (via tag id). evcc gives nice percentage values of how much electricity came from my roof and how much the charge costs.
I haven't thought or looked into the other automation options and thus can't say if a delay option would make sense there too.
The text was updated successfully, but these errors were encountered: