From what I understand, the way you installed it, it is basically running in a docker container. ssh doesn’t have access to the host system only the docket container.
I don’t know what your squeezebox is but you may need to use an alternate install method.
Thanks for the answer. I tought it was the only way to install it on a pi3.
which kind of install will you recommend to have it on a pi3?
update:
i’ve looked further, i’ve install what is called hassio. do you thing the problem comes from here? it was presented like the best way to do so…
if find apparently an other solution which is hassbian…
do you thing it will solve my problem??
If you still have your hassio config files, you can just pop them into the hassbian config folder and most of the work will already be done.
The yaml files are interchangeable on all of the installations.
I’ve install hassbian but i didn’t realize that i would not have the addon store any more coparing to hassio. So i think this solution is out of my reach… in order to install samba/configuration/duckdns and all… so anyone has a solution do add socat command in my hassio install?
All of the options are available, they just are not as easy as clicking the addon in the store.
sudo apt-get install samba
and you can setup your share. etc.
No ideas yet but i intend to use rfxtrx on Home Assistant via network… any suggestions welcome.
I already use rflink and dsmr via network using ser2net on a Pi, works fine. But those already support network in the yaml config out of the box.
I now see three approaches to this:
run socat on hassio to make HA think its a local device.
(this topic)
someone implements network support.
I never use Python …but im willing to dive into this.
So i created this topic for that: Adding network to rfxtrx component