Yeecli non functional from tasker

[termux]

Yeecli non functional from tasker

[unresolvedsymbol]

The command works perfectly fine from termux as it should

[agnostic-apollo]

Are you sure you have granted tasker com.termux.permission.RUN_COMMAND permission?

And does the action not throw any error? Make sure timeout value is greater than 0. And try with Execute in terminal session toggle disabled and flash %stdout and %stderr.

Edit: Actually, permission would have been granted, otherwise a warning would have been shown in the screenshot.

[unresolvedsymbol]

[unresolvedsymbol]

I will try your timeout suggestion but I'm pretty sure I tried tweaking that around

[unresolvedsymbol]

No dice

[agnostic-apollo]

Disable the Execute in terminal session toggle, set timeout to 10s and flash %stdout, %stderr and %result with a Flash action. Does the action even run successfully, green or red dot?

If that doesn't tell you anything, then we can check the logcat.

[unresolvedsymbol]

Yes the task stays green, I've tried both with and without "exec in terminal session" unfortunately I'm not too familiar with variables in tasker so I couldn't seem to get it to flash the stdout but here's an extract from logcat along with some device info: https://a.pomf.cat/ogfott.zip

[agnostic-apollo]

Just add a new action from Alert -> Flash and set value to

%stdout
%stderr
%result

And for getting more useful log entries of Termux:Tasker, set it to debug level from plugin configuration screen options (3 dots on top right), then run command.

https://github.com/termux/termux-tasker#debugging

It may not work under tasker if yeecli shebang is standard (like #!/usr/bin/env python or similar). All its parts should be fixed with utility termux-fix-shebang.

Reason why it works under Termux session is that termux-exec (https://wiki.termux.com/wiki/Termux-exec) is being used for interactive shell.

[agnostic-apollo]

Yeah, that might actually be it and that would show as bad interpreter errors in %stderr with a successful action.

It's also mentioned in the README.

https://github.com/termux/termux-tasker#termux-environment

Another reason why stderr should always be checked when running shell commands. There are template tasks available as well that test everything for you, specially if you are not skilled in tasker.

https://github.com/termux/termux-tasker#templates

[unresolvedsymbol]

This is what happens unfortunately.
Yes I've added a script to ~/.termux/tasked with

#!/data/data/com.termux/files/usr/bin/env bash
yee --ip 192.168.1.178 toggle

[unresolvedsymbol]

(Screenshot shows wrong binary but I switched it to the script with the same result)

[agnostic-apollo]

It wouldn't matter what your initial script shebang is since termux will handle it (unless interpreter doesn't exist at both paths, then plugin action will be stuck forever, will be fixed in next Termux version). However, the shebangs of all scripts like yee called inside your script matter. But apparently it's not showing an error, was the toggle disabled when you did the flash? Did logs show anything?

[unresolvedsymbol]

Check the logcat zip attached earlier, lmk if it has anything useful

[agnostic-apollo]

It didn't cause you are supposed to set log level to debug and then run the action like I said. Without it Termux:Tasker won't log parameters and results. And run it with the Execute in terminal session toggle disabled like I already mentioned, otherwise %stdout and %stderr are never set/returned.

And how did you even grab that logcat?

[unresolvedsymbol]

I've had these set if this is what you're referring to. Also MatLog (modernized catlog)

[agnostic-apollo]

I was referring to the first picture, it's fine. But did you create the zip after setting it to verbose or before? If before, then it should have had entries with termux-tasker tag by Termux:Tasker app and termux-task by Termux app (with toggle disabled). Try capturing again.

[agnostic-apollo]

Closing since currently inactive. Can be opened again if more info is provided.