3.5.4

[3.5.4] - 2026-08-26

Fixed

• Illuminance sensors now returns lx instead of lux.

3.5.3

[3.5.3] - 2026-08-26

Fixed

• Motion sensor for MSP02.4C device.

3.5.2

[3.5.2] - 2026-08-26

Fixed

• Lux now updates in real time via the 0xE441 broadcast. The MSP02.4C
  (and other sensors-in-one devices) automatically broadcast illuminance every
  ~60 s as opcode 0xE441 ([?, 1, HIGH, LOW, ?, ?]). The opcode was
  previously unmapped (operate_code: None in debug logs). It is now registered
  as BroadcastLuminanceResponse in the OperateCode enum and handled in the
  Sensor device: brightness = (payload[2] << 8) | payload[3]. Lux becomes
  available immediately on first broadcast without any poll.

3.5.1

[3.5.1] - 2026-08-26

Fixed

• HDL-MSP02.4C motion now updates in real time. The device broadcasts PIR
  state as a Universal Switch event (switch #201, opcode 0xE01D) in addition
  to the polled 0x1605 sensors-in-one frame. The integration now subscribes
  to that UV switch broadcast, so the motion binary sensor flips immediately on
  occupancy change instead of waiting up to one poll interval. The catalog entry
  for HDL-MSP02.4C records motion_uv_switch: 201; the Sensor device, the
  BusproModule.get_sensor() factory, and the managed sensor/binary-sensor
  setup all thread the value through.

• Illuminance sensors now poll, report available, and carry correct
  metadata. The catalog uses "illuminance" as the capability key, but the
  ILLUMINANCE constant equals "lux". The string comparison
  sensor_type == ILLUMINANCE therefore never matched for catalog-managed
  devices, causing four silent failures: the poll flag was not set (lux froze
  after the first reading), available always returned True even when no
  value had arrived, device_class and native_unit_of_measurement fell
  through to None, and state_class was not set. All comparisons now accept
  both ILLUMINANCE and "illuminance" via a small _is_illuminance() helper.

3.5.0

3.5.0 - 2026-08-26
Introduces automatic gateway discovery and bus scanning for device import. Also contains a broad stability pass targeting HA 2025 compatibility, gateway availability tracking, config-flow edge cases, and sensor correctness.

3.4.0 - 2026-08-25
Fixes illuminance (lux) and motion on the HDL-MSP02.4C multi-sensor, based on live buspro.telegram captures from a real device.

3.3.0

3.3.0 — 2026-08-25 (packaging release)

Changed

• Restructured to the standard custom_components/buspro/ HACS/HA layout

3.2.0

Release summary:

✅ Command Confirmation Feature

• Per-device enable/disable via YAML (enable_confirmation: true)
• Configurable timeout (5.0s default) and retries (3 default)
• Works with all 7 device types: Relay, Dimmer, Switch, Light, Cover, Fan, Climate
• Backward compatible (disabled by default)

✅ Device Diagnostics

• 5000-record circular buffer with device-specific decoders
• 50+ BusPro opcode support
• Detailed event logging for troubleshooting

✅ Multi-language Documentation

• Updated DEVICE_EXAMPLES.md for all 10 languages
• README.md Command Confirmation sections
• Complete configuration examples and best practices

3.0.3

📋 Release Notes - Version 3.0.0

Overview

Major release with significant architecture refactoring, comprehensive documentation in 10 languages, and improved device management.

---

⚠️ BREAKING CHANGES

IMPORTANT: Read the upgrade checklist before updating

1. Installation-specific devices no longer built into the integration

   • Device addresses, names, channel assignments, and device counts now belong to config-entry options or the Home Assistant Device Registry
   • The device catalog contains hardware capabilities only
   • Action required: Reconfigure devices through Settings > Devices & services > HDL Buspro > Configure

2. UI-managed relay modules use their physical channel count

   • HDL-MR1210.433 always exposes 12 channel slots
   • HDL-MR1610.433 always exposes 16 channel slots
   • An existing device cannot be reduced below its model's physical channel count

3. Empty channel names now disable channels

   • Disabled channels are not instantiated, do not create protocol objects
   • Previously they were created with default names

4. Exact model controls generated entities

   • Generic HDL panel has no known button count
   • Must select the physical model to create button events
   • Changing a model reloads the config entry

5. Home Assistant has its own Buspro address

   • Existing config entries migrate to 200.200
   • This address must be unused on the Buspro network
   • Can be changed under Configure > Gateway settings

6. Packet source IP no longer hardcoded

   • Integration derives it from the route to the configured gateway
   • Multi-interface Home Assistant hosts must route the gateway through the intended LAN interface

7. Panel action events now decoded

   • Automations consuming old raw action values need update
   • Events use channel_on, channel_off, channel_level, scene, universal_switch_on, or universal_switch_off
   • Includes target and summary attributes where available

8. Embedded Python API changed

   • Direct pybuspro.Buspro users must provide client_address
   • See pybuspro/README.md

---

✨ New Features

• Device Catalog System: Professional device registry with 57+ supported models
• Dual-Mode YAML Configuration: Entity-Centric (Legacy) and Device-Centric (Modern) approaches
• Comprehensive Multilingual Documentation: Full documentation in 10 languages
  • English, German, French, Spanish, Italian, Dutch, Russian, Ukrainian, Belarusian, Norwegian
• Model-Driven Device Management: Automatic entity creation based on exact device models
• Catalog Maintenance Helper: Tool to verify integration catalog against official HDL models
• Fan Device Support: Full support for variable-speed fans
• Enhanced Sensor Handling: Improved temperature, illuminance, humidity, and motion detection

---

🔧 Improvements

• Entry lifecycle management: Config-entry unload flow and module registry helpers
• Service stability: Idempotent service registration and re-bindable handlers
• Entity timer/callback cleanup: Prevents leaks and duplicates
• Startup performance: Bounded parallel refresh with Semaphore(5)
• Parser robustness: Guard against None telegrams before dispatch
• Memory optimization: Bounded dedup cache with periodic pruning
• Debug efficiency: Cost reduction for debug paths
• Exception hygiene: Structured logging instead of print/traceback output
• 19 protocol tests + 18 integration tests for comprehensive coverage

---

📚 Documentation

• Complete README with configuration examples, breaking changes checklist, and upgrade guide
• Device examples for all supported device types (light, dimmer, cover, fan, climate, sensors)
• Dual-mode YAML configuration guide with best practices
• 10 languages fully translated and maintained with flag-based navigation

---

📦 Dependencies

• No new external dependencies required
• pybuspro module included and updated

---

⚙️ Upgrade Checklist

1. ✅ Restart Home Assistant after replacing the custom component
2. ✅ Open Settings > Devices & services > HDL Buspro > Configure
3. ✅ Check the gateway host, ports, and unused Home Assistant Buspro address
4. ✅ Select the exact model for each device and verify channel names
5. ✅ Review and update automations that use panel events
6. ✅ Remove or comment out old YAML entities (after verifying UI-managed replacements)

⚠️ Do NOT keep the same physical channel configured in both YAML and UI — this creates duplicate entities and protocol subscriptions.

---

📝 Version History

• 2.1.4: Last stable 2.x release
• 3.0.0: Major refactoring with architecture improvements and comprehensive documentation

2.1.4

fix sensors (incorrect detection, parsing or values):

• movement
• illuminance
• temperature

2.1.3

• modernize config flow behavior
• add reconfiguration and options support
• add project tests