Most likely me… Lost power and other network issues over the last weeks… But thought I would check… Who knows… there could be others still here… Colin… 
But seriously… I am having issues with ZigbeeJS and NodeRED restarting even when the hub is up and running, complaining of:
2025-02-07 22:35:10 GMT+11 info time="2025-02-07T22:35:10+11:00" level=info msg="Error initializing configured OCI runtime kata: no valid executable found for OCI runtime kata: invalid argument"
2025-02-07 22:35:10 GMT+11 info time="2025-02-07T22:35:10+11:00" level=info msg="Setting parallel job count to 13"
2025-02-07 22:35:10 GMT+11 info Resolving "koenkk/zigbee2mqtt" using unqualified-search registries (/etc/containers/registries.conf)
2025-02-07 22:35:10 GMT+11 info Trying to pull docker.io/koenkk/zigbee2mqtt:latest...
2025-02-07 22:35:10 GMT+11 info time="2025-02-07T22:35:10+11:00" level=warning msg="failed, retrying in 1s ... (1/3). Error: Error initializing source docker://koenkk/zigbee2mqtt:latest: error pinging docker registry registry-1.docker.io: Get \"https://registry-1.docker.io/v2/\": dial tcp 3.94.224.37:443: connect: network is unreachable"
2025-02-07 22:35:11 GMT+11 info time="2025-02-07T22:35:11+11:00" level=warning msg="failed, retrying in 2s ... (2/3). Error: Error initializing source docker://koenkk/zigbee2mqtt:latest: error pinging docker registry registry-1.docker.io: Get \"https://registry-1.docker.io/v2/\": dial tcp 44.208.254.194:443: connect: network is unreachable"
2025-02-07 22:35:13 GMT+11 info Get "https://registry-1.docker.io/v2/": dial tcp [2600:1f18:2148:bc01:f43d:e203:cafd:8307]:443: connect: cannot assign requested address
2025-02-07 22:35:13 GMT+11 info Error: Error initializing source docker://koenkk/zigbee2mqtt:latest: error pinging docker registry registry-1.docker.io: Get "https://registry-1.docker.io/v2/": dial tcp [2600:1f18:2148:bc01:f43d:e203:cafd:8307]:443: connect: cannot assign requested address
2025-02-07 22:35:13 GMT+11 info Error: no arguments are needed with --latest or --cidfile
1 Like
Wow, my edit was registered… must be someone out there… 
It is a bit of a pain not having my Hue Tap Dial’s not working… Anyone else having this issue…?
Turned out there were some earlier error messages:
2025-02-14 18:39:03 GMT+11 info [2025-02-14 18:39:03] error: z2m: Error: USB adapter discovery error (No valid USB adapter found). Specify valid 'adapter' and 'port' in your configuration.
2025-02-14 18:39:03 GMT+11 info at discoverAdapter (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/adapterDiscovery.ts:523:15)
2025-02-14 18:39:03 GMT+11 info at processTicksAndRejections (node:internal/process/task_queues:105:5)
2025-02-14 18:39:03 GMT+11 info at Function.create (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/adapter.ts:68:33)
2025-02-14 18:39:03 GMT+11 info at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:132:24)
2025-02-14 18:39:03 GMT+11 info at Zigbee.start (/app/lib/zigbee.ts:69:27)
2025-02-14 18:39:03 GMT+11 info at Controller.start (/app/lib/controller.ts:142:13)
2025-02-14 18:39:03 GMT+11 info at start (/app/index.js:161:5)
2025-02-14 18:39:03 GMT+11 info [2025-02-14 18:39:03] error: z2m: If this happens after updating to Zigbee2MQTT 2.0.0, see https://github.com/Koenkk/zigbee2mqtt/discussions/24364
In particular the first one (No valid USB adapter found) and the last log entry…
I went to the link: Z2M 2.0.0: `USB adapter discovery error (No valid USB adapter found)` · Koenkk/zigbee2mqtt · Discussion #24364 · GitHub
and got frustrated when what it suggested didn’t work (adding an entry in the configuration.yaml file for z2m), but then I eventually stumbled across someone who posted about misspelling the word adapter as adaptor, like I had done… Grr…
So, while putting the full path to my zigbee dongle in the file as well, I also added the adapter line, one of those fixed it
serial:
port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_fac847613539ec118697e6680aac08d5-if00-port0
adapter: zstack
These were added / updated in: ~/data/z2m/configuration.yaml
Tip: I got the full path to the dongle by following the instructions here: Adapter settings | Zigbee2MQTT
In particular running this command in a terminal window:
ls -l /dev/serial/by-id
I copied the output from this and used in as the last part of the “port” setting under serial, shown above, i.e. /dev/serial/by-id/< paste-yours-here >
Now I can turn the lights off
2 Likes
Yup this recent update of Z2M wreaked havoc on me. I had all my device images offlined which puts them in the config file, but it broke my install, and I had to delete them all manually in nano. Then I had the same issue you described which thankfully was a simple fix, always check release notes before updating folks haha.
I haven’t tried offlining my icons since but maybe its fixed now??
1 Like
Not sure, I haven’t messed around with them…