OMG - What a ride... after tinkering and yelling at clouds @nocci was able to fix a lot of #NodeRED Code so my flow is way cleaner.
First pic is the whole mess noccis brain spit out yesterday and second shows his work after putting some "real" coding effort into this thing here. (now there are emojis)
(there are maybe some useful infos for you in the alt-text)
nodered
Stay informed about the latest radiation levels in northern Germany (in a small town called Schleswig) with this small and tiny bot.
It retrieves microsievert (µSv) data every hour from an #ESPHome device, seamlessly integrated with #HomeAssistant and #NodeRed.
This data is then forwarded to this #Sharkey instance, ensuring you receive timely updates on your social media feed.
Stay safe and stay informed! 
![Avatar for nocci [cyberpunk'd]](/proxy/identity_icon/431646236504492650/e65214abdf.png){kind=icon}
Over the past few days, I "channeled" my inner nerd into building an automated radiation detection system using open-source tools.
The device combines an ESP32 running #ESPHome for sensor data collection, my #HomeAssistant for centralized smart home integration, and #NodeRED for automating hourly Fediverse updates via a bot account
@Radiation_SL (since this Geiger counter is located in northern Germany ( #Schleswig )
Technical Breakdown:
Sensor: Radiation D-v1.1 (CAJOE) - radiation detector
Connectivity: ESP32 transmits via Wi-Fi to Home Assistant
Case: #3dPrinting the case (photo) - base is black and the lid is blue and shows the logo of "Fallout" (pc game/ TV series)
Automation: Node-RED flow formats data into ActivityPub messages
Decentralized Sharing: Posts include μSv/h readings
While this started as a hardware tinkering project, recent global events — nuclear rhetoric in conflict zones, aging power plants, and insufficient transparency in environmental monitoring — made me realize decentralized citizen science could play a crucial role.
Open-source tools eliminate single points of failure, and Fediverse integration ensures censorship-resistant data sharing.
Feel free to follow my bot account I mentioned above, if you are interested.
If I can find some time I will write a blogpost about the build process and link it in the bio / or just toot about it.
Got #homeassistant installed and connected to my MQTT server. Successfully detected 300+ devices - everything except my #zigbee switches it appears. If I can't get them into HA, there's no point in even thinking about trying to migrate from #nodered.
More tinkering tomorrow, I think.
Smart Home ohne Cloud
Wann: 20.04.2023, 19:30 Uhr
Wo: WIR Haus, Wülfrath
OSM: https://www.openstreetmap.org/relation/14772094
Wir spüren die hohen Engergiekosten. Wir zeigen Euch was Ihr dagegen tun könnt.
Alle sprechen über #smarthome aber wir leben es. Habt Ihr schonmal was von #homematic oder #nodered gehört?
Wir haben das #wirhaus im #KreisMettmann in #Wülfrath deutlich optimiert und den Energieverbrauch drastisch gesenkt.
#Heizungssteuerung #Energie #Freifunk #Gasheizung #hackspace #mqtt #Jugendhackt
Hi, I'm Sam! I taught myself #programming in the '80s on a Commodore 64 and an IBM PC XT with QBasic. Now I'm a software developer at IRCCloud, building #Android and #iOS apps in #java and #ObjectiveC. Previously I worked on #music streaming apps at Last.fm.
Here are a few topics I'm interested in:
#photography
#cooking
#gaming especially in #VR
#linux on #raspberrypi
#homeautomation using #homeassistant, #python, and #nodered
GitHub: https://github.com/c99koder
Okay, so let me tell you about my doorbell, from a #networking perspective.
When you push the button by the door, it sends a message over the #zigbee wireless mesh network in my house. It probably goes through a few hops, getting relayed along the way by the various Zigbee light switches and "smart outlets" I have.
Once it makes it to my utility closet, it's received by a Zigbee-to-USB dongle, through a USB hub (a simple tree network) plugged into an SFF PC. From there, it gets fed into zigbee2mqtt, which, as the name implies, publishes it to my local #mqtt broker.
The mqtt broker is in the small #kubernetes cluster of #raspberrypi nodes I run in my utility closet. To get in (via a couple of #ethernet switch hops), it goes through #metallb, which is basically a proxy-ARP type service that advertises the IP address for the mqtt endpoint to the rest of my network, then passes the traffic to the appropriate container via a #linux veth device.
I have #HomeAssistant, running in the same Kubernetes cluster, subscribed to these events. Within Kubernetes, the message goes through the CNI plugin that I use, #flannel. If the message has to pass between hosts, Flannel encapsulates it in VXLAN, so that it can be directed to the correct veth on the destination host.
Because I like #NodeRed for automation tasks more than HomeAssistant, your press of the doorbell takes another hop within the Kubernetes cluster (via a REST call) so that NodeRed can decide whether it's within the time of day I want the doorbell to ring, etc. If we're all good, NodeRed publishes an mqtt message (more VXLANs, veths, etc.)
(Oh and it also sends a notification to my phone, which means another trip through the HomeAssistant container, and leaving my home network involves another soup of acronyms including VLANs, PoE, QoS, PPPoE, NAT or IPv6, DoH, and GPON. And maybe it goes over 5G depending on where my phone is.)
Of course something's got to actually make the "ding dong" sound, and that's another Raspberry Pi that sits on top of my grandmother clock. So to get *there* the message hops through a couple Ethernet switches and my home WiFi, where it gets received by a little custom daemon I wrote that plays the sound via an attached #HiFiBerry board. Oh but wait! We're not quite done with networking, because the sound gets played through PulseAudio, which is done through a UNIX domain socket.
SO ANYWAY, that's why my doorbell rarely works and why you've been standing outside in the snow for five minutes.
