AutoRemote Autoremote no longer working - The callable returned a null value

Discussion in 'AutoApps' started by tboooe, May 26, 2018.

  1. tboooe

    tboooe Member

    Joined:
    Oct 20, 2017
    Messages:
    70
    Likes Received:
    1
    After the most recent update Autoremote is no longer working for me with IFTT and Zapier. I get the error "The callable returned a null value". I see in the Autoremote logs that a message is received but the Tasker function does not execute. Any ideas?
     
    Last edited: May 26, 2018
  2. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    6,552
    Likes Received:
    580
    Hi there, thanks for the report! Does it work to send messages to other devices?
     
  3. tboooe

    tboooe Member

    Joined:
    Oct 20, 2017
    Messages:
    70
    Likes Received:
    1
    Yes, sending messages works. Some of my IFTT functions still work while others wont. The issue started about 2 updates ago. I have not made any changes to my AutoRemote settings or my Tasker functions.
     
    Last edited: May 29, 2018
  4. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    6,552
    Likes Received:
    580
    Can you please try this in AutoRemote for a function that doesn't work:
    - clear logs
    - enable system logs
    -do command
    -export logs and paste them here

    Thanks!
     
  5. tboooe

    tboooe Member

    Joined:
    Oct 20, 2017
    Messages:
    70
    Likes Received:
    1
    Dumb question...are system logs different from the regular Autoremote logs?
     
  6. tboooe

    tboooe Member

    Joined:
    Oct 20, 2017
    Messages:
    70
    Likes Received:
    1
    Now I feel extra dumb...I think the error is not from AutoRemote but from Autonotification. When looking more closely at the toast error, the icon looks like the one for AN. Anyway, I have enabled System Logs in AN and will post when I see error again.
     
  7. tboooe

    tboooe Member

    Joined:
    Oct 20, 2017
    Messages:
    70
    Likes Received:
    1
    Here is the log from AN
    version 3.8.4.bf2

    OS Build MHA-L29 8.0.0.360(C567)
    OS Code 26
    Device MHA-L29
    Manufacturer HUAWEI
    Product MHA-L29

    Notification Intercepts - 2018-05-30 18:56:51.301 - Set last update from notification from com.google.android.apps.inbox
    Notification Intercepts - 2018-05-30 18:56:51.287 - Set last update from notification from com.google.android.apps.inbox
    Notification Intercepts - 2018-05-30 18:56:51.257 - New notification from com.google.android.apps.inbox
    Notification Intercepts - 2018-05-30 18:56:51.254 - New notification from com.google.android.apps.inbox
    Notification Intercepts - 2018-05-30 18:12:25.892 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:12:25.870 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:12:25.606 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:12:25.582 - Removed notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:12:22.202 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:12:22.194 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:12:22.179 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:12:22.166 - New notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:12:19.109 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:12:19.101 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:12:19.091 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:12:19.069 - New notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:12:15.496 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:12:15.456 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:12:15.438 - New notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:12:15.435 - New notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:04:37.615 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:04:37.606 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:04:37.382 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:04:37.362 - Removed notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:04:32.918 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:04:32.911 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:04:32.892 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:04:32.878 - New notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:04:32.489 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:04:32.451 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:04:32.393 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:04:32.359 - New notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:04:31.410 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:04:31.386 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:04:31.360 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:04:31.320 - New notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:03:59.869 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:03:59.862 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:03:59.703 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:03:59.667 - Removed notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:03:52.987 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:03:52.963 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:03:52.909 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:03:52.776 - New notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:03:50.590 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:03:50.579 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 18:03:50.544 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 18:03:50.482 - New notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 17:59:19.696 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 17:59:19.690 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 17:59:19.685 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 17:59:19.681 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 17:59:19.623 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 17:59:19.601 - Removed notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 17:59:19.576 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 17:59:19.553 - New notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 17:59:19.242 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 17:59:19.236 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 17:59:19.067 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 17:59:19.036 - Removed notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 17:59:14.966 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 17:59:14.959 - com.google.android.talk matches text "null": false
    Notification Intercepts - 2018-05-30 17:59:14.920 - Set last update from notification from com.google.android.talk
    Notification Intercepts - 2018-05-30 17:59:14.873 - New notification from com.google.android.talk
     
  8. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    6,552
    Likes Received:
    580
    Hmmm... Do you happen to know exactly when that is happening? Do you see any pattern for when that toast shows up? Thanks!
     
  9. tboooe

    tboooe Member

    Joined:
    Oct 20, 2017
    Messages:
    70
    Likes Received:
    1
    I dont know....thats the confusing part. I am not sure whats happening. Sometimes the toast appears sometimes it doesnt. For example, this morning, AutoRemote received a message from IFTT but the Tasker task did not execute. No toast.

    This is what I know for sure:

    After the recent updates to AutoRemote, sometimes the Tasker task that rely on the AutoRemote condition does not run. As a check I put a Notify step at the very beginning of the task which I am not seeing all. However, in AutoRemote logs, I see that the IFTT message is received. It seems that AutoRemote is not passing the condition to Tasker? BTW, I have made no changes to Autoremote or Tasker. Everything was working fine until about 2 weeks ago.

    Perhaps the toast error from AN is an unrelated problem? So it seems I have 2 separate problem...AutoRemote no longer working and this weird toast from AN.
     
    Last edited: May 31, 2018
  10. tboooe

    tboooe Member

    Joined:
    Oct 20, 2017
    Messages:
    70
    Likes Received:
    1
    Ok more testing...I think I figured out the issue with AutoRemote. When my phone screen is off, my AutoRemote condition and Tasker task do not function properly. Whats odd is that AutoRemote still receives the message. It just doesnt pass the message to Tasker.

    I have not updated my phone in a very long time and made no changes to any settings. The only change I did was update AutoRemote. Perhaps did you make a recent change to AutoRemote that makes it not work with Tasker when the screen is off or vice versa?

    I just checked the Tasker run logs and can confirm that it never starts the task based on the AutoRemote condition when the screen is off.
     
    Last edited: May 31, 2018
  11. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    6,552
    Likes Received:
    580
    I didn't change anything related to that, but maybe you can try removing both Tasker and AutoRemote from battery optimizations on your phone and see if that helps?
     
  12. tboooe

    tboooe Member

    Joined:
    Oct 20, 2017
    Messages:
    70
    Likes Received:
    1
    Both apps are already removed from battery optimizations. As I mentioned, I have made no changes to my phone settings in a long time and everything used to work. Perhaps something changed with Google Play Services?
     
  13. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    6,552
    Likes Received:
    580
    Yes, maybe something related to that could be the issue.... I don't have the issue myself though.. :(
     
  14. tboooe

    tboooe Member

    Joined:
    Oct 20, 2017
    Messages:
    70
    Likes Received:
    1
    Uggh...this is very frustrating because I have not made many changes to my phone firmware or settings. Such a bummer because my Autoremote and Tasker tasks were working very well!!! Not sure what to do now....
     
  15. Huitre Ahurie

    Huitre Ahurie New Member

    Joined:
    May 25, 2016
    Messages:
    2
    Likes Received:
    0
    Hi ,

    Sorry for coming in your topic, i have the same problem but it's not only from Autoinput, i get the same toast from Autonotification and Autoinput.
    It began since the update (last?) week.
    I disabled tasker, turn off every profile and saved and deleted every task related to Autoinput and Autonotification but the toast still appears. Did you manage to fix it ?
     
  16. joaomgcd

    joaomgcd Administrator Staff Member

    Joined:
    Feb 3, 2015
    Messages:
    6,552
    Likes Received:
    580
    I've now fixed AutoNotification and AutoVoice. Can you please confirm that it's working now?
     
  17. Ron Parker

    Ron Parker New Member

    Joined:
    Jun 8, 2017
    Messages:
    18
    Likes Received:
    2
    I have the same "The callable returned a null value" error in AutoRemote. I have two android devices joined. I use autoremote to send message from device a to device b. On device b, I have an autoremote tasker profile that looks for the message "clock", and when received executes a task that launches a clock. According to logs, device b receives the message every time, but does not execute the task every time. The pattern seems to be that I have to send the message 2 to 3 times before device b executes the task. When device b doesn't execute the task, it reports "The callable returned a null value". The image below is the error message I see on device b when tasker fails. How do I fix this? Screenshot_2018-07-16-15-55-40.png
     
  18. Ron Parker

    Ron Parker New Member

    Joined:
    Jun 8, 2017
    Messages:
    18
    Likes Received:
    2
    One more note that I thought might be interesting: I created a Net http get task on device a that sends a join push via url to join receiver task on device b. That works -- virtually every time. https://joinjoaomgcd.appspot.com/_ah/api/messaging/v1/sendPush?deviceId=my_device_id&apikey=my_api_key&text=clock

    I created a join push send task on device a to send the same exact text to device b, and it fails to trigger profile on device b every time. And, as mentioned before, the autoremote send fails every other time with a "null value" error message.
     
: error

Share This Page