#Z2M add-on no longer running after moving apartments

1 messages · Page 1 of 1 (latest)

wide ocean
#

Hey all,

I recently moved apartments, connected my rpi that I use to run hass into the WiFi router, and was able to connect via my computer.

However, im unable to start the z2m add-on. Does anyone know if there are settings that I need to adjust in order to get this working?

I use a Sonoff Zigbee Dongle

drifting mantle
#

Please check and share the addon log.

wide ocean
#

Not sure if this is equivalent but this is from the supervisor log:

2024-11-09 20:05:10.883 WARNING (MainThread) [supervisor.addons.options] Unknown option 'serial' for Zigbee2MQTT (45df7312_zigbee2mqtt)
2024-11-09 20:05:23.808 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Zigbee2MQTT is failed, restarting...
2024-11-09 20:05:23.821 INFO (SyncWorker_6) [supervisor.docker.manager] Cleaning addon_45df7312_zigbee2mqtt application
2024-11-09 20:05:26.821 WARNING (MainThread) [supervisor.addons.options] Unknown option 'serial' for Zigbee2MQTT (45df7312_zigbee2mqtt)
#
2024-11-09 21:29:57.801 WARNING (MainThread) [supervisor.addons.options] Unknown option 'serial' for Zigbee2MQTT (45df7312_zigbee2mqtt)
2024-11-09 21:30:23.089 INFO (MainThread) [supervisor.jobs] 'Tasks._update_supervisor' blocked from execution, not enough free space (0.9GB) left on the device
2024-11-09 21:34:41.506 ERROR (MainThread) [supervisor.api.ingress] Stream error with http://172.30.33.4:1337/stable-952523f288b1351f622a19507eb699b97c1d6410/static/out/vs/code/browser/workbench/workbench.js: Cannot write to closing transport
2024-11-09 21:34:41.862 WARNING (MainThread) [supervisor.addons.options] Unknown option 'serial' for Zigbee2MQTT (45df7312_zigbee2mqtt)
2024-11-09 21:34:43.311 WARNING (MainThread) [supervisor.addons.options] Unknown option 'serial' for Zigbee2MQTT (45df7312_zigbee2mqtt)
2024-11-09 21:34:43.332 WARNING (MainThread) [supervisor.addons.options] Unknown option 'serial' for Zigbee2MQTT (45df7312_zigbee2mqtt)
2024-11-09 21:34:43.355 INFO (SyncWorker_3) [supervisor.docker.manager] Cleaning addon_45df7312_zigbee2mqtt application
2024-11-09 21:34:46.385 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-aarch64 with version 1.41.0-1
2024-11-09 21:34:46.413 WARNING (MainThread) [supervisor.addons.options] Unknown option 'serial' for Zigbee2MQTT (45df7312_zigbee2mqtt)
2024-11-09 21:34:46.437 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.1:8099 ssl:default [Connect call failed ('172.30.33.1', 8099)]
2024-11-09 21:34:46.447 WARNING (MainThread) [supervisor.addons.options] Unknown option 'serial' for Zigbee2MQTT (45df7312_zigbee2mqtt)
#

screenshot of the same code above

drifting mantle
#

It's helpful but not the addon log. Each addon has its own log tab. Please also share its config section.

drifting mantle
#

Why is there a serial in your mqtt section?
The address is also not ehat serial expects. Please read the addon docs again.

wide ocean
#

Interesting.. my z2m addon is working now and the config is still the same setup as above (same serial as well).

Issue was fixed by plugging the dongle into another usb 3.0 port on my rpi

drifting mantle
#

Doesn't change that the config is invalid though.

#

By the way /dev/ttyX is not a reliable path. Use /dev/serial/by-id/X as the documentation suggests.

wide ocean
wide ocean
drifting mantle
#

Yes but you can't just put a random name there. Maybe I should have explained that X part better.

#

Check below for the path.

round yewBOT
#

Open your Home Assistant instance and show hardware information

drifting mantle
wide ocean