Overview
AI reading
Loading…
quietbusy
Checking your session…
Loading…
Loading…
Loading…
Loading…
Loading…
Projected runtime
What the old schedule did
Same comparison, held against one variable at a time
Detail
Loading…
A new Shelly gets its own ingest token — it can never mix into another circuit's readings. After creating it, wire it with the command shown.
Marginal cost per extra kWh, derived from each bill. Sessions keep the rate that was live when they ran.
The nightly watchdog (9:00 am ET) pushes what changed: a silent meter, the 400 kWh tier, a Pepco rate change, a step in the standing load, an overdue bill or Green Button import, and the water-heater follow-ups from the Testing page. One publish per event — a phone push via the webhook, plus an email copy if an address is set. Silence means nothing needs you.
The easiest is ntfy — free push notifications, no account:
https://ntfy.sh/<your-topic> as the webhook URL here and save. Send a test message from the ntfy app to prove the pipe.A Slack or Discord channel webhook works too — paste its URL instead, no other changes. The email field rides the same ntfy publish, so it needs an ntfy-style URL to work.
Muted categories still appear on the Overview page — they just stop pushing. Re-enabling a reminder resumes it if the work is still owed.
Arm/disarm history turns an empty home from a guess into a measurement.
Ring keeps only about 60 days, so this records nightly — a day missed is gone.
Mint a token with npx -p ring-client-api ring-auth-cli; it is stored
write-only and never read back.
The Pi draw figures only model the estimate on the Raspberry Pi tab; measure once with a plug meter to calibrate them.