NEWS
Zwave läuft nicht iobroker als Raspberrymatic addon
-
@rhartmann76 Und in der Admin konfiguration hast Du danach den Port eingetragen und gespeichert?
@apollon77 @Thomas-Braun sorry, wo muss man dies einstellen?
Also in dem Z-wave Adapter habe ich in der Konfiguration /dev/ttyAMA0 eingetragen und einen Code generieren lassen.
Sonst habe ich nichts geändert.2021-03-19 09:57:17.081 - info: host.raspberrypi "system.adapter.zwave2.0" disabled 2021-03-19 09:57:17.089 - info: host.raspberrypi stopInstance system.adapter.zwave2.0 (force=false, process=true) 2021-03-19 09:57:17.113 - info: host.raspberrypi stopInstance system.adapter.zwave2.0 send kill signal 2021-03-19 09:57:17.114 - info: zwave2.0 (1886) Got terminate signal TERMINATE_YOURSELF 2021-03-19 09:57:17.136 - info: zwave2.0 (1886) Shutting down driver... 2021-03-19 09:57:17.148 - info: zwave2.0 (1886) terminating 2021-03-19 09:57:17.154 - info: zwave2.0 (1886) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2021-03-19 09:57:17.919 - info: host.raspberrypi instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2021-03-19 09:57:20.103 - info: host.raspberrypi "system.adapter.zwave2.0" enabled 2021-03-19 09:57:20.250 - info: host.raspberrypi instance system.adapter.zwave2.0 started with pid 1916 2021-03-19 09:57:27.107 - info: zwave2.0 (1916) starting. Version 1.8.11 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.21.0, js-controller: 3.2.16 -
@apollon77 @Thomas-Braun sorry, wo muss man dies einstellen?
Also in dem Z-wave Adapter habe ich in der Konfiguration /dev/ttyAMA0 eingetragen und einen Code generieren lassen.
Sonst habe ich nichts geändert.2021-03-19 09:57:17.081 - info: host.raspberrypi "system.adapter.zwave2.0" disabled 2021-03-19 09:57:17.089 - info: host.raspberrypi stopInstance system.adapter.zwave2.0 (force=false, process=true) 2021-03-19 09:57:17.113 - info: host.raspberrypi stopInstance system.adapter.zwave2.0 send kill signal 2021-03-19 09:57:17.114 - info: zwave2.0 (1886) Got terminate signal TERMINATE_YOURSELF 2021-03-19 09:57:17.136 - info: zwave2.0 (1886) Shutting down driver... 2021-03-19 09:57:17.148 - info: zwave2.0 (1886) terminating 2021-03-19 09:57:17.154 - info: zwave2.0 (1886) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2021-03-19 09:57:17.919 - info: host.raspberrypi instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2021-03-19 09:57:20.103 - info: host.raspberrypi "system.adapter.zwave2.0" enabled 2021-03-19 09:57:20.250 - info: host.raspberrypi instance system.adapter.zwave2.0 started with pid 1916 2021-03-19 09:57:27.107 - info: zwave2.0 (1916) starting. Version 1.8.11 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.21.0, js-controller: 3.2.16sudo timedatectl set-timezone Europe/Berlin -
sudo timedatectl set-timezone Europe/Berlin2021-03-19 09:57:17.081 - info: host.raspberrypi "system.adapter.zwave2.0" disabled 2021-03-19 09:57:17.089 - info: host.raspberrypi stopInstance system.adapter.zwave2.0 (force=false, process=true) 2021-03-19 09:57:17.113 - info: host.raspberrypi stopInstance system.adapter.zwave2.0 send kill signal 2021-03-19 09:57:17.114 - info: zwave2.0 (1886) Got terminate signal TERMINATE_YOURSELF 2021-03-19 09:57:17.136 - info: zwave2.0 (1886) Shutting down driver... 2021-03-19 09:57:17.148 - info: zwave2.0 (1886) terminating 2021-03-19 09:57:17.154 - info: zwave2.0 (1886) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2021-03-19 09:57:17.919 - info: host.raspberrypi instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2021-03-19 09:57:20.103 - info: host.raspberrypi "system.adapter.zwave2.0" enabled 2021-03-19 09:57:20.250 - info: host.raspberrypi instance system.adapter.zwave2.0 started with pid 1916 2021-03-19 09:57:27.107 - info: zwave2.0 (1916) starting. Version 1.8.11 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.21.0, js-controller: 3.2.16 2021-03-19 10:06:24.385 - error: host.raspberrypi Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 2021-03-19 10:06:24.388 - warn: host.raspberrypi instance system.adapter.zwave2.0 terminated due to SIGABRT 2021-03-19 10:06:24.390 - info: host.raspberrypi instance system.adapter.zwave2.0 terminated with code NaN () 2021-03-19 10:06:24.391 - info: host.raspberrypi Restart adapter system.adapter.zwave2.0 because enabled 2021-03-19 10:06:54.436 - info: host.raspberrypi instance system.adapter.zwave2.0 started with pid 1949 2021-03-19 10:07:01.114 - info: zwave2.0 (1949) starting. Version 1.8.11 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.21.0, js-controller: 3.2.16 2021-03-19 10:09:45.749 - info: host.raspberrypi "system.adapter.zwave2.0" disabled 2021-03-19 10:09:45.758 - info: host.raspberrypi stopInstance system.adapter.zwave2.0 (force=false, process=true) 2021-03-19 10:09:45.791 - info: host.raspberrypi stopInstance system.adapter.zwave2.0 send kill signal 2021-03-19 10:09:45.796 - info: zwave2.0 (1949) Got terminate signal TERMINATE_YOURSELF 2021-03-19 10:09:45.818 - info: zwave2.0 (1949) Shutting down driver... 2021-03-19 10:09:45.823 - info: zwave2.0 (1949) terminating 2021-03-19 10:09:45.827 - info: zwave2.0 (1949) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2021-03-19 10:09:46.556 - info: host.raspberrypi instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2021-03-19 10:09:47.825 - info: host.raspberrypi "system.adapter.zwave2.0" enabled 2021-03-19 10:09:47.963 - info: host.raspberrypi instance system.adapter.zwave2.0 started with pid 2012 2021-03-19 11:09:54.749 - info: zwave2.0 (2012) starting. Version 1.8.11 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.21.0, js-controller: 3.2.16 -
2021-03-19 09:57:17.081 - info: host.raspberrypi "system.adapter.zwave2.0" disabled 2021-03-19 09:57:17.089 - info: host.raspberrypi stopInstance system.adapter.zwave2.0 (force=false, process=true) 2021-03-19 09:57:17.113 - info: host.raspberrypi stopInstance system.adapter.zwave2.0 send kill signal 2021-03-19 09:57:17.114 - info: zwave2.0 (1886) Got terminate signal TERMINATE_YOURSELF 2021-03-19 09:57:17.136 - info: zwave2.0 (1886) Shutting down driver... 2021-03-19 09:57:17.148 - info: zwave2.0 (1886) terminating 2021-03-19 09:57:17.154 - info: zwave2.0 (1886) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2021-03-19 09:57:17.919 - info: host.raspberrypi instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2021-03-19 09:57:20.103 - info: host.raspberrypi "system.adapter.zwave2.0" enabled 2021-03-19 09:57:20.250 - info: host.raspberrypi instance system.adapter.zwave2.0 started with pid 1916 2021-03-19 09:57:27.107 - info: zwave2.0 (1916) starting. Version 1.8.11 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.21.0, js-controller: 3.2.16 2021-03-19 10:06:24.385 - error: host.raspberrypi Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 2021-03-19 10:06:24.388 - warn: host.raspberrypi instance system.adapter.zwave2.0 terminated due to SIGABRT 2021-03-19 10:06:24.390 - info: host.raspberrypi instance system.adapter.zwave2.0 terminated with code NaN () 2021-03-19 10:06:24.391 - info: host.raspberrypi Restart adapter system.adapter.zwave2.0 because enabled 2021-03-19 10:06:54.436 - info: host.raspberrypi instance system.adapter.zwave2.0 started with pid 1949 2021-03-19 10:07:01.114 - info: zwave2.0 (1949) starting. Version 1.8.11 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.21.0, js-controller: 3.2.16 2021-03-19 10:09:45.749 - info: host.raspberrypi "system.adapter.zwave2.0" disabled 2021-03-19 10:09:45.758 - info: host.raspberrypi stopInstance system.adapter.zwave2.0 (force=false, process=true) 2021-03-19 10:09:45.791 - info: host.raspberrypi stopInstance system.adapter.zwave2.0 send kill signal 2021-03-19 10:09:45.796 - info: zwave2.0 (1949) Got terminate signal TERMINATE_YOURSELF 2021-03-19 10:09:45.818 - info: zwave2.0 (1949) Shutting down driver... 2021-03-19 10:09:45.823 - info: zwave2.0 (1949) terminating 2021-03-19 10:09:45.827 - info: zwave2.0 (1949) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2021-03-19 10:09:46.556 - info: host.raspberrypi instance system.adapter.zwave2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2021-03-19 10:09:47.825 - info: host.raspberrypi "system.adapter.zwave2.0" enabled 2021-03-19 10:09:47.963 - info: host.raspberrypi instance system.adapter.zwave2.0 started with pid 2012 2021-03-19 11:09:54.749 - info: zwave2.0 (2012) starting. Version 1.8.11 in /opt/iobroker/node_modules/iobroker.zwave2, node: v12.21.0, js-controller: 3.2.16@rhartmann76 sagte in Zwave läuft nicht iobroker als Raspberrymatic addon:
error: host.raspberrypi Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
free -hsagt?
-
@rhartmann76 sagte in Zwave läuft nicht iobroker als Raspberrymatic addon:
error: host.raspberrypi Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
free -hsagt?
@thomas-braun said in Zwave läuft nicht iobroker als Raspberrymatic addon:
free -h
pi@raspberrypi:~ $ free -h total used free shared buff/cache available Mem: 924Mi 330Mi 445Mi 6.0Mi 148Mi 562Mi Swap: 99Mi 0B 99Mi -
@thomas-braun said in Zwave läuft nicht iobroker als Raspberrymatic addon:
free -h
pi@raspberrypi:~ $ free -h total used free shared buff/cache available Mem: 924Mi 330Mi 445Mi 6.0Mi 148Mi 562Mi Swap: 99Mi 0B 99Mi@rhartmann76
Gut, da ist eigentlich nicht viel los.
Keine Ahnung warum da auf dem Heap der Speicher ausgeht.Und auf dem Master schaut das wie aus?
-
@rhartmann76
Gut, da ist eigentlich nicht viel los.
Keine Ahnung warum da auf dem Heap der Speicher ausgeht.Und auf dem Master schaut das wie aus?
@thomas-braun das ist der Master - ich habe auf dem Pi3, wo das zwave Modul steckt, nun den Master eingerichtet.
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden