Weblog down... poging 2
There it is. The first real blog about my migration from Homey to Home Assistant.
The first things i would like to tell and discuss and the following :
- Why is Homey not enough?
- Why is Home Assistant the better solution according to me?
- How am i going to migrate without "downtime"?
Why is Homey not enough?
Don't get me wrong; i really like Athom's product. It's a pretty fancy product, priced well and it has A LOT of hardware on board which makes it an ideal hub to control everything in your home.They base everything on NodeJS, which is a good choice because of the easy way to step in to developing your own apps.
But it also has some downsides. Because the product is so broad the developers at Athom need to develop all kinds of things. The last few months i had a few times that because of an update my Homey was not working correctly anymore. Implementations of Z-Wave or Zigbee broke down, WiFi issues, apps crashing etc. That is not bad by any means.... if you use it for your hobby project. If you use Homey to control everything (or almost everything) in your home, then it needs to be stable and you need to be able to rely on it. If it breaks down, your lights won't go on in the evening, your music won't start or all or your flows won't fire.
I really have faith in the Athom developers, and they will make software better... they have a pretty decent roadmap with a lot of nice features... but then there is the second big issue :
The hardware. Years ago, when they started the project as a crowdfunding campaign they made a hardware design; Sufficient for that time, pretty insufficient now. If you run > 10 apps, it already tells you "Please not : Homey can be slower then usual do to the amount of apps".... If you then start using a lot of devices, with a lot of apps and flows, Homey is really slowing then. It even got to a point that the speech of Homey (one of the "big" things in the beginning) started stuttering in every sentence.
And that is why Homey is not enough for me. It was in the beginning, and i really enjoyed it, but i want a more stable platform that i can control myself.
Why is Home Assistant the better solution according to me?
Ok, so then i started looking for something new, a better, more reliable product or piece of software that could control my home. I was thinking about just "buying" a new controller like a Vera or Zipato. Nice products, with long living support, but pricey and getting pretty old.
I already played with Home-Assistant a few years ago, and while it was promising, i was not able to get it up and running in a timely fashion so i stopped checking it out.
But now, while i was checking it out, i ran into it again. And i saw they now had Docker support, had their own OS for Home-Assistant, had add-ons, a lot more supported devices and then it became pretty interesting to check it out again. So that is what i did.
I had an old Intel NUC with a pretty old Intel Pentium CPU thingy and 2GB RAM. Was not using it, so i wanted to do a POC (Proof of Concept) with it on the NUC. So i installed Ubuntu on the NUC and tried to install Home-Assistant. That worked, because they have a pretty nice installer, so i was happy with that. But then i started thinking that i want more flexibility, even more then just a plain OS on a machine (because i cannot easily snapshot it and things like that). So i reinstalled the NUC with Promox, a free Hypervisor.
After that i again installed a Ubuntu VM, but this time in VM on Proxmox. After that, i ran the install script again and Home-Assistant was already running. That was good news, i was happy.
I started playing around a bit with it, trying to add some simple switches, my Hue lights and tried to get a "feel" with Home-Assistant, trying to see if i liked their way of working. And i kind of did.
Don't get me wrong, HA is based on YAML, and YAML can be (read: is) a bitch. So i was fucking around (and swearing) with the config a lot the first few hours. But after that i was getting good with it :-D!
I did a lot of research on supported devices, ways of coding it, automations, scripts, scenes and after that i was convinced. There it was, my new home-automation product.
How am i going to migrate without "downtime"
Yep, and then we were at the phase of planning. I wanted to migrate things from Homey to Home-Assistant without "downtime". With downtime i mean, i don't want to come home and find out that my lights are not working anymore. Or that my alarm is going wonky in the middle of the night, waking me up with 2 sirens...
But after some thinking, it was kinda simple. I'm just picking up Homey flows, checking out what they do, and moving them to Home-Assistant (coding a new automation that does the same thing as the flow), then disable the Homey flow, start testing with the Home-Assistant automation, and if it works, enable it on HA, remove it on Homey.
And that was beginning of my migration adventure. Currently i have already migrated some really basic flows, which i will show you and tell you more about in the next blogs.
For now : This is what i need to migrate on devices :
And i need to migrate 54 flows.
Want to read more? Subscribe with an RSS feed, or keep checking my Tweakblogs. I will post bits and pieces there
Thanks. Goede tip. Daar las ik al meer over, maar ben nog niet zover gekomen om er mee te stoeien. Ga ik wel even doen binnenkort!ygma!l schreef op woensdag 25 april 2018 @ 10:02:
Je hebt helemaal gelijk wat betreft YAML. De configuratie is niet erg fijn. Alvast een tip voor 'automations': gebruik Node-RED! Als je gebruik maakt van hass.io (heb ik op Ubuntu gezet), kun je gebruik maken van deze add-on: https://github.com/notori...dons/tree/master/node-red
Nu alleen nog YAML leren ..
Reageren is niet meer mogelijk