1133
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Jul 2023
1133 points (97.1% liked)
Selfhosted
40708 readers
459 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
I wish Home assistant was more conducive to running on Kubernetes. I tried it but so much of the local discovery doesn't work without being in the same LAN as all your IoT devices.
There's an easy answer to that...don't use IoT devices. I recently rebuilt my HA setup into a VM running on Proxmox, added a Zoos USB to ZWave dongle and then replaced every device that needed a network connection with a Z-Wave device. I have nothing left that needs, or can even connect to, the Internet and all of my routines / automations are fully local. I can turn my Router off and the only thing it will impact is remote access and voice control.
True. I kind of consider IoT a category of device nomenclature but that's not true.
I run my instance via docker-compose, and it's just a matter of setting
network_mode: hoston the container (in the YAML).I'll have to take another crack at it sometime. You can do all kinds of container privilege modification in Kubernetes and maybe I just missed the one I need to set. I'll try to find the analog for the one you shared here. Thanks!
Looks like it's not all that hard, jsut have to give home assistant some additional permissions to networking at a lower level of the stack