reddysi
@nreddy · Joined November 2025
System integrator · water and wastewater · 6 years in the field
- Topics
- 3
- Replies
- 14
- Points
- 0
Forum Replies Created
Put hysteresis on the battery rule, something like below 20 with a margin of 5. Cold mornings make batteries dip and you’ll get an alarm every dawn otherwise.
Did exactly this for a client last week. The dry run listed two cards as Skipped, both process diagram cards, because the client org didn’t have the SCADA module on yet. Turned it on, deleted the first import, imported again and all 14 cards came across. Read the dry run, it tells you exactly which card and why.
Question on the webhook part. Does “repaired after an outage” mean the calls that came in during the outage get run afterwards, or only that the trigger comes back by itself?
Water site sounds very close to my day job, tanks and pump stations. Is it included or does it need something extra on the plan?
Both work, I have both in the field. On Bookworm it’s much less fiddly, NetworkManager does the AP and the NAT in one go:
sudo nmcli dev wifi hotspot ifname wlan0 ssid shed-iot password 'long-passphrase-here'
sudo nmcli con mod Hotspot connection.autoconnect yes ipv4.method sharedipv4.method shared hands out DHCP to the ESP32s and NATs them out of whatever has the default route, your 4G dongle. The Pi’s onboard Wi-Fi is fine for 8 clients at short range.
Where I’d think twice is heat and SD cards, plus nobody can reach the Pi when it hangs. If you go Pi: metal case as heatsink, a decent industrial SD or USB SSD, read-only root if you can, and the hardware watchdog enabled.
What a licensed router gives you on Hermetry for the money: you claim it with the code on its local Cloud page, it logs in with its own certificate, you can change its settings and update its firmware from Hermetry, and you can open its web panel from its device page without a fixed IP, which on a 4G link you won’t have. It’s a device in your org itself and counts once against the device limit. Remote access sessions are time-limited and audited.
My rule: one site I can drive to, Pi. Sites that need a ute and a day, licensed router. Details: Licensed gateways and Hermetry Edge.
Is VREF tied to 3.3 V? If VREF floats you get exactly that 0 / 1023 behaviour.
Complementary filter at 0.98 and a timer-driven loop, and it stands. Tuned it with P=18, D=0.6, a tiny I, plus a 6 % deadband. The 1 message per second batches at 20 Hz work, no more rate_limit, and the angle chart on the booth board looks great. My mistake was publishing from inside the control loop, every publish stretched the loop and made the oscillation worse too.
That explains the disconnects. So how do people get fast data for tuning, without getting kicked?
For 80 m and 12 nodes I’d not go I2C, even with extenders the capacitance adds up. CAN would work fine, MCP2515 boards are cheap. But RS-485 with Modbus is easier to debug with a USB dongle and a laptop.
Keys expire after 90 days by default (a year at most), so put a reminder somewhere or your shortcut dies quietly in three months. And keep the key file chmod 600, not in your dotfiles repo.
Client’s mechanic welded simple guide rails onto the docks, and I changed the robot code to check charge current with 3 retries. Two weeks, one failed dock, and that one showed up red on the site view within a minute, so someone went over. Added Rachel’s battery alarm too.
No. It declares “docked” when the IR signal is strongest and stops.
NM is “not mounted”, same as DNP (do not populate). The footprint is on the board but no part goes in it.
rc=2 is “client ID rejected”. Colons are allowed in Hermetry client IDs (letters, digits and . _ : -, 1 to 64 chars), so it’s not the MAC format. Something else is getting into the ID.