search

home-assistant / addons

:heavy_plus_sign: Docker add-ons for Home Assistant
https://home-assistant.io/hassio/
Apache License 2.0
1.52k stars 1.47k forks source link

Silicon Labs Multiprotocol v1.0.0 Breaks mDNS UDP within container #2899

Closed josh-blake closed 1 year ago

josh-blake commented 1 year ago

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://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

version core-2023.3.0
installation_type Home Assistant Supervised
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.10.10
os_name Linux
os_version 5.15.61-v8+
arch aarch64
timezone Australia/Sydney
config_dir /config
Home Assistant Community Store GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.31.0 Stage | running Available Repositories | 1305 Downloaded Repositories | 4 HACS Data | ok
Home Assistant Cloud logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Home Assistant Supervisor host_os | Debian GNU/Linux 11 (bullseye) -- | -- update_channel | stable supervisor_version | supervisor-2023.01.1 agent_version | 1.2.2 docker_version | 23.0.1 disk_total | 937.6 GB disk_used | 22.4 GB healthy | true supported | true supervisor_api | ok version_api | ok installed_addons | Let's Encrypt (4.12.8), Terminal & SSH (9.6.1), Mosquitto broker (6.1.3), MariaDB (2.5.2), File editor (5.5.0), ecowitt2mqtt (2023.02.1), Silicon Labs Multiprotocol (1.0.0), Matter Server (4.0.0), Zigbee2MQTT (1.30.2-1)
Dashboards dashboards | 1 -- | -- resources | 2 views | 2 mode | storage
Recorder oldest_recorder_run | October 27, 2022 at 8:44 AM -- | -- current_recorder_run | March 2, 2023 at 11:49 PM estimated_db_size | 3820.39 MiB database_engine | mysql database_version | 10.6.10
Spotify api_endpoint_reachable | ok -- | --

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?

