I have the following problem:
I have the android alarm as a flow trigger,but in addition to the programmed alarm, other triggers are happening, I don't know where they come from.
The alarm is only at 8:30 am, but we can see they trigger several times during the night
22.03.2020 01:00:48.025 [Acordar bom copy] Starting to execute flow 'Acordar bom copy' with Context{global{},local{triggertime=1584838848021,flow_name=Acordar bom copy,trigger=Next Alarm}}
.
.
.
22.03.2020 04:52:44.718 [Acordar bom copy] Starting to execute flow 'Acordar bom copy' with Context{global{},local{triggertime=1584852764704,flow_name=Acordar bom copy,trigger=Next Alarm}}
.
.
.
22.03.2020 07:37:01.571 [Acordar bom copy] Starting to execute flow 'Acordar bom copy' with Context{global{},local{triggertime=1584862621567,flow_name=Acordar bom copy,trigger=Next Alarm}}
22.03.2020 07:37:01.577 [Acordar bom copy] Start executing condition 'WiFi Connected: All SSIDs'
22.03.2020 07:37:01.600 [Acordar bom copy] End executing condition 'WiFi Connected: All SSIDs' with return value false
22.03.2020 07:37:01.601 [Acordar bom copy] Flow continues executing with the next step.
22.03.2020 07:37:01.601 [Acordar bom copy] Start executing condition 'Time Range: between 07:00 - 11:30'
22.03.2020 07:37:01.601 [Acordar bom copy] End executing condition 'Time Range: between 07:00 - 11:30' with return value true
22.03.2020 07:37:01.601 [Acordar bom copy] Flow continues executing with the next step.
22.03.2020 07:37:01.601 [Acordar bom copy] Start executing action 'Set WiFi State: On'
22.03.2020 07:37:01.607 [Acordar bom copy] Action 'Set WiFi State: On' enable = true
22.03.2020 07:37:01.647 [Acordar bom copy] End executing action 'Set WiFi State: On'
22.03.2020 07:37:01.648 [Acordar bom copy] Flow continues executing with the next step.
22.03.2020 07:37:01.648 [Acordar bom copy] Start executing action 'Sleep: 20s (keep device awake)'
22.03.2020 07:37:01.648 [Acordar bom copy] Action 'Sleep: 20s (keep device awake)' Sleeping for 20s (keep device awake)
22.03.2020 07:37:21.654 [Acordar bom copy] End executing action 'Sleep: 20s (keep device awake)'
22.03.2020 07:37:21.654 [Acordar bom copy] Flow continues executing with the next step.
22.03.2020 07:37:21.655 [Acordar bom copy] Start executing action 'Plugin: A Thing Thing: Virtual acordar
problems with alarm triggering, false alarm
Moderator: Martin
Re: problems with alarm triggering, false alarm
I remember that the system will query the next_alarm several times before due, that's why the trigger got triggered at different time.
Better init variable system for the next_alarm value. it is usually something like this
Category : [system]
key : next_alarm_formatted
value : Thu 07:00
After you get Thu 07:00, then you can parsed this using script as here : viewtopic.php?f=5&t=8441&p=26516&hilit= ... arm#p26516
Save the parsed time into global variable and use trigger Global Variable Date/Time upon that glovar as the time.
Better init variable system for the next_alarm value. it is usually something like this
Category : [system]
key : next_alarm_formatted
value : Thu 07:00
After you get Thu 07:00, then you can parsed this using script as here : viewtopic.php?f=5&t=8441&p=26516&hilit= ... arm#p26516
Save the parsed time into global variable and use trigger Global Variable Date/Time upon that glovar as the time.
Index of Automagic useful thread List of my other useful posts (and others')
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.