Start with a RPI2 or 3 - doesnt matter
and this tutorial - with HASSbian you wont need to bother with the installation of pre-reqs, such as python and pip, its all done for you
Get familiar with the UI by playing about a bit⌠start to look at the configuration YAML files to get an idea of whats going on and how to change stuff in the front end
The next best place for learning how it all hangs together, is the cookbook where people have various examples of their system set up.
And finally, this community is great at helping out other people - so dont be afraid to ask any questions, big or small and even if you think its a stupid question. I guarantee you, someone will be on hand to assist!
If its something thats designed to run Kodi specifically, like LibreELEC or whatever, youâll find its going to be difficult to set up Home Assistant - although it is entirely possible if you know what youre doing
The other problem you may run into, is performance. not sure if theres enough resource for both on a Pi2 ?
With regards to an emulated Hue, not sure. I run an actual Hugh Bridge and have never needed to.
Your aim is to control your lights with your voice via google home.
Are your lights these ones??
In the case of voice control, yes is the short answer - you will need to create a Hue bridge. The long answer is probably a bit advanced at the moment, but it is entirely possible for you to get to where you want to be - there are a lot of threads on here around google home, hue and controlling various things via the emulated bridge
Yes correct lights.
Would a hue brdge need another pi or can it be on same one. probably getting ahead of myself but I find when I throw myself in at the deep end i do better
and can an official hue bridge controll limitless as if so I will just buy one to make life easierâŚ
Not sure on your emulated hue on the same host question as I dont run it. For simplicity, id just run it on the same installation and use the localhosts IP for it when needed.
There is a few light controllers that work with Hue, but generally no, out of the box, the official Hue bridge will only work with Philips Hue branded lights/lamps/LED strips
In the first instance, id get your HA set up on the Pi and add the Limitless LED config lines to your config as above link. See what functionality that gives you, then look into controlling it with your google home via the hue bridge
Emulated_hue just makes your home assistant react like a hue bridge so far as Google Home and Amazon Echo are concerned.
So if you had a genuine hue bridge and shouted âHey Google, switch on the living room lightsâ the Hue bridge takes care of it.
If you use Emulated_hue, you shout the exact same command, Google Home thinks itâs talking to a Hue bridge but really itâs your home assistant, and home assistant takes care of it.
I have both a hue bridge and Emulated_hue here, and I only let my Amazon Echo see the emulated_hue on home assistant. If I command one of the Hue lights to do something, home assistant tells the Hue bridge to carry out the task.
You donât install it on a separate pi, you just add the line emulated_hue: to your home assistant configuration with the appropriate configuration options and youâre done.
And, if you are running (the latest version of) LibreElec, it has support for Docker, so you could run the Home Assistant docker image if you wanted to.
But then instead of the docker-run command for ha-bridge, use this page:
Only at the end of the command instead of the standard image, youâll need the specific raspberry pi image:
for rpi1:
homeassistant/raspberrypi-homeassistant
for rpi2:
homeassistant/raspberrypi2-homeassistant
for rpi3:
homeassistant/raspberrypi3-homeassistant
That looked all quite straight forward until the docker bit.
I would be using windows but got confused at the
When running Home Assistant in Docker on Windows, you may have some difficulty getting ports to map for routing (since the --net=host switch actually applies to the hypervisorâs network interface). To get around this, you will need to add port proxy ipv4 rules to your local Windows machine, like so (Replacing â192.168.1.10â with whatever your Windows IP is, and â10.0.50.2â with whatever your Docker containerâs IP is):
This is for docker on raspberry pi. So it has nothing to do with your windows pc.
Ah I see now what your problem is. Just use the linux docker install command, no need to read any further on that page.
Edit: So just follow the first tutorial but instead of running ha-bridge, youâre going to run home assistant.
This should be the correct docker-run command for that (on a single line): docker run -d --name="homeassistant" -v /storage/docker/homeassistant:/config -v /etc/localtime:/etc/localtime:ro --net=host --restart=always homeassistant/raspberrypi3-homeassistant
I checked the tutorial and it wasnât explicitly mentioning that you need to run that command from the raspberrypiâs/libreelecâs shell. You can connect to that via SSH on windows using Putty, or directly from the commandline on OSX and Linux. Default LibreElec ssh (when enabled from Kodi options) is: user:root password: libreelec
Had a bit of a mare setting it up. My Pi" kept failing to install any setups so had to drop it for the night.
Im going to pick up a Pi3 this afternoon as it got me thinking if every the Pi2 needs updating I run ligtberry for tv ambient light. When i update im back to square one. with seperate device for ÂŁ30 seems safer.
