Skip to content

Binary Sensors & Contacts (WHO = 25, WHO = 1, WHO = 9)

The MyHOME integration provides monitoring for dry contact interfaces, PIR motion sensors, and security auxiliary contacts across OpenWebNet WHO = 25, WHO = 1, and WHO = 9.

In v2, setup and management are 100% UI-first: binary sensors are automatically discovered from SCS bus events, and device presentation (such as choosing between a door sensor, window contact, or motion detector) is configured directly in Home Assistant's UI settings.

🚀 Supported Binary Sensor Types

1. Dry Contact Interfaces (WHO = 25)

  • Hardware: BTicino 3477 flush-mounted contact interface, magnetic reed switches, mechanical window switches, technical alarm contacts.
  • Addresses: WHERE = 31 through 3201.
  • Auto-Discovery: As soon as a dry contact changes state on the SCS bus, the integration automatically creates the corresponding binary sensor entity.

2. Motion / PIR Sensors (WHO = 1)

  • Hardware: Legrand 048822, BTicino BMSE1001 or standard SCS ceiling/wall motion sensors configured in scenario mode.
  • Operation: When movement is detected, the sensor broadcasts an event frame on WHO 1 that sets the binary sensor to on (Detected), returning to off (Clear) when timeout expires.
  • Address: a WHO 1 point address; an area-0 point with PL 1..9 is spelled in two digits (04), so where: "0004" in myhome.yaml is resolved to 04 and a …-1-0004-motion entity is moved to …-1-04-motion at startup (#147).

3. Auxiliary Alarm Sensors (WHO = 9)

  • Hardware: Auxiliary sensors, technical transmitters (water leak, methane gas), or peripheral contacts connected to the burglar alarm central unit.
  • Addresses: WHERE = 0 through 9.

🚪 Selecting Device Classes in the UI ("Show As")

In legacy versions, specifying whether a contact was a door, garage door, or window required manual YAML class: keys. In v2, this is configured directly in Home Assistant's UI:

  1. Navigate to Settings → Devices & Services → Entities.
  2. Select your binary sensor (e.g. binary_sensor.garage_entry_door).
  3. Click the Settings (gear) icon.
  4. Under Show As, select the appropriate device class:
  5. Door: Entry doors, interior doors.
  6. Window: Opening windows, skylights.
  7. Garage Door: Motorized or monitored garage gates.
  8. Motion: PIR motion and occupancy detectors.
  9. Moisture: Water leak detectors.
  10. Gas / Smoke: Technical safety sensors.
  11. Lock / Tamper: Anti-tampering switches on enclosures.
  12. Click Update. Home Assistant immediately applies appropriate dynamic icons (e.g. open/closed doors, motion waves) and integrates the sensor into Area security summaries.

🔁 Inverting Normally-Closed Contacts in the UI ("Invert state")

Third-party wired motion sensors, alarm reed switches, and twilight switches connected to a dry contact interface (F428 / 3477 / 3480 / F482, WHO = 25) or auxiliary channel (WHO = 9) frequently use normally-closed (NC) contacts: the loop stays closed (WHAT = 31, on) at rest and opens (WHAT = 32, off) on detection or tamper.

Every WHO = 25 dry contact and WHO = 9 auxiliary device exposes a per-device Invert state toggle under Configuration (EntityCategory.CONFIG), with no myhome.yaml needed:

  1. Navigate to Settings → Devices & Services → MyHOME → Devices and open your dry contact or auxiliary device.
  2. Under Configuration, toggle Invert state on.
  3. The binary sensor flips its live state immediately (without reloading the gateway or polling the SCS bus) and persists the setting in Home Assistant's config entry options across restarts.

Tip

If an existing myhome.yaml entry specifies inverted: true, Invert state starts enabled automatically, and toggling it off or on from the UI takes precedence over myhome.yaml.

🔄 Legacy YAML Note

Note

If you are upgrading from legacy v0.9 installations and still have manual binary_sensor: blocks in /config/myhome.yaml, please refer to the v0.9.4 Legacy Binary Sensor Documentation or the Legacy YAML Migration Guide. In v2, all binary sensors are discovered dynamically.