New: the AI firewall watches the whole platform and explains each incident in plain words. See how it works

Rachel Roberts

rachelr77

@roberts-r · Joined November 2025

Newcomer

Facility manager · buildings · new to IoT

Topics
2
Replies
34
Points
0
Newcomer10 points to Member

Forum Replies Created

Viewing 15 posts – 1 through 15 (of 34 total)

I’m new to IoT too, but we did exactly this for soap dispensers in our buildings last year and fought the same e-mail flood, so here’s what ended up working.

Send a fill level in percent instead of millimetres, it’s easier for the cleaners to understand: fill_pct = (190 - dist) / 150 * 100 on the ESP32. Then add debounce and hysteresis to the rule so one odd reading can’t open it, and a reading hovering at the limit can’t close and reopen it. Ours, adjusted to your numbers:

{
  "type": "paper_low",
  "title": "{{device.name}}: paper at {{value}} %",
  "severities": [
    { "severity": "WARNING", "condition": { "key": "fill_pct", "op": "<", "value": 20 } }
  ],
  "debounce": { "mode": "count", "raise": 4, "clear": 2 },
  "hysteresis": 10,
  "notify": {
    "recipients": [ { "kind": "email", "email": "cleaning-lead@yourcompany.example" } ],
    "minSeverity": "WARNING"
  },
  "enabled": true
}

With readings every 30 s, raise 4 means it has to be low for about 2 minutes in a row, and it only clears once it’s back above 30 % (after a refill). Paste it in the profile’s Alarm rules tab in JSON mode. E-mail only goes to explicit addresses in the notify block, so use the supervisor’s address there, not a role. Name the devices after the restroom (“2F Men, towels”) because the title uses the device name. The debounce settings are explained on Debounce, hysteresis and dampening.

Timestamps in UTC or it didn't happen.
Accepted solution♥ 2

Built my first one this morning following the getting started page. Took me a while to work out that you resize a card by dragging its corner, my chart was a thin strip at first and I thought the data was wrong lol

Timestamps in UTC or it didn't happen.
♥ 0

I am new to the IoT side but HVAC I know a bit from our buildings, and we had the same discussion with our installer.

Leave the mains alone. Most wall splits of that size have a connector on the indoor unit board for an external on/off contact (installers use it for key card switches in hotels and for fire panel shutdown). Some brands need a small interface adapter for it, the installer will know the part number for your model. A closed contact means run, open means stop, and the unit does its normal start and stop sequence, so the compressor is protected and it restarts after a power cut on its own logic.

So the plug relay does not switch the AC load any more, it only switches that low voltage contact. Your ESP8266 firmware and the plug.set command stay exactly as they are; I would rename it to something like ac.enable so nobody thinks it cuts power.

On the Hermetry side what we did:

  • the command is Basic tier in the profile’s Commands tab, otherwise the board will not send it
  • Switch card, Current state bound to a key the unit really reports (we read the indoor unit’s run status contact, ac.running), not to the command
  • a rule: room.temp rises above 27 and stays so for 5 minutes, then Send a command ac.enable with on true, then Tell people

The control card page explains the tier and current value parts: Control cards. Reading back the real state is the part that saved us, a switch that shows “on” because you clicked it is worse than no switch.

Timestamps in UTC or it didn't happen.
Accepted solution♥ 1
Viewing 15 posts – 1 through 15 (of 34 total)