Error processing platform zha.silabs_multiprotocol - KeyError: 'radio_type'

[Seger85]

The problem

Recurring error message which is very strange to me, can anyone help me?

See below for more details.

What version of Home Assistant Core has the issue?

core-2024.1.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

zha silabs multiprotocol

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

There is no multiprotocol installed! The Sky Connect has the latest firmware EZSP. installed. No ZHA is set up under HA.

The stick is forwarded to zigbee2mqqt, with the following setting: port: /dev/ttyUSB1 adapter: ezsp

zigbee2mqqt works properly.

[Seger85]

I just saw that it will probably be fixed with this fix. @frenck @puddly you had added a cherry :-) to the whole thing, is it still expected in January? https://github.com/home-assistant/core/pull/106756

Thank you very much!

[puddly]

This isn't a known issue. Can you upload a complete debug log of this error being logged?

[Seger85]

@puddly home-assistant.log 2024-01-06 01:36:03.546 ERROR

[puddly]

I'm seeing the following in your log:

2024-01-06 01:35:52.485 DEBUG (MainThread) [zigpy.appdb] SQLite version for <module 'sqlite3' from '/usr/local/lib/python3.11/sqlite3/__init__.py'>: 3.41.2
2024-01-06 01:35:52.894 INFO (MainThread) [zigpy.serial] Using pyserial-asyncio-fast in place of pyserial-asyncio

Do you have zha: in your configuration.yaml file?

[Seger85]

zha: zigpy_config: ota: ikea_provider: true # Auto update Trådfri devices ledvance_provider: true # Auto update LEDVANCE/OSRAM devices salus_provider: true # Auto update SALUS/Computime devices inovelli_provider: true # Auto update INOVELLI devices thirdreality_provider: true # Auto update 3REALITY devices otau_directory: config/homeassistant/zigpy_ota # Utilize .ota files to update everything else

[puddly]

So you have ZHA set up then. Remove the config.

[Seger85]

I'll do it straight away, I still had it in there and thought that as it's "only" for ota, it won't interfere. I'll delete it and test it again.

[Seger85]

okay, error did not reappear after the restart, since it has repeated itself, I will continue to monitor it. But it certainly will have been, thank you very much! And I thought the fix sounded totally like my problem :-).

It's offtopic now, don't need to answer it, only if it fits, thanks! Tell me, is there a configuration.yaml setting you can recommend so that I don't clutter everything with rubbish and then set it to debug if necessary? I just did it like this:

logger:
  default: debug

Now I would go back to Info, is that OK?

And in this context, maybe you have a tip regarding the recorder, do I always have to record everything? I have the feeling that there is quite a lot going on in my network :-)

edit: Found while browsing: https://community.home-assistant.io/t/2024-1-happy-automating/665947/30

[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.