Test Adapter zigbee2mqtt

[A Former User]

@biker1602 wenn zigbee2mqtt nicht in einem Container läuft dann ja

[biker1602]

@ciddi89
Habe den Raspi neu gestartet aber kein Erfolg der Adapter bleibt gelb

Konsole gestartet
cd /opt/zigbee2mqtt
npm start

Adapter sofort grün

[A Former User]

@biker1602 was fürn raspberry ist das? 0, 1 oder höher?

[biker1602]

@ciddi89 said in Test Adapter zigbee2mqtt:

@biker1602 was fürn raspberry ist das? 0, 1 oder höher?

Raspi 4 ohne SD-Karte, sondern mit SSD Festplatte.

[A Former User]

@biker1602 wie sieht die config aus?

sudo nano /etc/systemd/system/zigbee2mqtt.service

[biker1602]

@ciddi89

[Unit]
Description=zigbee2mqtt
After=network.target

[Service]
ExecStart=/usr/local/bin/npm start
WorkingDirectory=/opt/zigbee2mqtt
StandardOutput=inherit
# Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5)
StandardError=inherit
Restart=always
RestartSec=10s
User=pi

[Install]
WantedBy=multi-user.target

[A Former User]

@biker1602 da fehlt eine Zeile.

[Unit]
Description=zigbee2mqtt
After=network.target

[Service]
Environment=NODE_ENV=production
ExecStart=/usr/bin/npm start
WorkingDirectory=/opt/zigbee2mqtt
StandardOutput=inherit
# Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5)
StandardError=inherit
Restart=always
RestartSec=10s
User=pi

[Install]
WantedBy=multi-user.target

Danach

sudo systemctl start zigbee2mqtt

Und Ergebnis von

systemctl status zigbee2mqtt.service

[biker1602]

@ciddi89

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Dec 20 08:45:59 2022 from 192.168.57.120
#pi@raspberrypi:~ $ sudo systemctl enable zigbee2mqtt.service
pi@raspberrypi:~ $ sudo nano /etc/systemd/system/zigbee2mqtt.service
pi@raspberrypi:~ $ sudo systemctl start zigbee2mqtt
Warning: The unit file, source configuration file or drop-ins of zigbee2mqtt.service changed on disk. Run 'systemctl daemon-reload' to reload units.
pi@raspberrypi:~ $ systemctl status zigbee2mqtt.service
Warning: The unit file, source configuration file or drop-ins of zigbee2mqtt.service changed on disk. Run 'systemctl daemon-reload' to reload units.
● zigbee2mqtt.service - zigbee2mqtt
   Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2022-12-20 09:07:18 CET; 10s ago
  Process: 5532 ExecStart=/usr/local/bin/npm start (code=exited, status=203/EXEC)
 Main PID: 5532 (code=exited, status=203/EXEC)
pi@raspberrypi:~ $

[A Former User]

@biker1602
Mach mal

systemctl daemon-reload

Und dann noch mal

sudo systemctl start zigbee2mqtt

Und Ergebnis von

systemctl status zigbee2mqtt.service

[biker1602]

@ciddi89 said in Test Adapter zigbee2mqtt:

systemctl daemon-reload

Authentication is required to reload the systemd state.
Multiple identities can be used for authentication:
 1.  ,,, (pi)
 2.  root
Choose identity to authenticate as (1-2): Failed to reload daemon: Method call timed out

Was soll ich da nehmen 1 oder 2?

[A Former User]

@biker1602 pi

[A Former User]

@ciddi89 wenn das nicht geht dann mit sudo. Hatte ich vergessen.

sudo systemctl daemon-reload

[biker1602]

@ciddi89

pi@raspberrypi:~ $ sudo systemctl start zigbee2mqtt
pi@raspberrypi:~ $ systemctl status zigbee2mqtt.service
● zigbee2mqtt.service - zigbee2mqtt
   Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2022-12-20 09:21:49 CET; 7s ago
  Process: 7179 ExecStart=/usr/local/bin/npm start (code=exited, status=203/EXEC)
 Main PID: 7179 (code=exited, status=203/EXEC)
pi@raspberrypi:~ $

[A Former User]

@biker1602 vielleicht bist du zu schnell da steht noch activating. Mach jetzt noch mal

systemctl status zigbee2mqtt.service

[biker1602]

@ciddi89

pi@raspberrypi:~ $ systemctl status zigbee2mqtt.service
● zigbee2mqtt.service - zigbee2mqtt
   Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor pres
   Active: activating (auto-restart) (Result: exit-code) since Tue 2022-12-20 09
  Process: 8239 ExecStart=/usr/local/bin/npm start (code=exited, status=203/EXEC
 Main PID: 8239 (code=exited, status=203/EXEC)
lines 1-5/5 (END)
● zigbee2mqtt.service - zigbee2mqtt
   Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2022-12-20 09:29:51 CET; 3s ago
  Process: 8239 ExecStart=/usr/local/bin/npm start (code=exited, status=203/EXEC)
 Main PID: 8239 (code=exited, status=203/EXEC)

[biker1602]

@ciddi89
Bin mal kurz weg

[A Former User]

@biker1602 ja irgendwie startet er den Dienst nicht. Vielleicht weiß @IdleBit noch was

[crunchip]

@biker1602 sagte in Test Adapter zigbee2mqtt:

ExecStart=/usr/local/bin/npm start

liegt das denn in dem Pfad?

[Thomas Braun]

@biker1602

Nodejs./npm-Installation prüfen.
Da scheinen mal wieder die falschen Pfade vorzuliegen (ergo falsch installiert).

[biker1602]

@thomas-braun
Behebt er das mit dem Fixer?