v1.7.2

Added

• Tandwiel-menu: "Modules opzoeken op de veldbus" — stuurt POST /api/v1/discover op de gateway en toont het resultaat ({added} toegevoegd, {changed} bijgewerkt, {removed} verwijderd + duur) in een vervolgscherm. Vervangt de noodzaak om de discover-knop op het gateway-apparaat te zoeken. Tot ~120 s timeout (zelfde budget als de bestaande knop).
• Tandwiel-menu: "Knoppen en module-info bijwerken" — stuurt POST /api/v1/modules/refresh op de gateway en toont het aantal bijgewerkte modules en knoppen. Gebruik dit nadat je een wandknop of IP1100PoE-instelling op de module zelf hebt gewijzigd; de gateway pusht dan een WS-snapshot zodat de companion nieuwe namen/drempels oppikt zonder integratie-reload. Vindt geen nieuwe modules — daarvoor blijft Modules opzoeken.

Changed

• button.ipbuilding_gateway_run_discovery_sweep hernoemd van "Run discovery sweep" / "Discovery sweep starten" naar "Scan field bus for modules" / "Modules opzoeken op de veldbus" zodat de naam consistent is met het nieuwe menu-item. Geen functionele wijziging.

Fixed

• HA 2026.6 update-listener reload — config flow gebruikt reload_on_update=False; de update listener plant reload via async_schedule_reload i.p.v. async_reload. Voorkomt dubbele reload en de deprecation-warning die vanaf HA 2026.12 een error wordt.

v1.7.1

Highlights since v1.2.2

Added

• single_press button event + single_pressed device trigger — gateway classificeert kort/lang zelf
• dim_start / dim_stop services op light.-entities — native IP0300PoE ramp
• button_standard v9 — 3-slot universele wandknop (Indrukken / Vasthouden / Loslaten)
• button_dim v8 + nieuwe button_dim_stepwise blueprint

Changed

• Dimmer light.toggle → native T<ch>991000 (gebruikt IP0300PoE-geheugen)
• button_dim race-fix: release-trigger nu gescopet met from: "long_press"
• Blueprints triggeren direct op single_press (geen wait_for_trigger meer)
• button_standard v9: mode van single → queued
• single_press state-vertaald in EN + NL
• Blueprint-teksten gereviseerd; versie-header onderaan in plaats van bovenaan

Fixed

• Race tussen single_press en trailing release in button_dim / button_cover

Removed

• button_cover blueprint (gebruik button_standard met cover-acties)
• button_scene blueprint (gebruik button_standard met scene-actie)
• dim_button.yaml deprecation-stub (migreer naar button_dim)

Breaking

• button_standard v7 verwijdert oude inputs — bestaande instanties moeten opnieuw
• Bus-event hernoemd: ipbuilding_gateway_ha.* → ha_ipbuilding_gateway.*

Requirements

• Gateway add-on ≥ 1.1.0 voor single_press-events en DIM_START / DIM_STOP
• Voor dim-while-hold: gateway met feature/dimmer-downstream-td of nieuwer

v1.2.2

v1.2.2 — mDNS-first discovery + D3 naamgeving

Changed

• Integration heet nu IPBuilding Gateway (was IPBuilding Gateway Companion). De device-tree blijft gateway → module → kanaal.
• mDNS-first discovery (zoals Shelly). async_step_zeroconf werkt nu ook voor Supervisor add-ons — de duplicate-guard already_discovered_addon is verwijderd.
• async_step_hassio leest nu instance_id uit de Supervisor config payload, zodat de unique_id tussen zeroconf en HassIO discovery aligned is.

Added

• Discovery TXT schema v2: nieuwe TXT-velden sw (alias van version), host, port en mac. DISCOVERY_SCHEMA_VERSION gebumped naar 2.
• Naamgeving bij toevoegen (D3): één nieuwe confirm step vervangt hassio_confirm en discovery_confirm. Default naam = instance_id[:8] (of gateway), operator kan aanpassen. Gekozen naam komt in config-entry title (IPBuilding Gateway (<naam>)) en flow_title.
• mac en sw_version in GatewayDiscoveryInfo. Lege mac → None.
• Translaties: nieuwe flow_title en confirm step met placeholders {addon}, {version}, {url}, {name}.

Tests

• Nieuw: tests/test_discovery_parser.py (schema v2 + mac + sw-fallback) en tests/test_config_flow_confirm.py (default naam truncatie + refactor smoke-tests).

Vereisten

