brian14
@russo-b · Joined December 2025
IT and security admin · energy
- Topics
- 4
- Replies
- 7
- Points
- 0
Forum Replies Created
Thanks, the explanation helped me write it up for my manager. Batched to one message every 2 minutes with 4 readings and keepalive 90 s first: no keepalive timeouts in a week. The yard AP on a bridge is approved for next month.
2.4 GHz, 20 MHz channels. The ESP32 can’t do 5 GHz anyway.
We’d rather push high severity events into our SIEM than poll the API. Any hook for that?
SDN was floating. Tied it through the library pin and init succeeded on the first try. Sender at the tank, receiver on a second Pro Mini that passes lines to the Pi over USB, 900 m with RSSI around -95. Tank level is in Hermetry as tank.level_cm. Thanks Eric, and Maria for the reminder about power limits, I backed it off.
Fixed. Interfaces file cleaned, static config in dhcpcd.conf with noipv4ll, rebooted the Pi ten times in a row this morning and the gateway connected within a few seconds every time. The Log tab now shows one clean connect per boot.
Yes, ifdown says interface eth0 not configured and ifup fails the same way afterwards.
Kept the check valves (maintenance lead agreed with jessicathompson37). My compressor 2 pipe was drawn from the receiver, as you guessed. Redrew both from the compressors, now only the running one animates. Compressor symbols appeared after purchasing asked about the Process library, we had only the core set. Bypass added.