[00:14:17:540363] Info : [CPCd v4.2.1.0] [Library API v3] [RCP Protocol v3]
[00:14:17:540481] Info : Git commit: 038cccb2222f18096b6f7f43f73f4220479239ef / branch: 
[00:14:17:540484] Info : Sources hash: 5d47e3b41b2e023f52d5d5d2814ddf2dc2219a62e8d6e9e5f22f08f7d54206dc
[00:14:17:540497] WARNING : In function 'main' in file /usr/src/cpc-daemon/main.c at line #188 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
[00:14:17:540527] Info : Reading cli arguments
[00:14:17:540534] Info : /usr/local/bin/cpcd 
[00:14:17:545720] Info : Reading configuration
[00:14:17:545736] Info : file_path = /usr/local/etc/cpcd.conf
[00:14:17:545739] Info : instance_name = cpcd_0
[00:14:17:545740] Info : socket_folder = /dev/shm
[00:14:17:545742] Info : operation_mode = MODE_NORMAL
[00:14:17:545743] Info : use_encryption = false
[00:14:17:545745] Info : binding_key_file = /etc/binding-key.key
[00:14:17:545746] Info : binding_key_override = false
[00:14:17:545747] Info : binding_method = 
[00:14:17:545749] Info : stdout_tracing = false
[00:14:17:545750] Info : file_tracing = false
[00:14:17:545751] Info : lttng_tracing = false
[00:14:17:545752] Info : enable_frame_trace = false
[00:14:17:545754] Info : traces_folder = /dev/shm/cpcd-traces
[00:14:17:545755] Info : bus = UART
[00:14:17:545756] Info : uart_baudrate = 115200
[00:14:17:545758] Info : uart_hardflow = true
[00:14:17:545760] Info : uart_file = /dev/ttyUSB0
[00:14:17:545761] Info : spi_file = /dev/spidev0.0
[00:14:17:545762] Info : spi_bitrate = 1000000
[00:14:17:545764] Info : spi_mode = SPI_MODE_0
[00:14:17:545765] Info : spi_bit_per_word = 8
[00:14:17:545766] Info : spi_cs_chip = gpiochip0
[00:14:17:545768] Info : spi_cs_pin = 8
[00:14:17:545769] Info : spi_irq_chip = gpiochip0
[00:14:17:545770] Info : spi_irq_pin = 22
[00:14:17:545771] Info : fu_reset_chip = gpiochip0
[00:14:17:545772] Info : fu_spi_reset_pin = 23
[00:14:17:545774] Info : fu_wake_chip = gpiochip0
[00:14:17:545775] Info : fu_spi_wake_pin = 24
[00:14:17:545776] Info : fu_recovery_enabled = false
[00:14:17:545777] Info : fu_connect_to_bootloader = false
[00:14:17:545779] Info : fu_enter_bootloader = false
[00:14:17:545780] Info : fu_file = 
[00:14:17:545781] Info : restart_cpcd = false
[00:14:17:545782] Info : board_controller_ip_addr = 
[00:14:17:545784] Info : application_version_validation = false
[00:14:17:545785] Info : print_secondary_versions_and_exit = false
[00:14:17:545786] Info : use_noop_keep_alive = false
[00:14:17:545788] Info : reset_sequence = true
[00:14:17:545789] Info : uart_validation_test_option = 
[00:14:17:545790] Info : stats_interval = 0
[00:14:17:545792] Info : rlimit_nofile = 2000
[00:14:17:545793] Info : ENCRYPTION IS DISABLED 
[00:14:17:545794] Info : Starting daemon in normal mode
[00:14:17:561754] Info : Connecting to Secondary...
[00:14:17:650718] Info : Connected to Secondary
[00:14:17:656149] Info : Secondary Protocol v3
[00:14:17:668242] Info : Secondary CPC v4.2.1
[00:14:17:673869] Info : Secondary bus speed is 115200
[00:14:17:680004] Info : Secondary APP vUNDEFINED
[00:14:17:680135] Info : Daemon startup was successful. Waiting for client connections
[00:14:18] INFO: Setup OTBR firewall...
[00:14:18] INFO: Starting otbr-agent...
otbr-agent[291]: [NOTE]-AGENT---: Running 0.3.0
otbr-agent[291]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[291]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[291]: [NOTE]-AGENT---: Radio URL: spinel+cpc://cpcd_0?iid=2
otbr-agent[291]: [NOTE]-ILS-----: Infra link selected: eth0
otbr-agent[291]: 50d.04:50:10.786 [C] Platform------: mCpcBusSpeed = 115200
[00:14:18:749930] Info : New client connection using library v4.2.1.0
[00:14:18:756693] Info : Opened connection socket for ep#12
[00:14:18:756895] Info : Endpoint socket #12: Client connected. 1 connections
[00:14:19:284357] Info : New client connection using library v4.2.1.0
[00:14:19:291138] Info : Endpoint socket #12: Client connected. 2 connections
otbr-agent[291]: 50d.04:50:12.868 [N] Platform------: RCP API Version: 6
otbr-agent[291]: 00:00:00.135 [N] BorderRouter--: BR ULA prefix: fdbe:c8ce:7975::/48 (loaded)
otbr-agent[291]: 00:00:00.135 [N] BorderRouter--: Local on-link prefix: fdde:ad00:beef:cafe::/64
otbr-agent[291]: 00:00:00.138 [N] BorderRouter--: Local on-link prefix: fdde:ad00:beef:cafe::/64
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
[00:14:21] INFO: Successfully sent discovery information to Home Assistant.
s6-rc: info: service otbr-agent-rest-discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
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::40d4:3fff:fe9e:34ed/veth37f960e/122
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::40d4:3fff:fe9e:34ed/veth37f960e/122
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::40d4:3fff:fe9e:34ed/veth37f960e/122
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::40d4:3fff:fe9e:34ed/veth37f960e/122
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::40d4:3fff:fe9e:34ed/veth37f960e/122
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::40d4:3fff:fe9e:34ed/veth37f960e/122
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::40d4:3fff:fe9e:34ed/veth37f960e/122
Accepted connection 7.
Restarting
[00:14:58:983784] Info : Endpoint socket #12: Client disconnected. 1 connections
[00:14:58:983855] Info : Client disconnected
[00:14:59:986870] Info : New client connection using library v4.2.1.0
[00:14:59:993746] Info : Endpoint socket #12: Client connected. 2 connections
Reusing socket from previous instance.
Socket connection has been closed, restarting...
Listening on port 9999 for connection...
Accepting connection.

