core Cannot communicate with Nous A1Z Plugs after some time

The problem

Opening a new thread as requested here:

For your problem, it's clear the issue is RF noise. Changing the channel will often help but if the noise moves around too (2.4GHz WiFi automatically picking channels), it's only a matter of time before it comes back. But a single delivery failures in 10 days seems perfectly fine.

I'm going to mark this issue as resolved.

If you're still having issues, please open a separate issue with debug logs!

I am having the same issue recently.

Currently my setup is as follows:

1 Home Assistant Green with SkyConnect dongle. Using the provided USB cable at positioned the furthest away from the box.
8 TS0601 Temperature/Humidity Sensor. (Only device that is battery powered)
2 Power sensors Zemismart working via a custom quirk.
4 Ledvance LED Lamps.
1 IKEA E27 Tradfri Lamp.
16 NOUS A1Z Plugs with Power Metering.
2 Repeaters IKEA Tradfri.
All this is within a 30m radius (but with some brick walls in between).

I have a 2.4Ghz Wi-Fi Network: 2 access points are operating on the channel 1 and 6. The SkyConnect runs on channel 20. From what I read there should not be interferences between both. Neighours are not an issue, I live in a pretty remote place 🧑‍🌾 .

I am running the latest versions of HASS: I tend to update very quickly once they are out.

