[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing...
[19:26:18] INFO: MQTT available, fetching server detail ...
[19:26:19] INFO: MQTT server settings not configured, trying to auto-discovering ...
[19:26:22] INFO: Configuring 'mqtt://core-mosquitto:1883' mqtt server
[19:26:23] INFO: MQTT credentials not configured, trying to auto-discovering ...
[19:26:24] INFO: Configuring'addons' mqtt user
[19:26:24] INFO: Previous config file found, checking backup
[19:26:24] INFO: Creating backup config in '/config/zigbee2mqtt/.configuration.yaml.bk'
[19:26:25] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[19:26:28] INFO: Handing over control to Zigbee2mqtt Core ...
> zigbee2mqtt@1.22.1 start
> node index.js
(node:395) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/config/zigbee2mqtt/ptvo_counter_2ch.js'
at Object.openSync (fs.js:497:3)
at Object.readFileSync (fs.js:393:35)
at loadModuleFromFile (/app/lib/util/utils.ts:154:27)
at Object.getExternalConvertersDefinitions (/app/lib/util/utils.ts:165:25)
at getExternalConvertersDefinitions.next (<anonymous>)
at new ExternalConverters (/app/lib/extension/externalConverters.ts:12:20)
at new Controller (/app/lib/controller.ts:83:58)
at start (/app/index.js:96:18)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:395) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:395) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[19:26:45] INFO: Handing over control to Zigbee2mqtt Core ...
> zigbee2mqtt@1.22.1 start
> node index.js
(node:435) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/config/zigbee2mqtt/ptvo_counter_2ch.js'
at Object.openSync (fs.js:497:3)
at Object.readFileSync (fs.js:393:35)
at loadModuleFromFile (/app/lib/util/utils.ts:154:27)
at Object.getExternalConvertersDefinitions (/app/lib/util/utils.ts:165:25)
at getExternalConvertersDefinitions.next (<anonymous>)
at new ExternalConverters (/app/lib/extension/externalConverters.ts:12:20)
at new Controller (/app/lib/controller.ts:83:58)
at start (/app/index.js:96:18)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:435) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:435) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[19:27:00] INFO: Handing over control to Zigbee2mqtt Core ...
> zigbee2mqtt@1.22.1 start
> node index.js
я также мучаюсь с установкой и запуском этой интеграции на D1
у меня во время установки отваливается supervisor - помогает только ребут
иногда удается поставить, но при запуске всё начинает висеть, удаляю и заново ставлю… пока не понимаю почему
в логах
Logger: homeassistant.components.hassio
Source: components/hassio/__init__.py:559
Integration: Home Assistant Supervisor ([documentation](https://www.home-assistant.io/integrations/hassio), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+hassio%22))
First occurred: 16:30:16 (10 occurrences)
Last logged: 17:17:04
Can't read Supervisor data:
Logger: homeassistant.components.hassio.handler
Source: components/hassio/handler.py:237
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 16:30:16 (30 occurrences)
Last logged: 17:17:04
Timeout on /addons/core_configurator/stats request
Timeout on /addons/core_mosquitto/stats request
Timeout on /addons/094a1135_jethub-mqtt-io/stats request
Logger: homeassistant.components.hassio.http
Source: components/hassio/http.py:119
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 17:01:43 (1 occurrences)
Last logged: 17:01:43
Client timeout error on API request app/entrypoint.js
Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:119
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 16:26:05 (2 occurrences)
Last logged: 16:26:16
Failed to to call /addons/45df7312_zigbee2mqtt/start - Image zigbee2mqtt/zigbee2mqtt-aarch64:1.22.1-1 does not exist for addon_45df7312_zigbee2mqtt
Failed to to call /addons/45df7312_zigbee2mqtt/uninstall - Addon is not installed
Добрый день!
Удалось ли вам победить проблему с Zigbee2MQTT?
Имею то же самое и уже месяц не могу решить.
[06:23:36] INFO: Handing over control to Zigbee2mqtt Core …
zigbee2mqtt@1.22.1 start
node index.js
Zigbee2MQTT:error 2021-12-21 06:24:10: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-12-21 06:24:10: Failed to start zigbee
Zigbee2MQTT:error 2021-12-21 06:24:10: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2021-12-21 06:24:10: Exiting…
Zigbee2MQTT:error 2021-12-21 06:24:11: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:102:27)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:123:29)
at Zigbee.start (/app/lib/zigbee.ts:58:27)
at Controller.start (/app/lib/controller.ts:100:27)
at start (/app/index.js:97:5)
тогда первый вариант: у вас сломался z2m. к jethome это не имеет отношения.
если разбираетесь в json файлах - проверьте файл data/database.db, если нет просто попробуйте его удалить и запустить еще раз (удаление файла обнулит всю базу подключенных устройств)