10
submitted 9 months ago* (last edited 9 months ago) by TCB13@lemmy.world to c/selfhosted@lemmy.world

Hello,

My IoT/Home Automation needs are centered around custom built ESPHome devices and I currently have them all connected to a HA instance and things work fine.

Now, I like HA's interface and all the sugar candy, however I don't like the massive amounts of resources it requires and the fact that the storage usage keeps growing and it is essentially a huge, albeit successful, docker clusterfuck.

Is there any alternative dashboard that just does this:

  1. Specifically made for ESPHome devices - no other devices required;
  2. Single daemon or something PHP/Python/Node that you can setup manually with a few systemd units;
  3. Connects to the ESPHome devices, logs the data and shows a dashboard with it;
  4. Runs offline, doesn't go into 24234 GitHub repositories all the time and whatnot.

Obviously that I'm expecting more manual configuration, I'm okay with having to edit a config file somewhere to add a device, change the dashboard layout etc. I also don't need the ESPHome part that builds and deploys configurations to devices as I can do that locally on my computer.

Thank you.

you are viewing a single comment's thread
view the rest of the comments
[-] b1g_bake@sh.itjust.works 18 points 9 months ago

How has home assistant become a resource monster? What kind of integrations are you using aside from ESPHome?

[-] Zeoic@lemmy.world 10 points 9 months ago

Yeah, home assistant is tiny... I'm not sure what he expects? Does he need it to run on a pi zero or something? Lol

[-] mangaskahn@lemmy.world 1 points 9 months ago* (last edited 9 months ago)

He's trying to run it on an esp32, didn't you read the title? /s

[-] TCB13@lemmy.world -4 points 9 months ago* (last edited 9 months ago)

Tiny you say... answer to what you asked: https://lemmy.world/comment/7101252

[-] TCB13@lemmy.world -4 points 9 months ago

I'm not using any other integration. Isn't this a resource monster?

I just don't want to keep running an entire VM with their image. Something more simple that could be used on a LXC / systemd-nspawn container or directly on a base system would be nicer.

[-] ikidd@lemmy.world 10 points 9 months ago

It's half a GB of ram and virtually no CPU usage. You could run it on a Pi 3 with a 16Gb SD card and have resources to spare.

This is just weird.

[-] TCB13@lemmy.world 1 points 9 months ago

What is weird is having to waste almost 700MB of ram + 10GB of storage for a simple webui that charts sensor data and only keeps it for 10 days. As a comparison my NAS container runs Samba4, FileBrowser, Syncthing, Transmission, and a few others under 300MB of RAM with pontual spikes on operations.

[-] ikidd@lemmy.world 2 points 9 months ago

There's a lot of difference between a container and a VM. You can install HA on a container, all you have to do is set it up according to the manual install instructions, and work around any hardware interfacing issues that come up. You'll save 200MB of RAM and will have to do any upgrades manually. Doesn't seem worth it to me, but to each their own.

[-] TexMexBazooka@lemm.ee 1 points 9 months ago

You have found the smallest, tiniest, itty bittiest potatoe to get upset about here. You could run this on a toaster.

[-] scarilog@lemmy.world 4 points 9 months ago

In what world is this is a resource monster??

[-] TexMexBazooka@lemm.ee 3 points 9 months ago

If this is what you consider a resource monster you’re gonna have a really, really rough time

[-] b1g_bake@sh.itjust.works 1 points 9 months ago

Do you have the entire hass-os image running in a VM?

[-] TCB13@lemmy.world 1 points 9 months ago
this post was submitted on 28 Jan 2024
10 points (70.8% liked)

Selfhosted

39700 readers
652 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS