v1.11.0

Added

• Internal temperature for the MotionProtect Curtain Outdoor Plus / Base (#229). Unlike the Mini, the Plus and Base variants don't carry an internal-temperature field in the per-device gRPC data, so no temperature sensor appeared. Their temperature is now read from the hub's HTS status channel (the same channel the WallSwitch electrical readings use) and surfaced as the standard temperature sensor. The reading is additive and safe: it only fills in when no temperature is already provided over gRPC, so every other device is untouched, and an implausible value is declined rather than shown.

Fixed

• Per-group/zone alarm panels follow an app-side arm/disarm without push (#266). Arming or disarming a single group (e.g. a dedicated "Garage" zone) from the Ajax app only changes that group's state, which the lightweight per-cycle poll doesn't carry — per-group state comes from the heavier hourly snapshot. The space-level panel already re-read its state on the hub's arm/disarm event, but group panels didn't, so without FCM push a zone panel could lag up to an hour behind. The same hub event now also forces an immediate re-read of group states, so per-group panels update within about a second on installs without push (and remain instant with push). The heavier read runs only on an actual arm/disarm event, not on every poll.

Documentation

• Clarified that arm/disarm panel state now follows within ~1 s without push. The README's FCM comparison table and account-separation tip still said app-side arm/disarm only updated on the next poll without FCM; since the hub status-event re-read (space panel, then per-group panels) that's no longer true. Real-time event notifications (alarm, doorbell, motion) still require FCM.