this post was submitted on 28 Jan 2024
11 points (69.0% liked)

Selfhosted

40394 readers
391 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 2 years ago
MODERATORS
 

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
[–] TCB13@lemmy.world -3 points 10 months ago (4 children)

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 11 points 10 months ago (1 children)

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 3 points 10 months ago (2 children)

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 6 points 10 months ago (1 children)

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.

[–] TCB13@lemmy.world 1 points 10 months ago (1 children)

What I'm going to do is setup HA Core on a container manually and run without addons / docker. That will be about installing python and should waste way less resources.

[–] iarigby@lemmy.world 1 points 10 months ago (1 children)

setup on a container run without docker

??

[–] TCB13@lemmy.world 2 points 10 months ago* (last edited 10 months ago) (1 children)

If you don't need the addons you don't need Docker. HA Core is a python script with a few dependencies that can run with pyenv and a simple systemd service unit at every boot.

[–] iarigby@lemmy.world 1 points 10 months ago (1 children)

yeah but that’s not setting up a container that’s just setting up python env

[–] TCB13@lemmy.world 1 points 10 months ago (1 children)

Yes, but I would rather do it inside a LXC container.

[–] iarigby@lemmy.world 1 points 10 months ago

ah got it, thanks

[–] TexMexBazooka@lemm.ee 0 points 10 months ago (1 children)

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

[–] TCB13@lemmy.world 2 points 10 months ago

I'm not upset, just wondering / looking for way to keep the potato from growing further and/or alternatives.

[–] TexMexBazooka@lemm.ee 6 points 10 months ago (1 children)

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

[–] TCB13@lemmy.world 2 points 10 months ago (1 children)

This isn't reasonable at all, 700MB of ram + 10GB of storage for a simple webui that charts sensor data and only keeps it for 10 days.

[–] eatfudd@lemm.ee 2 points 10 months ago (1 children)

You need to edit your configuration.yaml file to exclude certain sensors or values. I excluded some of the more chatty sensors that I didn't need and my disk use went from around 40gb to 150mb

[–] TCB13@lemmy.world 1 points 10 months ago

Interesting. I'll have to check what might be logging so much info.

[–] scarilog@lemmy.world 5 points 10 months ago

In what world is this is a resource monster??

[–] b1g_bake@sh.itjust.works 1 points 10 months ago (1 children)

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

[–] TCB13@lemmy.world 1 points 10 months ago