v10.5.3 — mark_events_read default flipped to OFF
What changed
mark_events_read default flipped to OFF. v10.5.2 introduced the option but kept the previous behaviour as default — events were still being marked as read on the Bosch cloud after HA processed them, which silently consumed the "new event" highlight in the Bosch app for users who only use HA for live streaming.
The default in OPTIONS_DEFAULTS, in the Configure dialog, and in all five gating call sites now resolves to False — fresh installs and existing installs that never explicitly toggled the option both stop firing PUT /v11/events {isRead: true}. The Bosch app keeps treating new events as unread regardless of whether HA already saw them.
Who is affected
- Default user (HA + Bosch app side-by-side): new behaviour — events stay unread in the Bosch app, just like when no integration is installed. This is what most users expect.
- HA-as-primary-client user: if you prefer the v10.5.2 behaviour (HA marks events read so the app doesn't show stale "new event" badges), enable it via Integration → Configure → Mark Bosch cloud events as read.
Local dedup via _last_event_ids is unaffected — automation triggers on binary_sensor.bosch_*_motion continue to fire normally.
Reported by
Thanks to xDraGGi on the simon42 forum (Topic 81743 / Post 366006) for surfacing this.