• Gateway ≥ 1.0.4 voor de nieuwe TXT-velden. Oudere gateways blijven werken via fallback.

v1.2.1

v1.2.1 — Supervisor discovery fix

Fixed

• async_step_hassio now matches any add-on slug ending in ipbuilding_gateway (suffix match via _is_ipbuilding_gateway_addon) instead of strict equality. This unblocks Instellingen → Apparaten & diensten → Ontdekt when the add-on is installed from a custom repository (slug 3059e002_ipbuilding_gateway). The bare store slug remains accepted.

IPBuilding Gateway Companion v1.2.0

Breaking

• Onboarding wizard removed from the config flow. Fresh installs use Configure → Assign IPBuilding groups to areas (map_rooms) to link IPBuilding groups to Home Assistant areas. Silent name-matching (_suggest_channel_areas) and suggested_area on devices still work.
• Button import removed. Use the bundled blueprints (button_standard, button_toggle, button_dim, button_cover, dim_button) or your own HA automations instead of wizard-imported automations.yaml entries.
• Pre-change snapshot: last release with the full wizard is tagged v1.1.0-with-onboarding-wizard on b80346f.

Added

• Group → area mapping via integration options (gear menu). One AreaSelector per IPBuilding group; empty fields fall back to an HA area with the same name. Stored in entry.options[room_mappings] and reapplied on every reload.
• Auto-offer mapping once after adding a gateway when groups are known and no mapping exists yet (room_mapping_offered flag prevents repeat prompts).

Changed

• Config flow creates the entry immediately after discovery — no wizard spinner.
• Options flow rewritten to a single map_rooms step; room-mapping copy uses IPBuilding groups → HA areas/ruimtes terminology.
• Fixed options persistence: async_create_entry(data={}) no longer wipes stored mappings.

Removed

• Wizard modules (onboarding_flow, gateway_rest, button_automation_builder, automation_store, target_resolver, button_mapping) and related tests/constants/i18n.

Full changelog: CHANGELOG.md

IPBuilding Gateway Companion - Latest

Highlights

• First public release of the IPBuilding Gateway HA companion — an open Home Assistant integration for the IPBuilding field-bus (UDP/1001 to IP0200PoE relays, IP0300PoE dimmers, and IP1100PoE input modules). Scenes, automations, and button→action logic stay in Home Assistant; the companion is a thin client that turns the gateway's WebSocket /ws and REST /api/v1/ into standard HA entities.
• Auto-discovery: Supervisor discovery when the gateway runs as an HA add-on; Zeroconf (_ipbgw._tcp.local.) for standalone gateways; manual host/port entry as a fallback.
• Entities: light (relays + dimmers), switch (with semantic types: plug, fan, …), event for physical IP1100PoE buttons (press / long_press / release), sensor for per-channel power, and a discovery-sweep button on the hub device.
• Three-tier device tree — gateway → module (relay / dimmer / input) → channel — with via_device links and optional channel → area mapping from devices.json on the gateway.
• English + Dutch UI translations.

Requirements

• A running IPBuilding Gateway reachable from Home Assistant (HA add-on on the same host, or any host on your IPBuilding VLAN). Default port: 8080.
• Home Assistant 2023.8 or newer (for EventEntity).

Install (HACS)

1. HACS → Integrations → ⋮ → Custom repositories.
2. Add https://github.com/markminnoye/ha-ipbuilding-gateway as type Integration.
3. Search for IPBuilding Gateway HA and install.
4. Restart Home Assistant.
5. The integration appears under Settings → Devices & Services → Discovered when the gateway is reachable. Click Add to set it up; or add it manually with the gateway's host and port.

Full installation and configuration guide: README.

First steps

• The companion mirrors the gateway's devices.json. If the gateway has no devices yet, a one-time discovery sweep runs automatically on first start and reloads the integration. You can also trigger a sweep from the Run discovery sweep button on the hub device.
• Channels and modules show up in the device registry. To suggest a Home Assistant area per channel, set room on the device in the gateway's devices.json (the companion will match it to an existing HA area, or pre-select it during the "Name and assign" onboarding step).
• For button-to-action automations, use the event.<hardware_id> entities on IP1100PoE inputs. The companion also publishes typed bus events (ha_ipbuilding_gateway.button_pressed / button_long_pressed / button_released) for use in legacy event-trigger automations.

Acknowledgements

Built against the open IPBuilding Gateway (field-bus hub). The legacy IPBox REST/WebConfig is not a dependency of this integration.