Open ecchodun opened 9 months ago
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!
(message by CodeOwnersMention)
zha documentation zha source (message by IssueLinks)
Looks like your network setting is being out of sync.
homeassistant.exceptions.HomeAssistantError: Network settings do not match most recent backup
Reconfigure you network from the ZHA integration and look if its working but it can being you is loosing some or all devices the doing it.
Looks like your network setting is being out of sync.
homeassistant.exceptions.HomeAssistantError: Network settings do not match most recent backup
Reconfigure you network from the ZHA integration and look if its working but it can being you is loosing some or all devices the doing it.
It's only showing it as out of sync because before I copied the log, I changed the ZHA channel from [AUTO] to "22" to try to resolve the issue. The issue is still present though. See this thread for others with the same issue - https://community.home-assistant.io/t/failed-to-deliver-message-emberstatus-delivery-failed-102/592145/27
In your log it says:
2023-11-06 18:29:29.490 WARNING (MainThread) [zigpy.application] Zigbee channel 22 utilization is 93.76%! 2023-11-06 18:29:29.490 WARNING (MainThread) [zigpy.application] If you are having problems joining new devices, are missing sensor updates, or have issues keeping devices joined, ensure your coordinator is away from interference sources such as USB 3.0 devices, SSDs, WiFi routers, etc.
Re-run the channel migration but leave the channel selector on auto
. This isn't a persistent setting, it just tells ZHA to pick the best channel in the moment. It won't change the channel a second time until you run the channel migration tool again.
In your log it says:
2023-11-06 18:29:29.490 WARNING (MainThread) [zigpy.application] Zigbee channel 22 utilization is 93.76%! 2023-11-06 18:29:29.490 WARNING (MainThread) [zigpy.application] If you are having problems joining new devices, are missing sensor updates, or have issues keeping devices joined, ensure your coordinator is away from interference sources such as USB 3.0 devices, SSDs, WiFi routers, etc.
Re-run the channel migration but leave the channel selector on
auto
. This isn't a persistent setting, it just tells ZHA to pick the best channel in the moment. It won't change the channel a second time until you run the channel migration tool again.
I apologize if I'm not being clear. The DELIVERY_FAILED: 102 error has occurred at varying instances for over a year. Just prior to providing my core log, I changed the channel in the ZHA configuration from Auto to Channel 22 to see if it would help. ZHA configuration is now indicating channel 22 as the active channel and thus, far (over 24 hours), I've not received the DELIVERY_FAILED error. I do know that its occurrence appears random though.
Hello,
same problem here: The problem Randomly, Zigbee ZHA devices won't work (appear as unavailable, sometimes (like today at 5AM) appears like avivable but stopped working). First day (11.11) it was lightbulb unavivable, restart lightbulb worked, next day second lightbulb unavivable, next day all Zigbee devices stoped working, but looks avivable, restart ZHA module solved problem.
What version of Home Assistant Core has the issue? core-2023.11.2 What was the last working version of Home Assistant Core? 2023.11.0 - not 100% sure
What type of installation are you running? Home Assistant OS
Integration causing the issue Zigbee Home Automation
Link to integration documentation on our website https://www.home-assistant.io/integrations/zha/
Diagnostics information - probably does not help, because it is after restart HA home-assistant_2023-11-13T05-08-22.892Z.log
New error that i get few last days:
Default channel (auto), never changed.
Logger: zigpy.application Source: components/zha/core/gateway.py:209 First occurred: 05:20:07 (2 occurrences) Last logged: 05:20:07
Zigbee channel 11 utilization is 84.16%! If you are having problems joining new devices, are missing sensor updates, or have issues keeping devices joined, ensure your coordinator is away from interference sources such as USB 3.0 devices, SSDs, WiFi routers, etc.
Two errors today: First: Logger: homeassistant.components.automation.bedroom_light_on_off_baby_light Source: components/automation/init.py:676 Integration: Automation (documentation, issues) First occurred: 06:59:27 (1 occurrences) Last logged: 06:59:27
Error while executing automation automation.bedroom_light_on_off_baby_light: Failed to send request: Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>
Second: Logger: homeassistant.components.automation.bedroom_light_on_off_baby_light Source: helpers/script.py:1783 Integration: Automation (documentation, issues) First occurred: 06:59:27 (3 occurrences) Last logged: 07:05:03
BEDROOM - Light On/Off - Baby Light: Choose at step 1: choice 1: Error executing script. Error for call_service at pos 1: Failed to send request: Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102> BEDROOM - Light On/Off - Baby Light: Error executing script. Error for choose at pos 1: Failed to send request: Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102> BEDROOM - Light On/Off - Baby Light: Already running
Today again same problem. All Zigbee devices stoped working. Reload integration fixed problem. Here are logs when problem occures: Debug ZHA: home-assistant_zha_2023-11-20T17-01-09.044Z.log
Complete log: home-assistant_2023-11-20T17-03-29.960Z.log
I have the same issue.
I have a mix of zigbee brands from IKEA, Ecodim, Sonoff and Tuya knockoff brands. The (end and router) devices are located all over the house. I use a Sonoff ZBBridge over wifi with tasmota and ZHA.
I have changed the channel to channel 22.
energy_scan: "11": 99.94584318876281, "12": 99.89631182837557, "13": 99.92977369505088, "14": 99.82571687826758, "15": 93.76433891498253, "16": 65.26028270288712, "17": 82.35373987514762, "18": 59.15797905332195, "19": 62.257682586134884, "20": 59.15797905332195, "21": 52.75969252664325, "22": 49.512515447068886, "23": 68.14622793558128, "24": 75.96022321405563, "25": 80.38447947821754, "26": 73.50699819621309
I have limited the number of end device to the coordinator and have rebuild the zigbee network by turning off the power of the coordinator by an hour.
I have noticed that 102 failure does not occur with the IKEA and ecodim devices. The failure occurs sending a command to the Tuya device’s and my newly installed ZBMiniL2 (end device).
The other way around the state of a device changes directly in HA when for example switching off the smart plug with the button on the device.
Does anyone recognise this behaviour?
Thank you for your research. I use some Tuya TRVs connected over an ikea driver and encounter same issues. I bound them directly to my main coordinator now. Time will see if errors occur again.
With EZSP is possible forcing end device using routers and not the coordinator by adding this in the HA config and the coordinator is blocked having direct children (End devices):
zha:
zigpy_config:
ezsp_config:
CONFIG_MAX_END_DEVICE_CHILDREN: 0
Its recommended pouting in in after adding at least one router to the network and then restart HA so its being used and then end devices is b´not getting problems if the coordinator is off line for upgrade or having problems.
I don't think the coordinator is the problem but the combination of routers and end devices in this case ikea router and tuya end devices.
Couldn't a "number of retries before fail" option be added to the Zigbee integration to at least gives those with this issue a fighting chance. As it is, I've nested "until" programming into some of my animations to act as a retry function just to get past the issues (e.g., until status of switch is on, keep turning on switch).
Couldn't a "number of retries before fail" option be added to the Zigbee integration to at least gives those with this issue a fighting chance.
Every request is retried three times with a small delay before giving up.
Stacking retries won't fix your underlying network issue, which is the root cause of this problem. Can you upload diagnostics information for the ZHA integration? If you're still using channel 22, it's not a good choice, as per the startup warning.
Couldn't a "number of retries before fail" option be added to the Zigbee integration to at least gives those with this issue a fighting chance.
Every request is retried three times with a small delay before giving up.
Stacking retries won't fix your underlying network issue, which is the root cause of this problem. Can you upload diagnostics information for the ZHA integration? If you're still using channel 22, it's not a good choice, as per the startup warning.
Apologize for the ignorance, but how do I get upload diagnostics? Also, channel 22 seems to be more stable for me than channel 15, but that could be a coincidence.
Click the cog wheel next to "Zigbee Home Automation" and then look under the three dot menu:
Click the cog wheel next to "Zigbee Home Automation" and then look under the three dot menu:
![]()
See attached. Thank you. diagnostics.txt
From the diagnostics, you can see the percentage utilization of every channel:
"11": 96.64469941013013,
"12": 96.19660508390695,
"13": 96.19660508390695,
"14": 96.64469941013013,
"15": 65.26028270288712,
"16": 28.30261646762903,
"17": 19.00785284282869,
"18": 55.9836862725909,
"19": 52.75969252664325,
"20": 36.830390267097734,
"21": 13.711043742539033,
"22": 92.95959997754716, # Your network's channel
"23": 23.33483723001185,
"24": 8.631361812931262,
"25": 36.830390267097734,
"26": 62.257682586134884
As you can see, there's a lot of interference across the board. I suggest moving your coordinator away from USB 3.0 ports, SSDs, 2.4GHz routers, etc. and onto a USB extension cable. Once that is done, run the scan again and see what happens. Running the channel migration tool in ZHA will pick the quietest channel at the time of you running it, which seems like 25 (though other channels may be better once you eliminate interference sources).
From the diagnostics, you can see the percentage utilization of every channel:
"11": 96.64469941013013, "12": 96.19660508390695, "13": 96.19660508390695, "14": 96.64469941013013, "15": 65.26028270288712, "16": 28.30261646762903, "17": 19.00785284282869, "18": 55.9836862725909, "19": 52.75969252664325, "20": 36.830390267097734, "21": 13.711043742539033, "22": 92.95959997754716, # Your network's channel "23": 23.33483723001185, "24": 8.631361812931262, "25": 36.830390267097734, "26": 62.257682586134884
As you can see, there's a lot of interference across the board. I suggest moving your coordinator away from USB 3.0 ports, SSDs, 2.4GHz routers, etc. and onto a USB extension cable. Once that is done, run the scan again and see what happens. Running the channel migration tool in ZHA will pick the quietest channel at the time of you running it, which seems like 25 (though other channels may be better once you eliminate interference sources).
The coordinator is about 5+ feet from the server computer and any routers on a USB extension cable. What's this about away from USB 3.0 ports though? I assume that doesn't include the port it's currently plugged into? Should I switch to channel 25 and give you a new report in about an hour?
Ok so what i did to make zigbe network works again:
New errors:
I have debug zigbee log but it has over 160MB so i cannot upload it here.
I don't think the coordinator is the problem but the combination of routers and end devices in this case ikea router and tuya end devices.
The coordinator is having the same chip in my case and the coordinator is one router with one extra trust center and its need time communicating with the host system and doing more works. I have sniffing many systems and most coordinators router part is morally lazy (some very) and can needing more retries for acking some frames and its no large problems with routers but end devices is very bad then they is going to sleep and is i using only 1/ of the RF power as one router with the came chip is using.
tuya "old" devices (that is using Silabs chips) is normally working OK bu the new ones (TELink) is can having little more bugs (i have one working 100% OK and other little strange some time) and 95% of all tuya devices is not certificated (only the"A" devices like LIDLs) and IKEA is 100% and is very "Zigbee R22 / 23". I think our Puddly is having the same experience.
I think in the end its RF problems and / or bad routers that cant communicating OK all the time.
Edit: If getting this problems from sleeping end devices and is from color or OTA cluster request like [0xBCEF:1:0x0020] (IKEA Dimmer switch) its very likely one bug in ZHA then i getting it from ore devices thatis having good routers (the OTA is requested from the device and its waiting some seconds for getting replay and if the system or the network having large delays its going back to sleep and cant getting the replay and the system is timing out).
Today I restarted home assistant and my log shows:
Zigbee channel 25 utilization is 80.38%!
After half an hour I've downloaded the coordinator diagnosic:
"energy_scan": {
"11": 92.95959997754716,
"12": 94.48255331375627,
"13": 95.69133648577223,
"14": 93.76433891498253,
"15": 73.50699819621309,
"16": 65.26028270288712,
"17": 75.96022321405563,
"18": 80.38447947821754,
"19": 55.9836862725909,
"20": 43.057636198227904,
"21": 52.75969252664325,
"22": 46.26944564832987,
"23": 43.057636198227904,
"24": 43.057636198227904,
"25": 36.830390267097734,
"26": 89.93931580241996
}
I am curious about why this happens. Is zha flooding the devices with some alive pings after restart?
So after backup recovery problem is back. Next step is change channel again and readd/ repair network again. And Yes energy scan seems to scan local zigbee network as well, anytime, when i migrate to different channel, then utilization is much bigger then before.
There is topic with more users and same problem: https://community.home-assistant.io/t/failed-to-deliver-message-emberstatus-delivery-failed-102/592145/48
@puddly I was updating HA to 2024.1.3 and my production system was looping 11 times before coming online. I have one LIDL outdoor plug [0x4CBF:1:0x0006]
that is offline (was getting water inside it so its have burned) and the neighbors Philips HUE light bulb [0x6FB6:11:0x0006/:0x0008]
have joining the system (agen) but i cant getting it leaving then its 98% of the time un powered and online late in the night some seconds.
I sending you the log by email.
Thanks in advance !!!
Since I moved to channel 16 now (52% optimization), I continue to get the same error here though not as frequently (once every few days). Frustrating that this is an issue and we can't completely figure out the root of it. Should I just buy a new Zigbee dongle? I'm using the Sonoff Zigbee 3.0 Plus E?
In my case I discovered it was only one temperature sensor the one who failed. I tired to put it closer to the zigbee router and the problem disappeared. When I put it in the original place I started to get the error messages again...
So I changed the sensor with problems by other closer to the Zigbee router and now I don't have the error.
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.
I still see this error occasionally. I am on (almost) latest version.The only way I have found to clear it is by reloading the integration. I cannot find any way to reproduce it.
I did change my zigbee channel, repair battery devices and everything works for few months without problem. This is only solution, that helped me in the past.
Still present.
Though it's been awhile.
Happened again for me today. 2024.3.3 It happened for a sunrise automation (opening blinds) and then world not work again until ZHA was reloaded.
I'm also still having major issues with my Zigbee network. What I have tried so far:
My setup:
What I have tried:
Issues / symptoms:
Questions
The last thing I would do to fix this, is install a second NUC in the secondary building with ZB2MQTT and a seperate Zigbee network. Not ideal, and I'd rather use only one Zigbee network. I've read it can be done with the amount of lights I have, but I start to wonder how, since Ive tried everything
@anthony-nl Post your ZHA integration diagnostics JSON. It will include values for the various EZSP counters and the channel energy scan, which shows what your actual channel noise is. If 11 is noisier than 15, you will have network issues.
Once your channel is properly set and confirmed to be away from 2.4GHz noise (WiFi isn't the only source), the next thing to try is source routing. It may reduce routing traffic and help with delivery errors:
zha:
zigpy_config:
source_routing: true
@anthony-nl Post your ZHA integration diagnostics JSON. It will include values for the various EZSP counters and the channel energy scan, which shows what your actual channel noise is. If 11 is noisier than 15, you will have network issues.
Once your channel is properly set and confirmed to be away from 2.4GHz noise (WiFi isn't the only source), the next thing to try is source routing. It may reduce routing traffic and help with delivery errors:
zha: zigpy_config: source_routing: true
@puddly Yes, I understand that you must move to a channel without too much interference. I live in an open space with practically no neighbors. But I did look at the energy scan (after moving to channel 12 with Zigbee):
"11": 1.9464625152460222,
"12": 7.659755505061292,
"13": 3.6632469452765037,
"14": 12.244260188723507,
"15": 95.12234809209261,
"16": 1.7132450748239665,
"17": 5.317630506738386,
"18": 10.914542804728702,
"19": 3.6632469452765037,
"20": 6.011489450827149,
"21": 62.257682586134884,
"22": 91.05606689948522,
"23": 92.0598007161209,
"24": 85.82097888710312,
"25": 5.317630506738386,
"26": 39.90320178295578
My wifi exists of 4 Unifi access points, 2 in each bulding. I put them all on wifi channel 11 for 2.4 ghz (zigbee channels 21 to 26)
As you can see, channel 15 is / was pretty busy. I suspect this is something like bluetooth or my wireless headset or something like that. Channel 12 is not busy at all.
Still interesting to know what happens in the spectrum when I controll more lights. Maybe I will bring a Cisco 2702 AP from my work and put it into monitor mode, to have a live graph in the spectrum.
Can you include the rest of the diagnostics JSON? The counters in it are useful to have too.
@puddly Here is the entire diag:
```json
{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2024.5.3",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.12.2",
"docker": true,
"arch": "x86_64",
"timezone": "Europe/Amsterdam",
"os_name": "Linux",
"os_version": "6.6.29-haos",
"supervisor": "2024.05.1",
"host_os": "Home Assistant OS 12.3",
"docker_version": "25.0.5",
"chassis": "vm",
"run_as_root": true
},
"custom_components": {
"afvalwijzer": {
"documentation": "https://github.com/xirixiz/homeassistant-afvalwijzer/blob/master/README.md",
"version": "2021.10.02",
"requirements": []
},
"remeha_home": {
"documentation": "https://github.com/msvisser/remeha_home",
"version": "0.1.12",
"requirements": []
},
"dwains_dashboard": {
"documentation": "https://dwainscheeren.github.io/dwains-lovelace-dashboard/",
"version": "2.0.3",
"requirements": []
},
"cryptoinfo": {
"documentation": "https://github.com/heyajohnny/cryptoinfo",
"version": "0.0.8",
"requirements": []
},
"zha_toolkit": {
"documentation": "https://github.com/mdeweerd/zha-toolkit",
"version": "v0.9.9",
"requirements": [
"pytz"
]
},
"daikin_residential": {
"documentation": "https://github.com/rospogrigio/daikin_residential/",
"version": "2.3.1",
"requirements": [
"oic==1.6.0"
]
},
"hacs": {
"documentation": "https://hacs.xyz/docs/configuration/start",
"version": "1.34.0",
"requirements": [
"aiogithubapi>=22.10.1"
]
},
"miele": {
"documentation": "https://github.com/HomeAssistant-Mods/home-assistant-miele",
"version": "v2021.10.12",
"requirements": [
"requests_oauthlib>=1.3.0"
]
}
},
"integration_manifest": {
"domain": "zha",
"name": "Zigbee Home Automation",
"after_dependencies": [
"onboarding",
"usb"
],
"codeowners": [
"@dmulcahey",
"@adminiuga",
"@puddly",
"@TheJulianJES"
],
"config_flow": true,
"dependencies": [
"file_upload"
],
"documentation": "https://www.home-assistant.io/integrations/zha",
"iot_class": "local_polling",
"loggers": [
"aiosqlite",
"bellows",
"crccheck",
"pure_pcapy3",
"zhaquirks",
"zigpy",
"zigpy_deconz",
"zigpy_xbee",
"zigpy_zigate",
"zigpy_znp",
"universal_silabs_flasher"
],
"requirements": [
"bellows==0.38.4",
"pyserial==3.5",
"pyserial-asyncio==0.6",
"zha-quirks==0.0.115",
"zigpy-deconz==0.23.1",
"zigpy==0.64.0",
"zigpy-xbee==0.20.1",
"zigpy-zigate==0.12.0",
"zigpy-znp==0.12.1",
"universal-silabs-flasher==0.0.18",
"pyserial-asyncio-fast==0.11"
],
"usb": [
{
"vid": "10C4",
"pid": "EA60",
"description": "*2652*",
"known_devices": [
"slae.sh cc2652rb stick"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "*slzb-07*",
"known_devices": [
"smlight slzb-07"
]
},
{
"vid": "1A86",
"pid": "55D4",
"description": "*sonoff*plus*",
"known_devices": [
"sonoff zigbee dongle plus v2"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "*sonoff*plus*",
"known_devices": [
"sonoff zigbee dongle plus"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "*tubeszb*",
"known_devices": [
"TubesZB Coordinator"
]
},
{
"vid": "1A86",
"pid": "7523",
"description": "*tubeszb*",
"known_devices": [
"TubesZB Coordinator"
]
},
{
"vid": "1A86",
"pid": "7523",
"description": "*zigstar*",
"known_devices": [
"ZigStar Coordinators"
]
},
{
"vid": "1CF1",
"pid": "0030",
"description": "*conbee*",
"known_devices": [
"Conbee II"
]
},
{
"vid": "0403",
"pid": "6015",
"description": "*conbee*",
"known_devices": [
"Conbee III"
]
},
{
"vid": "10C4",
"pid": "8A2A",
"description": "*zigbee*",
"known_devices": [
"Nortek HUSBZB-1"
]
},
{
"vid": "0403",
"pid": "6015",
"description": "*zigate*",
"known_devices": [
"ZiGate+"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "*zigate*",
"known_devices": [
"ZiGate"
]
},
{
"vid": "10C4",
"pid": "8B34",
"description": "*bv 2010/10*",
"known_devices": [
"Bitron Video AV2010/10"
]
}
],
"zeroconf": [
{
"type": "_esphomelib._tcp.local.",
"name": "tube*"
},
{
"type": "_zigate-zigbee-gateway._tcp.local.",
"name": "*zigate*"
},
{
"type": "_zigstar_gw._tcp.local.",
"name": "*zigstar*"
},
{
"type": "_uzg-01._tcp.local.",
"name": "uzg-01*"
},
{
"type": "_slzb-06._tcp.local.",
"name": "slzb-06*"
}
],
"is_built_in": true
},
"data": {
"config": {
"device_config": {
"54:0f:57:ff:fe:92:41:bd-1": {
"type": "switch"
},
"54:0f:57:ff:fe:92:42:d9-1": {
"type": "switch"
}
},
"enable_quirks": true
},
"config_entry": {
"entry_id": "8ba3087b1968fb1795b8c662bb074ebc",
"version": 4,
"minor_version": 1,
"domain": "zha",
"title": "SkyConnect v1.0",
"data": {
"device": {
"path": "/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_0a036fa7583aed119e79885634a5ded1-if00-port0",
"flow_control": "software",
"baudrate": 115200
},
"radio_type": "ezsp"
},
"options": {
"custom_configuration": {
"zha_options": {
"group_members_assume_state": false,
"default_light_transition": 0,
"enhanced_light_transition": false,
"light_transitioning_flag": true,
"always_prefer_xy_color_mode": true,
"enable_identify_on_join": true,
"consider_unavailable_mains": 7200,
"consider_unavailable_battery": 21600
}
}
},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "usb",
"unique_id": "**REDACTED**",
"disabled_by": null
},
"application_state": {
"node_info": {
"nwk": 0,
"ieee": "**REDACTED**",
"logical_type": 0,
"model": "SkyConnect v1.0",
"manufacturer": "Nabu Casa",
"version": "7.4.2.0 build 0"
},
"network_info": {
"extended_pan_id": "**REDACTED**",
"pan_id": 26279,
"nwk_update_id": 1,
"nwk_manager_id": 0,
"channel": 12,
"channel_mask": 134215680,
"security_level": 5,
"network_key": "**REDACTED**",
"tc_link_key": {
"key": [
90,
105,
103,
66,
101,
101,
65,
108,
108,
105,
97,
110,
99,
101,
48,
57
],
"tx_counter": 0,
"rx_counter": 0,
"seq": 0,
"partner_ieee": "**REDACTED**"
},
"key_table": [],
"children": [],
"nwk_addresses": {},
"stack_specific": {
"ezsp": {
"hashed_tclk": "f5941a85edb4a1d8f8038b7ed9d4382d"
}
},
"metadata": {
"ezsp": {
"stack_version": 13,
"can_burn_userdata_custom_eui64": true,
"can_rewrite_custom_eui64": true
}
},
"source": "bellows@0.38.4"
},
"counters": {
"ezsp_counters": {
"MAC_RX_BROADCAST": {
"__type": "
@anthony-nl are you passing just the USB device (skyconnect dongle) to your proxmox VM or the whole USB controller using PCI passthrough? I've had issues before with qemu's USB passthrough, the speed is far from native.
@mamoit I am passing the USB port to HA, using the option "Use USB Port", and then select the Skyconnect. The configuration shows: host=1-5.4
(Before it was host=1-4, when I wasnt using a USB2.0 hub)
Is this the right way, or should I go with "Use USB Vendor/Device ID" ?
@anthony-nl Did you try the source routing config? In your log, I did not notice any sort of communication issues reported by the stick so I don't think your problem is caused by USB passthrough.
@puddly Thanks for your answer, I will try this later this week. I made a few adjustments, and I want to make sure my Zigbee network is not converging or anything. And I want to make sure that the issue is still there after a couple things ive tried.
@anthony-nl Yeah, that's exactly the USB passthrough that I meant, either by vendor, device id or whatever the "USB Device" will always be a passthrough and suffer from performance degradation. I had this happen with a DVB-T2 USB dongle that suffered from inexplicable data drops.
@puddly has a good point though and it is probably not an issue caused by the USB passthrough.
If you still want to try to pass the whole controller you should use neither of those, but instead "Add > PCI Device" instead of "Add > USB Device". Both are under the Hardware tab.
You can check the manual on how to setup PCI passthrough if you want to give it a go, but be aware that the whole USB controller and whatever else is in the same IOMMU group will be passed through to the VM.
Make sure you know what IOMMU groups are and how they are structured on your hardware in particular. If by any chance you pass your GPU or a NIC, which may be in the same group as the USB controller, to the VM it can a pain to revert your changes and ultimately bork your host.
On the host this should tell you all the USB controllers in your system, you'll have to find the right one where the dongle is connected to.
lspci | grep USB
Then add a PCI device to your VM with the device ID that you found previously.
@puddly Yesterday I've activated source routing with the exact config you shared, and rebooted Home Assistant. As I understand, each router only learns a route back to the coordinator, and does not maintain a routing table for each destination router in the network. Then the coordinator decides within each packet, which path it needs to follow, right? But for now, it looks like the lights are responding even worse, and I got the 102 error even more often now.
@mamoit I think this is too much of a risk to break anything, especially if this doesn't look like a passtrhough issue. What I can try, is installing home assistant on a secondary NUC I have here, and see what happens when I use it on bare metal.
The problem
Randomly, Zigbee ZHA devices won't work (appear as unavailable) and the aforementioned error is reported. Had the same error with varying success from prior versions of Core. If it can't be fixed, permit Core to allow a user-specified number of retries before Zigbee device animations are skipped. Using Zigbee USB device off a USB extension. Move from Channel Auto to Channel 22 to check if connection would be better.
What version of Home Assistant Core has the issue?
What was the last working version of Home Assistant Core?
Never totally worked
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Zigbee Home Automation
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
Diagnostics information
home-assistant_2023-11-07T00-46-31.718Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response