Other programming languages • zigbee2mqtt.service: Start request repeated too quickly.

Hi,

After reinstalling zigbee2mqtt, I am having trouble starting z2m as a service. When I run ‘sudo journalctl -u zigbee2mqtt.service -f’, I get the following error message:

Jan 16 17:40:59 beepi node[3539]: at Object.Module._extensions..js (internal/modules/cjs/loader.js10)
Jan 16 17:40:59 beepi node[3539]: (Use `node --trace-warnings ...` to show where the warning was created)
Jan 16 17:40:59 beepi node[3539]: (node:3539) 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_unh ... tions_mode). (rejection id: 1)
Jan 16 17:40:59 beepi node[3539]: (node:3539) [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.
Jan 16 17:40:59 beepi systemd[1]: zigbee2mqtt.service: Succeeded.
Jan 16 17:41:00 beepi systemd[1]: zigbee2mqtt.service: Scheduled restart job, restart counter is at 5.
Jan 16 17:41:00 beepi systemd[1]: Stopped zigbee2mqtt.
Jan 16 17:41:00 beepi systemd[1]: zigbee2mqtt.service: Start request repeated too quickly.
Jan 16 17:41:00 beepi systemd[1]: zigbee2mqtt.service: Failed with result 'start-limit-hit'.
Jan 16 17:41:00 beepi systemd[1]: Failed to start zigbee2mqtt.

I can start z2m manually from the /opt/zigbee2mqtt directory using the command ‘node index.js’.

Where could this error come from?

BR
KP

Statistics: Posted by Ka<Pe777 — Fri Jan 16, 2026 5:22 pm — Replies 1 — Views 16

---