Skip to content

2.8.0 — poll only what you use (beta)

Latest

Choose a tag to compare

@nerdaxic nerdaxic released this 09 Jul 12:24

Beta release — the production resolution of the ProjectorService crash investigation (#1), and a rework of how polling works. This is the candidate for 3.0.0: it will be promoted to stable after an extended period of real-world use and the full hardware click-through in TESTING.md.

Polling now follows your entities

  • Only enabled entities are polled. Disable an entity in the UI and its RS232 query disappears from the cycle. Fewer enabled entities = shorter cycles = fresher values.
  • Device details are read once at startup (firmware, MAC, serial) instead of every cycle, retried only until the projector reports real values.
  • The interval adapts to power state: your configured interval while the projector is on, relaxed to ≥60 s in standby. The projector's own power-on push (or an HA power command) restores fast polling instantly.
  • Poll-interval changes from the options flow apply live, no restart.

UHZ68LV firmware bug — resolved by default

The investigation in #1 traced the "ProjectorService: Central service has been disconnected" toast to the projector's own firmware: the IP-address query ~XX87 3 intermittently (~1 in 20 calls) crashes its internal service on firmware DDP C22 / MCU M12 / Scalar S32. The IP Address sensor ships disabled, and disabled entities are never polled — so a default install never sends the query. If you enable that sensor and see the toast, disable it again (documented in the README's known issues). Reported to Optoma.

Also included (since 2.7.0)

  • Dolby Vision: added Dolby Vision Vivid, corrected the DV read-back codes (45/46/47 — hardware-validated; the official command table is wrong here).
  • Filmmaker Mode picture mode (write 54 / read 52), available for SDR and HDR content.
  • README: usage examples, rewritten polling docs, beta status.
  • TESTING.md: the hardware verification checklist gating the 3.0.0 stable release.

Known gap: HDR10+ has no confirmed read-back code (#2) — selecting it works; the Picture Mode sensor may show a raw number while HDR10+ content plays.

Diagnostic pre-releases 2.7.1–2.7.3 (branch test/no-polling) served the crash investigation and are superseded by this build; that branch is now closed.