Domoticz

Decided to build new Domoticz server and move from Phoscon/deConz to zigbee2mqtt, followed instructions on z2m site, build and install went fine without errors however I could not access the z2m frontend, if I run "sudo npm start" it all works, I can see the front end, pair devices and see them in Domoticz but as soon as I "ctrl c" and stop the process and then try and start it permanently with "sudo systemctl start zigbee2mqtt" and then check if its running with "systemctl status zigbee2mqtt" I get this, I don't understand why it seems to imply it's been running since Sat 21st

pi@Domoticz-New:/opt/zigbee2mqtt $ systemctl status zigbee2mqtt
● zigbee2mqtt.service - zigbee2mqtt
Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2022-05-21 13:00:49 BST; 5 days ago
Main PID: 469 (npm)
Tasks: 23 (limit: 2059)
CGroup: /system.slice/zigbee2mqtt.service
├─469 npm
├─619 sh -c node index.js
└─620 node index.js

May 21 13:01:03 Domoticz-New npm[469]: at Array.forEach (<anonymous>)
May 21 13:01:03 Domoticz-New npm[469]: at rmkidsSync (/opt/zigbee2mqtt/node_modules/rimraf/rimraf.js:336:26)
May 21 13:01:03 Domoticz-New npm[469]: at rmdirSync (/opt/zigbee2mqtt/node_modules/rimraf/rimraf.js:329:7)
May 21 13:01:03 Domoticz-New npm[469]: at Function.rimrafSync [as sync] (/opt/zigbee2mqtt/node_modules/rimraf/rimraf.js:301:9)
May 21 13:01:03 Domoticz-New npm[469]: at /opt/zigbee2mqtt/lib/util/logger.ts:138:20
May 21 13:01:03 Domoticz-New npm[469]: at Array.forEach (<anonymous>)
May 21 13:01:03 Domoticz-New npm[469]: at cleanup (/opt/zigbee2mqtt/lib/util/logger.ts:136:21)
May 21 13:01:03 Domoticz-New npm[469]: (Use `node --trace-warnings ...` to show where the warning was created)
May 21 13:01:03 Domoticz-New npm[469]: (node:620) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a prom
May 21 13:01:03 Domoticz-New npm[469]: (node:620) [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-z
lines 1-20/20 (END)

TIA
Dave

Well I thought I'd fixed, followed the instructions here to update to the lastest version of z2m (I was on 1.25.0)

https://www.zigbee2mqtt.io/guide/instal ... st-version

After I completed the update runnning "sudo systemctl start zigbee2mqtt" started it successfully, I could access the web interface etc however after a reboot the web interface is no longer available again and running "systemctl status zigbee2mqtt" gives me the same error as before apart from telling me it has now "Active: active (running) since Fri 2022-05-27 12:09:35 BST; 6min ago" which was when I rebooted it !

I get exactly the same thing
Looks like it happens on re-boot

Have you considered running zigbee2mqtt in a docker container? I can't really tell where this error comes from other than it may be down to version incompatabilities. You would need to ask on the z2m forum. That said, these problems would most likely go away running it in docker anyway and future incompatibility issues prevented...

I’m not keen to start using docker on my raspberry just yet. Happy with it running as is (if possible)

I've found that restarting the zigbee2mqtt service seems to fix the problem though:
my service file is: