ZWAVE2 adapter will nicht grün werden
-
Ich habe jetzt lange rumprobiert. Leider keine Lösung gefunden.
System:
Raspberry Pi 3b Rev. 1.3
Zigbee Stick an USB (Adapter läuft)
Razberry2 an GPIO (Adapter will nicht laden, egal welcher)Hab zuletzt zwave2 probiert. Die Fehlermeldung die ich aktuell erhalte ist:
Failed to initialize the driver, no response from the controller. Are you sure this is a Z-Wave controller?Als Schnittstelle habe ich /dev/ttyAMA0 gewählt. Der Adapter bleibt gelb.
Ich komme einfach nicht weiter.Gruß
Roman -
@LukyLuke
Das logfile sagt? -
host.ioBroker-Pi 2020-10-09 15:39:22.507 info Update repository "default" under "http://download.iobroker.net/sources-dist.json" zwave2.0 2020-10-09 15:38:22.015 error (11769) Failed to initialize the driver, no response from the controller. Are you sure this is a Z-Wave controller? zwave2.0 2020-10-09 15:38:13.102 info (11769) starting. Version 1.5.0 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.19.0, js-controller: 3.1.6 host.ioBroker-Pi 2020-10-09 15:38:09.324 info instance system.adapter.zwave2.0 started with pid 11769 host.ioBroker-Pi 2020-10-09 15:38:09.259 info "system.adapter.zwave2.0" enabled host.ioBroker-Pi 2020-10-09 15:37:54.616 info instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zwave2.0 2020-10-09 15:37:54.082 info (21152) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zwave2.0 2020-10-09 15:37:54.080 info (21152) terminating zwave2.0 2020-10-09 15:37:54.077 info (21152) Cleaned everything up! zwave2.0 2020-10-09 15:37:54.076 info (21152) Resetting node status... zwave2.0 2020-10-09 15:37:54.073 info (21152) Shutting down driver... zwave2.0 2020-10-09 15:37:54.069 info (21152) Got terminate signal TERMINATE_YOURSELF host.ioBroker-Pi 2020-10-09 15:37:54.061 info stopInstance system.adapter.zwave2.0 send kill signal host.ioBroker-Pi 2020-10-09 15:37:54.056 info stopInstance system.adapter.zwave2.0 (force=false, process=true) host.ioBroker-Pi 2020-10-09 15:37:54.044 info "system.adapter.zwave2.0" disabled cloud.0 2020-10-09 15:17:24.026 info (20297) Connection changed: connect cloud.0 2020-10-09 15:17:23.926 info (20297) Trying to connect as system.user.admin zwave2.0 2020-10-09 15:17:00.285 error (21152) Failed to initialize the driver, no response from the controller. Are you sure this is a Z-Wave controller? zwave2.0 2020-10-09 15:16:51.350 info (21152) starting. Version 1.5.0 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.19.0, js-controller: 3.1.6 -
@LukyLuke
Bitte Konsolentext auch in CodeTags setzen. Danke. -
@Thomas-Braun
ich wills versuchen, bin aber noch Anfänger ....
hier der zwave2 log:15:38:13.230 DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗ ╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝ ███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗ ███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║ ███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║ ╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝ 15:38:13.236 DRIVER version 4.2.3 15:38:13.237 DRIVER 15:38:13.238 DRIVER starting driver... 15:38:13.238 DRIVER opening serial port /dev/ttyAMA0 15:38:13.351 DRIVER serial port opened 15:38:13.356 SERIAL » [NAK] (0x15) 15:38:14.859 DRIVER loading configuration... 15:38:15.981 DRIVER beginning interview... 15:38:15.984 DRIVER added request handler for AddNodeToNetwork (0x4a)... 1 registered 15:38:15.985 DRIVER added request handler for RemoveNodeFromNetwork (0x4b)... 1 registered 15:38:15.989 CNTRLR beginning interview... 15:38:15.990 CNTRLR querying version info... 15:38:16.000 DRIVER » [REQ] [GetControllerVersion] [P: Controller] 15:38:16.003 SERIAL » 0x01030015e9 (5 bytes) 15:38:17.606 DRIVER Timeout occured waiting for ACK - scheduling transmission attempt (2/3) in 100 ms... 15:38:17.706 DRIVER » [REQ] [GetControllerVersion] [attempt 2/3] 15:38:17.707 SERIAL » 0x01030015e9 (5 bytes) 15:38:19.308 DRIVER Timeout occured waiting for ACK - scheduling transmission attempt (3/3) in 110 0 ms... 15:38:20.408 DRIVER » [REQ] [GetControllerVersion] [attempt 3/3] 15:38:20.410 SERIAL » 0x01030015e9 (5 bytes) 15:38:22.011 DRIVER Timeout occured waiting for ACK received - maximum transmission attempts for t he current transaction reached, dropping it... 15:38:22.013 DRIVER Failed to initialize the driver, no response from the controller. Are you sure this is a Z-Wave controller? 15:38:22.017 DRIVER destroying driver instance...und hier nochmal ausm iobroker:
zwave2.0 2020-10-09 15:38:22.015 error (11769) Failed to initialize the driver, no response from the controller. Are you sure this is a Z-Wave controller? zwave2.0 2020-10-09 15:38:13.102 info (11769) starting. Version 1.5.0 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.19.0, js-controller: 3.1.6 host.ioBroker-Pi 2020-10-09 15:38:09.324 info instance system.adapter.zwave2.0 started with pid 11769 host.ioBroker-Pi 2020-10-09 15:38:09.259 info "system.adapter.zwave2.0" enabled host.ioBroker-Pi 2020-10-09 15:37:54.616 info instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zwave2.0 2020-10-09 15:37:54.082 info (21152) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zwave2.0 2020-10-09 15:37:54.080 info (21152) terminating zwave2.0 2020-10-09 15:37:54.077 info (21152) Cleaned everything up! zwave2.0 2020-10-09 15:37:54.076 info (21152) Resetting node status... zwave2.0 2020-10-09 15:37:54.073 info (21152) Shutting down driver... zwave2.0 2020-10-09 15:37:54.069 info (21152) Got terminate signal TERMINATE_YOURSELF host.ioBroker-Pi 2020-10-09 15:37:54.061 info stopInstance system.adapter.zwave2.0 send kill signal host.ioBroker-Pi 2020-10-09 15:37:54.056 info stopInstance system.adapter.zwave2.0 (force=false, process=true) host.ioBroker-Pi 2020-10-09 15:37:54.044 info "system.adapter.zwave2.0" disabled cloud.0 2020-10-09 15:17:24.026 info (20297) Connection changed: connect cloud.0 2020-10-09 15:17:23.926 info (20297) Trying to connect as system.user.adminDanke
-
@LukyLuke was für js-controller hast du da ???
und nimm mal die 1.7.4 vom GIT des zwave2
-
ioBroker-Pi Typ: js-controller Titel: JS controller OS: linux Verfügbar: 3.1.6 Installiert: 3.1.6 Ereignisse: ↦16 / ↦13ich versuchs nachher mal
-
War wohl die Version 1.5.0
Habe jetzt über die Katze die v1.7.4 installiert. Hier der Log:zwave2.0 2020-10-09 19:17:10.678 error (1566) The Z-Wave driver could not be started: Error: Permission denied, cannot open /dev/ttyAMA0 zwave2.0 2020-10-09 19:17:10.285 info (1566) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.19.0, js-controller: 3.1.6und
19:15:33.894 DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗ ╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝ ███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗ ███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║ ███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║ ╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝ 19:15:33.900 DRIVER version 5.2.2 19:15:33.901 DRIVER 19:15:33.902 DRIVER starting driver... 19:15:33.949 DRIVER opening serial port /dev/ttyAMA0 19:15:34.042 DRIVER serial port opened 19:15:34.048 SERIAL » [NAK] (0x15) 19:15:35.557 DRIVER loading configuration... 19:15:36.848 DRIVER beginning interview... 19:15:36.851 DRIVER added request handler for AddNodeToNetwork (0x4a)... 1 registered 19:15:36.852 DRIVER added request handler for RemoveNodeFromNetwork (0x4b)... 1 registered 19:15:36.856 CNTRLR beginning interview... 19:15:36.857 CNTRLR querying version info... 19:15:36.890 SERIAL » 0x01030015e9 (5 bytes) 19:15:36.893 DRIVER » [REQ] [GetControllerVersion] 19:15:37.904 CNTRLR No response from controller after 1/3 attempts. Scheduling next try in 100 ms. 19:15:38.008 SERIAL » 0x01030015e9 (5 bytes) 19:15:38.009 DRIVER » [REQ] [GetControllerVersion] 19:15:39.014 CNTRLR No response from controller after 2/3 attempts. Scheduling next try in 1100 ms . 19:15:39.565 DRIVER destroying driver instance...immer noch gelb
-
@LukyLuke Da stimmt was mit den Rechten nicht:
zwave2.0 2020-10-09 19:17:10.678 error (1566) The Z-Wave driver could not be started: Error: Permission denied, cannot open /dev/ttyAMA0 -
pi@ioBroker-Pi:~ $ ls -l /dev/ttyA* crw-rw---- 1 root dialout 166, 0 Okt 9 19:32 /dev/ttyACM0 crw--w---- 1 root tty 204, 64 Okt 9 19:15 /dev/ttyAMA0ich vermute in Zeile 3 müsste auch rw rein. Hatte ich manuell geändert. Dann kam:
Failed to initialize the driver, no response from the controller. Are you sure this is a Z-Wave controller? -
@LukyLuke An der Stelle macht man nix manuell.
Was hast du denn da nun genau gemacht?In welchen Gruppen ist der iobroker drin?
sudo -u iobroker groups -
pi@ioBroker-Pi:~ $ sudo -u iobroker groups iobroker tty dialout audio video bluetooth gpio i2c -
@LukyLuke Das passt. Und was hast du in /dev manuell rumgefrickelt?
Schalt mal die anderen Funkdinger aus. Blutooth, Zigbee usw.
-
@Thomas-Braun
nein, ich denke nicht. Lediglich:
sudo chmod g+r /dev/ttyAMA0Den iobroker fixer habe ich auch drüber laufen lassen .... nix
-
@Thomas-Braun said in ZWAVE2 adapter will nicht grün werden:
Blutooth
Zigbee ist aus. Wie bekomme ich Bluetooth ausgeschaltet?
-
-
@Thomas-Braun
so sieht meine config.txt aus:dtoverlay=pi3-disable-bt dtoverlay=pi3-miniuart-bt enable_uart=1 force_turbo=1leider immer noch der selbe Fehler
-
@LukyLuke Keine Ahnung
-
@Thomas-Braun
ich bin etwas weiter. Ich habe die Platine auf einem PiZeroW mit zway image getestet. Auch hier war keine Verbindung möglich. Erst auf einem Pi2 lief es auf anhieb. Der hat kein Wlan und kein Bluetooth.
Ich denke irgendwo gibts ein Problem mit der WLAN und BT Hardware. Die ist irgendwie so im System verbunden, das der Razberry (GPIO) ausgesperrt bleibt. Leider bin ich hier totaler Laie.
