grimmace92 wrote:
> Just curious. I'd rather have HA running in docker as the version is
> always updated. The syno community package isn't. I made a little
> progress where if I run a spotify command in putty it will update the
> sensors and they appear in HA updated. I'm pretty sure its a path issue
> now. I see this in the log Error running command: `bash
> /volume1/web/docker/homeassistant/shell/spot_art_top.sh {{text1}}`,
> return code: 127
>
> 12:36 AM /usr/src/app/homeassistant/components/shell_command.py (ERROR)
>
> I tried /config and /.config for the path as well and no luck. Any
> other last ditch ideas? Otherwise I will stick with the non docker
> package for now. Thanks!
See exit codes: http://tldp.org/LDP/abs/html/exitcodes.html
Exit Code Number Meaning Example Comments
1 Catchall for general errors let "var1 = 1/0" Miscellaneous
errors,
such as "divide by zero" and other impermissible operations
2 Misuse of shell builtins (according to Bash
documentation) empty_function() {} Missing keyword or command, or
permission problem (and diff return code on a failed binary file
comparison).
126 Command invoked cannot execute /dev/null Permission problem or
command is not an executable
127 "command not found" illegal_command Possible problem with $PATH or a
typo
128 Invalid argument to exit exit 3.14159 exit takes only integer
args
in the range 0 - 255 (see first footnote)
128+n Fatal error signal "n" kill -9 $PPID of script $? returns 137 (128
+ 9)
130 Script terminated by Control-C Ctl-C Control-C is fatal error signal
2, (130 = 128 + 2, see above)
255* Exit status out of range exit -1 exit takes only integer args in
the range 0 - 255
If a command is not found, the child process created to execute it
returns a status of 127. If a com- mand is found but is not executable,
the return status is 126. If a command fails because of an error during
expansion or redirection, the exit status is greater than zero.
Basically command not found (path is incorrect or file does not exist).
The intention is to make the shell sub directory just under where ever
your configuration.yaml file is stored. This will ensure it can be
found by the HA system. Then you can go to
https://yourdomain.duckdns.org/dev-info and see the path to
configuration.yaml in my example this is:
" Path to configuration.yaml: /config "
Ynot
*software* - logitech media server version: 7.9.1, home assistant
0.84.6, dialogflow - v.1 api, lms controls app - voice control of lms,
openmediavault 4.1.17 - storage
*add-ons* - spotty, upnp / dlna bridge, chromecast bridge,
*players* - sonos, upnp, pi3 - pi core player 3.5.0, android- sb player
v1.4.0, airplay to googlehome and minis
*hardware* - server - i7-3.4ghz, 4gb ram, 6tb storage, debian - 4.18
------------------------------------------------------------------------
ynot1234567890's Profile: http://forums.slimdevices.com/member.php?userid=66569
View this thread: http://forums.slimdevices.com/showthread.php?t=109273
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
