v0.3.6

What's Changed

Fixes

• Outputs 11 and 12 now reflect their real state instead of always reading off. The inbound state frame was decoded as plain hex while the outbound frame was BCD-encoded, so state broadcasts for those two outputs landed under the wrong cache keys. Both directions are now symmetric.
• Adding a light no longer delays the entity from appearing. The fast-path reload used to block on the response burst before re-forwarding the platform. It now fires the state dump and lets the running read loop push the fresh state to the entity as it arrives, so the entity shows up immediately and settles within a fraction of a second.

Full Changelog: v0.3.5...v0.3.6

v0.3.5

What's Changed

Fixes

• Adding a light to an existing module now settles immediately and reflects the correct physical state. The state-cache refresh used to watch only state-change signals, so a dump reply that matched the cache never triggered it and the platform reload waited the full timeout while the new entity read a stale value. The refresh now hooks into raw frame arrivals and returns as soon as the response burst starts, then drains until it goes silent.
• Two overlapping refreshes are now serialised so the second caller cannot orphan the first caller's wait.

Full Changelog: v0.3.4...v0.3.5

v0.3.4

What's Changed

Fixes

• Adding a light to an existing module now correctly reflects the physical state on the first render. The state-cache refresh on the fast-path reload used to return before the DOBISS bus had a chance to reply, leaving the new entity showing as off. It now waits for the first response frame, then drains until the burst settles.

Full Changelog: v0.3.3...v0.3.4

v0.3.3

What's Changed

Improvements

• Lights and covers are grouped under their module device again in Settings > Devices & Services, so navigating from a module surfaces its outputs.
• Friendly name is exactly the output name you typed at setup, without a module prefix.
• Module devices are created with no area set, so each entity stays individually area-assignable. Set the area per light or cover in the entity settings dialog.
• Fast-path reload propagates a module rename straight to the module device name without a bus reconnect.

Full Changelog: v0.3.2...v0.3.3

v0.3.2

What's Changed

Breaking

• Entity IDs are re-shaped to lead with the sx_evo_ prefix and include the module letter. Automations, scripts, and dashboards that reference the previous entity IDs need to be updated after upgrading. No automatic migration is performed.

Improvements

• Entities are no longer tied to a per-module device. DOBISS modules physically span rooms, so device-based area inheritance did not make sense. Assign each light or cover to a room individually in Settings > Devices & Services > Entities.
• Friendly names now lead with the module subentry title, so the module context stays visible in dashboards.
• The Max200 hub remains as the integration identity in the device registry.
• Tightened internal type annotations on the reload listener helpers.

Full Changelog: v0.3.1...v0.3.2

v0.3.1

What's Changed

Fixes

• Adding a light to an existing module no longer renders the new entity as off when the light is physically on. The fast-path reload now refreshes the controller state cache and waits for the burst to settle before recreating entities.

Other

• Refreshed brand assets from the official DOBISS logo and app icon.

Full Changelog: v0.3.0...v0.3.1

v0.3.0

What's Changed

Highlights

• Integration now genuinely meets the Gold quality scale (adds py.typed, links the "cannot connect" repair issue directly into the reauth/reconfigure flow)
• Entity IDs are prefixed with sx_evo_ (e.g. light.sx_evo_kitchen). Friendly names are unaffected
• First on/off action after adding a light no longer lags. The CAN notifier is now shared across discovery and read loop, so notifier.stop() never blocks the event loop
• Adding, removing, or renaming outputs on an existing module skips the full bus reconnect and just reloads the platforms. Module renames update the device name in place

Full Changelog: v0.2.1...v0.3.0

v0.2.1

What's Changed

• Declare usb component dependency so hassfest validation passes

Full Changelog: v0.2.0...v0.2.1

v0.2.0

What's Changed

• Add support for USB CAN adapters (slcan-compatible, e.g. CANable) by @DaanVervacke

Highlights

• Two-step config flow: pick socketcand or USB CAN adapter on setup
• USB adapters detected from the host's serial ports, picked via a labelled dropdown
• Reauth and reconfigure flows now branch by connection type
• Diagnostics report the active connection type
• Repair issues surface connection-type-specific placeholders

Full Changelog: v0.1.0...v0.2.0

v0.1.0

What's Changed

• Initial release of the DOBISS SX Evolution integration by @DaanVervacke

Highlights

• Config flow for local hub setup (host, port, and CAN interface)
• Local push integration over CAN bus via socketcand and python-can
• Platforms: light (with dimmer support) and cover (shutters)
• Subentry-based module configuration: add lights and shutters per physical module
• Optimistic brightness tracking for smooth dimmer control
• Exponential backoff reconnection with Home Assistant repair issues
• Gold quality scale

Full Changelog: https://github.com/DaanVervacke/hass-dobiss-sx-evolution/commits/v0.1.0