Hi!
I have the problem with Zigbee2mqtt. The 502 bad gateway errors have appeared after the comlete new HA+Mosquitto+Zigbee2mqtt installation on my RPi4 8GB (SD card). I can not run the Z2M.
Z2M config:
data_path: /config/zigbee2mqtt
external_converters:
- freepad_ext.js
- one-more-converter.js
- fromZigbee.js
- homeassistant.js
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: true
mqtt:
base_topic: Zigbee2mqtt
server: mqtt://core-mosquitto
serial:
port: >-
/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2422042-if00
adapter: deconz
advanced:
log_level: warn
pan_id: 6754
channel: 11
network_key:
- 1
- 3
- 5
- 7
- 9
- 11
- 13
- 15
- 0
- 2
- 4
- 6
- 8
- 10
- 12
- 13
availability_blocklist: []
availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
port: 8099
experimental: {}
socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: '-d -d'
log: true
zigbee_herdsman_debug: true
Z2M log:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing...
[12:01:44] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing...
[12:01:45] INFO: MQTT available, fetching server detail ...
[12:01:45] INFO: MQTT credentials not configured, trying to auto-discovering ...
[12:01:46] INFO: Configuring'addons' mqtt user
[12:01:46] INFO: Previous config file found, checking backup
[12:01:46] INFO: Creating backup config in '/config/zigbee2mqtt/.configuration.yaml.bk'
[12:01:46] 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.
[12:01:47] INFO: Zigbee Herdsman debug logging enabled
[12:01:47] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start
> node index.js
(node:350) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/config/zigbee2mqtt/freepad_ext.js'
at Object.openSync (fs.js:498:3)
at Object.readFileSync (fs.js:394:35)
at loadModuleFromFile (/app/lib/util/utils.ts:151:27)
at Object.getExternalConvertersDefinitions (/app/lib/util/utils.ts:163:25)
at getExternalConvertersDefinitions.next (<anonymous>)
at new ExternalConverters (/app/lib/extension/externalConverters.js:10:20)
at new Controller (/app/lib/controller.js:79:34)
at start (/app/index.js:94:18)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:350) 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:350) [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.
[12:01:53] INFO: Zigbee Herdsman debug logging enabled
[12:01:54] INFO: Handing over control to Zigbee2mqtt Core ...
System log:
21-09-12 11:58:40 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-09-12 12:01:38 INFO (SyncWorker_2) [supervisor.docker.interface] Stopping addon_45df7312_zigbee2mqtt application
21-09-12 12:01:41 INFO (SyncWorker_2) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt application
21-09-12 12:01:43 INFO (SyncWorker_4) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-aarch64 with version 1.21.1-1
21-09-12 12:02:30 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.2:8099 ssl:default [Connect call failed ('172.30.33.2', 8099)]
Thx for your time and help too!!!
