Service calls work in the plugin but not when called by Tasker.
cisco187 opened this issue · comments
I'm having a problem I can see others have had, but the fixes aren't working for me. When I call a HA service in the plugin (testing it), it works but I get the below error when calling it from Tasker. I've confirmed it's not battery optimized, it's allowed to access the internet in the background, and I've made no recent changes to the credentials. Can't seem to figure out the problem.
14.27.27/E FIRE PLUGIN: Call Service / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 7 bundle keys
14.27.27/E Call Service: plugin comp: com.markadamson.taskerplugin.homeassistant/com.markadamson.taskerplugin.homeassistant.receiver.FireReceiver
14.27.27/E add wait type Plugin1 time 10
14.27.27/E add wait type Plugin1 done
14.27.27/E add wait task
14.27.37/E Error: null
Same here, all battery optimizations disabled for the Tasker and Plugin. Plugin version 1.1.5 and Xiaomi Mi6.
10.21.11/E FIRE PLUGIN: Get State / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 8 bundle keys
10.21.11/E Get State: plugin comp: com.markadamson.taskerplugin.homeassistant/com.markadamson.taskerplugin.homeassistant.receiver.FireReceiver
10.21.11/E add wait type Plugin1 time 5
10.21.11/E add wait type Plugin1 done
10.21.11/E add wait task
10.21.16/E Error: null
Same problem here on a xiaomi mi note 3.
@MarkAdamson Can you comment on this please? I'm having the same exact issue as the other two people who commented on this issue.
I'm having the exact same problem, did anyone figure it out?
There hasn't been any activity on this in over a year, I think it is abandoned.
I figured i give it a shot... That's too bad though.
@MarkAdamson , is there any chance you can review this issue and assist us?
The same error occured today:
FIRE PLUGIN: Get State / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 8 bundle keys
Get State: plugin comp: com.markadamson.taskerplugin.homeassistant/com.markadamson.taskerplugin.homeassistant.receiver.FireReceiver
add wait type Plugin1 time 10
add wait type Plugin1 done
add wait task
Fehler: null
More precisely, it works in the local network over wifi, but not over mobile network over a domain name.
Hi guys - as you've guessed, I haven't had a lot of time for this project. This issue seems to be a particular bugbear for some people, but it's hard to address when, unfortunately, it's never happened for me.
What would be most useful is if somebody could provide a logcat of the error occurring. For anyone inclined to do so, here is a guide on various ways to take a logcat:
https://www.xda-developers.com/how-to-take-logs-android/
With this, I'll try to find some time to figure out what's going wrong. I can't make any promises though.
Hi @MarkAdamson, for me this also started to happen when I upgraded to Android 12.
This is a logtrace from my phone filtered for "net.dinglisch.android.taskerm". I tried to call a HA service with timeout of 1. It fails with the aforementioned error: logcat.txt
Full log without filter: logcat.txt
Is this maybe the cause for the issue:
07-29 17:18:01.873 1874 2681 W ActivityManager: Foreground service started from background can not have location/camera/microphone access: service net.dinglisch.android.taskerm/com.joaomgcd.taskerm.plugin.ServiceRequestQuery
I know 'location/camera/microphone' is not really what the plugin does, but I thought it might be due to something with foreground/backround, because as others said, when you have the plugin opened it works.
Thanks for looking into! Love the plugin
I'm having the same issue as @cisco187
18.03.27/E FIRE PLUGIN: Call Service / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 7 bundle keys
18.03.27/E Call Service: plugin comp: com.markadamson.taskerplugin.homeassistant/com.markadamson.taskerplugin.homeassistant.receiver.FireReceiver
18.03.27/E add wait type Plugin1 time 10
18.03.27/E add wait type Plugin1 done
18.03.27/E add wait task
18.03.37/E Error: null
When i edit the "Call service" and click "Test service", it works without a problem.
When the action is called by a profile or when i run the task manually (the play button at the bottom), it doesn't work.
Would be really appreciated if @MarkAdamson could have a closer look at this.
Still having this issue now on the Pixel 8. It could be memory related but not sure. There isn't anything suspicious for this package in the logs.
10-24 18:14:32.783 549 549 I lowmemorykiller: Kill 'com.markadamson.taskerplugin.homeassistant:background' (7303), uid 10321, oom_score_adj 995 to free 83776kB rss, 5956kB swap; reason: low watermark is breached and swap is low (1280196kB < 3894104kB)
10-24 18:14:32.783 549 549 I killinfo: [7303,10321,995,201,83776,3,182184,1965528,24160,1064,52808,260036,3894104,3317592,371188,2882260,561764,1098012,140196,420232,110628,214000,215008,0,11556,645,52,49,0,5956,423752,0,0,15.370000,7.660000,9.320000,1.060000,55.599998]
10-24 18:14:32.802 1586 2250 I ActivityManager: Process com.markadamson.taskerplugin.homeassistant:background (pid 7303) has died: cch+95 CEM
10-24 18:14:32.802 1586 2250 I am_proc_died: [0,7303,com.markadamson.taskerplugin.homeassistant:background,995,19]