Benötige Hilfe zu Bäckup und Neuinstallation Pi / Fhem

Beta-User · 25 Oktober 2018, 19:50:41

Vielleicht wäre es sinnvoller, erst das Backup von FHEM auf der neuen Karte aufzuspielen, dann zu testen, ob alles funktioniert (fhem-log checken) und dann nochmal eine Sicherungskopie von dem neuen System auf die Seite zu legen. Dass die alte Karte mit dem uralt-System funktioniert, weißt du ja und kannst bei Bedarf immer noch einen Klon ziehen.

exot · 25 Oktober 2018, 23:16:04

Hallo,
Heute wieder die Karte gestartet und nur Fehler.
Danach eine Neuinstallation mit den selben Fehlern
Anschließend die Karte Intensiv formatiert ( 2,5 Stunden)
Nochmalige Installation.
Ich denke aber es ist wieder etwas nicht ok.

Code Auswählen

  pi@raspberrypi:/opt/zigbee2mqtt $ npm start

> zigbee2mqtt@0.1.8 start /opt/zigbee2mqtt
> node index.js

  zigbee2mqtt:info 2018-10-25 22:56:05 Logging to directory: '/opt/zigbee2mqtt/data/log/2018-10-25.22-56-05'
  zigbee2mqtt:info 2018-10-25 22:56:07 Starting zigbee2mqtt version 0.1.8 (commit #97cc56b)
  zigbee2mqtt:info 2018-10-25 22:56:07 Starting zigbee-shepherd
  zigbee2mqtt:info 2018-10-25 22:56:08 zigbee-shepherd started
  zigbee2mqtt:info 2018-10-25 22:56:08 Coordinator firmware version: '20180815'
  zigbee2mqtt:info 2018-10-25 22:56:08 Currently 0 devices are joined:
  zigbee2mqtt:warn 2018-10-25 22:56:08 `permit_join` set to  `true` in configuration.yaml.
  zigbee2mqtt:warn 2018-10-25 22:56:08 Allowing new devices to join.
  zigbee2mqtt:warn 2018-10-25 22:56:08 Set `permit_join` to `false` once you joined all devices.
  zigbee2mqtt:info 2018-10-25 22:56:08 Zigbee: allowing new devices to join.
  zigbee2mqtt:info 2018-10-25 22:56:08 Connecting to MQTT server at mqtt://localhost
  zigbee2mqtt:info 2018-10-25 22:56:08 zigbee-shepherd ready
  zigbee2mqtt:info 2018-10-25 22:56:09 Connected to MQTT server
  zigbee2mqtt:info 2018-10-25 22:56:09 MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'online'
^C  zigbee2mqtt:info 2018-10-25 22:56:56 MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'offline'
  zigbee2mqtt:info 2018-10-25 22:56:56 Disconnecting from MQTT server
  zigbee2mqtt:info 2018-10-25 22:56:56 zigbee-shepherd stopped
pi@raspberrypi:/opt/zigbee2mqtt $ sudo nano /etc/systemd/system/zigbee2mqtt.service
pi@raspberrypi:/opt/zigbee2mqtt $ sudo nano /etc/systemd/system/zigbee2mqtt.service
pi@raspberrypi:/opt/zigbee2mqtt $ sudo systemctl start zigbee2mqtt
pi@raspberrypi:/opt/zigbee2mqtt $ systemctl status zigbee2mqtt.service
● zigbee2mqtt.service - zigbee2mqtt
   Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2018-10-25 22:58:29 CEST; 16s ago
  Process: 2293 ExecStart=/usr/bin/npm start (code=exited, status=203/EXEC)
 Main PID: 2293 (code=exited, status=203/EXEC)

Okt 25 22:58:28 raspberrypi systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
Okt 25 22:58:29 raspberrypi systemd[1]: zigbee2mqtt.service: Service hold-off time over, scheduling restart.
Okt 25 22:58:29 raspberrypi systemd[1]: Stopped zigbee2mqtt.
Okt 25 22:58:29 raspberrypi systemd[1]: zigbee2mqtt.service: Start request repeated too quickly.
Okt 25 22:58:29 raspberrypi systemd[1]: Failed to start zigbee2mqtt.
Okt 25 22:58:29 raspberrypi systemd[1]: zigbee2mqtt.service: Unit entered failed state.
Okt 25 22:58:29 raspberrypi systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
pi@raspberrypi:/opt/zigbee2mqtt $ sudo systemctl enable zigbee2mqtt.service
Created symlink /etc/systemd/system/multi-user.target.wants/zigbee2mqtt.service → /etc/systemd/system/zigbee2mqtt.service.
pi@raspberrypi:/opt/zigbee2mqtt $ sudo systemctl stop zigbee2mqtt
pi@raspberrypi:/opt/zigbee2mqtt $ sudo systemctl start zigbee2mqtt
pi@raspberrypi:/opt/zigbee2mqtt $ sudo journalctl -u zigbee2mqtt.service -f
-- Logs begin at Thu 2016-11-03 18:16:43 CET. --
Okt 25 23:02:01 raspberrypi systemd[1]: Started zigbee2mqtt.
Okt 25 23:02:01 raspberrypi systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=203/EXEC
Okt 25 23:02:01 raspberrypi systemd[1]: zigbee2mqtt.service: Unit entered failed state.
Okt 25 23:02:01 raspberrypi systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
Okt 25 23:02:01 raspberrypi systemd[1]: zigbee2mqtt.service: Service hold-off time over, scheduling restart.
Okt 25 23:02:01 raspberrypi systemd[1]: Stopped zigbee2mqtt.
Okt 25 23:02:01 raspberrypi systemd[1]: zigbee2mqtt.service: Start request repeated too quickly.
Okt 25 23:02:01 raspberrypi systemd[1]: Failed to start zigbee2mqtt.
Okt 25 23:02:01 raspberrypi systemd[1]: zigbee2mqtt.service: Unit entered failed state.
Okt 25 23:02:01 raspberrypi systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
^C
pi@raspberrypi:/opt/zigbee2mqtt $ nano /opt/zigbee2mqtt/data/configuration.yaml
pi@raspberrypi:/opt/zigbee2mqtt $ nano /opt/zigbee2mqtt/data/configuration.yaml
pi@raspberrypi:/opt/zigbee2mqtt $ sudo systemctl start zigbee2mqtt
pi@raspberrypi:/opt/zigbee2mqtt $ sudo journalctl -u zigbee2mqtt.service -f
-- Logs begin at Thu 2016-11-03 18:16:43 CET. --
Okt 25 23:05:24 raspberrypi systemd[1]: Started zigbee2mqtt.
Okt 25 23:05:24 raspberrypi systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=203/EXEC
Okt 25 23:05:24 raspberrypi systemd[1]: zigbee2mqtt.service: Unit entered failed state.
Okt 25 23:05:24 raspberrypi systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
Okt 25 23:05:24 raspberrypi systemd[1]: zigbee2mqtt.service: Service hold-off time over, scheduling restart.
Okt 25 23:05:24 raspberrypi systemd[1]: Stopped zigbee2mqtt.
Okt 25 23:05:24 raspberrypi systemd[1]: zigbee2mqtt.service: Start request repeated too quickly.
Okt 25 23:05:24 raspberrypi systemd[1]: Failed to start zigbee2mqtt.
Okt 25 23:05:24 raspberrypi systemd[1]: zigbee2mqtt.service: Unit entered failed state.
Okt 25 23:05:24 raspberrypi systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.

Die LED am Stick leuchtet aber.
Ich werde noch wirr im Kopf.

Gute Nacht
Gruß Michael

Beta-User · 26 Oktober 2018, 05:50:40

1. Ständiges Neuinstallatieren ist eher Teil.des.Problems wie Teil der Lösung und in einer Linux-Welt UNNÖTIG.
2. Wenn die Karte einen Hau hat, hilft neu Formatieren nicht, zumal.die.bei der Installation des Raspian sowieso wieder neu partitioniert wird! Wenn du denkst, die Karte ist die Ursache, solltest du sie entsorgen.
3. Unter Linux ist es.normalerweise so, dass das Logfile Auskunft geben sollte,was schief gelaufen ist, ggf. nachdem man den loglevel hoch gedreht hat...

Du solltest also weniger rumprobieren und mehr nachdenken bzw. lesen. Aber mit deiner bisherigen Vorgehensweise kommst du umso weniger zum Ziel, je komplexer dein System wird.

Just my2ct.

Wernieman · 26 Oktober 2018, 07:58:14

Abgesehen davon, was Beta-User schreibt (und seeeehr Wichtig ist):
... mal andere Stromversorgung probiert?

exot · 26 Oktober 2018, 08:09:10

Guten Morgen,
Danke für Eure Nachrichten.
Vorab das Logfile aus Fhem:

Code Auswählen

  2018.10.25 22:08:53 1: Please consider using the global attribute sendStatistics
2018.10.25 22:15:51 0: Server shutdown
2018.10.25 22:15:52 1: Including fhem.cfg
2018.10.25 22:15:53 3: WEB: port 8083 opened
2018.10.25 22:15:53 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2018.10.25 22:15:53 1: Including ./log/fhem.save
2018.10.25 22:15:53 1: usb create starting
2018.10.25 22:15:54 3: Probing CUL device /dev/ttyAMA0
2018.10.25 22:15:54 1: CUL: Can't open /dev/ttyAMA0: Permission denied
2018.10.25 22:15:54 1: usb create end
2018.10.25 22:15:54 0: Featurelevel: 5.9
2018.10.25 22:15:54 0: Server started with 6 defined entities (fhem.pl:17613/2018-10-24 perl:5.024001 os:linux user:fhem pid:2420)
2018.10.25 22:27:58 0: Server shutdown
2018.10.25 22:28:08 1: Including fhem.cfg
2018.10.25 22:28:09 3: WEB: port 8083 opened
2018.10.25 22:28:09 2: eventTypes: loaded 1 events from ./log/eventTypes.txt
2018.10.25 22:28:09 1: Including ./log/fhem.save
2018.10.25 22:28:09 0: Featurelevel: 5.9
2018.10.25 22:28:09 0: Server started with 6 defined entities (fhem.pl:17613/2018-10-24 perl:5.024001 os:linux user:fhem pid:471)
2018.10.25 22:30:36 0: Server shutdown
2018.10.25 22:30:46 1: Including fhem.cfg
2018.10.25 22:30:47 3: WEB: port 8083 opened
2018.10.25 22:30:47 2: eventTypes: loaded 1 events from ./log/eventTypes.txt
2018.10.25 22:30:47 1: Including ./log/fhem.save
2018.10.25 22:30:47 0: Featurelevel: 5.9
2018.10.25 22:30:47 0: Server started with 6 defined entities (fhem.pl:17613/2018-10-24 perl:5.024001 os:linux user:fhem pid:458)
2018.10.26 07:25:20 1: Connection refused from the non-local address 93.227.22.201:43670, as there is no working allowed instance defined for it
2018.10.26 07:25:20 1: Connection refused from the non-local address 93.227.22.201:43671, as there is no working allowed instance defined for it
2018.10.26 07:25:20 1: Connection refused from the non-local address 93.227.22.201:43672, as there is no working allowed instance defined for it
2018.10.26 07:25:20 1: Connection refused from the non-local address 93.227.22.201:43673, as there is no working allowed instance defined for it
2018.10.26 07:25:20 1: Connection refused from the non-local address 93.227.22.201:43674, as there is no working allowed instance defined for it
2018.10.26 07:25:20 1: Connection refused from the non-local address 93.227.22.201:43675, as there is no working allowed instance defined for it
2018.10.26 07:25:21 1: Connection refused from the non-local address 93.227.22.201:43677, as there is no working allowed instance defined for it
2018.10.26 07:25:21 1: Connection refused from the non-local address 93.227.22.201:43678, as there is no working allowed instance defined for it
2018.10.26 07:25:27 1: Connection refused from the non-local address 93.227.22.201:43680, as there is no working allowed instance defined for it
2018.10.26 07:25:35 1: Connection refused from the non-local address 93.227.22.201:43692, as there is no working allowed instance defined for it
2018.10.26 07:25:35 1: Connection refused from the non-local address 93.227.22.201:43693, as there is no working allowed instance defined for it
2018.10.26 07:25:35 1: Connection refused from the non-local address 93.227.22.201:43694, as there is no working allowed instance defined for it
2018.10.26 07:25:35 1: Connection refused from the non-local address 93.227.22.201:43695, as there is no working allowed instance defined for it
2018.10.26 07:25:35 1: Connection refused from the non-local address 93.227.22.201:43696, as there is no working allowed instance defined for it
2018.10.26 07:25:35 1: Connection refused from the non-local address 93.227.22.201:43697, as there is no working allowed instance defined for it
2018.10.26 07:25:36 1: Connection refused from the non-local address 93.227.22.201:43699, as there is no working allowed instance defined for it
2018.10.26 07:25:38 1: Connection refused from the non-local address 93.227.22.201:43700, as there is no working allowed instance defined for it
2018.10.26 07:25:39 1: Connection refused from the non-local address 93.227.22.201:43701, as there is no working allowed instance defined for it
2018.10.26 07:25:39 1: Connection refused from the non-local address 93.227.22.201:43702, as there is no working allowed instance defined for it
2018.10.26 07:25:40 1: Connection refused from the non-local address 93.227.22.201:43703, as there is no working allowed instance defined for it
2018.10.26 07:25:40 1: Connection refused from the non-local address 93.227.22.201:43704, as there is no working allowed instance defined for it
2018.10.26 07:25:40 1: Connection refused from the non-local address 93.227.22.201:43705, as there is no working allowed instance defined for it
2018.10.26 07:25:40 1: Connection refused from the non-local address 93.227.22.201:43706, as there is no working allowed instance defined for it
2018.10.26 07:25:40 1: Connection refused from the non-local address 93.227.22.201:43707, as there is no working allowed instance defined for it
2018.10.26 07:25:40 1: Connection refused from the non-local address 93.227.22.201:43708, as there is no working allowed instance defined for it

Und das:

Code Auswählen


pi@raspberrypi:/opt/zigbee2mqtt $ sudo systemctl stop zigbee2mqtt
pi@raspberrypi:/opt/zigbee2mqtt $ sudo systemctl start zigbee2mqtt
pi@raspberrypi:/opt/zigbee2mqtt $ sudo journalctl -u zigbee2mqtt.service -f
-- Logs begin at Thu 2016-11-03 18:16:43 CET. --
Okt 26 07:47:00 raspberrypi systemd[1]: Started zigbee2mqtt.
Okt 26 07:47:00 raspberrypi systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=203/EXEC
Okt 26 07:47:00 raspberrypi systemd[1]: zigbee2mqtt.service: Unit entered failed state.
Okt 26 07:47:00 raspberrypi systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
Okt 26 07:47:00 raspberrypi systemd[1]: zigbee2mqtt.service: Service hold-off time over, scheduling restart.
Okt 26 07:47:00 raspberrypi systemd[1]: Stopped zigbee2mqtt.
Okt 26 07:47:00 raspberrypi systemd[1]: zigbee2mqtt.service: Start request repeated too quickly.
Okt 26 07:47:00 raspberrypi systemd[1]: Failed to start zigbee2mqtt.
Okt 26 07:47:00 raspberrypi systemd[1]: zigbee2mqtt.service: Unit entered failed state.
Okt 26 07:47:00 raspberrypi systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
^C
pi@raspberrypi:/opt/zigbee2mqtt $ cd
pi@raspberrypi:~ $ dpkg -l | grep mosquitto
ii  mosquitto                        1.4.10-3+deb9u2              armhf        MQTT version 3.1/3.1.1 compatible message broker
pi@raspberrypi:~ $ ps aux | grep mosquitto
mosquit+  2056  0.0  0.4   6332  4028 ?        S    Okt25   0:11 /usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf
pi        5733  0.0  0.0   4776   540 pts/0    S+   07:50   0:00 grep --color=auto mosquitto
pi@raspberrypi:~ $  /etc/init/mosquitto start
-bash: /etc/init/mosquitto: Datei oder Verzeichnis nicht gefunden

Das heißt doch, das mosquitto nicht gestartet ist?

Stromversorgung werde ich überprüfen

Gruß Michael

exot · 26 Oktober 2018, 08:57:09

Hallo,
Habe mir gerade mal die Stromversorgung angesehen.
Ausgang sind 5v und 2,0A
Ich denke das ist Ok.
Zumal ja bei der Zigbee Installation nur der Zigbee Stick angeschlossen ist.

Noch eine Frage zu mosquitto.
Wo sollte sich bas Verzeichnis befinden.

Code Auswählen

 /etc/init/mosquitto/

Hier gibt es kein mosquitto Verzeichnis.

Gruß Michael

Otto123 · 26 Oktober 2018, 09:04:07

Die Frage nach der Stromversorgung ist nicht allein in aufgedruckten Volt und Ampere beantwortet. Beim Raspberry muss das auch ankommen! Je nach Modell wird das auf dem Raspberry überprüft. So ziemlich bei allen gilt: Die rote LED darf niemals blinkern!!!

Eigentlich so gut wie alle "unklaren Dinge" beim raspberry hängen mit ungeeigneter Stromversorgung / dünne schlechte Kabel usw zusammen. Die Netzteile verändern sich manchmal über Jahre. Auch ein: ging bisher ohne Probleme - ist keine Garantie.

Gruß Otto

Beta-User · 26 Oktober 2018, 10:26:49

Da du ständig neu installiert hat, kann niemand sagen, welchen status mosquitto hat. Ich würde empfehlen, statt mosquitto MQTT2 einzusetzen...

exot · 26 Oktober 2018, 10:31:21

Hallo Beta-User,
Ich glaube jetzt das Log gefunden zu haben

Code Auswählen

  0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using npm@5.5.1
3 info using node@v8.9.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle zigbee2mqtt@0.1.8~prestart: zigbee2mqtt@0.1.8
6 info lifecycle zigbee2mqtt@0.1.8~start: zigbee2mqtt@0.1.8
7 verbose lifecycle zigbee2mqtt@0.1.8~start: unsafe-perm in lifecycle true
8 verbose lifecycle zigbee2mqtt@0.1.8~start: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/opt/zigbee2mqtt/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
9 verbose lifecycle zigbee2mqtt@0.1.8~start: CWD: /opt/zigbee2mqtt
10 silly lifecycle zigbee2mqtt@0.1.8~start: Args: [ '-c', 'node index.js' ]
11 silly lifecycle zigbee2mqtt@0.1.8~start: Returned: code: 1  signal: null
12 info lifecycle zigbee2mqtt@0.1.8~start: Failed to exec start script
13 verbose stack Error: zigbee2mqtt@0.1.8 start: `node index.js`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:280:16)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at EventEmitter.emit (events.js:214:7)
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at ChildProcess.emit (events.js:214:7)
13 verbose stack     at maybeClose (internal/child_process.js:925:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid zigbee2mqtt@0.1.8
15 verbose cwd /opt/zigbee2mqtt
16 verbose Linux 4.14.71-v7+
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
18 verbose node v8.9.0
19 verbose npm  v5.5.1
20 error code ELIFECYCLE
21 error errno 1
22 error zigbee2mqtt@0.1.8 start: `node index.js`
22 error Exit status 1
23 error Failed at the zigbee2mqtt@0.1.8 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Hilft das weiter?

Hallo Otto,
Danke für Deine Nachricht.
Bei einschalten pi leuchtet rot undgrün blinkt,
Danach leuchtet rot und grün blinkt gelegentlich bei Datenübertragung.
Das sollte doch passen!?

Gruß Michael

exot · 26 Oktober 2018, 10:36:49

Hallo Beta-User,
Ich werde jetzt nur noch bei dieser Installation bleiben!
Egal was kommt. Versprochen!
Hier mosquitto:

Code Auswählen

 pi@raspberrypi:~ $ sudo service mosquitto start
pi@raspberrypi:~ $ sudo service mosquitto status
● mosquitto.service - LSB: mosquitto MQTT v3.1 message broker
   Loaded: loaded (/etc/init.d/mosquitto; generated; vendor preset: enabled)
   Active: active (running) since Fri 2018-10-26 10:17:03 CEST; 16min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 313 ExecStart=/etc/init.d/mosquitto start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/mosquitto.service
           └─390 /usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf

Okt 26 10:17:03 raspberrypi systemd[1]: Starting LSB: mosquitto MQTT v3.1 message broker...
Okt 26 10:17:03 raspberrypi mosquitto[313]: Starting network daemon:: mosquitto.
Okt 26 10:17:03 raspberrypi systemd[1]: Started LSB: mosquitto MQTT v3.1 message broker.
pi@raspberrypi:~ $

Das sieht doch gut aus?

Gruß Michael

Beta-User · 26 Oktober 2018, 11:47:52

Hmm, ich werd daraus auch erst mal nicht schlau.
Könntest du den zigbee-Dienst erst mal auf der Konsole starten wie unter "running the bridge" im dortigen wiki beschrieben?
Da kommen dann evtl.weitere infos.

exot · 26 Oktober 2018, 12:14:00

Hallo Beta-User,
Ich denke das möchtest Du sehen:

Code Auswählen

pi@raspberrypi:/opt/zigbee2mqtt $ npm start

> zigbee2mqtt@0.1.8 start /opt/zigbee2mqtt
> node index.js


/opt/zigbee2mqtt/node_modules/js-yaml/lib/js-yaml/loader.js:171
  throw generateError(state, message);
  ^
YAMLException: duplicated mapping key at line 21, column -63:
    serial:
    ^
    at generateError (/opt/zigbee2mqtt/node_modules/js-yaml/lib/js-yaml/loader.js:165:10)
    at throwError (/opt/zigbee2mqtt/node_modules/js-yaml/lib/js-yaml/loader.js:171:9)
    at storeMappingPair (/opt/zigbee2mqtt/node_modules/js-yaml/lib/js-yaml/loader.js:308:7)
    at readBlockMapping (/opt/zigbee2mqtt/node_modules/js-yaml/lib/js-yaml/loader.js:1071:9)
    at composeNode (/opt/zigbee2mqtt/node_modules/js-yaml/lib/js-yaml/loader.js:1332:12)
    at readDocument (/opt/zigbee2mqtt/node_modules/js-yaml/lib/js-yaml/loader.js:1492:3)
    at loadDocuments (/opt/zigbee2mqtt/node_modules/js-yaml/lib/js-yaml/loader.js:1548:5)
    at load (/opt/zigbee2mqtt/node_modules/js-yaml/lib/js-yaml/loader.js:1569:19)
    at Object.safeLoad (/opt/zigbee2mqtt/node_modules/js-yaml/lib/js-yaml/loader.js:1591:10)
    at read (/opt/zigbee2mqtt/lib/util/settings.js:29:17)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! zigbee2mqtt@0.1.8 start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@0.1.8 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2018-10-26T10_10_42_193Z-debug.log
pi@raspberrypi:/opt/zigbee2mqtt $ sudo systemctl start zigbee2mqtt
pi@raspberrypi:/opt/zigbee2mqtt $ systemctl status zigbee2mqtt.service
● zigbee2mqtt.service - zigbee2mqtt
   Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2018-10-26 12:11:29 CEST; 15s ago
  Process: 1389 ExecStart=/usr/bin/npm start (code=exited, status=203/EXEC)
 Main PID: 1389 (code=exited, status=203/EXEC)

Okt 26 12:11:29 raspberrypi systemd[1]: zigbee2mqtt.service: Unit entered failed state.
Okt 26 12:11:29 raspberrypi systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
Okt 26 12:11:29 raspberrypi systemd[1]: zigbee2mqtt.service: Service hold-off time over, scheduling restart.
Okt 26 12:11:29 raspberrypi systemd[1]: Stopped zigbee2mqtt.
Okt 26 12:11:29 raspberrypi systemd[1]: zigbee2mqtt.service: Start request repeated too quickly.
Okt 26 12:11:29 raspberrypi systemd[1]: Failed to start zigbee2mqtt.
Okt 26 12:11:29 raspberrypi systemd[1]: zigbee2mqtt.service: Unit entered failed state.
Okt 26 12:11:29 raspberrypi systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
pi@raspberrypi:/opt/zigbee2mqtt $

Gruß Michael

Beta-User · 26 Oktober 2018, 12:59:01

Das sagt doch schon mal was. Da scheint.ein Fehler in der yaml zu sein (doppelter Eintrag.zu serial, Zeile 21).

Ansonsten mal z.b. hier lesen: https://stackoverflow.com/questions/42308879/npm-err-code-elifecycle

exot · 26 Oktober 2018, 15:07:29

Hallo Beta-User,
Danke für den Link.
Habe die Prozeduren mal durchgespielt.
Bei

Code Auswählen

npm start
startet zigbee2mqtt ist auch so zu sehen.
LED am Stick leuchtet
CTRL+C beendet den Vorgang Stopped
LED am Stick leuchtet

Code Auswählen

 sudo systemctl start zigbee2mqtt
 systemctl status zigbee2mqtt.service

Bringt wieder den Fehler
Aber zigbee2mqt wurde ja auch vorher beendet mit CTRL+C???

Code Auswählen

   i@raspberrypi:/opt/zigbee2mqtt $ npm start

> zigbee2mqtt@0.1.8 start /opt/zigbee2mqtt
> node index.js

  zigbee2mqtt:info 2018-10-26 14:48:00 Logging to directory: '/opt/zigbee2mqtt/data/log/2018-10-26.14-48-00'
  zigbee2mqtt:info 2018-10-26 14:48:00 Starting zigbee2mqtt version 0.1.8 (commit #97cc56b)
  zigbee2mqtt:info 2018-10-26 14:48:00 Starting zigbee-shepherd
  zigbee2mqtt:info 2018-10-26 14:48:01 zigbee-shepherd started
  zigbee2mqtt:info 2018-10-26 14:48:01 Coordinator firmware version: '20180815'
  zigbee2mqtt:info 2018-10-26 14:48:01 Currently 0 devices are joined:
  zigbee2mqtt:warn 2018-10-26 14:48:01 `permit_join` set to  `true` in configuration.yaml.
  zigbee2mqtt:warn 2018-10-26 14:48:01 Allowing new devices to join.
  zigbee2mqtt:warn 2018-10-26 14:48:01 Set `permit_join` to `false` once you joined all devices.
  zigbee2mqtt:info 2018-10-26 14:48:01 Zigbee: allowing new devices to join.
  zigbee2mqtt:info 2018-10-26 14:48:01 Connecting to MQTT server at mqtt://localhost
  zigbee2mqtt:info 2018-10-26 14:48:01 zigbee-shepherd ready
  zigbee2mqtt:info 2018-10-26 14:48:01 Connected to MQTT server
  zigbee2mqtt:info 2018-10-26 14:48:01 MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'online'

^C  zigbee2mqtt:info 2018-10-26 14:58:56 MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'offline'
  zigbee2mqtt:info 2018-10-26 14:58:56 Disconnecting from MQTT server
  zigbee2mqtt:info 2018-10-26 14:58:56 zigbee-shepherd stopped
pi@raspberrypi:/opt/zigbee2mqtt $ sudo systemctl start zigbee2mqtt
pi@raspberrypi:/opt/zigbee2mqtt $ systemctl status zigbee2mqtt.service
● zigbee2mqtt.service - zigbee2mqtt
   Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2018-10-26 15:02:37 CEST; 18s ago
  Process: 3166 ExecStart=/usr/bin/npm start (code=exited, status=203/EXEC)
 Main PID: 3166 (code=exited, status=203/EXEC)

Okt 26 15:02:37 raspberrypi systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
Okt 26 15:02:37 raspberrypi systemd[1]: zigbee2mqtt.service: Service hold-off time over, scheduling restart.
Okt 26 15:02:37 raspberrypi systemd[1]: Stopped zigbee2mqtt.
Okt 26 15:02:37 raspberrypi systemd[1]: zigbee2mqtt.service: Start request repeated too quickly.
Okt 26 15:02:37 raspberrypi systemd[1]: Failed to start zigbee2mqtt.
Okt 26 15:02:37 raspberrypi systemd[1]: zigbee2mqtt.service: Unit entered failed state.
Okt 26 15:02:37 raspberrypi systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
pi@raspberrypi:/opt/zigbee2mqtt $

Gruß Michael

Beta-User · 26 Oktober 2018, 17:10:36

Hmmmm,
schwierig, da was genaues zu sagen. Da sich der Dienst mit npm... starten lässt, würde ich auf eine defekte service-Datei tippen. Wie hast du die erstellt und auf den pi gebracht? (Tipp: "mc" installieren un "mcedit" verwenden)

Zwei andere Dinge noch:
Initalusbcheck ist aus?
Und es gibt auch kein port-forwarding? (Da waren diese seltsamen Meldungen von allowed im Fhem-log!)

Ansonsten sollte Ctrl+c no harm to the System sein und du solltest die Funktionalität ggf. auf Basis des manuell gestarteten Dienste mal mit Mosquitto und dann auch FHEM testen, damit du ein Gefühl dafür bekommst. Dazu am besten auch mit mosquitto_sub mal auf einer weiteren Konsole mithören.