Silicon Labs Multiprotocol v1.0.0 Breaks mDNS UDP within container #2899
Comments
|
I'll add that I am having issues using zigbee2mqtt connected to SiLabs-Multiprotocol and its possibly related to this mDNS errors. Here is an interesting log for SiLabs-Multiprotocol version 0.13.1. The only note-able from the log that I can see is that when the connection is accepted AND there are several mDNSPlatformSendUDP errors, zigbee2mqtt fails, but when the connection is accepted WITHOUT these errors, the connection stays. When using SiLabs Multiprotocol v1.0.0, I repeated this experiment, all of which ended in zigbee2mqtt failing: |
|
Hi, I'm getting the exact same issue. Running HA OS on Synology DSM 7's VM. |
|
i have the same issue. HA OS on a QNAP as Virtual Machine. |
|
ive also have these errors: |
|
My Thread devices are not working anymore. some are very laggy, but most doenst work. |
|
|
|
I get the same error in my silabs addon, BUT my zigbee network ist working. Silabs vers. 1.1.1.0 It works with zigbee2mqtt edge out of the box for me, but as soon as I install the normal zigbee2mqtt version everything crashes and I've got no idea how to get it to work. I will stick for now to the dev branch and will try to change back in a few month. |
Not passing through any VMs for you, @dreesi? |
|
I use HA in a proxmox container, so yes I am passing it through. Did you try z2m edge? |
|
@dreesi Yeah, even ZHA doesn't work for me, tried almost all permutations. 😂 |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Also getting this, and also running HAOS in a PVE VM. Anybody get anywhere with debugging this? |
|
Have this error constantly using HAOS on an Odroid M1. |
|
Can we reopen this? I also still have it 🙈
|
|
Same `Socket connection has been closed, restarting... Listening on port 9999 for connection... Accepting connection. Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::1833:ffff:fe45:12e2/veth0a1496e/27 Restarting |
|
Getting the same error. Listening on port 9999 for connection... |
|
Btw: I was able to pair a thread device (Eve Energy), even though I got those messages beforehand. To me it worked as soon as I went closer to the home assistant device (or probably better: the sky connect). |
|
Am having the exact same issue, running HA on a QNAP VM... I have gotten ZHA to work without issues (apart from the usual Aqara incompatibilities), but Zigbee2MQTT has proven to be impossible. The mDNS warnings show up every time I try to start the Zigbee2MQTT add-on. |
|
I found same issue on SiliconLab's log after have changed firmware on my SONOFF Dongle-E to the RCP ZigBee + Thread. Reconfigured ZigBee2MQTT, also I found this into its log: [16:31:04] INFO: Starting Zigbee2MQTT... Any idea ? Thanks |
I doubt that it's the same issue I was having, but just in case, I managed to solve mine by setting the port and adapter values in the Zigbee2MQTT Add-ons config to the following:
All the guides I found were referring to the dongle being used in single protocol mode, so the configs shared by literally everyone didn't apply to the dongle in multiprotocol mode, when using it in combination with the Silicon Labs Multiprotocol add-on. Hope this helps. |
|
I am also getting the above issues since adding he SiliconLabs multi protocol firmware. |
|
ma è normale che questo problema c'è da Marzo '23 e non si è ancora risolto ? |
|
I have the same issue and nothing work. Use it on Synology NAS with VM. |
|
I have the exact as the logs from start of the post, it started for me three days ago, out of the blue, nothing added or tweaked. What did I do: Odd it disconnects and starts a new session..? ZHA doesn’t give an error. All entities I see, try to switch a light, gives a failed send request error in RED. Restored from backup now twice no success thus far. Who has more info, steps to resolve?? |
|
also have Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface ....... any fix? |
|
Received the same errors (and more) when setting up SkyConnect through the OTBR add-on to run it as a Thread border router. It was a fresh install and the multi protocol selection is unchecked. HAOS 11.5 via Virtualbox HA Core 2024.2.1 |
|
same error here, its been a few months, has anyone made any progress? |
|
Same error with latest silicon labs multi protocol firmware |
where are you getting the latest firmware? |
On the darkxst‘s Web Flasher |
and others
Describe the issue you are experiencing
SILabs Multiprotocol v1.0.0 breaks mDNS within addon.
What type of installation are you running?
Home Assistant Supervised
Which operating system are you running on?
Debian
Which add-on are you reporting an issue with?
Silicon Labs Multiprotocol
What is the version of the add-on?
1.0.0
Steps to reproduce the issue
Start the Silabs Multiprotocol addon. Connect to addon via tcp:https://core-silabs-multiprotocol:9999 - in my case I use Zigbee2mqtt. Once the addon times out with: Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::40d4:3fff:fe9e:34ed/veth37f960e/122, then Zigbee2mqtt crashes and the whole system burns.
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Spotify
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: