In reply to @hexa:lossy.network
Check the journal

    import metno
ModuleNotFoundError: No module named 'metno'

In reply to @hexa:lossy.network
that's not ideal for components that are autodiscovered or setup via the wizard, but here we are

❯ ./result/bin/zigbee2mqtt
Building Zigbee2MQTT... (initial build), failed
(node:2382814) UnhandledPromiseRejectionWarning: Error: Command failed: npm run build
/bin/sh: line 1: npm: command not found

    at ChildProcess.exithandler (child_process.js:383:12)
    at ChildProcess.emit (events.js:400:28)
    at maybeClose (internal/child_process.js:1058:16)
    at Socket.<anonymous> (internal/child_process.js:443:11)
    at Socket.emit (events.js:400:28)
    at Pipe.<anonymous> (net.js:686:12)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:2382814) 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:2382814) [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.