Additional information

No response

tommyjlong commented 1 year ago

I'll add that I am having issues using zigbee2mqtt connected to SiLabs-Multiprotocol and its possibly related to this mDNS errors. I have had some success getting these two Add-Ons to work together (but not always) with SiLabs-Multiprotocol v0.13 and zigbee2mqtt version 1.30.1. I almost never have success with SiLabs-Multiprotocol version 1.0.0.

Here is an interesting log for SiLabs-Multiprotocol version 0.13.1. I restarted Multiprotocol and after around 30s or so, I restarted zigbee2mqtt
zigbee2mqtt's zigbeeherdsman says the socket opens successfully and starts a dialog which ended up failing saying it could not deliver a DATA message. I ended up restarting zigbee2mqtt a few times before it finally started working.

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.

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::94d6:28ff:fe1d:bc4d/veth7232e77/95
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::94d6:28ff:fe1d:bc4d/veth7232e77/95
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::94d6:28ff:fe1d:bc4d/veth7232e77/95
Accepted connection 7.
Restarting
[15:02:54:683768] Info : Endpoint socket #12: Client disconnected. 1 connections
[15:02:54:683816] Info : Client disconnected
[15:02:55:738644] Info : New client connection using library v4.2.1.0
[15:02:55:749306] Info : Endpoint socket #12: Client connected. 2 connections
Reusing socket from previous instance.
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::3c58:43ff:fe91:d6a4/veth8f0b3be/97
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::3c58:43ff:fe91:d6a4/veth8f0b3be/97
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::3c58:43ff:fe91:d6a4/veth8f0b3be/97
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::3c58:43ff:fe91:d6a4/veth8f0b3be/97
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::3c58:43ff:fe91:d6a4/veth8f0b3be/97
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::3c58:43ff:fe91:d6a4/veth8f0b3be/97
Accepted connection 8.
Restarting
[15:04:53:827354] Info : Endpoint socket #12: Client disconnected. 1 connections
[15:04:53:827387] Info : Client disconnected
[15:04:54:889964] Info : New client connection using library v4.2.1.0
[15:04:54:900579] Info : Endpoint socket #12: Client connected. 2 connections
Reusing socket from previous instance.

