AutoWear 'null' in Command Match

Discussion in 'AutoApps' started by DarthStark, Jun 12, 2018.

  1. DarthStark

    DarthStark New Member

    Joined:
    Apr 19, 2018
    Messages:
    16
    Likes Received:
    0
    Hello,

    I created a simple Buttons Screen to activate 3 tasks in Tasker depending on the string. All 3 commands have a common prefix and then the command itself.

    The screen worked for a few days and then stopped. Then I changed phones (from a 2014 Moto X to a Moto Z2 Play), reinstalled everything, and reset the watch (Zenwatch 3 with Wear 2) to pair with the new phone. Again, the screen worked for a few days and stopped.

    In both cases the logs show the same thing (screenshots attached, since I'm a gddm newb and don't know if it's the right way to send logs): the command is received by the phone but tries to match with 'null'.

    What am I doing wrong?

    Screenshot_20180612-123352.png Screenshot_20180611-080012.png Screenshot_20180611-080019.png Screenshot_20180611-080116.png
     
  2. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,481
    Likes Received:
    802
    Do you have 2 commas in the command list on purpose?
     
  3. DarthStark

    DarthStark New Member

    Joined:
    Apr 19, 2018
    Messages:
    16
    Likes Received:
    0
    Yes! There are 3 buttons. The middle one only works on long press (so I don't press it unintentionally). Bu I'll try to add some dummy commands there to check.

    When I recreate the screen, it works for a few hours -- i tried again yesterday. But then it starts failing (on all 3 commands).

    What looks strange to me: the commands and timestamps do not match between the "Commands" and "Command Match" logs.
     
  4. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,481
    Likes Received:
    802
    Very weird that it just stops after some time... If you check the screen in the main AutoWear app on your phone does it still show with the correct commands?
     
  5. DarthStark

    DarthStark New Member

    Joined:
    Apr 19, 2018
    Messages:
    16
    Likes Received:
    0
    Yep. Also, if I "Show" the screen from the phone, it starts working again for some time.
     
  6. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,481
    Likes Received:
    802
    Can you tell what exactly makes it stop working? Does it seem random?
     
  7. DarthStark

    DarthStark New Member

    Joined:
    Apr 19, 2018
    Messages:
    16
    Likes Received:
    0
    It's happening right now. I recreated the screen, sent a command using a button, and it was ignored. It shows up on the Commands log but nothing got to the Command Match log.
    It seems to me that the "null" in Command Match log is not related to the commands from the screen; the commands from the screen are not even matched.
    I don't think it's random, it seems to be related to not using the screen for a while. Now it seems to me to be more of a Tasker problem than an Autowear problem. Maybe Tasker is sleeping (even though I added it to the "no battery optimization" list).
     
  8. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,481
    Likes Received:
    802
    But does the command you send from the screen correctly appear in the AutoWear logs?
     
  9. DarthStark

    DarthStark New Member

    Joined:
    Apr 19, 2018
    Messages:
    16
    Likes Received:
    0
    Yes, in the Commands log.
     
  10. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,481
    Likes Received:
    802
    Oh, cool. Can you please enable the Tasker log to Internal Storage, send a command and then disable debug to internal storage and post the logs here? Thanks in advance!
     
  11. DarthStark

    DarthStark New Member

    Joined:
    Apr 19, 2018
    Messages:
    16
    Likes Received:
    0
    There you go. I had to try a few times to log the moment it did NOT work.
     

    Attached Files:

  12. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,481
    Likes Received:
    802
    Just to confirm, you wanted to trigger the "^timeP" profile?
     
  13. DarthStark

    DarthStark New Member

    Joined:
    Apr 19, 2018
    Messages:
    16
    Likes Received:
    0
    Exactly.
     
  14. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,481
    Likes Received:
    802
    Can you please let me know which version of Tasker you're using? Thanks
     
  15. DarthStark

    DarthStark New Member

    Joined:
    Apr 19, 2018
    Messages:
    16
    Likes Received:
    0
    It was 5.1m. While I was writing this it updated to 5.2.bf. Did not test yet after the update.
     
  16. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,481
    Likes Received:
    802
    Can you try with the new one please? Thanks!
     
  17. DarthStark

    DarthStark New Member

    Joined:
    Apr 19, 2018
    Messages:
    16
    Likes Received:
    0
    No problems so far!
     
  18. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    9,481
    Likes Received:
    802
  19. DarthStark

    DarthStark New Member

    Joined:
    Apr 19, 2018
    Messages:
    16
    Likes Received:
    0
    Happened again this morning.

    What I noticed: After I clicked the button2 ("timePdoSend" and "TimePdoCancel" on the Command log screenshot) nothing happened. After about 90 seconds, there is a lot of 'null' matches logged on Command Match.

    On the Tasker logs, you can see the command I sent 15 minutes earlier ("timePdoTest") being handled. But no sign of the last command.
     

    Attached Files:

  20. DarthStark

    DarthStark New Member

    Joined:
    Apr 19, 2018
    Messages:
    16
    Likes Received:
    0
    Looking back at the log, I don't think the "nulls" have anything to do with this problem. There are "null" commands being sent all the time (even when I'm not wearing the watch). The problem seems to be entirely that Tasker sometimes (even if it has just been used) fails to acknowledge the command filter.
     
: AutoWear

Share This Page