I am trying to use home assistant.
I find the whole home assistant and “hass.io ” quite confusing.
I am 99.9% sure “hass.io ” is IMPOSSIBLE to run on LibreElec, it does not have enough fundamental OS things loaded into it - and you can NOT customise it - it’s a very special, custom linux.
However, home-assistant (see my docker command at the top) does work.
nickrout
(Nick Rout)
August 12, 2019, 6:22am
22
hassio runs in docker too, but I agree that you should be able to run home assistant in docker on libreelec.
I may have to have a play!
Hassio is not a custom Linux. HassOS is.
nickrout
(Nick Rout)
August 12, 2019, 11:15am
24
Libreelec is a special custom linux.
Yes, I’m familiar with Libreelec, I just read the sentence incorrectly.
So the question is, does anyone else here, run home assistant, on LibreElec without issues?
I just want to be able to see my Xioami Aqara gateway.
I’m convinced, this is not a good sign.
The following components and platforms could not be set up:
Please check your config.
What the heck has occurred here, looks like some of my threads have been merged? No wonder this is confusing.
Will fix when I get home
nickrout
(Nick Rout)
August 16, 2019, 7:09am
31
Exactly what command are you running to make HA run in docker?
It’s all covered better in this thread.
Hi, I have hass.io working fine on my UbuntuVM
I want to run just home-assistant, under docker on my LibreElec Raspberry Pi.
Someone helped and it’s up.
docker run -d
–name=“home-assistant”
-v /storage/home-assist-config:/config
-v /etc/localtime:/etc/localtime:ro
-p 8123:8123/tcp
–restart=unless-stopped
homeassistant/raspberrypi3-homeassistant
I can’t see my Xiaomi_Aqara device and I don’t know how to fix it? Can TWO home assistant speak to the same gateway.
xiaomi_aqara:
dis…
The command is
docker run -d
–name=“home-assistant”
-v /storage/home-assist-config:/config
-v /etc/localtime:/etc/localtime:ro
-p 8123:8123/tcp
–restart=unless-stopped
homeassistant/raspberrypi3-homeassistant
Surprisingly it works fine, HA starts ok - it seems like it should work, however the ability of HA to perform a ‘detection’ against the entire network, appears to be unfortunately failing.
Again to be clear, I’m running under a tailored version of linux, found here.
https://libreelec.tv/downloads/
It used to be mentioned in the documentation, but if you want DISCOVERY to work, net has to be host, and you don’t specify a port.
You may need to open some more ports in docker for detection to work, try opening ports 53, or 5353, or even all ports to test detection.
You need to have network mode host…
HypnoToad:
try opening ports 53
That’s DNS. Home Assistant isn’t running a DNS server
nickrout
(Nick Rout)
August 16, 2019, 7:43pm
37
Those threads should be merged.
I don’t know why you are surprised it works. However see the other comments for the reason why discovery isn’t working.
flamingm0e:
It used to be mentioned in the documentation, but if you want DISCOVERY to work, net has to be host, and you don’t specify a port.
I do realise that, but unfortunately it spits out errors.
"
The following components and platforms could not be set up:
I am indeed already using --net=host
nickrout
(Nick Rout)
August 17, 2019, 11:48pm
40
I was looking at this yesterday. Maybe it is because zeroconf is already running on libreelec?
That’s totally possible? Is this a service which is not possible to take input from 2 applications?
I don’t suppose you or someone here has a spare R.Pi, VM etc to run LibreElec on?
It, it’s actually a fairly fast install