NEWS
Probleme mit Serialport bei zwave2
Tester
118
Beiträge
5
Kommentatoren
10.4k
Aufrufe
2
Watching
-
@thomas-braun said in Test Adapter Z-Wave 2 v1.10.x:
Nimm den Adapter aus der Adapterliste im Admin.
Hatte ich schon gemacht.
sogar sogar instance weg gemacht und neu gemacht
leider geht es nicht mehr
@esmax666 sagte in Test Adapter Z-Wave 2 v1.10.x:
leider geht es nicht mehr
Stimmt dann wohl.
Leider kann man aus deiner 'Fehlerbeschreibung' nichts herauslesen. -
@esmax666 sagte in Test Adapter Z-Wave 2 v1.10.x:
leider geht es nicht mehr
Stimmt dann wohl.
Leider kann man aus deiner 'Fehlerbeschreibung' nichts herauslesen.@thomas-braun was kann ich sonst noch als info geben ?
sonst habe ich noch 2 warn und 1 error
info.0 2021-05-16 13:07:15.628 warn (2791) State "info.0.uuid" has no existing object, this might lead to an error in future versions host.raspberrypi 2021-05-16 13:00:08.345 info instance system.adapter.ical.0 terminated with code 0 (NO_ERROR) host.raspberrypi 2021-05-16 13:00:00.042 info instance system.adapter.ical.0 started with pid 5361 zwave2.0 2021-05-16 12:59:53.829 info (5346) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 host.raspberrypi 2021-05-16 12:59:51.487 info instance system.adapter.zwave2.0 started with pid 5346 host.raspberrypi 2021-05-16 12:59:21.429 info Restart adapter system.adapter.zwave2.0 because enabled host.raspberrypi 2021-05-16 12:59:21.428 info instance system.adapter.zwave2.0 terminated with code NaN () host.raspberrypi 2021-05-16 12:59:21.427 warn instance system.adapter.zwave2.0 terminated due to SIGABRT host.raspberrypi 2021-05-16 12:59:21.422 error Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory zwave2.0 2021-05-16 12:45:57.264 info (5176) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 host.raspberrypi 2021-05-16 12:45:55.024 info instance system.adapter.zwave2.0 started with pid 5176 host.raspberrypi 2021-05-16 12:45:24.958 info Restart adapter system.adapter.zwave2.0 because enabled host.raspberrypi 2021-05-16 12:45:24.957 info instance system.adapter.zwave2.0 terminated with code NaN () host.raspberrypi 2021-05-16 12:45:24.956 warn instance system.adapter.zwave2.0 terminated due to SIGABRT host.raspberrypi 2021-05-16 12:45:24.950 error Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory info.0 2021-05-16 12:37:15.604 warn (2791) State "info.0.uuid" has no existing object, this might lead to an error in future versions zwave2.0 2021-05-16 12:32:01.208 info (5010) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 host.raspberrypi 2021-05-16 12:31:58.911 info instance system.adapter.zwave2.0 started with pid 5010 host.raspberrypi 2021-05-16 12:31:28.859 info Restart adapter system.adapter.zwave2.0 because enabled host.raspberrypi 2021-05-16 12:31:28.859 info instance system.adapter.zwave2.0 terminated with code NaN () host.raspberrypi 2021-05-16 12:31:28.858 warn instance system.adapter.zwave2.0 terminated due to SIGABRT host.raspberrypi 2021-05-16 12:31:28.857 error Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory -
@thomas-braun was kann ich sonst noch als info geben ?
sonst habe ich noch 2 warn und 1 error
info.0 2021-05-16 13:07:15.628 warn (2791) State "info.0.uuid" has no existing object, this might lead to an error in future versions host.raspberrypi 2021-05-16 13:00:08.345 info instance system.adapter.ical.0 terminated with code 0 (NO_ERROR) host.raspberrypi 2021-05-16 13:00:00.042 info instance system.adapter.ical.0 started with pid 5361 zwave2.0 2021-05-16 12:59:53.829 info (5346) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 host.raspberrypi 2021-05-16 12:59:51.487 info instance system.adapter.zwave2.0 started with pid 5346 host.raspberrypi 2021-05-16 12:59:21.429 info Restart adapter system.adapter.zwave2.0 because enabled host.raspberrypi 2021-05-16 12:59:21.428 info instance system.adapter.zwave2.0 terminated with code NaN () host.raspberrypi 2021-05-16 12:59:21.427 warn instance system.adapter.zwave2.0 terminated due to SIGABRT host.raspberrypi 2021-05-16 12:59:21.422 error Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory zwave2.0 2021-05-16 12:45:57.264 info (5176) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 host.raspberrypi 2021-05-16 12:45:55.024 info instance system.adapter.zwave2.0 started with pid 5176 host.raspberrypi 2021-05-16 12:45:24.958 info Restart adapter system.adapter.zwave2.0 because enabled host.raspberrypi 2021-05-16 12:45:24.957 info instance system.adapter.zwave2.0 terminated with code NaN () host.raspberrypi 2021-05-16 12:45:24.956 warn instance system.adapter.zwave2.0 terminated due to SIGABRT host.raspberrypi 2021-05-16 12:45:24.950 error Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory info.0 2021-05-16 12:37:15.604 warn (2791) State "info.0.uuid" has no existing object, this might lead to an error in future versions zwave2.0 2021-05-16 12:32:01.208 info (5010) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 host.raspberrypi 2021-05-16 12:31:58.911 info instance system.adapter.zwave2.0 started with pid 5010 host.raspberrypi 2021-05-16 12:31:28.859 info Restart adapter system.adapter.zwave2.0 because enabled host.raspberrypi 2021-05-16 12:31:28.859 info instance system.adapter.zwave2.0 terminated with code NaN () host.raspberrypi 2021-05-16 12:31:28.858 warn instance system.adapter.zwave2.0 terminated due to SIGABRT host.raspberrypi 2021-05-16 12:31:28.857 error Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory -
-
@esmax666
Bitte keine Bilderchen posten, KonsolenTEXT in CodeTags eingebettet hier rein. -
@Esmax666 die Datei brauchst du inzwischen nicht mehr manuell bearbeiten. Auf Pi 4 sind das die Schritte, die ausreichen: Konsole auf,
sudo raspi-config- 3 Interface Options
- P6 Serial Port
- "Would you like a login shell to be accessible over serial?" => NO
- "Would you like the serial port hardware to be enabled?" => YES
Danach sollte der Adapter funktionieren, wenn du
/dev/serial0einträgst - ist leider nicht in der Liste zu finden.Warum `sudo` böse ist: https://forum.iobroker.net/post/17109
-
@Esmax666 die Datei brauchst du inzwischen nicht mehr manuell bearbeiten. Auf Pi 4 sind das die Schritte, die ausreichen: Konsole auf,
sudo raspi-config- 3 Interface Options
- P6 Serial Port
- "Would you like a login shell to be accessible over serial?" => NO
- "Would you like the serial port hardware to be enabled?" => YES
Danach sollte der Adapter funktionieren, wenn du
/dev/serial0einträgst - ist leider nicht in der Liste zu finden.@alcalzone
An den Hardware-Part hatte ich noch gar nicht gedacht, bzw. vorausgesetzt das der natürlich auch aktiviert wurde.Wobei dann /dev/serial0 'nur' ein symlink auf das device node /dev/ttyAMA0 sein dürfte.
-
@Esmax666 die Datei brauchst du inzwischen nicht mehr manuell bearbeiten. Auf Pi 4 sind das die Schritte, die ausreichen: Konsole auf,
sudo raspi-config- 3 Interface Options
- P6 Serial Port
- "Would you like a login shell to be accessible over serial?" => NO
- "Would you like the serial port hardware to be enabled?" => YES
Danach sollte der Adapter funktionieren, wenn du
/dev/serial0einträgst - ist leider nicht in der Liste zu finden.ok ist jetzt aktviert
und auch neu gestartet
aber immer Driver could not be started
zwave2.0 2021-05-16 15:32:12.067 error (17665) The Z-Wave driver could not be started: Error: No such file or directory, cannot open /dev/serial0 zwave2.0 2021-05-16 15:32:11.921 info (17665) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 host.raspberrypi 2021-05-16 15:32:09.511 info instance system.adapter.zwave2.0 started with pid 17665 host.raspberrypi 2021-05-16 15:32:07.043 info instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zwave2.0 2021-05-16 15:32:06.372 info (5742) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zwave2.0 2021-05-16 15:32:06.371 info (5742) terminating zwave2.0 2021-05-16 15:32:06.369 info (5742) Shutting down driver... zwave2.0 2021-05-16 15:32:06.367 info (5742) Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2021-05-16 15:32:06.367 info stopInstance system.adapter.zwave2.0 send kill signal host.raspberrypi 2021-05-16 15:32:06.359 info stopInstance system.adapter.zwave2.0 (force=false, process=true) host.raspberrypi 2021-05-16 15:30:27.733 info instance system.adapter.ical.0 terminated with code 0 (NO_ERROR) ical.0 2021-05-16 15:30:27.198 info (8661) Terminated (NO_ERROR): Without reason -
ok ist jetzt aktviert
und auch neu gestartet
aber immer Driver could not be started
zwave2.0 2021-05-16 15:32:12.067 error (17665) The Z-Wave driver could not be started: Error: No such file or directory, cannot open /dev/serial0 zwave2.0 2021-05-16 15:32:11.921 info (17665) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 host.raspberrypi 2021-05-16 15:32:09.511 info instance system.adapter.zwave2.0 started with pid 17665 host.raspberrypi 2021-05-16 15:32:07.043 info instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zwave2.0 2021-05-16 15:32:06.372 info (5742) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zwave2.0 2021-05-16 15:32:06.371 info (5742) terminating zwave2.0 2021-05-16 15:32:06.369 info (5742) Shutting down driver... zwave2.0 2021-05-16 15:32:06.367 info (5742) Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2021-05-16 15:32:06.367 info stopInstance system.adapter.zwave2.0 send kill signal host.raspberrypi 2021-05-16 15:32:06.359 info stopInstance system.adapter.zwave2.0 (force=false, process=true) host.raspberrypi 2021-05-16 15:30:27.733 info instance system.adapter.ical.0 terminated with code 0 (NO_ERROR) ical.0 2021-05-16 15:30:27.198 info (8661) Terminated (NO_ERROR): Without reason@esmax666
Und wenn du das device direkt anrufst? Unter /dev/ttyAMA0Gibt es das Gerät?
ls -la /dev/ttyAMA0 sudo -u iobroker groups -
@esmax666
Und wenn du das device direkt anrufst? Unter /dev/ttyAMA0Gibt es das Gerät?
ls -la /dev/ttyAMA0 sudo -u iobroker groups@thomas-braun said in Probleme mit Serialport bei zwave2:
/dev/ttyAMA0
dann bekomme ich wie davor
zwave2.0 2021-05-16 15:39:28.776 info (15581) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 host.raspberrypi 2021-05-16 15:39:26.309 info instance system.adapter.zwave2.0 started with pid 15581 host.raspberrypi 2021-05-16 15:39:23.743 info instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zwave2.0 2021-05-16 15:39:23.146 info (17665) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zwave2.0 2021-05-16 15:39:23.145 info (17665) terminating zwave2.0 2021-05-16 15:39:23.143 info (17665) Shutting down driver... host.raspberrypi 2021-05-16 15:39:23.141 info stopInstance system.adapter.zwave2.0 send kill signal zwave2.0 2021-05-16 15:39:23.141 info (17665) Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2021-05-16 15:39:23.126 info stopInstance system.adapter.zwave2.0 (force=false, process=true)und als "debug level" bekomme ich das :
zwave2.0 2021-05-16 15:41:19.769 info (24494) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 zwave2.0 2021-05-16 15:41:19.518 debug (24494) statesDB connected zwave2.0 2021-05-16 15:41:19.517 debug (24494) States connected to redis: 127.0.0.1:9000 zwave2.0 2021-05-16 15:41:19.510 debug (24494) States create User PubSub Client zwave2.0 2021-05-16 15:41:19.508 debug (24494) States create System PubSub Client zwave2.0 2021-05-16 15:41:19.501 debug (24494) Redis States: Use Redis connection: 127.0.0.1:9000 zwave2.0 2021-05-16 15:41:19.498 debug (24494) objectDB connected zwave2.0 2021-05-16 15:41:19.469 debug (24494) Objects connected to redis: 127.0.0.1:9001 zwave2.0 2021-05-16 15:41:19.455 debug (24494) Objects client initialize lua scripts zwave2.0 2021-05-16 15:41:19.453 debug (24494) Objects create User PubSub Client zwave2.0 2021-05-16 15:41:19.451 debug (24494) Objects create System PubSub Client zwave2.0 2021-05-16 15:41:19.448 debug (24494) Objects client ready ... initialize now zwave2.0 2021-05-16 15:41:19.402 debug (24494) Redis Objects: Use Redis connection: 127.0.0.1:9001 host.raspberrypi 2021-05-16 15:41:17.450 info instance system.adapter.zwave2.0 started with pid 24494 host.raspberrypi 2021-05-16 15:41:17.338 info "system.adapter.zwave2.0" enabled host.raspberrypi 2021-05-16 15:41:15.669 info instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.raspberrypi 2021-05-16 15:41:15.087 info stopInstance system.adapter.zwave2.0 send kill signal zwave2.0 2021-05-16 15:41:15.048 info (22847) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zwave2.0 2021-05-16 15:41:15.046 info (22847) terminating zwave2.0 2021-05-16 15:41:15.044 info (22847) Shutting down driver... zwave2.0 2021-05-16 15:41:15.042 info (22847) Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2021-05-16 15:41:15.029 info stopInstance system.adapter.zwave2.0 (force=false, process=true) host.raspberrypi 2021-05-16 15:41:15.027 info "system.adapter.zwave2.0" disabled zwave2.0 2021-05-16 15:40:59.111 info (22847) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 zwave2.0 2021-05-16 15:40:58.808 debug (22847) statesDB connected zwave2.0 2021-05-16 15:40:58.807 debug (22847) States connected to redis: 127.0.0.1:9000 zwave2.0 2021-05-16 15:40:58.795 debug (22847) States create User PubSub Client zwave2.0 2021-05-16 15:40:58.794 debug (22847) States create System PubSub Client zwave2.0 2021-05-16 15:40:58.783 debug (22847) Redis States: Use Redis connection: 127.0.0.1:9000 zwave2.0 2021-05-16 15:40:58.781 debug (22847) objectDB connected zwave2.0 2021-05-16 15:40:58.751 debug (22847) Objects connected to redis: 127.0.0.1:9001 zwave2.0 2021-05-16 15:40:58.737 debug (22847) Objects client initialize lua scripts zwave2.0 2021-05-16 15:40:58.736 debug (22847) Objects create User PubSub Client zwave2.0 2021-05-16 15:40:58.735 debug (22847) Objects create System PubSub Client zwave2.0 2021-05-16 15:40:58.732 debug (22847) Objects client ready ... initialize now zwave2.0 2021-05-16 15:40:58.696 debug (22847) Redis Objects: Use Redis connection: 127.0.0.1:9001 host.raspberrypi 2021-05-16 15:40:56.599 info instance system.adapter.zwave2.0 started with pid 22847 host.raspberrypi 2021-05-16 15:40:56.462 info "system.adapter.zwave2.0" enabled host.raspberrypi 2021-05-16 15:40:50.698 info instance system.adapter.zwave2.0 terminated with code null () host.raspberrypi 2021-05-16 15:40:50.697 warn instance system.adapter.zwave2.0 terminated due to SIGTERM host.raspberrypi 2021-05-16 15:40:50.626 info stopInstance system.adapter.zwave2.0 killing pid 22283 host.raspberrypi 2021-05-16 15:40:49.624 info stopInstance system.adapter.zwave2.0 send kill signal host.raspberrypi 2021-05-16 15:40:49.613 info stopInstance system.adapter.zwave2.0 (force=false, process=true) host.raspberrypi 2021-05-16 15:40:49.613 info "system.adapter.zwave2.0" disabled host.raspberrypi 2021-05-16 15:40:49.345 info instance system.adapter.zwave2.0 started with pid 22283 host.raspberrypi 2021-05-16 15:40:46.840 info instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zwave2.0 2021-05-16 15:40:46.228 info (15581) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zwave2.0 2021-05-16 15:40:46.226 info (15581) terminating zwave2.0 2021-05-16 15:40:46.225 info (15581) Shutting down driver... zwave2.0 2021-05-16 15:40:46.223 info (15581) Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2021-05-16 15:40:46.223 info stopInstance system.adapter.zwave2.0 send kill signal host.raspberrypi 2021-05-16 15:40:46.210 info stopInstance system.adapter.zwave2.0 (force=false, process=true) zwave2.0 2021-05-16 15:39:28.776 info (15581) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 -
@thomas-braun said in Probleme mit Serialport bei zwave2:
/dev/ttyAMA0
dann bekomme ich wie davor
zwave2.0 2021-05-16 15:39:28.776 info (15581) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 host.raspberrypi 2021-05-16 15:39:26.309 info instance system.adapter.zwave2.0 started with pid 15581 host.raspberrypi 2021-05-16 15:39:23.743 info instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zwave2.0 2021-05-16 15:39:23.146 info (17665) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zwave2.0 2021-05-16 15:39:23.145 info (17665) terminating zwave2.0 2021-05-16 15:39:23.143 info (17665) Shutting down driver... host.raspberrypi 2021-05-16 15:39:23.141 info stopInstance system.adapter.zwave2.0 send kill signal zwave2.0 2021-05-16 15:39:23.141 info (17665) Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2021-05-16 15:39:23.126 info stopInstance system.adapter.zwave2.0 (force=false, process=true)und als "debug level" bekomme ich das :
zwave2.0 2021-05-16 15:41:19.769 info (24494) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 zwave2.0 2021-05-16 15:41:19.518 debug (24494) statesDB connected zwave2.0 2021-05-16 15:41:19.517 debug (24494) States connected to redis: 127.0.0.1:9000 zwave2.0 2021-05-16 15:41:19.510 debug (24494) States create User PubSub Client zwave2.0 2021-05-16 15:41:19.508 debug (24494) States create System PubSub Client zwave2.0 2021-05-16 15:41:19.501 debug (24494) Redis States: Use Redis connection: 127.0.0.1:9000 zwave2.0 2021-05-16 15:41:19.498 debug (24494) objectDB connected zwave2.0 2021-05-16 15:41:19.469 debug (24494) Objects connected to redis: 127.0.0.1:9001 zwave2.0 2021-05-16 15:41:19.455 debug (24494) Objects client initialize lua scripts zwave2.0 2021-05-16 15:41:19.453 debug (24494) Objects create User PubSub Client zwave2.0 2021-05-16 15:41:19.451 debug (24494) Objects create System PubSub Client zwave2.0 2021-05-16 15:41:19.448 debug (24494) Objects client ready ... initialize now zwave2.0 2021-05-16 15:41:19.402 debug (24494) Redis Objects: Use Redis connection: 127.0.0.1:9001 host.raspberrypi 2021-05-16 15:41:17.450 info instance system.adapter.zwave2.0 started with pid 24494 host.raspberrypi 2021-05-16 15:41:17.338 info "system.adapter.zwave2.0" enabled host.raspberrypi 2021-05-16 15:41:15.669 info instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.raspberrypi 2021-05-16 15:41:15.087 info stopInstance system.adapter.zwave2.0 send kill signal zwave2.0 2021-05-16 15:41:15.048 info (22847) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zwave2.0 2021-05-16 15:41:15.046 info (22847) terminating zwave2.0 2021-05-16 15:41:15.044 info (22847) Shutting down driver... zwave2.0 2021-05-16 15:41:15.042 info (22847) Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2021-05-16 15:41:15.029 info stopInstance system.adapter.zwave2.0 (force=false, process=true) host.raspberrypi 2021-05-16 15:41:15.027 info "system.adapter.zwave2.0" disabled zwave2.0 2021-05-16 15:40:59.111 info (22847) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 zwave2.0 2021-05-16 15:40:58.808 debug (22847) statesDB connected zwave2.0 2021-05-16 15:40:58.807 debug (22847) States connected to redis: 127.0.0.1:9000 zwave2.0 2021-05-16 15:40:58.795 debug (22847) States create User PubSub Client zwave2.0 2021-05-16 15:40:58.794 debug (22847) States create System PubSub Client zwave2.0 2021-05-16 15:40:58.783 debug (22847) Redis States: Use Redis connection: 127.0.0.1:9000 zwave2.0 2021-05-16 15:40:58.781 debug (22847) objectDB connected zwave2.0 2021-05-16 15:40:58.751 debug (22847) Objects connected to redis: 127.0.0.1:9001 zwave2.0 2021-05-16 15:40:58.737 debug (22847) Objects client initialize lua scripts zwave2.0 2021-05-16 15:40:58.736 debug (22847) Objects create User PubSub Client zwave2.0 2021-05-16 15:40:58.735 debug (22847) Objects create System PubSub Client zwave2.0 2021-05-16 15:40:58.732 debug (22847) Objects client ready ... initialize now zwave2.0 2021-05-16 15:40:58.696 debug (22847) Redis Objects: Use Redis connection: 127.0.0.1:9001 host.raspberrypi 2021-05-16 15:40:56.599 info instance system.adapter.zwave2.0 started with pid 22847 host.raspberrypi 2021-05-16 15:40:56.462 info "system.adapter.zwave2.0" enabled host.raspberrypi 2021-05-16 15:40:50.698 info instance system.adapter.zwave2.0 terminated with code null () host.raspberrypi 2021-05-16 15:40:50.697 warn instance system.adapter.zwave2.0 terminated due to SIGTERM host.raspberrypi 2021-05-16 15:40:50.626 info stopInstance system.adapter.zwave2.0 killing pid 22283 host.raspberrypi 2021-05-16 15:40:49.624 info stopInstance system.adapter.zwave2.0 send kill signal host.raspberrypi 2021-05-16 15:40:49.613 info stopInstance system.adapter.zwave2.0 (force=false, process=true) host.raspberrypi 2021-05-16 15:40:49.613 info "system.adapter.zwave2.0" disabled host.raspberrypi 2021-05-16 15:40:49.345 info instance system.adapter.zwave2.0 started with pid 22283 host.raspberrypi 2021-05-16 15:40:46.840 info instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zwave2.0 2021-05-16 15:40:46.228 info (15581) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zwave2.0 2021-05-16 15:40:46.226 info (15581) terminating zwave2.0 2021-05-16 15:40:46.225 info (15581) Shutting down driver... zwave2.0 2021-05-16 15:40:46.223 info (15581) Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2021-05-16 15:40:46.223 info stopInstance system.adapter.zwave2.0 send kill signal host.raspberrypi 2021-05-16 15:40:46.210 info stopInstance system.adapter.zwave2.0 (force=false, process=true) zwave2.0 2021-05-16 15:39:28.776 info (15581) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16ls -la /dev/ttyAMA0 sudo -u iobroker groups -
ls -la /dev/ttyAMA0 sudo -u iobroker groups@thomas-braun said in Probleme mit Serialport bei zwave2:
sudo -u iobroker groups
auch nicht
zwave2.0 2021-05-16 15:44:27.972 info (7201) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 host.raspberrypi 2021-05-16 15:44:25.611 info instance system.adapter.zwave2.0 started with pid 7201 host.raspberrypi 2021-05-16 15:44:25.529 info "system.adapter.zwave2.0" enabled host.raspberrypi 2021-05-16 15:44:24.965 info instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zwave2.0 2021-05-16 15:44:24.304 info (30224) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zwave2.0 2021-05-16 15:44:24.302 info (30224) terminating zwave2.0 2021-05-16 15:44:24.301 info (30224) Shutting down driver... host.raspberrypi 2021-05-16 15:44:24.299 info stopInstance system.adapter.zwave2.0 send kill signal zwave2.0 2021-05-16 15:44:24.298 info (30224) Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2021-05-16 15:44:24.285 info stopInstance system.adapter.zwave2.0 (force=false, process=true) host.raspberrypi 2021-05-16 15:44:24.278 info "system.adapter.zwave2.0" disabled zwave2.0 2021-05-16 15:44:11.075 debug (30224) system.adapter.admin.0: logging true zwave2.0 2021-05-16 15:44:06.538 debug (30224) system.adapter.admin.0: logging false -
@thomas-braun said in Probleme mit Serialport bei zwave2:
sudo -u iobroker groups
auch nicht
zwave2.0 2021-05-16 15:44:27.972 info (7201) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 host.raspberrypi 2021-05-16 15:44:25.611 info instance system.adapter.zwave2.0 started with pid 7201 host.raspberrypi 2021-05-16 15:44:25.529 info "system.adapter.zwave2.0" enabled host.raspberrypi 2021-05-16 15:44:24.965 info instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zwave2.0 2021-05-16 15:44:24.304 info (30224) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zwave2.0 2021-05-16 15:44:24.302 info (30224) terminating zwave2.0 2021-05-16 15:44:24.301 info (30224) Shutting down driver... host.raspberrypi 2021-05-16 15:44:24.299 info stopInstance system.adapter.zwave2.0 send kill signal zwave2.0 2021-05-16 15:44:24.298 info (30224) Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2021-05-16 15:44:24.285 info stopInstance system.adapter.zwave2.0 (force=false, process=true) host.raspberrypi 2021-05-16 15:44:24.278 info "system.adapter.zwave2.0" disabled zwave2.0 2021-05-16 15:44:11.075 debug (30224) system.adapter.admin.0: logging true zwave2.0 2021-05-16 15:44:06.538 debug (30224) system.adapter.admin.0: logging false -
@esmax666 Starte den Adapter mal auf der Konsole, da sieht man ggf. mehr:
cd /opt/iobroker/node_modules/iobroker.zwave2 node build/main.js --force --logs@alcalzone said in Probleme mit Serialport bei zwave2:
cd /opt/iobroker/node_modules/iobroker.zwave2
node build/main.js --force --logspi@raspberrypi:~ $ cd /opt/iobroker/node_modules/iobroker.zwave2 pi@raspberrypi:/opt/iobroker/node_modules/iobroker.zwave2 $ node build/main.js --force --logs 2021-05-16 16:43:17.078 - info: zwave2.0 (17697) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 Logging to file: /opt/iobroker/node_modules/iobroker.zwave2/build/zwavejs_2021-05-16.log 2021-05-16 16:43:17.235 - error: zwave2.0 (17697) The Z-Wave driver could not be started: Error Resource temporarily unavailable Cannot lock port ^C2021-05-16 16:43:47.907 - info: zwave2.0 (17697) Shutting down driver... 2021-05-16 16:43:47.916 - info: zwave2.0 (17697) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason pi@raspberrypi:/opt/iobroker/node_modules/iobroker.zwave2 $ -
@alcalzone said in Probleme mit Serialport bei zwave2:
cd /opt/iobroker/node_modules/iobroker.zwave2
node build/main.js --force --logspi@raspberrypi:~ $ cd /opt/iobroker/node_modules/iobroker.zwave2 pi@raspberrypi:/opt/iobroker/node_modules/iobroker.zwave2 $ node build/main.js --force --logs 2021-05-16 16:43:17.078 - info: zwave2.0 (17697) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 Logging to file: /opt/iobroker/node_modules/iobroker.zwave2/build/zwavejs_2021-05-16.log 2021-05-16 16:43:17.235 - error: zwave2.0 (17697) The Z-Wave driver could not be started: Error Resource temporarily unavailable Cannot lock port ^C2021-05-16 16:43:47.907 - info: zwave2.0 (17697) Shutting down driver... 2021-05-16 16:43:47.916 - info: zwave2.0 (17697) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason pi@raspberrypi:/opt/iobroker/node_modules/iobroker.zwave2 $ -
@esmax666 sagte in Probleme mit Serialport bei zwave2:
Cannot lock port
Da greift schon irgendwas anderes auf den Port zu.
sudo lsof /dev/ttyAMA0 -
sudo lsof /dev/ttyAMA0@thomas-braun said in Probleme mit Serialport bei zwave2:
sudo lsof /dev/ttyAMA0
pi@raspberrypi:/opt/iobroker/node_modules/iobroker.zwave2 $ sudo lsof /dev/ttyAMA0 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME hciattach 596 root 3u CHR 204,64 0t0 135 /dev/ttyAMA0 node 25167 iobroker 27uW CHR 204,64 0t0 135 /dev/ttyAMA0dann
pi@raspberrypi:/opt/iobroker/node_modules/iobroker.zwave2 $ cd /opt/iobroker/node_modules/iobroker.zwave2 pi@raspberrypi:/opt/iobroker/node_modules/iobroker.zwave2 $ node build/main.js --force --logs 2021-05-16 17:01:01.719 - info: zwave2.0 (5111) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 Logging to file: /opt/iobroker/node_modules/iobroker.zwave2/build/zwavejs_2021-05-16.log 2021-05-16 17:01:01.877 - error: zwave2.0 (5111) The Z-Wave driver could not be started: Error Resource temporarily unavailable Cannot lock port ^C2021-05-16 17:01:47.959 - info: zwave2.0 (5111) Shutting down driver... 2021-05-16 17:01:47.968 - info: zwave2.0 (5111) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason@AlCalzone
wie soll ich port freischalten ? die installation ist neu -
@thomas-braun said in Probleme mit Serialport bei zwave2:
sudo lsof /dev/ttyAMA0
pi@raspberrypi:/opt/iobroker/node_modules/iobroker.zwave2 $ sudo lsof /dev/ttyAMA0 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME hciattach 596 root 3u CHR 204,64 0t0 135 /dev/ttyAMA0 node 25167 iobroker 27uW CHR 204,64 0t0 135 /dev/ttyAMA0dann
pi@raspberrypi:/opt/iobroker/node_modules/iobroker.zwave2 $ cd /opt/iobroker/node_modules/iobroker.zwave2 pi@raspberrypi:/opt/iobroker/node_modules/iobroker.zwave2 $ node build/main.js --force --logs 2021-05-16 17:01:01.719 - info: zwave2.0 (5111) starting. Version 1.9.3 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.22.1, js-controller: 3.2.16 Logging to file: /opt/iobroker/node_modules/iobroker.zwave2/build/zwavejs_2021-05-16.log 2021-05-16 17:01:01.877 - error: zwave2.0 (5111) The Z-Wave driver could not be started: Error Resource temporarily unavailable Cannot lock port ^C2021-05-16 17:01:47.959 - info: zwave2.0 (5111) Shutting down driver... 2021-05-16 17:01:47.968 - info: zwave2.0 (5111) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason@AlCalzone
wie soll ich port freischalten ? die installation ist neu@esmax666 sagte in Probleme mit Serialport bei zwave2:
hciattach 596 root 3u CHR 204,64 0t0 135 /dev/ttyAMA0
Da greift bluetooth schon auf das Gerät zu. Merkwürden...
Ich bin jetzt nicht ganz sicher ob /dev/tttyAMA0 nicht doch das falsche Device ist. Oder da die Zuordnung falsch ist. Zieh den stick mal raus, starte neu ohne den Stick und dann schau nochmal nachdmesg -Tkurz nachdem du den stick eingesteckt hast.
-
@esmax666 sagte in Probleme mit Serialport bei zwave2:
hciattach 596 root 3u CHR 204,64 0t0 135 /dev/ttyAMA0
Da greift bluetooth schon auf das Gerät zu. Merkwürden...
Ich bin jetzt nicht ganz sicher ob /dev/tttyAMA0 nicht doch das falsche Device ist. Oder da die Zuordnung falsch ist. Zieh den stick mal raus, starte neu ohne den Stick und dann schau nochmal nachdmesg -Tkurz nachdem du den stick eingesteckt hast.
-
@thomas-braun was soll ich dann machen ?
@esmax666 Und deaktiviere den zwave2-Adapter vorerst mal für die ganze Prozedur.
Support us
707
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge