It’s not as far as I can see. It seems to be an example.
Option 2 WILL have access to the HA folders, because you are INSIDE the Home Assistant container, running with the same access as Home Assistant itself has.
anyhow, as it seems to be a 3 year old file(device.py), he will execute … he might need luck ( or Debug, ofcause )
It turned out that Advanced SSH under HACS gives you SSH access that will allow you better access and the ability to run the built in Python. And everything works perfect vs the standard SSH.
1 Like
I presume you’ll be marking a solution sometime soon?
Done… I am sorry i missed that.
So I give you the solution and you mark your own post as solution.
Merry Xmas.
He was given about 4 different valid solutions, he picked 1, and motivated it ( That his Solution )
I did! I picked one. Advanced SSH under HACS was the way to access Python in an SSH shell in HA. The normal SSH is giving you admin access and can’t use Python but Advanced SSH under HACS logins in as YOU and can even access dockers. So it is more powerful and will do the trick.
In other words, the solution I posted in post 17.
The sinope device.py run just fine in HA. You just need to use advance ssh & web terminal to give you access to internal python which HA is using. HA is build on python so it is mandatory that python is installed on the computer that run HA.
I’ve updated the doc of my custom_component to let user know that it need to use advance ssh & web terminal to have access to python to be able to run device.py. After that step everything run just fine. I’ve also remove deprecated hassbian path which does not exist anymore.
1 Like