search

zigbee2mqtt / hassio-zigbee2mqtt

Official Zigbee2MQTT Home Assistant add-on
https://www.zigbee2mqtt.io
Apache License 2.0
1.21k stars 439 forks source link

The zigbee2MQTT cannot start after 1.34 updated. #539

Closed arsancube closed 1 year ago

arsancube commented 1 year ago

Description of the issue

It could not start with following error.

[01:47:51] INFO: Preparing to start... [01:47:52] INFO: Socat not enabled [01:47:53] INFO: Starting Zigbee2MQTT...

/app/node_modules/zigbee-herdsman-converters/index.js:172 if (converter.options) { ^ TypeError: Cannot read properties of undefined (reading 'options') at Object.addDefinition [as addDeviceDefinition] (/app/node_modules/zigbee-herdsman-converters/index.js:172:23) at new ExternalConverters (/app/lib/extension/externalConverters.ts:15:17) at new Controller (/app/lib/controller.ts:84:58) at start (/app/index.js:106:18)

Addon version

1.34

Platform

Core 2023.11.3 Frontend 20231030.2 Operating System 11.1 Frontend 20231030.2 On synology linux VM

Logs of the issue (if applicable)

No response

ornago commented 1 year ago

Same here, I had to disable the external converter "Herdsman for Aqara T1" in my configuration to get Z2M running again. Unfortunately now I don't get sensor informations for Energy consumption from the Aquara SSM-U01. Hope it'll be fixed soon?

dguyton commented 1 year ago

Same here. New user with fresh install of HAOS, MQTT broker, and Zigbee2MQTT and Herdsman consistently fails to start regardless of config. ZHA works flawlessly. Note, I am using ZigStar UZB-01 v0.3 attached via network.

add-on version: 1.34.0-1

Log snapshot:

[13:28:09] INFO: Preparing to start...
[13:28:09] INFO: Socat not enabled
[13:28:10] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-12-03 13:28:11: Logging to console and directory: '/config/zigbee2mqtt/log/2023-12-03.13-28-11' filename: log.txt
Zigbee2MQTT:info  2023-12-03 13:28:11: Starting Zigbee2MQTT version 1.34.0 (commit #unknown)
Zigbee2MQTT:info  2023-12-03 13:28:11: Starting zigbee-herdsman (0.25.0)
Zigbee2MQTT:error 2023-12-03 13:28:11: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-12-03 13:28:11: Failed to start zigbee
Zigbee2MQTT:error 2023-12-03 13:28:11: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-12-03 13:28:11: Exiting...
Zigbee2MQTT:error 2023-12-03 13:28:11: Error: spawn udevadm ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:485:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Lonestar10 commented 1 year ago

Same here. Zigbee2mqtt will not start after the 1.34.0-1 update. I have tried removing and reinstalling Z2M from Github (Z2M appears in the Add-On store with a blue line -- doesn't that mean an update is available?). After adding credentials to Z2M and pointing it to the Zonoff USB Dongle P 3.0, I press Start. On the Info page, a green dot appears, but clicking on the Zigbee2mqtt Web UI fails to start it.
I'm running latest Home Assistant on a Generic x86-64.

Here is log from Zigbee2mqtt: [10:13:22] INFO: Preparing to start... [10:13:22] INFO: Socat not enabled [10:13:24] INFO: Starting Zigbee2MQTT...

/app/node_modules/js-yaml/lib/loader.js:183 return new YAMLException(message, mark); ^ YAMLException: duplicated mapping key (58:1)

55 | port: 8099 56 | experimental: {} 57 | 58 | external_converters: ------^ 59 | - lywsd03mmc.js at generateError (/app/node_modules/js-yaml/lib/loader.js:183:10) at throwError (/app/node_modules/js-yaml/lib/loader.js:187:9) at storeMappingPair (/app/node_modules/js-yaml/lib/loader.js:358:7) at readBlockMapping (/app/node_modules/js-yaml/lib/loader.js:1173:9) at composeNode (/app/node_modules/js-yaml/lib/loader.js:1441:12) at readDocument (/app/node_modules/js-yaml/lib/loader.js:1625:3) at loadDocuments (/app/node_modules/js-yaml/lib/loader.js:1688:5) at Object.load (/app/node_modules/js-yaml/lib/loader.js:1714:19) at Object.read (/app/lib/util/yaml.ts:7:21) at read (/app/lib/util/settings.ts:333:20)

((Here is the error message after clicking on Start Web UI)): z2m start button

moshin34 commented 1 year ago

Looks like i picked a hell of a time to move MQTT and Z2MQTT from my RasPi to the VM instance with HAOS. Fml

This is on a fresh install 


[14:48:02] INFO: Preparing to start...
[14:48:03] INFO: Socat not enabled
[14:48:03] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-12-04 14:48:05: Logging to console and directory: '/config/zigbee2mqtt/log/2023-12-04.14-48-05' filename: log.txt
Zigbee2MQTT:info  2023-12-04 14:48:05: Starting Zigbee2MQTT version 1.34.0 (commit #unknown)
Zigbee2MQTT:info  2023-12-04 14:48:05: Starting zigbee-herdsman (0.25.0)
Zigbee2MQTT:error 2023-12-04 14:48:05: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-12-04 14:48:05: Failed to start zigbee
Zigbee2MQTT:error 2023-12-04 14:48:05: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-12-04 14:48:05: Exiting...
Zigbee2MQTT:error 2023-12-04 14:48:05: Error: spawn udevadm ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:485:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
almanzarj commented 1 year ago

having similar issue after upgrading to 1.34.0-1

[19:54:13] INFO: Preparing to start...
[19:54:14] INFO: Socat not enabled
[19:54:15] INFO: Starting Zigbee2MQTT...

/app/node_modules/js-yaml/lib/loader.js:183
  return new YAMLException(message, mark);
         ^
YAMLException: duplicated mapping key (46:1)

 43 |   port: 8099
 44 | experimental: {}
 45 | availability: false
 46 | external_converters:
------^
 47 |   - lywsd03mmc.js
 48 |   
    at generateError (/app/node_modules/js-yaml/lib/loader.js:183:10)
    at throwError (/app/node_modules/js-yaml/lib/loader.js:187:9)
    at storeMappingPair (/app/node_modules/js-yaml/lib/loader.js:358:7)
    at readBlockMapping (/app/node_modules/js-yaml/lib/loader.js:1173:9)
    at composeNode (/app/node_modules/js-yaml/lib/loader.js:1441:12)
    at readDocument (/app/node_modules/js-yaml/lib/loader.js:1625:3)
    at loadDocuments (/app/node_modules/js-yaml/lib/loader.js:1688:5)
    at Object.load (/app/node_modules/js-yaml/lib/loader.js:1714:19)
    at Object.read (/app/lib/util/yaml.ts:7:21)
    at read (/app/lib/util/settings.ts:333:20)

update: I was able to get it working with uninstall and added my old configuration.yaml to the new install.

Toomblr commented 1 year ago

Having the same issue, fix mentioned by @almanzarj is not working.

Koenkk commented 1 year ago

One of your external converters is incompatible, remove it to make z2m start

moshin34 commented 1 year ago

Thank you Koen. Forgive my ignorance, but what is meant by "external converters". Can't be my conbee2 can it?

On Fri, Dec 8, 2023 at 9:04 AM Koen Kanters @.***> wrote:

Closed #539 https://github.com/zigbee2mqtt/hassio-zigbee2mqtt/issues/539 as not planned.

— Reply to this email directly, view it on GitHub https://github.com/zigbee2mqtt/hassio-zigbee2mqtt/issues/539#event-11193844081, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCY66I7QTEPQJZW2YAYCCQLYIMM5LAVCNFSM6AAAAABADUW6E6VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGE4TGOBUGQYDQMI . You are receiving this because you commented.Message ID: @.*** com>