52
submitted 9 months ago* (last edited 9 months ago) by taaz@biglemmowski.win to c/selfhosted@lemmy.world

I have a unused RPi4 (the 8Gig one) running DietPi. I did use it as a playground but ever since I am renting a Hetzner machine for (playground) stuff that I want web accessible, I don't have particular use for the Pi.

I am currently running (outdated) Home Assistant on it but there isn't much I can connect it with (yet, getting the flashable/compatible ikea smart lightning zigbee? bridge thingy is on my bucket list). Obviously I do have a pihole there.

Shoot me any other ideas I could run there. Some kind of monitoring of my rented infra would be cool (I already have uptime kuma on the dedi hetzner box). One idea I had was if there are some OSS security scanning "daemons" I could use on to monitor my other infra.

Thanks a lot!

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

Most people seem to just want to use RPIs as a very slow Linux server for some reason...

Use it to play around with hardware integration with the GPIO pins. Get a sensor HAT and start recording temperatures, write some code that turns on/off an LED, build a robot controller, etc. There are lots of kits and documentation on the various things you can do!

[-] mlaga97@lemmy.mlaga97.space 4 points 9 months ago

SBCs like the RPi are kind of awkwardly in-between a microcontroller like an Arduino or ESP32 that you can actually trust with handling GPIO and data logging, and a real Linux system that can actually do meaningful computational work.

Pretty much the only task I've found them reliably appropriate for is running OctoPrint, really really light computer vision tasks for robotics, or hooking up an RTL-SDR to use as a police/HAM scanner. Outside of those, it's so much easier to use either a cheaper and more reliable MCU or a much more powerful old laptop or desktop.

[-] atzanteol@sh.itjust.works 4 points 9 months ago

That's one of the nice things about them.

You can write code that has access to more resources. I had a RPI once that showed code build status on an led strip (red failed, green passed). It was a Java program that connected to AWS SQS for build event notifications. A micro controller would be much harder to do that on.

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

I've been wanting to use multiple raspberry pi zero w with sensory hats to feed data to a central home monitoring system. Would be a fun project.

[-] atzanteol@sh.itjust.works 2 points 9 months ago

It is! Especially if you want to write the code yourself. It's an interesting design problem if you start to consider cases where the PI may be offline (mobile on a battery in my case). Do you lose that data? Store and forward? In memory or to a local data store? It's a fun rainy-weekend project.

Word of caution - HATs can be a rather inaccurate in their temperature monitoring. The Pi gets warm. I had done my work using a PTC thermistor that was distanced from the Pi itself. I've got a friend using a HAT and it's been very off (up to 10C above ambient!). A Pi Zero may not give off as much heat as, say a Pi4 though. YMMV.

[-] taaz@biglemmowski.win 2 points 9 months ago* (last edited 9 months ago)

Unluckily last time I wanted to do sensor stuff the ~20 euro air quality multi-sensor (co2, pm1-10, humidity, voc?) board got lost in transit and I didn't bother since :(
The original plan was use it with my esp32 dev board (wroom32, so wifi) to have a portable sensor, this RPi was supposed to be the collection server (mqtt, influx, grafana).

I should revisit this idea soon, thanks for reminding me!

this post was submitted on 19 Jan 2024
52 points (88.2% liked)

Selfhosted

39700 readers
629 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