Be careful running it in a Pi because it’s a little heavy for that depending on how you configure it. A Pi model 4 is probably OK, but you wouldn’t want to run it on a model 3 or something even older, and you’re going to want to use one with at least 4GB of RAM.
It will probably run even in a Pi Model 1, it’s just going to be a bit slow to interact with, and you’re not going to be able to do anything more complicated like enable the voice support (which you probably don’t want anyway, because I think it’s dependent on internet access for that, and then we’re back to the same problem as Alexa, although I don’t use it myself so I can’t say for sure).
I’ll get a lot of hate for this but when you say pi you mean pi4. I kept seeing this HA on lemmy and tried it on a pi2. I don’t know if it worked or not, it’s a very bloated piece of software. After an hour of waiting I installed docker and the HA instance on my main server (which is ancient) in under a minute.
It’s cool and all but my feit dimmers require some pcb work and flashing to be compatible so verify what devices you have before you hop in.
I used to have an automated building running on a bare 386 and a floppy drive. Hate on me all you want but sending simple commands like turn device on shouldn’t require a giant software package but otherwise HA is neat, just a lot of overhead i can’t exactly justify.
To be fair It has its uses i suppose. I’ve had one running pihole since the original pi came out. Used PI2s in the past for OSMC and, even better, ambilight.
I think now a cheap android TV box you can flash is probably better for a simple less than 5watt device.
Besides the HA test I’ve been trying to use one to be an openvpn TAP interface but it’s been a fight and i think you just convinced me to do it in another docker instance on the server and save myself some headaches.
It seems like it would but the pivpn install script always hangs on me whether i I select openvpn or wireguard. Based on some reading I was lead to believe I needed to just use raw openvpn for a TAP interface. I’ve tried a few times but I always end up with CA issues or just flat out failure to connect.
It should be pretty simple, I’m just trying to bridge my network to a single remote device connected via cellular gateway. Maybe I’m just out of my depth. I’ve done it before with an old NAS years ago but I’ve tried a few step by step guides and no dice.
Yes. You can host it on a pi if you want
That’s badass. I’ve got one lying around actually.
Be careful running it in a Pi because it’s a little heavy for that depending on how you configure it. A Pi model 4 is probably OK, but you wouldn’t want to run it on a model 3 or something even older, and you’re going to want to use one with at least 4GB of RAM.
Ah shit, the raspberry I’ve got is old as hell. Thanks for the heads up.
It will probably run even in a Pi Model 1, it’s just going to be a bit slow to interact with, and you’re not going to be able to do anything more complicated like enable the voice support (which you probably don’t want anyway, because I think it’s dependent on internet access for that, and then we’re back to the same problem as Alexa, although I don’t use it myself so I can’t say for sure).
Saving the idea for a spare weekend. Cheers!
For when you get bored:
https://www.home-assistant.io/installation/raspberrypi/
I’ll get a lot of hate for this but when you say pi you mean pi4. I kept seeing this HA on lemmy and tried it on a pi2. I don’t know if it worked or not, it’s a very bloated piece of software. After an hour of waiting I installed docker and the HA instance on my main server (which is ancient) in under a minute.
It’s cool and all but my feit dimmers require some pcb work and flashing to be compatible so verify what devices you have before you hop in.
I used to have an automated building running on a bare 386 and a floppy drive. Hate on me all you want but sending simple commands like turn device on shouldn’t require a giant software package but otherwise HA is neat, just a lot of overhead i can’t exactly justify.
Worth trying out though.
I think reflow stole a lot of their code.
No hate from me.
Just about every project I’ve started with a pi has ended up working out a lot better as a vm on an x86 host. But lots of people seem to love them.
To be fair It has its uses i suppose. I’ve had one running pihole since the original pi came out. Used PI2s in the past for OSMC and, even better, ambilight.
I think now a cheap android TV box you can flash is probably better for a simple less than 5watt device.
Besides the HA test I’ve been trying to use one to be an openvpn TAP interface but it’s been a fight and i think you just convinced me to do it in another docker instance on the server and save myself some headaches.
PiVPN was actually one of the things I thought the HW handled pretty well. Other than how much it ends up getting throttled by the 100Mbps link.
It seems like it would but the pivpn install script always hangs on me whether i I select openvpn or wireguard. Based on some reading I was lead to believe I needed to just use raw openvpn for a TAP interface. I’ve tried a few times but I always end up with CA issues or just flat out failure to connect.
It should be pretty simple, I’m just trying to bridge my network to a single remote device connected via cellular gateway. Maybe I’m just out of my depth. I’ve done it before with an old NAS years ago but I’ve tried a few step by step guides and no dice.
If you have any tips that’d be great!
Wish I could help.
I used it a few years ago for a simple wireguard link but eventually moved the vpn into my opnsense instance