hassio is in a container - so your running docker exec on a container with seemingly no docker tools. Does the above actually yield a result.
The objective should be to ssh from hassio (as that is where the shell_commands run) to your synology NAS (the host) and then (&&) run the docker exec command (which is like ssh but its dockers way of connecting to a container to run commands)
Yes, but only if you run the community addon âSSH & Web Terminalâ and have âProtection Modeâ OFF.
That gives you access to docker in the core or hass.io.
And im sorry, but im am not running on a Synology device, im running in an VM on Proxmox on an intel Nuc
did you get anywhere with this? saw a related issue in another post. anyway as you know the problem is that when you generate your ssh key it goes into /root/.ssh/ and when you restart hassio it will be lost.
so i understand you can add a flag to the ssh login command to tell it where to pull the key from.
So try the following:
generate your ssh key. once you have it in /root/.ssh/ copy it to your config folder so it will persist.
you can then send the shell command like this:
ssh i /path/to/key [email protected] âdocker exec -it ADB adb shell input keyevent KEYCODE_WAKEUPâ
see if it works
I gave up, i cant ssh into the homeassistant docker to generate the ssh key.
Non of all the diffrent ways i have found have worked.
Maybe becaus im running the intel-nuc version?
If you press the >_ for console it doesnât let you access the container?
Are you doing it from within your local network?
I mean using the http:ip for your portainer, as opposed to the external https:
Canât access the container if youâre outside your network
These usb instructions are for accessing the os. Not the container.
What os are you running on the nuc.?
Been messing around with various options and found something i liked so thought Iâd shareâŚ
Prompted by this thread:
and this thread:
instead of doing the ADB lifting on the synology - i installed MQTT client, ADB Shell [tasker], Secure Settings (although only got secure settings to work a few times to wake the device) on the shield.
EDIT:
I actually used ADB as well for wake which works WAY more reliably, used the same command
input keyevent KEYCODE_POWER
Essentially iâm sending a MQTT command to the shield from HA - Tasker is listening via MQTT Client and then based on the action / appname in the topic / message then completes an action.
I can run an app (so have the icon in my lovelace UI like netflix 
)
I can wake the device up and turn the TV on
I can turn the device (and TV) off
I can also pause (and resume) whatever iâm watching.
(and have a sensor that reports on whatever is being shown)
in case anyone wanted the info:
input keyevent KEYCODE_MEDIA_PAUSE
input keyevent KEYCODE_MEDIA_PLAY
