![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Saturday, January 9th, 2021 11:40 am
home assistant has released its own open source hub
Due to so much current stress I've been skipping out on my posting here. I really am not feeling doing an update on life at this time, but I want to spread this far and wide.
I talked about starting to use open source Home Assistant for my home automation needs with a Raspberry Pi. since then I updated to an 8 GB Pi and added booting from an SSD.
Now there's something a thousand times better: Home Assistant Blue - $150
This is Home Assistant's own Automation Hub built by them. You do not need to build anything, like a Pi; it's a single board computer with 4 USB hubs, 1 ethernet, 1 HDMI, with a 128 eMMC hard drive and 4G RAM with Home Assistant pre-installed and a very cool blue case.
It's plug and play. Literally, you plug it in and turn it on; that's it.
Below the cut is a copy of my tumblr post on a reblog about open source that breaks down everything you need to know
If you want to try but are still intimidated by the work to put together/work with a Pi, Home Assistant has your back, and I’m so excited to tell people about this.
Home Assistant Blue - $140.00
This is your all-in-one solution to open source home automation, built by open source developers, and buying it supports open source!!
This is what you get:
- the single board computer with 4 USB ports, one ethernet port, case, drive, and Home Assistant installed and ready to go.
- This is plug and play; all you gotta do is plug it in and then go to local address on your own computer to set up. That’s it; there is no other work required but buying shit for it to control.
A Pi kit with all the pieces you need is roughly $80 - $100; an SSD runs around $30 to whatever; the SSD case you need so you can attach it to the Pi can run from $8 to whatever.
This price is roughly $10-$25 higher (maybe) than buying a pi kit plus SSD hard drive and hard drive case, but not when you factor in the lack of work involved.
a.) You do not need to put the Pi together by hand. It’s easy and actually almost foolproof, but it can be intimidating if you’ve never done anything like that.
b.) You don’t need to flash an SD card or SSD with the latest version of HA; Home Assistant is already installed and ready to go.
c.) Home Assistant Blue, unlike a Pi, doesn’t run off an SD card: it comes with a hard drive installed. The only way to make a Pi run off a hard drive is to do a fairly basic firmware update but still, extra work. You don’t have to do it.
d.) This was literally designed for Home Assistant by the people who developed Home Assistant.
e.) Also, you get a kick ass official Home Assistant case in blue.
This is, I cannot emphasize enough, a really fucking good deal.
Here is what doesn’t come with it:
- No wifi module, but for Home Assistant, it should have it on ethernet anyway. You don’t need it.
- No bluetooth module - you can buy one for under $20, but honestly, I have yet to have anything use mine but to tell me the MAC of my headphones. With the exception of something that only runs bluetooth that you want to control, you don’t need it.
- No z-wave module - you can buy a usb dongle for under $40 or use an existing z-wave hub (example: SmartThings Hub). You probably need this if you use SmartThings,
- No zigbee module - you can buy a usb dongle for under $40 or use an existing zigbee or z-wave/zigbee hub (example: SmartThings Hub)
Pi kits don’t come with the last two either, so again, we’re talking a $15 difference for less work, less stress, and something designed and built to run Home Assistant.
Now, real talk on zigbee and z-wave:
Get a consumer grade hub and don’t start with open source when it comes to controlling z-wave and zigbee if you’re not ready to sit down and work out the pieces. It’s not hard, it’s super learnable, there are tutorials everywhere, but if you’re just starting out and aren’t used to diy, make it easy on yourself.
Your goal is to get total open source, but you can and should do it in steps as small and easy as you need; don’t over think it. This should be functional and fun, and I promise you, this is so much fun if you don’t assume you should know everything all at once. You can and will learn everything–I promise you, it’s great–but do it at a sane pace and not one where you throw anything against the wall like some people I maybe heard about but never did that myself even like, once.
I do this as my major hobby on weekends–I’m downloading info on how to build my own humidity and temperature sensors from parts–but I’m still using my SmartThings Hub until I get a weekend free of anxiety attacks and stress to learn how to pair z-wave and zigbee from first principles.
Consumer grade hubs mean it’s plug and play; you make sure the devices you have are compatible–or buy your hub and then your devices that are compatible–then set up. It’s easy.
Personal example: SmartThings Hub.
You can get a SmartThings Hub that controls zigbee and z-wave for about $40 - $60, but you’ll need to pay $5 a month for remote access to use it. But that $5 also covers remote access to Home Assistant when you’re not home, too, so you probably want to add that to your budget anyway.
Setup for a SmartThings Hub is like an hour or less. Pretty much two thirds of the existing home automation shit is compatible with SmartThings, but there’s Wink, Vera, and several others, so sit down and google a bit.
You can feel free to email, DM, ask, or whatever me if you’re jumping in and want some advice, help, or just someone you can say “WTF” to or “Can I make this purple????” (You probably can.) or just want a learning buddy. I’m not a developer, I don’t even have a college degree, everything I know I learned by fucking up in many creative ways, this is just my hobby, but I’m a QC analyst and work in User Acceptance Testing and lead testing for the mobile app for my state because when you’ve crashed your own system sixteen times in a month because you wanted to see what those batch jobs and config files did, you get surprisingly good at analyzing for problems or finding them by accident.
You cannot surprise me with weird problems; I’ve reviewed miles of javacript code at work that calling spaghetti would be very kind to find the reason for an error that turned out to be even weirder than the problem and this was written by professionals making six figures. Again, I crashed my home server sixteen times in a month fucking with config files I didn’t understand because why the fuck not. You gotta feel at least ten times more competent just reading that sentence and realizing that actually happened. I think I wrote about it in my DW under the tags “my relationship with electronics” or “coding”. It’s honestly alarming when you sit and think about it too long.
(And now I get paid to do that: they call it stress testing, and gave me database and batch permissions so I can do it in new and scary ways. I love my job, God.)
This is incredible fun, and my goal in life is to show everyone how much fun and accessible this can be to anyone.
More importantly, however, automation can be a gamechanger for people with physical disabilities/differences, the neuroatypical, the elderly, and the more people who jump aboard, the more we can make open source and non-corporate options mainstream. The more we do now, the easier it gets for those who come after us.
Home Assistant also has addons for running your own DNS server, DHCP server, database, Samba, HDMI CEC scanner, SSH, code editors, ABD server, Tor, encryptors, Plex, and I think the equivalent of pi hole (either official or community) and that's just to start. It can do kind of everything.
Official Stuff
Official Integrations
Official Add-Ons
Community Supported (non-official):
HACS
The number of community integrations you can get in HACS are an order of magnitude more than the official and then there's the UI stuff. And then there's the ones not even in HACS yet which you can find if you just google "Home assistant" and "Your Thing" which are like--well, a lot lot lot.
If I can get enough people interested in trying, I want to start a DW comm where people can ask questions, post tutorials, code, or just get support and help. It can be intimidating to start something like this, but help and support make everything easier and fun, and I'd love love love to work with/help/talk/support and/or be main venting person to anyone who jumps in.
I talked about starting to use open source Home Assistant for my home automation needs with a Raspberry Pi. since then I updated to an 8 GB Pi and added booting from an SSD.
Now there's something a thousand times better: Home Assistant Blue - $150
This is Home Assistant's own Automation Hub built by them. You do not need to build anything, like a Pi; it's a single board computer with 4 USB hubs, 1 ethernet, 1 HDMI, with a 128 eMMC hard drive and 4G RAM with Home Assistant pre-installed and a very cool blue case.
It's plug and play. Literally, you plug it in and turn it on; that's it.
Below the cut is a copy of my tumblr post on a reblog about open source that breaks down everything you need to know
If you want to try but are still intimidated by the work to put together/work with a Pi, Home Assistant has your back, and I’m so excited to tell people about this.
Home Assistant Blue - $140.00
This is your all-in-one solution to open source home automation, built by open source developers, and buying it supports open source!!
This is what you get:
- the single board computer with 4 USB ports, one ethernet port, case, drive, and Home Assistant installed and ready to go.
- This is plug and play; all you gotta do is plug it in and then go to local address on your own computer to set up. That’s it; there is no other work required but buying shit for it to control.
A Pi kit with all the pieces you need is roughly $80 - $100; an SSD runs around $30 to whatever; the SSD case you need so you can attach it to the Pi can run from $8 to whatever.
This price is roughly $10-$25 higher (maybe) than buying a pi kit plus SSD hard drive and hard drive case, but not when you factor in the lack of work involved.
a.) You do not need to put the Pi together by hand. It’s easy and actually almost foolproof, but it can be intimidating if you’ve never done anything like that.
b.) You don’t need to flash an SD card or SSD with the latest version of HA; Home Assistant is already installed and ready to go.
c.) Home Assistant Blue, unlike a Pi, doesn’t run off an SD card: it comes with a hard drive installed. The only way to make a Pi run off a hard drive is to do a fairly basic firmware update but still, extra work. You don’t have to do it.
d.) This was literally designed for Home Assistant by the people who developed Home Assistant.
e.) Also, you get a kick ass official Home Assistant case in blue.
This is, I cannot emphasize enough, a really fucking good deal.
Here is what doesn’t come with it:
- No wifi module, but for Home Assistant, it should have it on ethernet anyway. You don’t need it.
- No bluetooth module - you can buy one for under $20, but honestly, I have yet to have anything use mine but to tell me the MAC of my headphones. With the exception of something that only runs bluetooth that you want to control, you don’t need it.
- No z-wave module - you can buy a usb dongle for under $40 or use an existing z-wave hub (example: SmartThings Hub). You probably need this if you use SmartThings,
- No zigbee module - you can buy a usb dongle for under $40 or use an existing zigbee or z-wave/zigbee hub (example: SmartThings Hub)
Pi kits don’t come with the last two either, so again, we’re talking a $15 difference for less work, less stress, and something designed and built to run Home Assistant.
Now, real talk on zigbee and z-wave:
Get a consumer grade hub and don’t start with open source when it comes to controlling z-wave and zigbee if you’re not ready to sit down and work out the pieces. It’s not hard, it’s super learnable, there are tutorials everywhere, but if you’re just starting out and aren’t used to diy, make it easy on yourself.
Your goal is to get total open source, but you can and should do it in steps as small and easy as you need; don’t over think it. This should be functional and fun, and I promise you, this is so much fun if you don’t assume you should know everything all at once. You can and will learn everything–I promise you, it’s great–but do it at a sane pace and not one where you throw anything against the wall like some people I maybe heard about but never did that myself even like, once.
I do this as my major hobby on weekends–I’m downloading info on how to build my own humidity and temperature sensors from parts–but I’m still using my SmartThings Hub until I get a weekend free of anxiety attacks and stress to learn how to pair z-wave and zigbee from first principles.
Consumer grade hubs mean it’s plug and play; you make sure the devices you have are compatible–or buy your hub and then your devices that are compatible–then set up. It’s easy.
Personal example: SmartThings Hub.
You can get a SmartThings Hub that controls zigbee and z-wave for about $40 - $60, but you’ll need to pay $5 a month for remote access to use it. But that $5 also covers remote access to Home Assistant when you’re not home, too, so you probably want to add that to your budget anyway.
Setup for a SmartThings Hub is like an hour or less. Pretty much two thirds of the existing home automation shit is compatible with SmartThings, but there’s Wink, Vera, and several others, so sit down and google a bit.
You can feel free to email, DM, ask, or whatever me if you’re jumping in and want some advice, help, or just someone you can say “WTF” to or “Can I make this purple????” (You probably can.) or just want a learning buddy. I’m not a developer, I don’t even have a college degree, everything I know I learned by fucking up in many creative ways, this is just my hobby, but I’m a QC analyst and work in User Acceptance Testing and lead testing for the mobile app for my state because when you’ve crashed your own system sixteen times in a month because you wanted to see what those batch jobs and config files did, you get surprisingly good at analyzing for problems or finding them by accident.
You cannot surprise me with weird problems; I’ve reviewed miles of javacript code at work that calling spaghetti would be very kind to find the reason for an error that turned out to be even weirder than the problem and this was written by professionals making six figures. Again, I crashed my home server sixteen times in a month fucking with config files I didn’t understand because why the fuck not. You gotta feel at least ten times more competent just reading that sentence and realizing that actually happened. I think I wrote about it in my DW under the tags “my relationship with electronics” or “coding”. It’s honestly alarming when you sit and think about it too long.
(And now I get paid to do that: they call it stress testing, and gave me database and batch permissions so I can do it in new and scary ways. I love my job, God.)
This is incredible fun, and my goal in life is to show everyone how much fun and accessible this can be to anyone.
More importantly, however, automation can be a gamechanger for people with physical disabilities/differences, the neuroatypical, the elderly, and the more people who jump aboard, the more we can make open source and non-corporate options mainstream. The more we do now, the easier it gets for those who come after us.
Home Assistant also has addons for running your own DNS server, DHCP server, database, Samba, HDMI CEC scanner, SSH, code editors, ABD server, Tor, encryptors, Plex, and I think the equivalent of pi hole (either official or community) and that's just to start. It can do kind of everything.
Official Stuff
Official Integrations
Official Add-Ons
Community Supported (non-official):
HACS
The number of community integrations you can get in HACS are an order of magnitude more than the official and then there's the UI stuff. And then there's the ones not even in HACS yet which you can find if you just google "Home assistant" and "Your Thing" which are like--well, a lot lot lot.
If I can get enough people interested in trying, I want to start a DW comm where people can ask questions, post tutorials, code, or just get support and help. It can be intimidating to start something like this, but help and support make everything easier and fun, and I'd love love love to work with/help/talk/support and/or be main venting person to anyone who jumps in.
