Thanks, this is the result:
openhabian:~ $ sudo openhabian-config
[sudo] password for openhabian:
2025-06-14_12:07:59_CEST [openHABian] Checking for root privileges… OK
2025-06-14_12:08:00_CEST [openHABian] Making sure router advertisements are available…
$ sysctl --load
net.ipv6.conf.all.accept_ra = 1
net.ipv6.conf.all.accept_ra_rt_info_max_plen = 64
OK
2025-06-14_12:08:00_CEST [openHABian] Loading configuration file ‘/etc/openhabian.conf’… OK
2025-06-14_12:08:01_CEST [openHABian] openHABian configuration tool version: [openHAB]{2025-04-27T00:37:57-06:00}(7f01c79)
2025-06-14_12:08:01_CEST [openHABian] Checking for changes in origin branch openHAB… OK
2025-06-14_12:08:03_CEST [openHABian] Switching to branch openHAB… OK
2025-06-14_12:08:03_CEST [openHABian] Checking openHAB Signing Key expiry.
2025-06-14_12:08:03_CEST [openHABian] Checking expiry date of apt keys… OK
2025-06-14_12:08:42_CEST [openHABian] Updating Linux package information… OK
$ nodejs_setup
2025-06-14_12:08:51_CEST [openHABian] Downloading Zigbee2MQTT…
$ zigbee2mqtt_download /opt
2025-06-14_12:08:54_CEST [openHABian] Downloading Zigbee2MQTT…
$ mkdir -p /opt/zigbee2mqtt
$ chown openhabian:openhab /opt/zigbee2mqtt
$ sudo -u openhabian git clone GitHub - Koenkk/zigbee2mqtt: Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨 /opt/zigbee2mqtt
Cloning into ‘/opt/zigbee2mqtt’…
remote: Enumerating objects: 33529, done.
remote: Counting objects: 100% (36/36), done.
remote: Compressing objects: 100% (28/28), done.
remote: Total 33529 (delta 17), reused 10 (delta 8), pack-reused 33493 (from 2)
Receiving objects: 100% (33529/33529), 109.72 MiB | 4.78 MiB/s, done.
Resolving deltas: 100% (25260/25260), done.
OK
2025-06-14_12:10:45_CEST [openHABian] Creating log directory… OK
2025-06-14_12:10:45_CEST [openHABian] Zigbee2MQTT install & config…
$ sudo -u openhabian git fetch origin
$ sudo -u openhabian git fetch --tags
$ sudo -u openhabian git checkout 1.42.0
Note: switching to ‘1.42.0’.
You are in ‘detached HEAD’ state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 861cba63 chore(dev): release 1.42.0 (#24569)
$ sudo -u openhabian npm ci
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jackspeak@4.0.2’,
npm WARN EBADENGINE required: { node: ‘20 || >=22’ },
npm WARN EBADENGINE current: { node: ‘v18.19.0’, npm: ‘9.2.0’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘path-scurry@2.0.0’,
npm WARN EBADENGINE required: { node: ‘20 || >=22’ },
npm WARN EBADENGINE current: { node: ‘v18.19.0’, npm: ‘9.2.0’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘lru-cache@11.0.2’,
npm WARN EBADENGINE required: { node: ‘20 || >=22’ },
npm WARN EBADENGINE current: { node: ‘v18.19.0’, npm: ‘9.2.0’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘rimraf@6.0.1’,
npm WARN EBADENGINE required: { node: ‘20 || >=22’ },
npm WARN EBADENGINE current: { node: ‘v18.19.0’, npm: ‘9.2.0’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘glob@11.0.0’,
npm WARN EBADENGINE required: { node: ‘20 || >=22’ },
npm WARN EBADENGINE current: { node: ‘v18.19.0’, npm: ‘9.2.0’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘minimatch@10.0.1’,
npm WARN EBADENGINE required: { node: ‘20 || >=22’ },
npm WARN EBADENGINE current: { node: ‘v18.19.0’, npm: ‘9.2.0’ }
npm WARN EBADENGINE }
(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ ‘/opt/zigbee2mqtt/node_modules/fsevents’ (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ '/opt/zigbee2mqtt/node_modules/fsev(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ '/opt/zigbee2mqtt/node_modules/fsev(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ '/opt/zigbee2mqtt/node_modules/fs(###(###(###(#######(#########⠂⠂⠂⠂⠂⠂(#######(###(#######(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify(###(#######(###(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂)(#########⠂⠂⠂⠂⠂⠂(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: s(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ '/opt/zigbee2mqtt/node_modules/fs(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ ‘/opt/zigbee2mqtt/node_modules/fsevents’ (#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ '/opt/zigbee2mqtt/node_modules/fsevents(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ '/opt/zigbee2mqtt/node_modules/fseven(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ '/opt/zigbee2mqtt/node_mo(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ '/opt/zigbee2mqtt/node_modules/f(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ '/opt/zigbee2mqtt/node_modules(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ '/opt/zigbee2mqtt/node_modul(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ '/opt/zigbee(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ '/opt/zigbee2mqtt/node_(#####(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:fsevents: sill reify mark deleted [ '/opt/zigbee2mqtt/node_modules/^[[A(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠼ reify:sd-notify: sill reify mark deleted [ '/opt/zigbee2mqtt/node_modules/s^[[C(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠼ reify:sd-notify: sill reify mark deleted [ '/opt/zigbee2mqtt/node_modules/s^[[C(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:nan: sill reify mark deleted [ '/opt/zigbee2mqtt/node_modules/unix-dg^[[C(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠏ reify:nan: sill reify mark deleted [ '/opt/zigbee2mqtt/node_modules/unix-dgnpm ERR! code ETIMEDOUT
npm ERR! syscall connect
npm ERR! errno ETIMEDOUT
npm ERR! network request to https://registry.npmjs.org/zigbee2mqtt-frontend/-/zigbee2mqtt-frontend-0.7.6.tgz failed, reason: connect ETIMEDOUT 2606:4700::6810:1d22:443
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network ‘proxy’ config is set properly. See: ‘npm help config’
npm ERR! A complete log of this run can be found in:
npm ERR! /home/openhabian/.npm/_logs/2025-06-14T10_10_51_349Z-debug-0.log
FAILED (npm ci)
2025-06-14_12:19:47_CEST [openHABian] Checking for default openHABian username:password combination… FAILED
2025-06-14_12:19:49_CEST [openHABian] We hope you got what you came for! See you again soon 
openhabian@openhabian:~ $
