[frahlg]

Problem

xorath, 5 Nov 2026: a battery charged 2.3 kW while FTW asked it to discharge 812 W. The box's page said Not following, and no phone heard. Core works out control_feedback only when someone asks for /api/status, and no notification rule read it.

Change

• A new catalogue-worded rule, control.not_following (go/internal/notifications/control.go):
  • On the HealthTick it reads the box's own answer, at most every 30 s. api.Server.ControlStates is the same builder /api/status serves, so a push never says what the box's page does not.
  • It fires once a device function has been not_following for the rule's threshold (default 600 s). It fires once until that device follows again, with the rule's cooldown on top (default 3600 s). The key is driver and kind.
  • The words come from the catalogue: "A device is not following FTW" / "{name} does not do what FTW asks. Open FTW to see why." {name} is the driver, as in driver.offline.
• The rule is on by default for owners who have notifications on (Fredrik, 5 Nov 2026). A box whose stored rules predate the kind takes the default, as FTW Cloud's own notices do. GET /api/notifications/rules already offers missing kinds at their default, so the phones' switches show it on.
• Settings → Notifications shows a threshold field for a stored control.not_following rule, as it does for the fuse rule.
• The changeset is minor, for a visible new notification. Fredrik asked for it ("kör på").

#1864 also edits service.go, but in dispatch/deliver. This PR touches the rule lists, the struct and Subscribe, so the two do not overlap.

Pairs

srcfl/ftw-webapp#117 holds the catalogue and the switch's label, and goes first. srcfl/ftw-app follows, with the copy, the phone's words and the iPhone's choices.

Contract-pair: srcfl/ftw-webapp@66f0797

Evidence

• make verify is clean on this machine.
• New tests:
  • TestControlNotFollowingTellsTheOwnerOnceAfterTenMinutes: quiet for ten minutes, one message with the catalogue's words, nothing more while still not following, the cooldown holds after a brief recovery, a second message after the hour, and at most one read in 20 s of ticks.
  • TestControlNotFollowingStaysQuietWhenTurnedOff: the rule off, or notifications off.
  • TestControlNotFollowingIsARuleThePhonesCanSet.
  • TestControlStatesAreTheStatusDocumentsVerdicts: a battery charging 4.4 kW against a 5 kW discharge reads not_following (power_wrong_direction) in both.
• TestRulesPutSeedsDefaultsOnFirstTouch now lists the kind among those on by default.
• I rendered the settings tab locally in a browser. The rule shows Threshold, Priority and Cooldown, like fuse.over_limit.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-05T14:03:09.470832Z	4fc3194	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4fc3194c60

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Reset the control observation window when notifications are disabled

If notifications are disabled after this rule has observed a device not following, this early return preserves controlFirstAt throughout the disabled period. Service.Reload also leaves that map intact, so reenabling notifications can immediately count the entire disabled interval toward the ten-minute threshold—even if the device recovered and only just started failing again. This can send an alert without the required sustained observation window. Clear the control observation state when disabling notifications or reset it on reload, while retaining lastFired for cooldown enforcement.

Useful? React with 👍 / 👎.