A number of those devices are in the utility room: 4 Nous A1Z Plugs, 1 IKEA Repeater, One of the Zemismart power sensors. While all the devices in the network run correctly, I have two devices that are not behaving properly since approximatively a month. One of them in the utility room (Boucle d'eau chaude) where I expected the network to be good.

I will remove the unplug-replug the A1Z Plugs from the mains it will work perfectly for a couple of minutes but then every time I try to turn it off or on I get a <sl_Status.ZIGBEE_DELIVERY_FAILED: 3074> error.

It was working fine until mid summer, where I started having issues. I first imagined it was a poor RF connection and I have therefore added the 2 IKEA Repeaters and move the plugs around to no help.

When visualizing the network, it shows that a lot of the links are pretty bad quality, and that the route choosen by the Zigbee network tends not to be optimal. It almost looks like it tries to take the furthest path across devices. Especially with the Ikea Tradfri signal repeaters or in the utility room where I would expect 'Green Links' as they are in the vicinity of each-others.

I Have added the ZHA debug Logs.
I have turned the power of the whole house, hoping that having all those devices offline for a 5 minutes would help rebuild a better network.
I have (maybe not all devices, but close to) tried to repaired the devices with HA as they use to move around a bit. It's not the case anymore. But I read that it was better to pair them on the final place if possible.

What version of Home Assistant Core has the issue?

core-2024.9.2

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

Link to integration documentation on our website

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

Diagnostics information

home-assistant_zha_2024-09-19T18-26-25.923Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

Sep 19 '24 19:09 bestycame

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

Sep 19 '24 19:09 home-assistant[bot]

Further configurations:

-----------------------------------------------------------
 Add-on: Silicon Labs Multiprotocol
 Zigbee and OpenThread multiprotocol add-on
-----------------------------------------------------------
 Add-on version: 2.4.5
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.1  (aarch64 / green)
 Home Assistant Core: 2024.9.2
 Home Assistant Supervisor: 2024.09.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[20:02:43] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa.
[20:02:43] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0
2024-09-19 20:02:47.199 HomeAssistant universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.3.1', ezsp_version='7.3.1.0', ot_rcp_version='SL-OPENTHREAD/2.3.1.0_GitHub-e6df00dd6' (2.3.1.0), cpc_version='4.3.1-4f7f9e99-dirty-de58d93e' (4.3.1), fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>, baudrate=460800)
2024-09-19 20:02:47.201 HomeAssistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-09-19 20:02:49.242 HomeAssistant universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2024-09-19 20:02:49.293 HomeAssistant universal_silabs_flasher.flasher INFO Detected ApplicationType.CPC, version '4.3.1-4f7f9e99-dirty-de58d93e' (4.3.1) at 460800 baudrate (bootloader baudrate None)
2024-09-19 20:02:49.293 HomeAssistant universal_silabs_flasher.flash INFO Firmware version '4.3.1-4f7f9e99-dirty-de58d93e' (4.3.1) is flashed, not re-installing
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service cpcd-config: starting
[20:02:50] INFO: Using known baudrate of 460800 for cpcd!
[20:02:52] INFO: Generating cpcd configuration.
s6-rc: info: service cpcd-config successfully started
s6-rc: info: service cpcd: starting
[20:02:53] INFO: Starting cpcd...
WARNING in function 'main' in file /usr/src/cpc-daemon/main.c at line #186 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
s6-rc: info: service cpcd successfully started
s6-rc: info: service zigbeed: starting
s6-rc: info: service zigbeed successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[20:02:54] INFO: Starting zigbeed...
[20:02:53:262266] Info : [CPCd v4.3.1.0] [Library API v3] [RCP Protocol v4]
[20:02:53:262437] Info : Git commit: 133b29678b3d0bc7578e098d2f46b4d5bcd2ebb4 / branch: 
[20:02:53:262442] Info : Sources hash: ff8300587e7e4ab1def7a89a272c0baef32f9eb3bff9b0ba06b94e655d652367
[20:02:53:262460] WARNING : In function 'main' in file /usr/src/cpc-daemon/main.c at line #186 : Running CPCd as 'root' is not recommended. Proceed at your own risk.
[20:02:53:262504] Info : Reading cli arguments
[20:02:53:262516] Info : /usr/local/bin/cpcd 
[20:02:53:273827] Info : Reading configuration
[20:02:53:273851] Info :   file_path = /usr/local/etc/cpcd.conf
[20:02:53:273855] Info :   instance_name = cpcd_0
[20:02:53:273858] Info :   socket_folder = /dev/shm
[20:02:53:273861] Info :   operation_mode = MODE_NORMAL
[20:02:53:273864] Info :   use_encryption = false
[20:02:53:273866] Info :   binding_key_file = /etc/binding-key.key
[20:02:53:273869] Info :   stdout_tracing = false
[20:02:53:273872] Info :   file_tracing = false
[20:02:53:273874] Info :   lttng_tracing = false
[20:02:53:273877] Info :   enable_frame_trace = false
[20:02:53:273879] Info :   traces_folder = /dev/shm/cpcd-traces
[20:02:53:273881] Info :   bus = UART
[20:02:53:273884] Info :   uart_baudrate = 460800
[20:02:53:273887] Info :   uart_hardflow = true
[20:02:53:273890] Info :   uart_file = /dev/ttyUSB0
[20:02:53:273893] Info :   fu_recovery_pins_enabled = false
[20:02:53:273896] Info :   fu_connect_to_bootloader = false
[20:02:53:273898] Info :   fu_enter_bootloader = false
[20:02:53:273901] Info :   restart_cpcd = false
[20:02:53:273904] Info :   application_version_validation = false
[20:02:53:273906] Info :   print_secondary_versions_and_exit = false
[20:02:53:273909] Info :   use_noop_keep_alive = false
[20:02:53:273911] Info :   reset_sequence = true
[20:02:53:273914] Info :   stats_interval = 0
[20:02:53:273917] Info :   rlimit_nofile = 2000
[20:02:53:273919] Info : ENCRYPTION IS DISABLED 
[20:02:53:273922] Info : Starting daemon in normal mode
[20:02:53:294793] Info : Connecting to Secondary...
[20:02:53:355726] Info : RX capability is 256 bytes
[20:02:53:355758] Info : Connected to Secondary
[20:02:53:359712] Info : Secondary Protocol v4
[20:02:53:367710] Info : Secondary CPC v4.3.1
[20:02:53:371711] Info : Secondary bus bitrate is 460800
[20:02:53:379722] Info : Secondary APP v4.3.1-4f7f9e99-dirty-de58d93e
[20:02:53:379914] Info : Daemon startup was successful. Waiting for client connections
[20:02:55:272370] Info : New client connection using library v4.3.1.0
[20:02:55:276942] Info : Opened connection socket for ep#12
[20:02:55:277065] Info : Endpoint socket #12: Client connected. 1 connections
Listening on port 9999 for connection...
Accepting connection.
Accepted connection 7.

Sep 19 '24 19:09 bestycame

Ah. Are you having the Thread half of multiprotocol? I suggest migrating back to Zigbee firmware, multiprotocol hasn't been updated in a very long time now.

https://connectzbt1.home-assistant.io/procedures/disable-multiprotocol/

Sep 19 '24 19:09 puddly

No, not using Thread at all. I tend to purchase only Zigbee products on order to increase the mesh... Will try :).

Sep 19 '24 19:09 bestycame

I'm not having the same menus as in your documentation: When clicking on Zigbee:

When clicking on Threads it installed the Add-on+Integration.

This is the Hardware info I have for the SkyConnect:

