Sentinel Pro 4.3 Beta Release Notes and Validation

>

Release Line

• Product release line: Sentinel Pro 4.3 Beta
• Bridge build identifier: v4.3b1-pro
• Release date baseline: 2026-04-01

1. Executive Change Summary

v4.3 beta is a stabilization and readiness milestone focused on:

• robust bridge update/deployment behavior
• homeowner-governed access controls
• high-state telemetry handling and service mapping reliability
• expanded documentation and beta handoff quality

2. Build and Artifact Naming

Canonical runtime:

• savant_network_sentinel_clean_rubi_bridge_v4_3b1_pro.rb

Companion diagnostics:

• manual_bridge_diagnose_v4_3b1_pro.sh
• probe_sclibridge_v4_3b1_pro.sh

Host-family script wrappers:

• install_sentinel_dependencies_ProHosts.sh
• install_sentinel_dependencies_SmartHosts.sh
• update_sentinel_bridge_ProHosts.sh
• update_sentinel_bridge_SmartHosts.sh

3. Functional Highlights in 4.3 Beta

3.1 Bridge Runtime and Operations

• Bridge reports version: 4.3b1-pro via root and health endpoints.
• Bridge now exposes PID and PID file paths in runtime payloads.
• Script and path model consolidated for SmartHosts default root:

/home/RPM/Sentinel.

• Health and site payloads include stronger bridge identity metadata for support

and app introspection.

3.2 Governance and Access

• Homeowner temporary integrator access control implemented and exposed via:

/api/v1/home/integrator-access.

• Permanent revoke endpoint maintained:

/api/v1/home/revoke-integrator.

• Integrator session closure enforced on temporary disable action.

3.3 User Management

• User creation flow supports temporary credential generation.
• Temporary password delivery metadata added for app/operator workflows.
• Home admin role assignment remains activation-gated for security.

3.4 Telemetry and Discovery

• Discovery and status endpoints include stronger manifest/debug context.
• Active config and runtime metadata propagation improved for UI mapping.
• Service/device/state/action catalog behavior maintained and documented.

3.5 Tools and Diagnostics

• Terminal open/run/close flow kept with command filtering and audit trails.
• Reboot endpoint keeps explicit double-confirmation requirement.
• Doorbell workflow supports status, sample preview, sample apply, custom upload,

compatibility validation, and service reload guidance.

4. API Surface Notes

Documented primary endpoint groups:

1. Authentication
2. Acknowledgments and pairing
3. Site config/status/discovery/runtime
4. Tools
5. Admin and audit
6. Homeowner integrator governance

Important implementation note:

• /api/v1/home/integrator-access is active in runtime even if not always

listed by root endpoint enumeration payload.

5. Deployment Notes

Repository:

• https://github.com/PanixP/Sentinel-Pro-beta4

ProHosts update:

curl -fsSL https://raw.githubusercontent.com/PanixP/Sentinel-Pro-beta4/main/update_sentinel_bridge_ProHosts.sh | bash

SmartHosts update:

curl -fsSL https://raw.githubusercontent.com/PanixP/Sentinel-Pro-beta4/main/update_sentinel_bridge_SmartHosts.sh | bash

6. Validation Checklist

6.1 Bridge Runtime Validation

1. curl -k https://<HOST_IP>:42042/health returns status ok.
2. Health payload reports version = 4.3b1-pro.
3. Health payload includes pid and pid_file.
4. Site config reports matching bridge_version.

6.2 App/Bridge Contract Validation

1. App login succeeds for each expected role.
2. Pairing and acknowledgment gates render correctly in app.
3. Active config filename appears in runtime widgets.
4. Service widgets populate with mapped state values in large homes.
5. Savant cloud and recent events modules populate from status data.

6.3 Governance Validation

1. Temporary disable blocks integrator login and closes active sessions.
2. Temporary re-enable restores integrator access.
3. Permanent revoke blocks integrator until reset/config revision path.
4. Audit events capture all governance actions.

6.4 Tools Validation

1. Terminal open/run/close cycle works with allowed commands.
2. Reboot action requires double confirmation and returns accepted response.
3. Doorbell sample preview returns playable audio stream.
4. Doorbell sample/custom apply path updates reference safely.

7. Known Beta Risks and Mitigations

7.1 Network Transition Risk

Risk:

• VPN/network transitions can leave app sessions in stale transport state.

Mitigation:

• app should detect unreachable bridge and force reconnect workflow
• clear user-facing state to avoid false "connected but stale" UX

7.2 Host-Family Script Drift

Risk:

• running ProHosts scripts on SmartHosts (or reverse) can cause path mismatch.

Mitigation:

• verify host family before install/update
• verify runtime root path and Blueprint path fields after update

7.3 TLS Configuration Drift

Risk:

• changed certificates without app trust update can break client trust.

Mitigation:

• keep TLS fingerprint onboarding/update documented in operator workflow

8. Recommended Beta Freeze Artifacts

To preserve reproducible beta testing:

1. Freeze bridge runtime and script set from main.
2. Export and archive matching Blueprint XML files.
3. Archive this full documentation pack with timestamp.
4. Record host family and path configuration per test home.
5. Capture pre/post-update /health and /api/v1/site/config payloads.

9. Forward-Looking Priorities for Next Beta

1. Additional API rate limit and anti-bruteforce telemetry.
2. Stronger in-app certificate lifecycle UX.
3. Expanded app-side connection recovery after network transitions.
4. Continued parser hardening for cross-blueprint state naming variance.
5. Formal endpoint list consistency (root endpoint list vs runtime routes).