NEWS
Z-Wave Adapter
-
Hallo,
kannst du mal auf deinem Rechner nach dieser Datei suchen? libopenzwave.so.1.4
Sollte normalerweise in "/usr/local/lib/libopenzwave.so.1.4" zu finden sein.
Ausserdem müsste "/usr/local/lib/pkgconfig/libopenzwave.pc" vorhanden sein.
Probier sonst mal ein "ldconfig", dann müsste dein LD_LIBRARY_PATH neu gesetzt werden.
Bzw. "ldconfig -p|grep zwave"
Dann siehst du wo im Cache die Datei sein sollte.
-
Hallo,
kannst du mal auf deinem Rechner nach dieser Datei suchen? libopenzwave.so.1.4
Sollte normalerweise in "/usr/local/lib/libopenzwave.so.1.4" zu finden sein.
Ausserdem müsste "/usr/local/lib/pkgconfig/libopenzwave.pc" vorhanden sein.
Probier sonst mal ein "ldconfig", dann müsste dein LD_LIBRARY_PATH neu gesetzt werden.
Bzw. "ldconfig -p|grep zwave"
Dann siehst du wo im Cache die Datei sein sollte. `
Sollte normalerweise in "/usr/local/lib/libopenzwave.so.1.4" zu finden sein. ````ist da wo sie sein sollAusserdem müsste "/usr/local/lib/pkgconfig/libopenzwave.pc" vorhanden sein.
so, "lldconfig -p|grep zwave" ist gemacht… schaut trotzdem komisch aus... LOG:iobroker 2016-03-25 18:15:36 info host.iobroker Restart adapter system.adapter.zwave.0 because enabled
iobroker 2016-03-25 18:15:36 error host.iobroker instance system.adapter.zwave.0 terminated with code 6 (uncaught exception)
zwave.0 2016-03-25 18:15:34 error TypeError: setValue: OpenZWave valueId not found at TypeError (native) at Socket. (/opt/iobroker/node_modules/iobroker.zwave/main.js:518:51) at Socket.onack (/opt/iobroker/node_
zwave.0 2016-03-25 18:15:34 error uncaught exception: setValue: OpenZWave valueId not found
zwave.0 2016-03-25 18:15:34 info zwave.0 setState for: nodeid=undefined: comclass=undefined: index=undefined: instance=undefined: value=true
zwave.0 2016-03-25 18:15:34 warn zwave.0 Object 'zwave.0.NODE9.ready' not found for stateChange
zwave.0 2016-03-25 18:15:34 warn zwave.0 Object 'zwave.0.NODE8.ready' not found for stateChange
zwave.0 2016-03-25 18:15:34 warn zwave.0 Object 'zwave.0.NODE7.ready' not found for stateChange
zwave.0 2016-03-25 18:15:34 warn zwave.0 Object 'zwave.0.NODE6.ready' not found for stateChange
zwave.0 2016-03-25 18:15:34 warn zwave.0 Object 'zwave.0.NODE5.ready' not found for stateChange
zwave.0 2016-03-25 18:15:34 warn zwave.0 Object 'zwave.0.NODE4.ready' not found for stateChange
zwave.0 2016-03-25 18:15:33 info zwave.0 Scan completed
zwave.0 2016-03-25 18:15:33 info zwave.0 node ready nodeid:9 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0301","productid":"0x1001","type":"Motor
zwave.0 2016-03-25 18:15:33 info zwave.0 node ready nodeid:8 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor
zwave.0 2016-03-25 18:15:33 info zwave.0 node ready nodeid:7 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor
zwave.0 2016-03-25 18:15:33 info zwave.0 node ready nodeid:6 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0301","productid":"0x1001","type":"Motor
zwave.0 2016-03-25 18:15:33 info zwave.0 node ready nodeid:5 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGWPE Wall Plug","producttype":"0x0600","productid":"0x1000","type":"Binary Switch","name":"",
zwave.0 2016-03-25 18:15:33 info zwave.0 node ready nodeid:4 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor
zwave.0 2016-03-25 18:15:29 info zwave.0 node ready nodeid:1 nodeinfo:{"manufacturer":"Aeotec","manufacturerid":"0x0086","product":"Z-Stick Gen5","producttype":"0x0001","productid":"0x005a","type":"Static PC Controller","name":"","lo
zwave.0 2016-03-25 18:15:22 info zwave.0 node9: nop, currently not implemented
zwave.0 2016-03-25 18:15:22 info zwave.0 node8: nop, currently not implemented
zwave.0 2016-03-25 18:15:22 info zwave.0 node7: nop, currently not implemented
zwave.0 2016-03-25 18:15:22 info zwave.0 node6: nop, currently not implemented
zwave.0 2016-03-25 18:15:22 info zwave.0 node5: nop, currently not implemented
zwave.0 2016-03-25 18:15:22 info zwave.0 node4: nop, currently not implemented
zwave.0 2016-03-25 18:15:22 info zwave.0 nodeid 9 is now available, but maybe not ready
zwave.0 2016-03-25 18:15:22 info zwave.0 nodeid 8 is now available, but maybe not ready
zwave.0 2016-03-25 18:15:22 info zwave.0 nodeid 7 is now available, but maybe not ready
zwave.0 2016-03-25 18:15:22 info zwave.0 nodeid 6 is now available, but maybe not ready
zwave.0 2016-03-25 18:15:22 info zwave.0 nodeid 5 is now available, but maybe not ready
zwave.0 2016-03-25 18:15:22 info zwave.0 nodeid 4 is now available, but maybe not ready
zwave.0 2016-03-25 18:15:21 info zwave.0 nodeid 1 is now available, but maybe not ready
zwave.0 2016-03-25 18:15:21 info zwave.0 driver ready: homeid = f331c5f6
zwave.0 2016-03-25 18:15:21 info zwave.0 scanning homeid=0xf331c5f6...
zwave.0 2016-03-25 18:15:21 info zwave.0 connected: homeid = 1.4.0
zwave.0 2016-03-25 18:15:19 info zwave.0 starting. Version 0.2.9 in /opt/iobroker/node_modules/iobroker.zwave
iobroker 2016-03-25 18:15:16 info host.iobroker instance system.adapter.zwave.0 started with pid 4874
iobroker 2016-03-25 18:14:45 info host.iobroker Restart adapter system.adapter.zwave.0 because enabled
iobroker 2016-03-25 18:14:45 error host.iobroker instance system.adapter.zwave.0 terminated with code 6 (uncaught exception)
zwave.0 2016-03-25 18:14:43 error TypeError: setValue: OpenZWave valueId not found at TypeError (native) at Socket. (/opt/iobroker/node_modules/iobroker.zwave/main.js:518:51) at Socket.onack (/opt/iobroker/node_
zwave.0 2016-03-25 18:14:43 error uncaught exception: setValue: OpenZWave valueId not found
zwave.0 2016-03-25 18:14:43 info zwave.0 setState for: nodeid=undefined: comclass=undefined: index=undefined: instance=undefined: value=true
zwave.0 2016-03-25 18:14:43 warn zwave.0 Object 'zwave.0.NODE9.ready' not found for stateChange
zwave.0 2016-03-25 18:14:43 warn zwave.0 Object 'zwave.0.NODE8.ready' not found for stateChange
zwave.0 2016-03-25 18:14:43 warn zwave.0 Object 'zwave.0.NODE7.ready' not found for stateChange
zwave.0 2016-03-25 18:14:43 warn zwave.0 Object 'zwave.0.NODE6.ready' not found for stateChange
zwave.0 2016-03-25 18:14:43 warn zwave.0 Object 'zwave.0.NODE5.ready' not found for stateChange
zwave.0 2016-03-25 18:14:43 warn zwave.0 Object 'zwave.0.NODE4.ready' not found for stateChange
zwave.0 2016-03-25 18:14:42 info zwave.0 Scan completed
zwave.0 2016-03-25 18:14:42 info zwave.0 node ready nodeid:9 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0301","productid":"0x1001","type":"Motor
zwave.0 2016-03-25 18:14:42 info zwave.0 node ready nodeid:8 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor
zwave.0 2016-03-25 18:14:42 info zwave.0 node ready nodeid:7 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor
zwave.0 2016-03-25 18:14:42 info zwave.0 node ready nodeid:6 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0301","productid":"0x1001","type":"Motor
zwave.0 2016-03-25 18:14:42 info zwave.0 node ready nodeid:5 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGWPE Wall Plug","producttype":"0x0600","productid":"0x1000","type":"Binary Switch","name":"",
zwave.0 2016-03-25 18:14:42 info zwave.0 node ready nodeid:4 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor
zwave.0 2016-03-25 18:14:40 info zwave.0 node9: timeout, currently not implemented
zwave-0 2016-03-25 18:14:28 info node9: timeout, currently not implemented
zwave-0 2016-03-25 18:14:18 info node9: timeout, currently not implemented
zwave-0 2016-03-25 18:14:08 info node ready nodeid:1 nodeinfo:{"manufacturer":"Aeotec","manufacturerid":"0x0086","product":"Z-Stick Gen5","producttype":"0x0001","productid":"0x005a","type":"Static PC Controller","name":"","loc":""}
zwave-0 2016-03-25 18:14:02 info node9: nop, currently not implemented
zwave-0 2016-03-25 18:14:02 info node8: nop, currently not implemented
zwave-0 2016-03-25 18:14:02 info node7: nop, currently not implemented
zwave-0 2016-03-25 18:14:02 info node6: nop, currently not implemented
zwave-0 2016-03-25 18:14:02 info node5: nop, currently not implemented
zwave-0 2016-03-25 18:14:02 info node4: nop, currently not implemented
zwave-0 2016-03-25 18:14:02 info nodeid 9 is now available, but maybe not ready
zwave-0 2016-03-25 18:14:02 info nodeid 8 is now available, but maybe not ready
zwave-0 2016-03-25 18:14:01 info nodeid 7 is now available, but maybe not ready
zwave-0 2016-03-25 18:14:01 info nodeid 6 is now available, but maybe not ready
zwave-0 2016-03-25 18:14:01 info nodeid 5 is now available, but maybe not ready
zwave-0 2016-03-25 18:14:01 info nodeid 4 is now available, but maybe not ready
zwave-0 2016-03-25 18:14:01 info nodeid 1 is now available, but maybe not ready
zwave-0 2016-03-25 18:14:01 info driver ready: homeid = f331c5f6
zwave-0 2016-03-25 18:14:01 info scanning homeid=0xf331c5f6...
zwave-0 2016-03-25 18:14:00 info connected: homeid = 1.4.0
zwave-0 2016-03-25 18:13:59 info starting. Version 0.2.9 in /opt/iobroker/node_modules/iobroker.zwave
host-iobroker 2016-03-25 18:13:55 info instance system.adapter.zwave.0 started with pid 4863
host-iobroker 2016-03-25 18:13:25 info Restart adapter system.adapter.zwave.0 because enabled
host-iobroker 2016-03-25 18:13:25 error instance system.adapter.zwave.0 terminated with code 6 (uncaught exception)
TypeError: 2016-03-25 18:13:23 error at Decoder.add (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/socket.io-parser/index.js:247:12)
TypeError: 2016-03-25 18:13:23 error at Decoder.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/socket.io-parser/node_modules/component-emitter/index.js:134:20)
TypeError: 2016-03-25 18:13:23 error at Decoder. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15)
TypeError: 2016-03-25 18:13:23 error at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:333:8)
TypeError: 2016-03-25 18:13:23 error at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-emitter/index.js:131:20)
TypeError: 2016-03-25 18:13:23 error at Manager. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15)
TypeError: 2016-03-25 18:13:23 error at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:229:12)
TypeError: 2016-03-25 18:13:23 error at Socket.onack (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:305:9)
TypeError: 2016-03-25 18:13:23 error at Socket. (/opt/iobroker/node_modules/iobroker.zwave/main.js:518:51)
TypeError: 2016-03-25 18:13:23 error at TypeError (native)
TypeError: 2016-03-25 18:13:23 error setValue: OpenZWave valueId not found
uncaught 2016-03-25 18:13:23 error exception: setValue: OpenZWave valueId not found
zwave-0 2016-03-25 18:13:23 info setState for: nodeid=undefined: comclass=undefined: index=undefined: instance=undefined: value=true
zwave-0 2016-03-25 18:13:23 warn Object 'zwave.0.NODE9.ready' not found for stateChange
zwave-0 2016-03-25 18:13:23 warn Object 'zwave.0.NODE8.ready' not found for stateChange
zwave-0 2016-03-25 18:13:23 warn Object 'zwave.0.NODE7.ready' not found for stateChange
zwave-0 2016-03-25 18:13:23 warn Object 'zwave.0.NODE6.ready' not found for stateChange
zwave-0 2016-03-25 18:13:23 warn Object 'zwave.0.NODE5.ready' not found for stateChange
zwave-0 2016-03-25 18:13:23 warn Object 'zwave.0.NODE4.ready' not found for stateChange
zwave-0 2016-03-25 18:13:22 info Scan completed
zwave-0 2016-03-25 18:13:22 info node ready nodeid:9 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0301","productid":"0x1001","type":"Motor Contro
zwave-0 2016-03-25 18:13:22 info node ready nodeid:8 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor Contro
zwave-0 2016-03-25 18:13:22 info node ready nodeid:7 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor Contro
zwave-0 2016-03-25 18:13:22 info node ready nodeid:6 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0301","productid":"0x1001","type":"Motor Contro
zwave-0 2016-03-25 18:13:22 info node ready nodeid:5 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGWPE Wall Plug","producttype":"0x0600","productid":"0x1000","type":"Binary Switch","name":"","loc":"
zwave-0 2016-03-25 18:13:22 info node ready nodeid:4 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor Contro
zwave-0 2016-03-25 18:13:19 info node9: timeout, currently not implemented
host-iobroker 2016-03-25 18:13:13 warn instance system.adapter.zwave.0 already running with pid 4853
zwave-0 2016-03-25 18:13:06 info node ready nodeid:1 nodeinfo:{"manufacturer":"Aeotec","manufacturerid":"0x0086","product":"Z-Stick Gen5","producttype":"0x0001","productid":"0x005a","type":"Static PC Controller","name":"","loc":""}
zwave-0 2016-03-25 18:12:59 info node9: nop, currently not implemented
zwave-0 2016-03-25 18:12:59 info node8: nop, currently not implemented
zwave-0 2016-03-25 18:12:59 info node7: nop, currently not implemented
zwave-0 2016-03-25 18:12:59 info node6: nop, currently not implemented
zwave-0 2016-03-25 18:12:59 info node5: nop, currently not implemented
zwave-0 2016-03-25 18:12:59 info node4: nop, currently not implemented
zwave-0 2016-03-25 18:12:59 info nodeid 9 is now available, but maybe not ready
zwave-0 2016-03-25 18:12:59 info nodeid 8 is now available, but maybe not ready
zwave-0 2016-03-25 18:12:58 info nodeid 7 is now available, but maybe not ready
zwave-0 2016-03-25 18:12:58 info nodeid 6 is now available, but maybe not ready
zwave-0 2016-03-25 18:12:58 info nodeid 5 is now available, but maybe not ready
zwave-0 2016-03-25 18:12:58 info nodeid 4 is now available, but maybe not ready
zwave-0 2016-03-25 18:12:58 info nodeid 1 is now available, but maybe not ready
zwave-0 2016-03-25 18:12:58 info driver ready: homeid = f331c5f6
zwave-0 2016-03-25 18:12:58 info scanning homeid=0xf331c5f6...
zwave-0 2016-03-25 18:12:57 info connected: homeid = 1.4.0
zwave-0 2016-03-25 18:12:56 info starting. Version 0.2.9 in /opt/iobroker/node_modules/iobroker.zwave
host-iobroker 2016-03-25 18:12:52 info instance system.adapter.zwave.0 started with pid 4853 -
Ok, der Fehler ist mir nicht klar, dagegen kann ich auch was machen:
zwave.0 2016-03-25 18:14:43 info zwave.0 setState for: nodeid=undefined: comclass=undefined: index=undefined: instance=undefined: value=trueMir ist nur nicht klar, warum der auftritt.
Hast du versucht einen Zustand zu verändern? Und wenn ja, welchen?
LG Christian
-
Kannst du in der main.js von zwave mal folgendes hinzufügen?
if (nodeid == undefined) { adapter.log.error("This state is not valid: " + JSON.stringify(state)); adapter.log.error("Object was: " + JSON.stringify(obj)); }Und zwar vor der Zeile 288
switch (action) {Und mir dann nochmals ein Log schicken?
-
Und mir dann nochmals ein Log schicken? `
jupp…
host-iobroker 2016-03-25 19:04:11 info Restart adapter system.adapter.zwave.0 because enabled host-iobroker 2016-03-25 19:04:11 error instance system.adapter.zwave.0 terminated with code 6 (uncaught exception) TypeError: 2016-03-25 19:04:09 error at Decoder.add (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/socket.io-parser/index.js:247:12) TypeError: 2016-03-25 19:04:09 error at Decoder.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/socket.io-parser/node_modules/component-emitter/index.js:134:20) TypeError: 2016-03-25 19:04:09 error at Decoder. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15) TypeError: 2016-03-25 19:04:09 error at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:333:8) TypeError: 2016-03-25 19:04:09 error at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-emitter/index.js:131:20) TypeError: 2016-03-25 19:04:09 error at Manager. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15) TypeError: 2016-03-25 19:04:09 error at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:229:12) TypeError: 2016-03-25 19:04:09 error at Socket.onack (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:305:9) TypeError: 2016-03-25 19:04:09 error at Socket. (/opt/iobroker/node_modules/iobroker.zwave/main.js:521:51) TypeError: 2016-03-25 19:04:09 error at TypeError (native) TypeError: 2016-03-25 19:04:09 error setValue: OpenZWave valueId not found uncaught 2016-03-25 19:04:09 error exception: setValue: OpenZWave valueId not found zwave-0 2016-03-25 19:04:09 info setState for: nodeid=undefined: comclass=undefined: index=undefined: instance=undefined: value=true zwave-0 2016-03-25 19:04:09 error Object was: {"common":{"name":"ready","role":"","type":"boolean","read":true,"write":true,"def":false},"native":{},"type":"state","_id":"zwave.0.ready"} zwave-0 2016-03-25 19:04:09 error This state is not valid: {"val":true,"ack":false,"ts":1458929048,"q":0,"from":"system.adapter.zwave.0","lc":1458929048} zwave-0 2016-03-25 19:04:09 warn Object 'zwave.0.NODE9.ready' not found for stateChange zwave-0 2016-03-25 19:04:09 warn Object 'zwave.0.NODE8.ready' not found for stateChange zwave-0 2016-03-25 19:04:09 warn Object 'zwave.0.NODE7.ready' not found for stateChange zwave-0 2016-03-25 19:04:09 warn Object 'zwave.0.NODE6.ready' not found for stateChange zwave-0 2016-03-25 19:04:08 warn Object 'zwave.0.NODE5.ready' not found for stateChange zwave-0 2016-03-25 19:04:08 warn Object 'zwave.0.NODE4.ready' not found for stateChange zwave-0 2016-03-25 19:04:08 error Object was: {"common":{"name":"zwave.0.NODE9.METER.Power_1","read":true,"write":true,"state":"mixed","role":"value.power","type":"number"},"native":{"value_id":"9-50-1-8","node_id":9,"class_id":50,"t zwave-0 2016-03-25 19:04:08 error This state is not valid: {"val":"0.0","ack":true,"ts":1458929047,"q":0,"from":"system.adapter.zwave.0","lc":1458925873} zwave-0 2016-03-25 19:04:08 error Object was: {"common":{"name":"zwave.0.NODE9.METER.Exporting_1","read":true,"write":true,"state":"mixed","role":"value","type":"boolean"},"native":{"value_id":"9-50-1-32","node_id":9,"class_id":50,"t zwave-0 2016-03-25 19:04:08 error This state is not valid: {"val":false,"ack":true,"ts":1458929047,"q":0,"from":"system.adapter.zwave.0","lc":1458925872} zwave-0 2016-03-25 19:04:07 info Scan completed zwave-0 2016-03-25 19:04:07 info node ready nodeid:9 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0301","productid":"0x1001","type":"Motor Contro zwave-0 2016-03-25 19:04:07 info node ready nodeid:8 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor Contro zwave-0 2016-03-25 19:04:07 info node ready nodeid:7 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor Contro zwave-0 2016-03-25 19:04:07 info node ready nodeid:6 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0301","productid":"0x1001","type":"Motor Contro zwave-0 2016-03-25 19:04:07 info node ready nodeid:5 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGWPE Wall Plug","producttype":"0x0600","productid":"0x1000","type":"Binary Switch","name":"","loc":" zwave-0 2016-03-25 19:04:07 info node ready nodeid:4 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor Contro zwave-0 2016-03-25 19:04:01 info node ready nodeid:1 nodeinfo:{"manufacturer":"Aeotec","manufacturerid":"0x0086","product":"Z-Stick Gen5","producttype":"0x0001","productid":"0x005a","type":"Static PC Controller","name":"","loc":""} zwave-0 2016-03-25 19:03:54 info node9: nop, currently not implemented zwave-0 2016-03-25 19:03:54 info node8: nop, currently not implemented zwave-0 2016-03-25 19:03:54 info node7: nop, currently not implemented zwave-0 2016-03-25 19:03:54 info node6: nop, currently not implemented zwave-0 2016-03-25 19:03:54 info node5: nop, currently not implemented zwave-0 2016-03-25 19:03:54 info node4: nop, currently not implemented zwave-0 2016-03-25 19:03:54 info nodeid 9 is now available, but maybe not ready zwave-0 2016-03-25 19:03:54 info nodeid 8 is now available, but maybe not ready zwave-0 2016-03-25 19:03:54 info nodeid 7 is now available, but maybe not ready zwave-0 2016-03-25 19:03:53 info nodeid 6 is now available, but maybe not ready zwave-0 2016-03-25 19:03:53 info nodeid 5 is now available, but maybe not ready zwave-0 2016-03-25 19:03:53 info nodeid 4 is now available, but maybe not ready zwave-0 2016-03-25 19:03:53 info nodeid 1 is now available, but maybe not ready zwave-0 2016-03-25 19:03:53 info driver ready: homeid = f331c5f6 zwave-0 2016-03-25 19:03:53 info scanning homeid=0xf331c5f6... zwave-0 2016-03-25 19:03:53 info connected: homeid = 1.4.0 zwave-0 2016-03-25 19:03:51 info starting. Version 0.2.9 in /opt/iobroker/node_modules/iobroker.zwave host-iobroker 2016-03-25 19:03:47 info instance system.adapter.zwave.0 started with pid 5021 host-iobroker 2016-03-25 19:03:47 info object change system.adapter.zwave.0 -
Hallo, hab in GitHub eine neue main.js hochgeladen.
Bitte nur diese austauschen und neustarten, ansonsten müsstest du alles nochmals installieren.
LG Christian `
getan… jetzt keine "roten" Log-Eiträge mehr...
is es egal welche node-Version ich habe? zurzeit ist 0.12.6 installiert...
Zeit Nachricht zwave-0 2016-03-25 19:34:30 warn Object 'zwave.0.NODE9.ready' not found for stateChange zwave-0 2016-03-25 19:34:30 warn Object 'zwave.0.NODE8.ready' not found for stateChange zwave-0 2016-03-25 19:34:30 warn Object 'zwave.0.NODE7.ready' not found for stateChange zwave-0 2016-03-25 19:34:30 warn Object 'zwave.0.NODE6.ready' not found for stateChange zwave-0 2016-03-25 19:34:30 warn Object 'zwave.0.NODE5.ready' not found for stateChange zwave-0 2016-03-25 19:34:30 warn Object 'zwave.0.NODE4.ready' not found for stateChange zwave-0 2016-03-25 19:34:28 info Scan completed zwave-0 2016-03-25 19:34:28 info node ready nodeid:9 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0301","productid":"0x1001","type":"Motor Contro zwave-0 2016-03-25 19:34:28 info node ready nodeid:8 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor Contro zwave-0 2016-03-25 19:34:28 info node ready nodeid:7 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor Contro zwave-0 2016-03-25 19:34:28 info node ready nodeid:6 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0301","productid":"0x1001","type":"Motor Contro zwave-0 2016-03-25 19:34:28 info node ready nodeid:5 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGWPE Wall Plug","producttype":"0x0600","productid":"0x1000","type":"Binary Switch","name":"","loc":" zwave-0 2016-03-25 19:34:28 info node ready nodeid:4 nodeinfo:{"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGRM222 Roller Shutter Controller 2","producttype":"0x0302","productid":"0x1000","type":"Motor Contro zwave-0 2016-03-25 19:34:27 info node9: timeout, currently not implemented zwave-0 2016-03-25 19:34:17 info node9: timeout, currently not implemented zwave-0 2016-03-25 19:34:05 info node ready nodeid:1 nodeinfo:{"manufacturer":"Aeotec","manufacturerid":"0x0086","product":"Z-Stick Gen5","producttype":"0x0001","productid":"0x005a","type":"Static PC Controller","name":"","loc":""} zwave-0 2016-03-25 19:33:59 info node9: nop, currently not implemented zwave-0 2016-03-25 19:33:59 info node8: nop, currently not implemented zwave-0 2016-03-25 19:33:59 info node7: nop, currently not implemented zwave-0 2016-03-25 19:33:59 info node6: nop, currently not implemented zwave-0 2016-03-25 19:33:59 info node5: nop, currently not implemented zwave-0 2016-03-25 19:33:59 info node4: nop, currently not implemented zwave-0 2016-03-25 19:33:59 info nodeid 9 is now available, but maybe not ready zwave-0 2016-03-25 19:33:59 info nodeid 8 is now available, but maybe not ready zwave-0 2016-03-25 19:33:59 info nodeid 7 is now available, but maybe not ready zwave-0 2016-03-25 19:33:58 info nodeid 6 is now available, but maybe not ready zwave-0 2016-03-25 19:33:58 info nodeid 5 is now available, but maybe not ready zwave-0 2016-03-25 19:33:58 info nodeid 4 is now available, but maybe not ready zwave-0 2016-03-25 19:33:58 info nodeid 1 is now available, but maybe not ready zwave-0 2016-03-25 19:33:58 info driver ready: homeid = f331c5f6 zwave-0 2016-03-25 19:33:58 info scanning homeid=0xf331c5f6... zwave-0 2016-03-25 19:33:58 info connected: homeid = 1.4.0 zwave-0 2016-03-25 19:33:56 info starting. Version 0.2.9 in /opt/iobroker/node_modules/iobroker.zwave host-iobroker 2016-03-25 19:33:52 info instance system.adapter.zwave.0 started with pid 2462 host-iobroker 2016-03-25 19:33:52 info object change system.adapter.zwave.0edit: die FIBAROS lassen sich über VIS ansteuern…
-
Hallo, na das Log sieht ja schon mal gut aus.
Ich arbeite mit 4.x habe aber auch mit 0.12 angefangen, sollte ansich kein Problem sein.
Seit letztens sollte auch die 0.10er funktionieren, aber die ist offiziell nicht supported damit.
Bitte ausgiebig testen und mir Bescheid geben.
LG Christian
-
Hallo, na das Log sieht ja schon mal gut aus.
Ich arbeite mit 4.x habe aber auch mit 0.12 angefangen, sollte ansich kein Problem sein.
Seit letztens sollte auch die 0.10er funktionieren, aber die ist offiziell nicht supported damit.
Bitte ausgiebig testen und mir Bescheid geben.
LG Christian `
jo, wie immer, Danke für die schnelle Hilfe…!
Was hast du denn für ein BS? Wheezy, Jessie???
Ich hatte in den lestzen Tagen echt viel probiert...
Banana pro mit Jessie mit Node 4.4.0 --> nur Installationsfehler
Banana pro mit Wheezy mit Node 4.4.0 --> nur Installationsfehler
Banana pro mit Wheezy mit Node 0.10* --> Installation klappt auch ohne "-unsafe -perm" Zeugs
Banana pro mit Wheezy mit Node 0.12* --> Installation klappt auch ohne "-unsafe -perm" Zeugs
Dachte mir, "musste doch mal das System aktualisieren" bums, Ende...
"never touch a running system!" ist wohl doch was dran an dem Spruch... :lol:
-
.) Statusmeldung des Adapters wie "alle Nodes fertig geladen", "Treiber/Controller fertig initialisiert"
-> erledigt `
Der Knaller, wird gleich ausprobiert!.) aktivieren/deaktivieren des inclusion/exclusion Modus der zwave-Platine
-> Siehe hierzu https://github.com/OpenZWave/node-openz … ME-mgmt.md
-> ...If your OZW version is 1.3 or greater, then there's a whole bunch of new calls, which effectively replace the old BeginControllerCommand. There's also no CancelControllerCommand thus you can't cancel any pending commands (they simply timeout)... `
Der Link ist mir bekannt. Ich hatte eine Weile damit gespielt, selbst per Skript eine eigene Instanz des Treibers zu initialisieren, das hat mir aber üblicherweise nur den RasPi aufgehängt oder die ioBroker-Prozesse abgeschossen.Habe mir mal die neue main.js angeschaut. Sehe ich das richtig, dass ich nur den State "zwave.0.GLOBAL_ACTION" überschreiben muss, um die von mir gewünschte Funktionalität zu erreichen?
Viele Grüße und danke für die superschnelle Reaktion!
-
Hallo, ja, kannst du normal überschreiben.
Hab es noch nicht dokumentiert, aber grundsätzlich ist es möglich die Funktionen per Javascript Adapter auszuführen.
Du musst nur die richtigen Parameter übergeben.
Falls es nicht funktioniert, muss ich noch was anpassen.
LG Christian
-
Hab es gerade mal ausprobiert, die .ready-States werden korrekt gesetzt.
Die Fernsteuerung des Adapters funktioniert über das Setzen des States leider nicht, da ein State im "javascript.0"-Namespace erstellt wird, was im zwave-Adapter im falschen Codepfad landet. Außerdem ist der Wert des States "null" und nicht das Objekt, das ich übergebe:
var stateName = "zwave.0.GLOBAL_ACTION"; var newState = {action: "remove_device"}; createState(stateName, newState, true);Im Prinzip möchte ich vom Skripting-Adapter aus in diesen Codepfad eingreifen:
https://github.com/husky-koglhof/ioBrok … in.js#L173
Edit: hab gerade deine Antwort gesehen, wie stelle ich das an, per JS die Funktionen auszuführen?
-
Guten Morgen!
Meine Mädels sind alle schon unterwegs, darum gibt es um die Uhrzeit schon ein Update:
In GitHub ist nun die Version 0.3.0 integriert.
Damit ist es nun möglich, direkt über Javascript / VIS / etc. eine Aktion an den zWave Adapter zu übermitteln.
Beispiel Javascript:
// Only for Documentation, all valid actions var actions = ['reset', 'assign_return_route', 'delete_all_return_routes', 'create_primary', 'replace_failed_node', 'transfer_primary', 'replication_send', 'add_button', 'remove_button', 'add_device', 'remove_device', 'receive_config', 'refresh_node', 'remove_failed_node', 'has_node_failed', 'request_node_neighbor_update', 'assign_return_route', 'delete_all_return_routes', 'send_node_information', 'request_network_update', 'refresh_device', 'healNetwork', 'updatenode', 'association', 'naming']; // Nodeid is always needed, get it from e.g. input from vis var nodeid = 10; // Action is always needed, get it from e.g. listbox from vis var action = 'naming'; // ButtonID is only needed for action = adddButton, removeButton var buttonid = 1; // Name and Location are needed only needed for action = naming var deviceName = 'New Name of Device'; var deviceLocation = 'New Location of Device'; // Heal and Count are needed only needed for action = healNetwork var heal = true; var count = 5; // Group and Nodes are needed only needed for action = association var group = 'GROUP NAME FROM ASSOCIATIONS'; var nodes = [1,2,3]; buildAction(action, nodeid, undefined, undefined, deviceName, deviceLocation, undefined, undefined); // Build correct Action function buildAction(executeAction, nodeid, heal, count, device_name, device_location, groupid, nodes) { switch (executeAction) { case 'association': submitAction(executeAction, nodeid, undefined, undefined, undefined, undefined, undefined, groupid, nodes); break; case 'updatenode': submitAction(executeAction, nodeid); break; case 'heal': submitAction(executeAction, nodeid, undefined, undefined, undefined, heal, count); break; case 'add_device': submitAction(executeAction); break; case 'remove_device': submitAction(executeAction); break; case 'receive_config': submitAction(executeAction); break; case 'refresh_node': submitAction(executeAction, nodeid); break; case 'remove_failed_node': submitAction(executeAction, nodeid); break; case 'has_node_failed': submitAction(executeAction, nodeid); break; case 'request_node_neighbor_update': submitAction(executeAction, nodeid); break; case 'send_node_information': submitAction(executeAction, nodeid); break; case 'request_network_update': submitAction(executeAction, nodeid); break; case 'refresh_device': submitAction(executeAction, nodeid); break; case 'naming': submitAction(executeAction, nodeid, undefined, device_name, device_location); break; case 'reset': submitAction(executeAction); break; case 'assign_return_route': submitAction(executeAction, nodeid); break; case 'delete_all_return_routes': submitAction(executeAction, nodeid); break; case 'create_primary': submitAction(executeAction); break; case 'replace_failed_node': submitAction(executeAction, nodeid); break; case 'transfer_primary': submitAction(executeAction); break; case 'replication_send': submitAction(executeAction, nodeid); break; case 'add_button': submitAction(executeAction, nodeid, buttonid); break; case 'remove_button': submitAction(executeAction, nodeid, buttonid); break; default: break; } } // Submit Action back to zWave Adapter function submitAction(action, nodeid, buttonid, name, location, heal, count, group, nodes) { if (nodeid !== undefined) { if (buttonid !== undefined) { setState('zwave.0.NODE' + nodeid + ".GLOBAL_ACTION", { val: {nodeid: nodeid, action: action, buttonid: buttonid}, ack: true}); } else if (name !== undefined && location !== undefined) { setState('zwave.0.NODE' + nodeid + ".GLOBAL_ACTION", { val: {nodeid: nodeid, action: action, name: name, location: location}, ack: true }); } else if (heal !== undefined) { setState('zwave.0.GLOBAL_ACTION', { val: {nodeid: nodeid, action: action, heal: heal, count: count}, ack: true }); } else if (group !== undefined) { setState('zwave.0.NODE' + nodeid + ".GLOBAL_ACTION", { val: {nodeid: nodeid, action: action, group: group, target_nodeid: nodes}, ack: true }); } else { setState('zwave.0.NODE' + nodeid + ".GLOBAL_ACTION", { val: {nodeid: nodeid, action: action}, ack: true }); } } else { setState('zwave.0.GLOBAL_ACTION', { val: {action:action}, ack: true }); } }In diesem Beispiel wird der Name und die Location des Node 10 verändert.
Wenn man den Befehl "buildAction(…)" dementsprechend anders parametrisiert, dann natürlich auch andere Actions.
Man kann aber auch direkt in die Variable zwave.0.NODE<id>.GLOBAL_ACTION z.B.
{"val":{"nodeid":10,"action":"naming","name":"New Name of Device","location":"New Location of Device"}}
reinschreiben.
Ich bin grade am überlegen, ob ich mir damit nicht selbst ein vis Widget baue...
LG Christian</id>
-
Funktioniert einwandfrei!
Gibt es eigentlich eine Möglichkeit, den Adapter zu updaten ohne jedesmal openzwave neu zu kompilieren?
Okay, habe gerade nen kleinen Bug gefunden. Bei re-initialisieren des Adapters werden die GLOBAL_ACTION und ready states der einzelnen Nodes nicht gelöscht.
-
Hallo, ist in GitHub jetzt drinnen.
Es wurde die preinstall.js dementsprechend angepasst.
Wenn die beiden Dateien
/usr/local/lib/libopenzwave.so und
/usr/local/etc/openzwave/manufacturer_specific.xml
existieren, wird keine erneute openzwave Installation durchgeführt.
-
Hallo Christian,
die Version 0.3.0 ist jetzt auch bei mir drauf.
Installation lief ohne Fehler durch. Habe jetzt auch keine Fehler mehr im Log.
Nur eins wundert mich etwas. Was hat die zwave-Instanz mit der mit der rpc-Instanz zu tun?
Im Log habe ich Warnhinweise:
zwave.0 2016-03-27 10:36:32 warn zwave.0 Object 'hm-rpc.1.CUX1200014.1.HUMIDITY' not found for stateChange zwave-0 2016-03-27 10:36:30 warn Object 'hm-rpc.1.CUX1200032.1.HUM_MAX_24H' not found for stateChangeDas betrifft meine CuxD-Geräte die offensichtlich durch den rpc-Adapter falsch erkannt werden. (es fehlen sämtliche Humidity-Kanäle)
Das war mal in einer früheren rpc-Version anders.
Grüße, Lenny
Support us
395
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge