v1.2.34

What's Changed

• Record verified diagnostics release and Pi deployment by @jjziets in #10
• Fix panel session recovery and stale phone/watch status by @jjziets in #11

Full Changelog: v1.2.33...v1.2.34

Bridge 1.0.13

What's Changed

• Fix live PAI constructor compatibility for bridge 1.0.13 by @jjziets in #12

Full Changelog: bridge-v1.0.12...bridge-v1.0.13

Bridge 1.0.12

Bridge 1.0.12 is withdrawn from stable automatic deployment.

Live qualification found that this Pi's PAI 3.7.0 installation already had the definitions_loaded subscription typo corrected. The new adapter assumed the stock typo and failed initialization while removing the absent subscription. The signed updater rejected the release's fresh-panel check and successfully rolled back to healthy 1.0.11.

This release is marked pre-release so normal signed update discovery skips it. The immutable tag and signed artifacts are retained for evidence. Do not force-install it. A separately tested and signed follow-up version will normalize either subscription variant without changing credentials, TLS keys or alarm control semantics.

Phone/watch 1.2.34 is separate and its tests and signed builds passed.

v1.2.33

Phone 1.2.33 (build 82) and watch 1.2.33 (build 27).

Diagnostics

• New phone Settings > Diagnostics > Send diagnostic report collects phone and watch logs, including watch quick-panel activity.
• Bounded private 24-hour logs exclude tokens, PINs, raw payloads and sensor names.
• If the Pi is offline, the capture is saved privately for retry. Delivery is confirmed only after a matching Pi receipt.
• Reports use pinned HTTPS and your existing login.

Install the phone update, then update the watch from phone Settings. The Pi endpoint requires bridge 1.0.11, published separately through the signed Pi release pipeline.

This release collects evidence for the intermittent panel communication issue. It does not claim to fix that underlying fault.

Guide: https://github.com/jjziets/Remote-Paradox/blob/main/docs/client-diagnostics.md
Implementation: #9

Bridge 1.0.11

What's Changed

• Add phone/watch diagnostic reports and prepare signed releases by @jjziets in #9

Full Changelog: v1.2.32...bridge-v1.0.11

v1.2.32

Watch 1.2.32 (Build 26)

• Fixes the zone-bypass confirmation opening and immediately closing when arming from the status tile.
• Keeps the watch activity open while bypass consent or an alarm command is pending.
• Clears stale tile completion state on a new tile or launcher entry.

On your phone, open Settings and select Update Watch, then approve installation on the watch.

The phone stays on 1.2.31 (81) and the Pi on 1.0.10. The phone APK remains attached for independent update discovery; it does not need an update for this fix.

Both APKs are signed by GitHub CI using the existing signing certificate. Local tests: 76 watch and 52 phone passed, including eight new bypass-flow state regressions. No physical alarm commands or on-device UI test were performed during this release.

Change: #8

v1.2.31

What's Changed

• Crash-recovery hardening + from-scratch install guide by @jjziets in #3
• Fix phone/watch alarm status and deploy signed Pi releases by @jjziets in #6

Full Changelog: v1.2.29...v1.2.31

Bridge 1.0.10

What's Changed

• Crash-recovery hardening + from-scratch install guide by @jjziets in #3
• Fix phone/watch alarm status and deploy signed Pi releases by @jjziets in #6

Full Changelog: v1.2.29...bridge-v1.0.10

v1.2.30

Full Changelog: v1.2.29...v1.2.30

v1.2.29

Full Changelog: v1.2.28...v1.2.29