When using SiLabs Multiprotocol v1.0.0, I repeated this experiment, all of which ended in zigbee2mqtt failing:

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::54e5:18ff:fe93:b48f/vethd9f99e7/103
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::54e5:18ff:fe93:b48f/vethd9f99e7/103
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::54e5:18ff:fe93:b48f/vethd9f99e7/103
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::54e5:18ff:fe93:b48f/vethd9f99e7/103
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::54e5:18ff:fe93:b48f/vethd9f99e7/103
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::54e5:18ff:fe93:b48f/vethd9f99e7/103
Accepted connection 7.
Restarting
[15:58:42:194501] Info : Endpoint socket #12: Client disconnected. 1 connections
[15:58:42:194535] Info : Client disconnected
[15:58:43:249106] Info : New client connection using library v4.2.1.0
[15:58:43:262184] Info : Endpoint socket #12: Client connected. 2 connections
Reusing socket from previous instance.
[15:58:46] INFO: zigbeed ended with exit code 256 (signal 13)...
[15:58:46:502950] Info : Endpoint socket #12: Client disconnected. 1 connections
[15:58:46:503022] Info : Client disconnected
[15:58:47] INFO: Starting zigbeed...
[15:58:48:946588] Info : New client connection using library v4.2.1.0
[15:58:48:959587] Info : Endpoint socket #12: Client connected. 2 connections
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::8f8:78ff:fec3:c92f/veth7772907/105
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8f8:78ff:fec3:c92f/veth7772907/105
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8f8:78ff:fec3:c92f/veth7772907/105
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8f8:78ff:fec3:c92f/veth7772907/105
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8f8:78ff:fec3:c92f/veth7772907/105
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8f8:78ff:fec3:c92f/veth7772907/105
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8f8:78ff:fec3:c92f/veth7772907/105
Accepted connection 7.
Restarting
[16:01:07:868593] Info : Endpoint socket #12: Client disconnected. 1 connections
[16:01:07:868647] Info : Client disconnected
[16:01:08:930517] Info : New client connection using library v4.2.1.0
[16:01:08:941171] Info : Endpoint socket #12: Client connected. 2 connections
Reusing socket from previous instance.
[16:01:12] INFO: zigbeed ended with exit code 256 (signal 13)...
[16:01:12:167724] Info : Endpoint socket #12: Client disconnected. 1 connections
[16:01:12:167756] Info : Client disconnected
[16:01:13] INFO: Starting zigbeed...
[16:01:14:332493] Info : New client connection using library v4.2.1.0
[16:01:14:342573] Info : Endpoint socket #12: Client connected. 2 connections
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::2082:c9ff:fe87:24c0/vethbba126a/107
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::2082:c9ff:fe87:24c0/vethbba126a/107
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::2082:c9ff:fe87:24c0/vethbba126a/107
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::2082:c9ff:fe87:24c0/vethbba126a/107
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::2082:c9ff:fe87:24c0/vethbba126a/107
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::2082:c9ff:fe87:24c0/vethbba126a/107
Accepted connection 7.
Restarting
[16:04:20:882834] Info : Endpoint socket #12: Client disconnected. 1 connections
[16:04:20:882879] Info : Client disconnected
[16:04:21:952374] Info : New client connection using library v4.2.1.0
[16:04:21:964520] Info : Endpoint socket #12: Client connected. 2 connections
Reusing socket from previous instance.
[16:04:25] INFO: zigbeed ended with exit code 256 (signal 13)...
[16:04:25:198131] Info : Endpoint socket #12: Client disconnected. 1 connections
[16:04:25:198168] Info : Client disconnected
[16:04:26] INFO: Starting zigbeed...
[16:04:27:379418] Info : New client connection using library v4.2.1.0
[16:04:27:391591] Info : Endpoint socket #12: Client connected. 2 connections
Listening on port 9999 for connection...
Accepting connection.
samuelthng commented 1 year ago

Hi, I'm getting the exact same issue. Unplugging and replugging the SkyConnect, restarts all did not resolve the issue.

Running HA OS on Synology DSM 7's VM.

mbay0r commented 1 year ago

i have the same issue. HA OS on a QNAP as Virtual Machine.

mbay0r commented 1 year ago

ive also have these errors:

otbr-agent[290]: 00:00:25.234 [N] MeshForwarder-: Dropping rx frag frame, error:Drop, len:9, src:0xb000, dst:0x7800, tag:14768, offset:504, dglen:513, sec:yes
otbr-agent[290]: 00:00:25.586 [N] MeshForwarder-: Dropping rx frag frame, error:Drop, len:96, src:0x0800, dst:0x7800, tag:43136, offset:216, dglen:513, sec:yes
otbr-agent[290]: 00:00:25.617 [N] MeshForwarder-: Dropping rx frag frame, error:Drop, len:96, src:0x0800, dst:0x7800, tag:43136, offset:312, dglen:513, sec:yes
otbr-agent[290]: 00:00:25.695 [N] MeshForwarder-: Dropping rx frag frame, error:Drop, len:96, src:0x0800, dst:0x7800, tag:43136, offset:408, dglen:513, sec:yes
otbr-agent[290]: 00:00:25.705 [N] MeshForwarder-: Dropping rx frag frame, error:Drop, len:9, src:0x0800, dst:0x7800, tag:43136, offset:504, dglen:513, sec:yes
Accepted connection 7.
otbr-agent[290]: 00:01:22.629 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:157, chksum:19a0, ecn:no, to:0xb400, sec:yes, error:NoAck, prio:net
mbay0r commented 1 year ago

