🛡️ MyHOME v2.0.0b15 Pre-Release: Learning to fail gracefully

[GreenGrassBlueOcean]

🛡️ MyHOME v2.0.0b15 is out: Learning to fail gracefully

MyHOME v2.0.0b15 is now tagged and ready for field testing! Following the massive architectural landing of b14, b15 is all about hardware reality: what happens when actuators fail, bulbs blow, gateways go quiet, or physical wiring is imperfect.

This release includes 41 merged pull requests on top of our freshly published companion engine, OWNd 2.0.0b10.

📦 Release Assets & Release Notes: v2.0.0b15 on GitHub Releases
📚 Documentation Hub: openwebnet-ha.github.io/MyHOME/beta/

---

💡 The Theme of b15: Learning to Fail Gracefully

In a perfect lab environment, every OpenWebNet command receives an ACK, every light responds instantly, and sensors never drop off the wire. In real homes:

• Relay actuators suffer mechanical faults or trip thermal cutoffs.
• Dimmers connected to burnt-out LED lamps report "no load" (WHAT 19).
• Quiet houses with low bus traffic cause passive event sessions to wonder if the gateway disconnected.
• A faulty or unconfigured actuator chatters on the bus, flooding the log.

In v0.9.x (and early betas), unexpected frames often caused silent entity unavailability, infinite reconnection loops, or misleading error spam. v2.0.0b15 teaches MyHOME to fail gracefully, isolate faults, and self-heal.

---

🌟 Key Highlights & What's New

