Since updating MyHOME to 0.9.4

[pakob81]

Since updating MyHOME to 0.9.4, entities on BUS 0 work correctly, while entities configured on secondary BUS interfaces (1–6) have no state in Home Assistant.

Commands work correctly because they use self._full_where:
WHERE#4#INTERFACE

However, switch.py async_update() sends the status request using self._where instead of self._full_where:

Current:
OWNLightingCommand.status(self._where)

Expected:
OWNLightingCommand.status(self._full_where)

For example, for WHERE 41 and interface 2, the integration sends:
#141##

instead of:
#141#4#2##

Replacing self._where with self._full_where in switch.py restores status updates for devices on secondary BUS interfaces.
@anotherjulien

[GreenGrassBlueOcean]

Hi @pakob81,

Thank you for reporting this and for the spot-on diagnosis! You nailed the exact root cause: switch.py was querying OWNLightingCommand.status(self._where) instead of self._full_where, which stripped the #4#<interface> routing suffix on status requests for secondary BUS interfaces.

The 0.9.x series is our legacy release line, but we've completely overhauled the integration in the v2.0.0 beta architecture (currently on v2.0.0b13). In v2:

• This exact bug is resolved—status requests, sweeps, and commands across switch, light, cover, and climate consistently use full_where (WHERE#4#INTERFACE).
• Cross-bus routing (F422 interfaces) and bus auto-discovery have been heavily hardened.
• The underlying engine is powered by the async-native OWNd 2.0 protocol handler with hardware-specific command pacing.

Would you be open to giving the v2.0.0b13 beta a try on your setup to see if it resolves this cleanly for your secondary bus devices?

How to test:

Note

The v2 beta requires Home Assistant 2026.3+. All existing entity names, unique IDs, and gateway configurations are preserved automatically.

Because HACS 2.0 has known caching issues with pre-release toggles, the easiest way to install it is via the Terminal & SSH add-on (takes about 10 seconds):

cd /config/custom_components
# Safety backup outside custom_components:
[ -d myhome ] && rm -rf /config/myhome_backup && cp -r myhome /config/myhome_backup
# Download and install v2.0.0b13:
rm -rf myhome
wget -O myhome_beta.zip https://github.com/OpenWebNet-HA/MyHOME/releases/download/2.0.0b13/myhome.zip
unzip -q myhome_beta.zip -d myhome
rm myhome_beta.zip
ha core restart

(Alternatively, you can manually grab myhome.zip from the v2.0.0b13 Release Page and unpack it into /config/custom_components/myhome/).

We would love to hear your feedback on how your secondary BUS entities behave on the beta!

[pakob81]

I installed the latest release. It automatically recognized all the secondary buses; the only thing I noticed is that it imported all the entities—such as "Light 13I03" and the climate control entities—but it didn't carry over the names I had defined in my configuration.yaml (which I’ve attached). Did I do something wrong?
myhome.txt

[GreenGrassBlueOcean]

Hi @pakob81,

Thank you for sharing your configuration! We analyzed your attached file and diagnosed exactly why your entity names were not carried over.

(Note: In the snippets below, your gateway MAC address has been partially redacted as 00:03:50:XX:XX:XX. MAC addresses are unique hardware identifiers that can be used for device fingerprinting and network reconnaissance, so it is always good practice to redact the last three device-specific octets on public forums while keeping the vendor OUI 00:03:50 visible).

---

1. MAC Address Typo in the YAML Header

In your configuration file, the MAC address was specified as:

server1:
  mac: '00:3:50:XX:XX:XX'

Notice the second octet: '3' instead of '03'. Legrand/BTicino MAC addresses strictly require two hexadecimal digits per octet (00:03:50:...). Because the second octet was only one character, the validator rejected the MAC address (Invalid MAC address at 'server1.mac'), which caused Home Assistant to abort reading the file at startup.

Updating the second octet to two digits:

server1:
  mac: '00:03:50:XX:XX:XX'

allows all 235 lights, 54 covers, and 11 climate zones in your file to validate and load cleanly!

---

2. File Location: /config/myhome.yaml

In your comment, you mentioned configuration.yaml. In Home Assistant, MyHOME does not read device declarations directly from configuration.yaml (doing so triggers a log warning that configuration.yaml is not supported).

Make sure your file is saved as:

/config/myhome.yaml

(placed in the root of your Home Assistant /config folder, alongside configuration.yaml, but as its own dedicated file).

---

3. How to Cleanly Restore Your Friendly Names

Because Home Assistant started earlier without the YAML file loaded, the on-wire bus discovery automatically onboarded the devices using default hardware names (such as Light 13I03 and Climate Zone 1).

Once Home Assistant has registered an entity under a default name, it keeps it in its entity registry. To cleanly apply your YAML friendly names:

1. Ensure your file is saved as /config/myhome.yaml with the corrected MAC address (00:03:50:...).
2. In Home Assistant, navigate to Settings → Devices & Services → MyHOME.
3. Click the 3 dots (⋮) on your gateway entry and select Delete (this purges the default auto-discovered entity entries).
4. Restart Home Assistant (Developer Tools → YAML → Restart).
5. Home Assistant will discover the gateway, or you can re-add it (Settings → Devices & Services → Add Integration → MyHOME).

Upon boot, the integration will parse /config/myhome.yaml, and your lights (e.g., faretti_corridoio_hotel_3 → "Faretti Corridoio Hotel 3") and climate zones (e.g., termo_controlroom → "Condizionatore ControlRoom") will appear with your configured names!

(We've also opened PR #414 to automatically normalize single-digit MAC octets and harden secondary bus key indexing in upcoming beta builds).

[pakob81]

Perfect, everything is resolved; the names are back in their proper place—I hadn't spotted the error. Il giorno sab 19 set 2026 alle ore 13:00 GreenGrassBlueOcean < ***@***.***> ha scritto:

…

Hi @pakob81 <https://github.com/pakob81>, Thank you for sharing your configuration! We analyzed your attached file and diagnosed exactly why your entity names were not carried over. *(Note: In the snippets below, your gateway MAC address has been partially redacted as 00:03:50:XX:XX:XX. MAC addresses are unique hardware identifiers that can be used for device fingerprinting and network reconnaissance, so it is always good practice to redact the last three device-specific octets on public forums while keeping the vendor OUI 00:03:50 visible).* ------------------------------ 1. MAC Address Typo in the YAML Header In your configuration file, the MAC address was specified as: server1: mac: '00:3:50:XX:XX:XX' Notice the second octet: '3' instead of '03'. Legrand/BTicino MAC addresses strictly require two hexadecimal digits per octet (00:03:50:...). Because the second octet was only one character, the validator rejected the MAC address (Invalid MAC address at 'server1.mac'), which caused Home Assistant to abort reading the file at startup. Updating the second octet to two digits: server1: mac: '00:03:50:XX:XX:XX' allows all *235 lights*, *54 covers*, and *11 climate zones* in your file to validate and load cleanly! ------------------------------ 2. File Location: /config/myhome.yaml In your comment, you mentioned configuration.yaml. In Home Assistant, MyHOME does *not* read device declarations directly from configuration.yaml (doing so triggers a log warning that configuration.yaml is not supported). Make sure your file is saved as: /config/myhome.yaml *(placed in the root of your Home Assistant /config folder, alongside configuration.yaml, but as its own dedicated file).* ------------------------------ 3. How to Cleanly Restore Your Friendly Names Because Home Assistant started earlier without the YAML file loaded, the on-wire bus discovery automatically onboarded the devices using default hardware names (such as Light 13I03 and Climate Zone 1). Once Home Assistant has registered an entity under a default name, it keeps it in its entity registry. To cleanly apply your YAML friendly names: 1. Ensure your file is saved as /config/myhome.yaml with the corrected MAC address (00:03:50:...). 2. In Home Assistant, navigate to *Settings → Devices & Services → MyHOME*. 3. Click the 3 dots (*⋮*) on your gateway entry and select *Delete* (this purges the default auto-discovered entity entries). 4. Restart Home Assistant (*Developer Tools → YAML → Restart*). 5. Home Assistant will discover the gateway, or you can re-add it (*Settings → Devices & Services → Add Integration → MyHOME*). Upon boot, the integration will parse /config/myhome.yaml, and your lights (e.g., faretti_corridoio_hotel_3 → *"Faretti Corridoio Hotel 3"*) and climate zones (e.g., termo_controlroom → *"Condizionatore ControlRoom"*) will appear with your configured names! *(We've also opened PR #414 <#414> to automatically normalize single-digit MAC octets and harden secondary bus key indexing in upcoming beta builds).* — Reply to this email directly, view it on GitHub <#408?email_source=notifications&email_token=CADQP6OIXZX75YFC53DKSHD5PZROLA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBVGE2DGMZTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18514333>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CADQP6MIVDRJJWJXJEIGGHL5PZROLAVCNFSNUABIKJSXA33TNF2G64TZHMZDONJTHA4DAMRSHNCGS43DOVZXG2LPNY5TCMBYGQZTCOBUUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CADQP6K7MF3HUBCEBARRJPD5PZROLA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBVGE2DGMZTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/CADQP6LILBHYMHSN53GO3ZL5PZROLA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBVGE2DGMZTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>