Skyconnect multiprotocol suppressed in 2025.4

[pousca]

The problem

Due probably to the fix #141959, the upgrade to 2025.4.1 deletes the config entry of my skyconnect and ask to reconfigure it. If I try to configure, it does not propose the multiprotocol anymore, only zigbee or Threads.

It is said. "A future PR will auto-setup the ZBT-1, SkyConnect, and Yellow config entries (skipping discovery) if they are detected to be in use by ZHA or OTBR." which couls solve the problem. But what mean future: next mai update?

What version of Home Assistant Core has the issue?

core- 2025.4.1

What was the last working version of Home Assistant Core?

core- 2025.3.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Zigbee home integration SkyConnect Multiprotocol

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant[bot]]

Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zha documentation zha source _{^{(message by IssueLinks)}}

[puddly]

If I try to configure, it does not propose the multiprotocol anymore, only zigbee or Threads.

Multiprotocol was frozen last year and will be formally deprecated in an upcoming release. It has not been possible to set up multiprotocol automatically for many many months. If you rely on multiprotocol support, you really should migrate to two independent radios, one for each protocol.

[pousca]

Thanks for the information. I was aware that the multiprotocol was no more available for new systems, but it was said that the existing customers could continue to use it in the future, but without update. It looks that this is no more the case.

I am rather a new HA user. Are you aware of a method to migrate to 2 keys keeping the matter devices associated?

In any case, thanks for your involment.

Le lun. 7 avr. 2025, 22:45, puddly @.***> a écrit :

If I try to configure, it does not propose the multiprotocol anymore, only zigbee or Threads.

Multiprotocol was frozen last year https://www.home-assistant.io/blog/2024/01/25/matter-livestream-blog/#using-home-assistant-yellow-or-home-assistant-skyconnect and will be formally deprecated in an upcoming release. It has not been possible to set up multiprotocol automatically for many many months. If you rely on multiprotocol support, you really should migrate to two independent radios, one for each protocol.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/142466#issuecomment-2784586270, or unsubscribe https://github.com/notifications/unsubscribe-auth/BENHDA6LT2TOYND6LEZMHTD2YLPXRAVCNFSM6AAAAAB2TGQK4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBUGU4DMMRXGA . You are receiving this because you authored the thread.Message ID: @.***> [image: puddly]puddly left a comment (home-assistant/core#142466) https://github.com/home-assistant/core/issues/142466#issuecomment-2784586270

If I try to configure, it does not propose the multiprotocol anymore, only zigbee or Threads.

Multiprotocol was frozen last year https://www.home-assistant.io/blog/2024/01/25/matter-livestream-blog/#using-home-assistant-yellow-or-home-assistant-skyconnect and will be formally deprecated in an upcoming release. It has not been possible to set up multiprotocol automatically for many many months. If you rely on multiprotocol support, you really should migrate to two independent radios, one for each protocol.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/142466#issuecomment-2784586270, or unsubscribe https://github.com/notifications/unsubscribe-auth/BENHDA6LT2TOYND6LEZMHTD2YLPXRAVCNFSM6AAAAAB2TGQK4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBUGU4DMMRXGA . You are receiving this because you authored the thread.Message ID: @.***>

[puddly]

There should be no changes to how multiprotocol functions and it should still keep working as before. If it isn't, that is a bug.

Does ZHA no longer function for you? If so, can you upload a debug log of ZHA starting up and a screenshot of the debug page of your multiprotocol addon?

[pousca]

Sorry to react to your message so late, but it was not possible to stop HA and retry version 2025.4 to send you the logs. But good news it is no more necessary: I updated to 2025.5.1 this weekend and surprisingly without any intervention from my part the multiprocol was there and working perfectly for all my zigbee and threads devices since 24h. Maybe you have an explanation, but I saw corrections in the entities firmware of threads device from "unknown" to "up to date" value. So it looks like there has been some changes in the reading of the entities attributes used by the multiprotocol.

On the other hand, there is now a skyconnect integration visible whose device is display as "unknown" as shown below: [image: image.png]

I suppose this is because the multiprotocol is not recognized.

In conclusion you can close my issue. Sorry to have taken part of your time for a non problem.

Le lun. 7 avr. 2025 à 23:05, puddly @.***> a écrit :

There should be no changes to how multiprotocol functions and it should still keep working as before. If it isn't, that is a bug.

Does ZHA no longer function for you? If so, can you upload a debug log of ZHA starting up and a screenshot of the debug page of your multiprotocol addon?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/142466#issuecomment-2784625708, or unsubscribe https://github.com/notifications/unsubscribe-auth/BENHDAZV4X52JGHAEYDPSH32YLSBVAVCNFSM6AAAAAB2TGQK4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBUGYZDKNZQHA . You are receiving this because you authored the thread.Message ID: @.***> [image: puddly]puddly left a comment (home-assistant/core#142466) https://github.com/home-assistant/core/issues/142466#issuecomment-2784625708

There should be no changes to how multiprotocol functions and it should still keep working as before. If it isn't, that is a bug.

Does ZHA no longer function for you? If so, can you upload a debug log of ZHA starting up and a screenshot of the debug page of your multiprotocol addon?oo

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/142466#issuecomment-2784625708, or unsubscribe https://github.com/notifications/unsubscribe-auth/BENHDAZV4X52JGHAEYDPSH32YLSBVAVCNFSM6AAAAAB2TGQK4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBUGYZDKNZQHA . You are receiving this because you authored the thread.Message ID: @.***>

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.