AutoAlarm always shows 00:00

Discussion in 'AutoApps' started by dyadMisha, Jan 19, 2020.

  1. dyadMisha

    dyadMisha New Member

    Joined:
    Jan 19, 2020
    Messages:
    6
    Likes Received:
    0
    Hi,

    i'm trying to get next alarm time, but to no avail.

    tried 2 methods - AutoAlarm plugin and builtin "Test Next Alarm" function.
    always getting 00:00 as a result.
    My device is Xiaomi Note 8 pro with stock official firmware.

    Could someone assist please?
     
  2. dyadMisha

    dyadMisha New Member

    Joined:
    Jan 19, 2020
    Messages:
    6
    Likes Received:
    0
    alarm is set for понедельник (which is monday on Russian, пн is short for monday) 08:10.
    %raw variable contain correct value "пн 08:10", but %taskertime contains 00:00 and AutoAlarm test shows "Next alarm detected: Mon Jan 20 00:00:00 GMT+07:00 2020"

    here are details from AutoAlarm:

    Code (Text):

    NOTE: This will not work correctly if the 'Relible Alarms' option is enabled in Tasker.

    Time now is: Sun Jan 19 23:36:14 GMT+07:00 2020

    Next alarm detected: Mon Jan 20 00:00:00 GMT+07:00 2020

    You can use these variables in Tasker in the entry Task of an AutoAlarm condition:
    %hours: 0,4
    %daysc: 0
    %dayweek: 2
    %year: 2020
    %minutes: 23,76
    %raw: пн 08:10
    %shortdayname: пн
    %milis: 1425875
    %error: null
    %minutesc: 23
    %minute: 0
    %second: 0
    %taskertime: 00:00
    %seconds: 1425,88
    %hour: 0
    %month: 1
    %dayname: понедельник
    %secondsc: 45
    %days: 0,02
    %day: 20
    %hoursc: 0
     
     
    Last edited: Jan 19, 2020
  3. dyadMisha

    dyadMisha New Member

    Joined:
    Jan 19, 2020
    Messages:
    6
    Likes Received:
    0
    nothing changed in the alarm settings, but now %taskertime contains 01:01

    Code (Text):

    NOTE: This will not work correctly if the 'Relible Alarms' option is enabled in Tasker.

    Time now is: Mon Jan 20 00:23:15 GMT+07:00 2020

    Next alarm detected: Mon Jan 20 01:01:40 GMT+07:00 2020

    You can use these variables in Tasker in the entry Task of an AutoAlarm condition:
    %hours: 0,64
    %daysc: 0
    %dayweek: 2
    %year: 2020
    %minutes: 38,41
    %raw: пн 08:10
    %shortdayname: пн
    %milis: 2304761
    %error: null
    %minutesc: 38
    %minute: 1
    %second: 40
    %taskertime: 01:01
    %seconds: 2304,76
    %hour: 1
    %month: 1
    %dayname: понедельник
    %secondsc: 24
    %days: 0,03
    %day: 20
    %hoursc: 0
     
     
  4. dyadMisha

    dyadMisha New Member

    Joined:
    Jan 19, 2020
    Messages:
    6
    Likes Received:
    0
    AutoAlarm (v 1.6.0-beta) with "Old Method" works.
    but I also had to set "Decimals" to "0", because Tasker error occur when %hours contains value with decimal separator: ","
     
  5. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    8,967
    Likes Received:
    758
  6. dyadMisha

    dyadMisha New Member

    Joined:
    Jan 19, 2020
    Messages:
    6
    Likes Received:
    0
    how can i get next alarm only set by specific app?
    i can not just check %na_package and skip setting variable, because my automation in homeassistant should be triggered before the alarm time and there is a risk to loose it.

    Can you add white/black lists of apps in "test next alarm" action please?

     
  7. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    8,967
    Likes Received:
    758
    There's no way to get it just for a specific app, sorry!
     
  8. dyadMisha

    dyadMisha New Member

    Joined:
    Jan 19, 2020
    Messages:
    6
    Likes Received:
    0
    is android only allows you to get the first alarm in the list and not the whole array? hmm..
     
  9. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    8,967
    Likes Received:
    758
    Yes, that's correct
     
: AutoAlarm

Share This Page