ttyUSB0
/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_46e23cdfa2dded11b7edef2d62c613ac-if00-port0
Subsystem:
tty
Device path:
/dev/ttyUSB0
ID:
/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_46e23cdfa2dded11b7edef2d62c613ac-if00-port0
Attributes:
DEVLINKS: >-
  /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_46e23cdfa2dded11b7edef2d62c613ac-if00-port0
  /dev/serial/by-path/platform-fd840000.usb-usb-0:1:1.0-port0
  /dev/serial/by-path/platform-fd840000.usb-usbv1-0:1:1.0-port0
DEVNAME: /dev/ttyUSB0
DEVPATH: /devices/platform/fd840000.usb/usb6/6-1/6-1:1.0/ttyUSB0/tty/ttyUSB0
ID_BUS: usb
ID_MODEL: SkyConnect_v1.0
ID_MODEL_ENC: SkyConnect\x20v1.0
ID_MODEL_ID: ea60
ID_PATH: platform-fd840000.usb-usb-0:1:1.0
ID_PATH_TAG: platform-fd840000_usb-usb-0_1_1_0
ID_PATH_WITH_USB_REVISION: platform-fd840000.usb-usbv1-0:1:1.0
ID_REVISION: '0100'
ID_SERIAL: Nabu_Casa_SkyConnect_v1.0_46e23cdfa2dded11b7edef2d62c613ac
ID_SERIAL_SHORT: 46e23cdfa2dded11b7edef2d62c613ac
ID_TYPE: generic
ID_USB_DRIVER: cp210x
ID_USB_INTERFACES: ':ff0000:'
ID_USB_INTERFACE_NUM: '00'
ID_USB_MODEL: SkyConnect_v1.0
ID_USB_MODEL_ENC: SkyConnect\x20v1.0
ID_USB_MODEL_ID: ea60
ID_USB_REVISION: '0100'
ID_USB_SERIAL: Nabu_Casa_SkyConnect_v1.0_46e23cdfa2dded11b7edef2d62c613ac
ID_USB_SERIAL_SHORT: 46e23cdfa2dded11b7edef2d62c613ac
ID_USB_TYPE: generic
ID_USB_VENDOR: Nabu_Casa
ID_USB_VENDOR_ENC: Nabu\x20Casa
ID_USB_VENDOR_ID: 10c4
ID_VENDOR: Nabu_Casa
ID_VENDOR_ENC: Nabu\x20Casa
ID_VENDOR_ID: 10c4
MAJOR: '188'
MINOR: '0'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '5225289'

Tried to uninstall Silicon Labs Multiprotocol but no luck so far.

Sep 19 '24 20:09 bestycame

Hmm. You may need to perform the steps manually:

Uninstall the multiprotocol addon, OpenThread border router addon, and Silicon Labs flasher addon.
Disable ZHA.
Install the Silicon Labs flasher addon and in its settings, point it to the SkyConnect.
Run the addon. It'll take a minute.
Enable ZHA. If it fails to start up because network settings changed, allow it to restore the last settings.

Sep 19 '24 20:09 puddly

Oh, and the most important step:

4.5. in ZHA, click "Migrate Radio" and then select "Re-configure settings". You can then select the SkyConnect serial port and restore the last backup.

Sep 19 '24 20:09 puddly

✅
✅ 3/4: ✅ Step 4.5: Unable to restore the backup, either a manual one of today, or the last automatic one:

Debug Logging: home-assistant_zha_2024-09-19T20-28-06.509Z.log

Sep 19 '24 20:09 bestycame

Interesting, it looks like there's a timing bug with it.

I think if you restart Core it will be able to restore properly.

Sep 19 '24 20:09 puddly

Well, not really sure what happend. Needed to restart twice and the whole network re-appeared by itself! 🤷

Sep 19 '24 20:09 bestycame

LQI and RSSI's are showing more realistic values: RSSI and LQI for the device producing the <sl_Status.ZIGBEE_DELIVERY_FAILED: 3074> is showing -73 dBm / 108 respectively.

Sep 19 '24 20:09 bestycame

With the new firmware, could you also attach diagnostics information for the ZHA integration?

Sep 19 '24 21:09 puddly

I'm getting this problem. Haven't made any changes but now getting lots of 3074 errors.

Sep 20 '24 06:09 martin334466

error_log22.txt

Sep 20 '24 07:09 martin334466

Hello, Yes of course, Here are the Diagnostics and the Debug Logs :) config_entry-zha-25707297bea3fba0ea021086f95914e6 (1).json home-assistant_zha_2024-09-20T09-34-27.247Z.log

Thank you for your time and insights,

Sep 20 '24 09:09 bestycame

I have the same issue, i have a Skyconnect with only Zigbee protocol. Loose different devices over time with the 3074. Started with 2024.09.

Sep 20 '24 13:09 roccolord

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.

Dec 19 '24 14:12 issue-triage-workflows[bot]