My Thread devices are not working anymore. some are very laggy, but most doenst work.

mbay0r commented 1 year ago

otbr-agent[291]: 00:24:14.816 [N] MeshForwarder-: Dropping (reassembly queue) IPv6 UDP msg, len:195, chksum:0919, ecn:no, sec:yes, error:ReassemblyTimeout, prio:net, rss:-80.0

dreesi commented 1 year ago

I get the same error in my silabs addon, BUT my zigbee network ist working.

Silabs vers. 1.1.1.0 Z2M edge

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.

samuelthng commented 1 year ago

I get the same error in my silabs addon, BUT my zigbee network ist working.

Silabs vers. 1.1.1.0 Z2M edge

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? If so, it seems like anytime there's a VM it will refuse to work on multiprotocol.

dreesi commented 1 year ago

I use HA in a proxmox container, so yes I am passing it through. Did you try z2m edge?

samuelthng commented 1 year ago

@dreesi Yeah, even ZHA doesn't work for me, tried almost all permutations. 😂

github-actions[bot] commented 1 year ago

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.

TFenby commented 1 year ago

Also getting this, and also running HAOS in a PVE VM. Anybody get anywhere with debugging this?

matjahs commented 1 year ago

Have this error constantly using HAOS on an Odroid M1.

klassm commented 1 year ago

Can we reopen this? I also still have it 🙈

Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address)

diegocade1 commented 1 year ago

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 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::1833:ffff:fe45:12e2/veth0a1496e/27 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::1833:ffff:fe45:12e2/veth0a1496e/27 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::1833:ffff:fe45:12e2/veth0a1496e/27 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::1833:ffff:fe45:12e2/veth0a1496e/27 Accepted connection 8.