1. 🩺 Hardware Fault Tracking & Self-Clearing Repairs (#593)

When a physical actuator emits a fault frame (such as WHAT 4 overload/fault):

• Instead of crashing or marking the entity unavailable permanently, MyHOME detects the specific failure and creates a native, actionable Home Assistant Repair Issue (actuator_fault) identifying the exact device and address.
• Self-Healing: The moment the physical actuator recovers and emits a normal operational frame, the repair issue automatically withdraws itself without requiring an integration restart.
• Documented operational frames are cleanly separated so normal wall presses never trigger false fault warnings.

2. 🔕 Silencing Problem Devices: ignored_addresses (#611, #621)

Have a malfunctioning actuator, an abandoned dry contact, or a noisy scenario module that you cannot physically replace right away?

• You can now specify ignored_addresses directly in the gateway Options Flow.
• Ignored addresses are cleanly silenced: they will not generate phantom entities, trigger status sweeps, or create repair issues.

3. 💡 Dimmer "No Load" (WHAT 19) & 1% Clamping (#619, #622, #635)

• Dimmer No Load Handling: When a light bulb blows or an LED driver is disconnected, BTicino dimmers (F414, F418U2, etc.) broadcast WHAT 19. The integration now recognizes this state, maintains entity availability, and flags the condition rather than resetting the entity to unknown.
• Zero-Brightness Safeguard: Setting a light brightness to 0% is now safely converted to an explicit turn_off telegram (*1*0*WHERE##), preventing firmware NACKs from gateways that reject WHAT 0 brightness writes. Dimmable group sweeps clamp to a minimum of 1% when on.

4. 🌡️ Thermoregulation & Central Unit Protocol Parity (#77, #582, #630, #641)

• Central Unit Mode Parity: Master heating/cooling commands (HEAT, COOL, AUTO, ANTIFREEZE, PROTECTION) now adhere strictly to canonical protocol findings confirmed against firmware reverse-engineering (libqtdevices).
• Graceful Fan Speeds: Invalid fan speed requests outside 0–3 are intercepted and converted into user-friendly validation errors rather than unhandled library exceptions.
• Informational Status Sweeps: Master Central Units (#0, #0#1, 99) are exempt from intrusive status polling that previously risked phantom zone creation or false unresponsive_zone flags.
• Negative Zero Guard: Temperature telemetry properly decodes signed sub-zero readings without creating -0.0°C edge cases.

5. 🚨 Burglar Alarm Subsystem (WHO 5) Parity (#609, #616, #618)

• System Frame Routing: Empty-WHERE broadcast frames (*5*11##, maintenance/disarm) route reliably to the central alarm panel entity.
• Read-Only Panel Mode: Support for installations where the alarm is monitored passively via AUX frames without allowing software arming/disarming without a security code.

6. 🔘 Scenario Controls (WHO 15 & 25) (#624, #638)

• 4-Digit Physical Addresses: Native support for 4-digit physical pushbuttons and scenario modules (WHERE > 999) with wire-address tolerance.
• Fail-Closed Triggers: Automation triggers for physical pushbuttons fail closed if a linked device is removed, logging a clear warning instead of raising uncaught key errors.

7. 🔌 Gateway Watchdogs & Connection Resilience (#606, #637, #640)

• Quiet Plant Watchdog: Inactivity timeouts on the event session are automatically disabled on low-traffic plants so that hours of silence on the SCS bus no longer trigger unnecessary socket reconnects.
• Connection Diagnostics: Setup failures now provide localized, specific explanations (e.g., wrong password vs. connection refused vs. session limit exhausted).
• Default Session Allocations: New gateways are automatically configured with concurrency limits appropriate for their hardware profile.

---

🧪 Real-World Bus Traces in CI

Thanks to the authentic bus traces shared in issue #466, our automated CI test suite now tests 3,464 automated tests with 100.0% statement coverage on every pull request.

New authentic plant replays added in b15:

• 🟢 BTicino F454: Relative step positioning and bus sweep traces (Central unit (WHERE #0) is marked "unresponsive" after two restarts, although it answers a plain status request #629, test(trace): add authentic F454 relative step positioning trace and replay test (#466) #646).
• 🟢 Legrand F455: Basic Gateway dual-bus trace replay (Community Call for Real-World Gateway Traces: Help Us Eliminate Hardware Blind Spots! 📡 #466, test(trace): add authentic Legrand F455 Basic Gateway trace and plant fixtures (#466) #596).
• 🟢 MH200 + F422: Cross-bus timed cover automation traces (Community Call for Real-World Gateway Traces: Help Us Eliminate Hardware Blind Spots! 📡 #466, test(trace): add authentic MH200 F422 timed covers and plant trace (#466) #648).
• 🟢 MH202: Alarm platform status frames (It is not possible to add the anti-theft system during the configuration of the H4890 secondary gateway or the MH202. #564).
• 🟢 Living Now / LivingLight CEN/CEN+: Short press and multi-step hold traces (Bus traces wanted: CEN (WHO 15) button presses and WHO 1 dimension 4 from a dimmer #434, test(trace): add authentic CEN short and long press bus traces (#434) #638).

---

⚠️ Behaviour Changes to Keep in Mind

1. Light Brightness 0%: Sending a light.turn_on command with brightness 0 now explicitly turns the light off to avoid gateway NACK rejections.
2. CEN / CEN+ Triggers: Pushbutton triggers are strictly scoped to their own family (a CEN trigger will no longer fire on a CEN+ telegram from a similarly numbered button).
3. Actuator Errors in Repairs: If an actuator on your bus has a blown fuse or thermal cut-off, Home Assistant will now alert you under Settings → System → Repairs.

---

📥 How to Install / Upgrade

Recommended: Terminal & SSH

# Navigate to custom_components
cd /config/custom_components 2>/dev/null || cd /homeassistant/custom_components

# Download, unpack, and verify 2.0.0b15
wget -O myhome_b15.zip https://github.com/OpenWebNet-HA/MyHOME/releases/download/2.0.0b15/myhome.zip
rm -rf myhome
unzip -q myhome_b15.zip -d myhome
rm myhome_b15.zip

# Confirm version output prints "2.0.0b15"
grep '"version"' myhome/manifest.json

# Restart Home Assistant (OWNd 2.0.0b10 installs automatically)
ha core restart

(Note: Requires Home Assistant Core ≥ 2026.3 and Python 3.14).

---

💬 What We'd Love Feedback On

1. Repairs Framework: Do actuator fault repairs trigger and self-clear as expected when hardware recovers?
2. Central Heating Units: How do master central unit switches behave with your zone thermostats?
3. Ignored Addresses: Does silencing noisy or faulty addresses in the Options Flow resolve background log chatter?

Thank you to everyone testing, reporting quirks, and exporting bus traces — you are helping make MyHOME rock-solid! 🚀

[GreenGrassBlueOcean]

tagging for some visibility @xtimmy86x @anotherjulien @fedem95 @Interstellar0verdrive @DPeeters811 @depeche