techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

4.7K
active users

#influxdb

2 posts2 participants0 posts today

On the theme of #homebrew #beer , software, and #selfhosting I wanna give a shout out to a really cool solution for collecting fermentation data from the highly-popular #tilt hydrometer using Tilt-Pi, #influxdb , and #grafana :
github.com/StianJosok/tilt-pi-

My implementation is still a bit rough around the edges, but it allows me to track and visualize every fermentation, and even make the status of my beers visible when I am away from home! Props to GitHub user StianJosek for putting it together!!

Continued thread

This seems to be an issue with rtl_433 while using -F "influx://", not an issue with the firewall or InfluxDB docker container.

I can run a test python script from the same machine that is running the rtl_433 tool and write successfully to the remote InfluxDB instance. Also tried the same and different API Tokens as well as the same and different buckets just to check.

Unclear why rtl_433 can only write to a local InfluxDB instance.

#RTLSDR
#RTL433
#InfluxDB

I've been learning a lot about the rtl-433 library used with an RTLSDR v4 dongle and trying to capture data from my AcuRite 5 in 1 weather station.

Debian 12 currently has the following versions available through the package manager:

librtlsdr-dev (0.6.0-4)
rtl-sdr (0.6.0-4)
rtl-433 (22.11-1)

However, it seems like the driver for the v4 dongle is too old to properly support it. I kept getting the error:

bitbuffer_add_bit: Warning: row count limit (50 rows) reached

#RTLSDR
#RTL433
#InfluxDB

I've been postponing upgrading my InfluxDB v1 to v2 for months. When I finally decide to do it, I realize there is v3, but lots of people recommend to just stay on v1 (v2 has always been considered a bad idea anyway).

Now I have no idea what to do, and it will take a few other months to come up with a decision. 😄

Ja großartig.
Ich habe eine #Influxdb, scheinbar schreibt wenigstens ein #Telegraf dort hinein. Jetzt muß ich nur noch herausbekommen, wo dieses Telegraf läuft und was es schreibt 😀

Oh, einen Kandidaten habe ich gefunden: den Router.

root@sokoll-router:~# systemctl --full --no-pager status telegraf
* telegraf.service - The plugin-driven server agent for reporting metrics into InfluxDB
   Loaded: loaded (/lib/systemd/system/telegraf.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2025-03-12 06:25:26 CET; 2 months 19 days ago
     Docs: https://github.com/x70b1/telegraf-edgeos
 Main PID: 895 (telegraf)
   CGroup: /system.slice/telegraf.service
           `-895 /usr/bin/telegraf -config /etc/telegraf/telegraf.conf -config-directory /etc/telegraf/telegraf.d

Und dort finde ich unter anderem:
[agent]
  hostname = "router.sokoll"
  urls = ["https://a.sokoll.com:8086"]
  username = "telegraf"

Keine Ahnung, ob noch weitere Clients existieren.

Ja, ich bin Archäologe 😉