Shell: Couldn't convert from easy command/doesn't have a valid component?

[whitedavidp]

I have been having sporadic issues with one of my tasks that runs a root shell commmand. It seems that the command is NOT being executed. In trying to get to the bottom of this, I find the following in the Tasker log file:

22-09-2021 Shell: 02.27.45#b#Shell: Couldn't convert from easy command: echo 1 > /sys/devices/platform/lge-unified-nodes/charging_enable; echo 1 > /sys/devices/platform/soc/a90000.i2c/i2c-4/4-0061/power_supply/wireless/charging_enabled doesn't have a valid component

Here is the more complete context from the log:

22-09-2021 Shell: 02.27.45#b#Shell: runSync su -c id root: true timeout: 3000
22-09-2021 Shell: 02.27.45#b#Shell: runBackground echo 1 > /sys/devices/platform/lge-unified-nodes/charging_enable; echo 1 > /sys/devices/platform/soc/a90000.i2c/i2c-4/4-0061/power_supply/wireless/charging_enabled root: true timeout: -1
22-09-2021 Shell: 02.27.45#b#Shell: start process-thread ID 354
22-09-2021 E: 02.27.45#b#E: add wait type Shell3 time 2147483647
22-09-2021 E: 02.27.45#b#E: add wait type Shell3 done
22-09-2021 E: 02.27.45#b#E: add wait task
22-09-2021 M: 02.27.45.255#b#M: checkMatchStates: handleChanges: true handle:
22-09-2021 Shell: 02.27.45#b#Shell: have process
22-09-2021 Shell: 02.27.45#b#Shell: write cmd: su -c id
22-09-2021 Shell: 02.27.45#b#Shell: start process timeout timer 3000ms for: su -c id
22-09-2021 M: 02.27.45#b#M: occurred event count: 1 with action: net.dinglisch.android.tasker.VSETUM
22-09-2021 Shell: 02.27.45#b#Shell: start process-thread ID 356
22-09-2021 E: 02.27.45#b#E: stillWaiting: test Shell3
22-09-2021 Shell: 02.27.45#b#Shell: have process
22-09-2021 E: 02.27.45#b#E: still waiting for Shell3: Power Enable Charging
22-09-2021 E: 02.27.45#b#E: nothing chosen, check exit
22-09-2021 E: 02.27.45#b#E: wait for 1000ms
22-09-2021 Shell: 02.27.45#b#Shell: Couldn't convert from easy command: echo 1 > /sys/devices/platform/lge-unified-nodes/charging_enable; echo 1 > /sys/devices/platform/soc/a90000.i2c/i2c-4/4-0061/power_supply/wireless/charging_enabled doesn't have a valid component
22-09-2021 Shell: 02.27.45#b#Shell: write cmd: echo 1 > /sys/devices/platform/lge-unified-nodes/charging_enable; echo 1 > /sys/devices/platform/soc/a90000.i2c/i2c-4/4-0061/power_supply/wireless/charging_enabled
22-09-2021 Shell: 02.27.45#b#Shell: out of wait
22-09-2021 Shell: 02.27.45#b#Shell: exit result: 0
22-09-2021 Shell: 02.27.45#b#Shell: record back result: 0
22-09-2021 Shell: 02.27.45#b#Shell: kick exe thread
22-09-2021 Shell: 02.27.45#b#Shell: kicked
22-09-2021 E: 02.27.45#b#E: wait int
22-09-2021 E: 02.27.45#b#E: stillWaiting: test Shell3
22-09-2021 E: 02.27.45#b#E: Run Shell:  ->
22-09-2021 E: 02.27.45#b#E: Run Shell:  ->
22-09-2021 E: 02.27.45#b#E: Run Shell:  ->
22-09-2021 E: 02.27.45#b#E: removeWait: Shell3
22-09-2021 E: 02.27.45#b#E: finished waiting for Shell3 (task Power Enable Charging)
22-09-2021 E: 02.27.45#b#E: remove finished task from q: Power Enable Charging
22-09-2021 E: 02.27.45#b#E: nothing chosen, check exit
22-09-2021 E: 02.27.45#b#E: fix finished, remove wait flag
22-09-2021 E: 02.27.45#b#E: exe sync stoplock
22-09-2021 E: 02.27.45#b#E: exe insync stoplock
22-09-2021 E: 02.27.45#b#E: stopSelf: 8 alldone: true eqtimes: 0
22-09-2021 E: 02.27.45#b#E: exe postsync stoplock
22-09-2021 E: 02.27.45#b#E: exe thread tidy up
22-09-2021 E: 02.27.45#m#E: ondestroy
22-09-2021 WakeLockManager: 02.27.45#b#WakeLockManager: acquired partial lock for M flags: 1 autorelease: true warn: true
22-09-2021 WakeLockManager: 02.27.45#b#WakeLockManager: setClearAlarm: not setting, last set 2201ms ago
22-09-2021 E: 02.27.45#b#E: onUtteranceCompleted: exeThreadTidy id: null err: false

I have no idea what an "easy command" is or why there should be a problem in doing this. I have no idea what the needed "component" might be.

Can anyone shed some light on this? I am stumped. Thanks

[João Dias]

That is just a log line that says that the command isn't an easy command, it's not actually an error. :) An easy command is a command that you generate with the helper available in the action when you're setting it up and use the Services option there. 

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[ktmom]

I gather that you are using this command with Tasker's battery level context to manage charging.  If it works at all, then sporadic issues are more likely due to the task not running when the display is off/locked or that Tasker is sleeping and the battery level gets missed.  Something along those lines.

[whitedavidp]

Thanks to all. Yes, I am using it with the battery level context. But I have excepted Tasker from battery optimizations. And it does show its icon in the notification area. I specifically disable Doze at boot. So not sure what might be killing tasker or blocking this.