Restarting Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::1833:ffff:fe45:12e2/veth0a1496e/27`

willysagefalk commented 1 year ago

Getting the same error.

Listening on port 9999 for connection... Accepting connection. otbr-agent[321]: 00:00:55.131 [N] RoutingManager: Local on-link prefix: fdf8:7d0a:41dc:a33c::/64 otbr-agent[321]: 00:00:55.329 [N] Mle-----------: Role disabled -> detached otbr-agent[321]: 00:00:55.330 [N] Platform------: [netif] Changing interface state to up. otbr-agent[321]: 00:00:55.425 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::f8f7:c9ff:fe8b:a7a9/vethcf8d64a/20 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::f8f7:c9ff:fe8b:a7a9/vethcf8d64a/20

klassm commented 1 year ago

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

lucasstinis commented 9 months ago

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.

tirreni8a commented 9 months ago

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... Zigbee2MQTT:info 2023-12-17 16:31:05: Logging to console and directory: '/config/zigbee2mqtt/log/2023-12-17.16-31-05' filename: log.txt Zigbee2MQTT:info 2023-12-17 16:31:05: Starting Zigbee2MQTT version 1.34.0 (commit #unknown) Zigbee2MQTT:info 2023-12-17 16:31:05: Starting zigbee-herdsman (0.25.0) Assertion failed: Command (setConfigurationValue) returned unexpected state: [object Object] Assertion failed: Command (setValue) returned unexpected state: 55 Zigbee2MQTT:info 2023-12-17 16:31:11: zigbee-herdsman started (resumed)

Any idea ? Thanks

lucasstinis commented 9 months ago

I found same issue on SiliconLab's log after have changed firmware on my SONOFF Dongle-E to the RCP ZigBee + Thread.

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:

port: tcp://core-silabs-multiprotocol:9999 adapter: ezsp

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.

Evaske commented 8 months ago

I am also getting the above issues since adding he SiliconLabs multi protocol firmware.

Nosari89 commented 8 months ago

ma è normale che questo problema c'è da Marzo '23 e non si è ancora risolto ? chiedo da nuovissimo in HA e sono anch'io nella stessa barca ='(

Acey-yo commented 8 months ago

I have the same issue and nothing work. Use it on Synology NAS with VM.

HFeenstra commented 7 months ago

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. Running an Home Assistant Blue, 2024.1.3 with Skyconnect, 2.4.2 Sillicon lab firmware, looks like it started when upgrading to 2.4.4 (firmware as of 26-1-2024). Have ZHA integration and was working perfectly until this interruption.

What did I do: Restore backup before this issue, then reboot the whole system including hardware, then it works for 15 min and gives these issues in logbook: Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::404:86ff:fe05:cc18/vetha5a6c7e/67 otbr-agent[324]: 00:00:27.117 [N] Mle-----------: RLOC16 2c00 -> fffe otbr-agent[324]: 00:00:27.121 [W] Platform------: [netif] Failed to process request#5: Unknown error -95 otbr-agent[324]: 00:00:27.659 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset otbr-agent[324]: 00:00:34.159 [N] RouterTable---: Allocate router id 11 otbr-agent[324]: 00:00:34.159 [N] Mle-----------: RLOC16 fffe -> 2c00 otbr-agent[324]: 00:00:34.162 [N] Mle-----------: Role detached -> leader otbr-agent[324]: 00:00:34.162 [N] Mle-----------: Partition ID 0x3f3010f5 otbr-agent[324]: 00:00:34.288 [W] Platform------: [netif] Failed to process request#6: Unknown error -17 otbr-agent[324]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary! Accepted connection 7. Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c4c:38ff:feb2:fca2/veth137d550/69 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c4c:38ff:feb2:fca2/veth137d550/69 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c4c:38ff:feb2:fca2/veth137d550/69 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c4c:38ff:feb2:fca2/veth137d550/69 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c4c:38ff:feb2:fca2/veth137d550/69 Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::c4c:38ff:feb2:fca2/veth137d550/69 Socket connection has been closed, restarting... Listening on port 9999 for connection... Accepting connection. Accepted connection 7. Restarting [17:46:53:865568] Info : Endpoint socket #12: Client disconnected. 1 connections [17:46:53:865631] Info : Client disconnected [17:46:54:869883] Info : New client connection using library v4.3.1.0 [17:46:54:873434] Info : Endpoint socket #12: Client connected. 2 connections Reusing socket from previous instance.

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??

BacchusIX commented 7 months ago

also have Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface ....... any fix?

bluefunoodle311 commented 7 months ago

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

bobloadmire commented 5 months ago

same error here, its been a few months, has anyone made any progress?

JrCs commented 5 months ago

Same error with latest silicon labs multi protocol firmware

bobloadmire commented 5 months ago

Same error with latest silicon labs multi protocol firmware

where are you getting the latest firmware?

JrCs commented 5 months ago

Same error with latest silicon labs multi protocol firmware

where are you getting the latest firmware?

On the darkxst‘s Web Flasher

ssorgatem commented 2 months ago

Same error here, running HAOS on a KVM on Debian.

cjessing commented 1 month ago

Fwiw then this post was the key for me:

https://community.home-assistant.io/t/open-thread-border-router-or-apple-google/691903/2

I have HA running in a Proxmox container using a SkyConnect mapped into HA using the "Use USB Vendor/Device ID" in Proxmox. I was getting the "Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet" error but after sync'ing credentials from HA onto my Pixel 7 phone as described, the device connected.

I had previously flashed the latest Thread firmware onto my SkyConnect from this page (after installing the Silicon Labs drivers on my windoze machine):

https://connectzbt1.home-assistant.io/firmware-update/#from-skyconnect

Maybe this helps others, who knows :-)