Test Adapter z-wave v1.6.x
-
@Stormbringer said in Test Adapter z-wave v1.6.x:
ok kann ich gern mal probieren und dir dann den ganzen Salat schicken oder brauchst du was bestimmtes?
Ich würde das sehr spezifisch machen. Adapter auf debug starten, scan abwarten und dann mal Bewegung bei einem node auslösen. Und dann schauen wir uns den Ausschnitt an.
-
@Stormbringer said in Test Adapter z-wave v1.6.x:
Looool echt? dachte nur FHEM und Openhab ned
Hab mich verlesen, es gibt nur ein binding lol
-
@cburghardt Hab jetzt mal Node als erstes geupdeted... NPM rebuild hab ich gemacht... Alle Adapter laufen nur Z Wave meckert:
Sagt das was mein Hauptproblem ist g?
-
@cburghardt sagte in Test Adapter z-wave v1.6.x:
@Stormbringer said in Test Adapter z-wave v1.6.x:
Looool echt? dachte nur FHEM und Openhab ned
Hab mich verlesen, es gibt nur ein binding lol
Glaub bei denen heißt alles Binding loool Binding ist bei denen sowas wie bei uns Adapter.... Hab das beim Umstieg von den ganzen Kaufsystemen neben FHEM und Broker getestet. Nur irgendwie ist das da saukompliziert im Vergleich zum Broker.
-
@Stormbringer die node version hat nichts mit openzwave zu tun und somit auch nichts mit dem Problem. Aber nun gut, zu dem Fehler:
https://www.iobroker.net/#de/documentation/install/updatenode.md -
@cburghardt sagte in Test Adapter z-wave v1.6.x:
https://www.iobroker.net/#de/documentation/install/updatenode.md
Ah ok, was willst du mir mit dem Link sagen? Das ich reinstall-skript versuchen soll?
-
@cburghardt Habs hinbekommen. Anscheinend hat das npm rebuild nicht funktioniert.
cd /opt/iobroker sudo mv reinstall.sh reinstall.dos sudo tr -d '\r' < reinstall.dos > reinstall.sh sudo chmod +x reinstall.shund dann npm rebuild hat geholfen. Stell jetzt auf debug.
-
Verstehs nicht, jetzt kennt er batterie und strom gemischt nicht. Heißt manche Strom gehen, manche Batterie gehen.... Bei einem Aeon Multisensor 6 (strombetrieben) kommt im LOG beim Aufwecken:
zwave.0 2019-11-10 03:05:17.192 info node ready nodeID: 58, nodeInfo: {"manufacturer":"AEON Labs","manufacturerid":"0x0086","product":"ZW100 MultiSensor 6","producttype":"0x0002","productid":"0x0064","type":"Routing Multilevel Sensor","n
zwave.0 2019-11-10 03:05:17.099 debug node58: timeoutAber Datenpunkte legt er nur so an (nach Scan Complete):
.Downgrade auf 1.6.0 zeigt er komischerweise auch nicht mehr an.
Ich schlaf mal ne Runde drüber, vielleicht hab ich ja Glück und dir fällt noch was ein. Wär spaßhalber möglich die 1.7.0 mit der ozw libaray von der 1.6.0 umzustellen?
-
@Stormbringer said in Test Adapter z-wave v1.6.x:
Verstehs nicht, jetzt kennt er batterie und strom gemischt nicht. Heißt manche Strom gehen, manche Batterie gehen.... Bei einem Aeon Multisensor 6 (strombetrieben) kommt im LOG beim Aufwecken:
zwave.0 2019-11-10 03:05:17.192 info node ready nodeID: 58, nodeInfo: {"manufacturer":"AEON Labs","manufacturerid":"0x0086","product":"ZW100 MultiSensor 6","producttype":"0x0002","productid":"0x0064","type":"Routing Multilevel Sensor","n
zwave.0 2019-11-10 03:05:17.099 debug node58: timeouttimeout deutet eher auf ein Kommunikationsproblem hin. Kommt nach dem timeout noch was anderes?
Aber Datenpunkte legt er nur so an (nach Scan Complete):
Ich verstehe die Aussage nicht. Warum sollten Datenpunkte nach einem normalen Neustart angelegt werden?
Und der Screenshot hat nur Basisdaten.Downgrade auf 1.6.0 zeigt er komischerweise auch nicht mehr an.
Ich schlaf mal ne Runde drüber, vielleicht hab ich ja Glück und dir fällt noch was ein. Wär spaßhalber möglich die 1.7.0 mit der ozw libaray von der 1.6.0 umzustellen?Wie gesagt: die Version 1.6.0 hat einfach nur den master von openzwave verwendet. Aber der entwickelt sich natürlich laufend weiter.
Du kannst es natürlich versuchen und den Master-Stand runterladen (https://github.com/OpenZWave/open-zwave/archive/master.zip), kompilieren und installieren. Aber ob der Adapter damit läuft, kann ich nicht sagen. -
@cburghardt ne da kam sonst nichts anderes. Aber nach ein paar unfreiwilligen Neustarts durch Test von einem anderen Adapter hat er sich jetzt eigentlich gut eingependelt. Ähnlich wie die 1.6.0, also Top Arbeit mal wieder. Fettes Danke ;o)
Das Einzige was er jetzt noch hat aber offiziell per LOG meldet ist, dass die Karte nicht mehr geht
zwave.0 2019-11-11 19:20:11.707 error at Decoder.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15)
zwave.0 2019-11-11 19:20:11.707 error at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8)
zwave.0 2019-11-11 19:20:11.707 error at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
zwave.0 2019-11-11 19:20:11.707 error at Manager.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15)
zwave.0 2019-11-11 19:20:11.707 error at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:228:12)
zwave.0 2019-11-11 19:20:11.707 error at Socket.onevent (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:270:10)
zwave.0 2019-11-11 19:20:11.707 error at Socket.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
zwave.0 2019-11-11 19:20:11.707 error at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInMemClient.js:52:30)
zwave.0 2019-11-11 19:20:11.707 error at Object.change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3679:41)
zwave.0 2019-11-11 19:20:11.707 error at Object.message (/opt/iobroker/node_modules/iobroker.zwave/main.js:214:65)
zwave.0 2019-11-11 19:20:11.707 error TypeError: Cannot read property 'common' of undefined
zwave.0 2019-11-11 19:20:11.705 error message messagebox.system.adapter.zwave.0 [object Object] Cannot read property 'common' of undefinedOder ist dir das als GitHub Issue lieber?
-
@Stormbringer said in Test Adapter z-wave v1.6.x:
Oder ist dir das als GitHub Issue lieber?
Ja das wäre super
-
für mich sieht die 1.6.3 des Z-Wave Adapters auch sehr gut aus
, abgesehen von
https://github.com/ioBroker/ioBroker.zwave/issues/96
(MacOS Catalina, node10.17, npm 6.11.3, AEOTEC Gen5 Z-Wave USB-Stick)
Viele Grüße
Christoph -
@Stormbringer said in Test Adapter z-wave v1.6.x:
Das Einzige was er jetzt noch hat aber offiziell per LOG meldet ist, dass die Karte nicht mehr geht
Gefixt in der GitHub Version (aktuell über GitHub zu beziehen, demnächst auch als 1.7.1)
-
@cburghardt Danke, hab die 1.7.1 jetzt drauf
-
@cburghardt Die läuft im übrigen Bombe. Hast du auch nen Paypalaccount um die mal n Bier für die Top Arbeit zu spendieren
Das einzige was suboptimal ist, wenn man Info aktualisiert löscht er alle Datenpunkte. Weiß war eine beabsichtigte Änderung aber warum? Wenn die DP gelöscht werden spinnt der JS Adapter kurz rum, weil ihm die abpumpte fehlen, Historywerte muss man wieder neu setzen und die Namensgebung
-
@Stormbringer ich weiß, das ist unschön, aber nicht zu vermeiden, openzwave selber löscht alle Attribute und dann die node bei diesem refresh. In vorherigen Versionen war das nicht so, weil der refresh faktisch nicht funktioniert hat, war ein Bug bei openzwave
Aber das Info aktualisieren sollte nur in Ausnahmefällen nötig sein. -
Was Z-Wave betrifft, bin ich mir nicht mehr sicher ob der Wechsel zu ioBroker die richtige Entscheidung war...
Ich habe am Wochende das Upgrade von 1.7.0 auf 1.7.2 durchgeführt. Aber eigentlich ist es nur schlimmer geworden.
Das beim Wechsel von 1.4.x auf 1.6.x alle relevanten DPs sich ändern muss man wohl so hinnehmen. Das sollte m.E. präsenter drauf hingewiesen werden.
Dann heißt es auf Github "On first run, the Adapter needs "some" time, to calculate all..." Das stimmt so auch nicht ganz. Fast alle Batterie-betriebenen Geräte wachen per Default nur alle 24 Stunden auf. Ich habe alleine 12 Fensterkontakte, die sich aus ioBroker-Sicht bis zum WAKEUP "tot" stellen, also bis zu 24 Stunden kein Fenster offen melden.Mit dem Update auf 1.7.2 führt der Reboot des Raspi oder auch nur ein einfaches "Info aktualisieren" nun dazu, dass der Z-Wave Adapter wieder alle Nodes neu scannt.
Ansonsten ist mir noch aufgefallen, dass die Datenpunkte unter Configuration der jeweiligen Nodes anscheinend die Defaults des Herstellers sind und nicht das was tatsächlich konfiguriert ist. Demnach müssten alle meine Kontakte u.a. die Temperatur in Fahrenheit ausgeben. Auch eine 6-fach Steckdose, die ja immer erreichbar ist, hat nach dem erneuten Scan meine Einstellungen in den Datenpunkten wieder vergessen/zeigt den Default an.
Einige Geräte/Datenpunkte werden nicht korrekt übernommen(?). Z.B. ein Fibaro Walli Rolladenschalter:
"states": { "0": "Roller blind", "1": "Venetian blind", "2": "roller blind with built-in driver", "3": "roller blind with built-in driver (impulse)" }In der zugehörigen openzwave.xml:
<Value genre="config" index="151" label="Operating mode" size="1" type="list" value="1"> <Help>This parameter allows adjusting operation according to the connected device.</Help> <Item label="Roller blind" value="1"/> <Item label="Venetian blind" value="2"/> <Item label="roller blind with built-in driver" value="5"/> <Item label="roller blind with built-in driver (impulse)" value="6"/> </Value>Wenn der Z-Wave Adapter neu startet braucht er auch immer mehrere "Anläufe" bis sich berappelt (Nein, ich war nicht zu ungeduldig):
2019-12-02 19:34:43.225 info: zwave.0 List of ports: [{"comName":"/dev/ttyACM0"},{"comName":"/dev/ttyAMA0"}] 2019-12-02 19:34:57.909 info: zwave.0 Execute refreshNodeInfo for 15 2019-12-02 19:34:58.179 info: zwave.0 node removed: 15 2019-12-02 19:34:58.258 info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Config_File_Revision = undefined, index = 1, comClass = 114, instance = 1 2019-12-02 19:34:58.260 info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Loaded_Config_Revision = undefined, index = 0, comClass = 114, instance = 1 2019-12-02 19:34:58.262 info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.Power_delta = undefined, index = 0, comClass = 112, instance = 1 2019-12-02 19:34:58.263 info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.No_communication_light = undefined, index = 1, comClass = 112, instance = 1 2019-12-02 19:34:58.264 info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.Room_color = undefined, index = 2, comClass = 112, instance = 1 2019-12-02 19:34:58.265 info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.Power_on_relay = undefined, index = 3, comClass = 112, instance = 1 2019-12-02 19:34:58.266 info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.LED_on_network_error = undefined, index = 4, comClass = 112, instance = 1 2019-12-02 19:34:58.305 info: zwave.0 State created: zwave.0.NODE15.VERSION.Library_Version = undefined, index = 0, comClass = 134, instance = 1 2019-12-02 19:34:58.317 info: zwave.0 State created: zwave.0.NODE15.VERSION.Protocol_Version = undefined, index = 1, comClass = 134, instance = 1 2019-12-02 19:34:58.366 error: Caught by controller[0]: terminate called after throwing an instance of 'OpenZWave::OZWException' 2019-12-02 19:34:58.367 error: Caught by controller[0]: what(): Manager.cpp:1514 - InvalidValueIDError (101) Msg: Invalid ValueID passed to GetValueLabel 2019-12-02 19:34:58.367 warn: host.mdomu*** instance system.adapter.zwave.0 terminated due to SIGABRT 2019-12-02 19:34:58.367 error: host.mdomu*** instance system.adapter.zwave.0 terminated with code null () 2019-12-02 19:34:58.367 info: host.mdomu*** Restart adapter system.adapter.zwave.0 because enabled 2019-12-02 19:35:28.403 info: host.mdomu*** instance system.adapter.zwave.0 started with pid 14993 2019-12-02 19:35:29.092 info: zwave.0 starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.zwave, node: v10.17.0 2019-12-02 19:35:33.609 info: zwave.0 scanning homeid=0xe58b19ca... 2019-12-02 19:35:33.611 info: zwave.0 driver ready: homeid = e58b19ca 2019-12-02 19:35:33.615 info: zwave.0 Update zwave.0.NODE1 2019-12-02 19:35:33.626 info: zwave.0 Update zwave.0.NODE2 *** 2019-12-02 19:35:34.191 info: zwave.0 Update zwave.0.NODE30 2019-12-02 19:35:34.216 info: zwave.0 Update zwave.0.NODE31 2019-12-02 19:35:37.378 info: zwave.0 node ready nodeID: 1, nodeInfo: {"manufacturer":"Z-Wave.Me","manufacturerid":"0x0115","product":"ZME_UZB1 USB Stick","producttype":"0x0400","productid":"0x0001","type":"Static PC Controller","name":"","loc":""} 2019-12-02 19:35:37.379 info: zwave.0 Update zwave.0.NODE1 2019-12-02 19:35:37.533 info: zwave.0 State created: zwave.0.NODE15.SWITCH_ALL.Switch_All = undefined, index = 0, comClass = 39, instance = 1 2019-12-02 19:35:51.664 info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Latest_Available_Config_File_Revision = undefined, index = 2, comClass = 114, instance = 1 2019-12-02 19:35:51.670 info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Device_ID = undefined, index = 3, comClass = 114, instance = 1 2019-12-02 19:35:51.672 info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Serial_Number = undefined, index = 4, comClass = 114, instance = 1 2019-12-02 19:36:03.510 info: zwave.0 State created: zwave.0.NODE15.VERSION.Library_Version = undefined, index = 0, comClass = 134, instance = 1 2019-12-02 19:36:03.517 info: zwave.0 State created: zwave.0.NODE15.VERSION.Protocol_Version = undefined, index = 1, comClass = 134, instance = 1 2019-12-02 19:36:03.560 error: Caught by controller[0]: terminate called after throwing an instance of 'OpenZWave::OZWException' 2019-12-02 19:36:03.561 error: Caught by controller[0]: what(): Manager.cpp:1514 - InvalidValueIDError (101) Msg: Invalid ValueID passed to GetValueLabel 2019-12-02 19:36:03.561 warn: host.mdomu*** instance system.adapter.zwave.0 terminated due to SIGABRT 2019-12-02 19:36:03.561 error: host.mdomu*** instance system.adapter.zwave.0 terminated with code null () 2019-12-02 19:36:03.562 info: host.mdomu*** Restart adapter system.adapter.zwave.0 because enabled 2019-12-02 19:36:33.591 info: host.mdomu*** instance system.adapter.zwave.0 started with pid 16274 2019-12-02 19:36:34.257 info: zwave.0 starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.zwave, node: v10.17.0 2019-12-02 19:36:36.414 info: zwave.0 scanning homeid=0xe58b19ca... 2019-12-02 19:36:36.416 info: zwave.0 driver ready: homeid = e58b19ca 2019-12-02 19:36:36.421 info: zwave.0 Update zwave.0.NODE1 2019-12-02 19:36:36.433 info: zwave.0 Update zwave.0.NODE2 *** 2019-12-02 19:36:36.681 info: zwave.0 Update zwave.0.NODE30 2019-12-02 19:36:37.159 info: zwave.0 Update zwave.0.NODE31 2019-12-02 19:36:40.264 info: zwave.0 node ready nodeID: 1, nodeInfo: {"manufacturer":"Z-Wave.Me","manufacturerid":"0x0115","product":"ZME_UZB1 USB Stick","producttype":"0x0400","productid":"0x0001","type":"Static PC Controller","name":"","loc":""} 2019-12-02 19:36:40.265 info: zwave.0 Update zwave.0.NODE1 2019-12-02 19:37:05.662 info: zwave.0 State created: zwave.0.NODE15.VERSION.Protocol_Version = undefined, index = 1, comClass = 134, instance = 1 2019-12-02 19:37:05.669 info: zwave.0 State created: zwave.0.NODE15.VERSION.Application_Version = undefined, index = 2, comClass = 134, instance = 1 2019-12-02 19:37:05.671 info: zwave.0 State created: zwave.0.NODE15.INDICATOR.Indicator_1 = undefined, index = 0, comClass = 135, instance = 1 2019-12-02 19:37:05.673 info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Protection = undefined, index = 0, comClass = 117, instance = 1 2019-12-02 19:37:52.887 info: zwave.0 node ready nodeID: 3, nodeInfo: {"manufacturer":"Devolo home Control","manufacturerid":"0x0175","product":"Metering Plug MT02646","producttype":"0x0001","productid":"0x0011","type":"On/Off Power Switch","name":"","loc":""} 2019-12-02 19:37:52.889 info: zwave.0 Update zwave.0.NODE3 2019-12-02 19:37:52.957 info: zwave.0 node ready nodeID: 16, nodeInfo: {"manufacturer":"Popp & Co","manufacturerid":"0x0154","product":"Smoke Detector and Siren","producttype":"0x0100","productid":"0x0201","type":"Smoke Alarm Sensor","name":"","loc":""} 2019-12-02 19:37:52.957 info: zwave.0 Update zwave.0.NODE16 2019-12-02 19:37:53.057 info: zwave.0 node ready nodeID: 24, nodeInfo: {"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGS223 Double Relay","producttype":"0x0203","productid":"0x1000","type":"On/Off Power Switch","name":"","loc":""} 2019-12-02 19:37:53.058 info: zwave.0 Update zwave.0.NODE24 2019-12-02 19:37:53.153 info: zwave.0 node ready nodeID: 25, nodeInfo: {"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGS223 Double Relay","producttype":"0x0203","productid":"0x1000","type":"On/Off Power Switch","name":"","loc":""} 2019-12-02 19:37:53.154 info: zwave.0 Update zwave.0.NODE25 2019-12-02 19:37:53.226 info: zwave.0 node ready nodeID: 27, nodeInfo: {"manufacturer":"Popp & Co","manufacturerid":"0x0154","product":"Smoke Detector and Siren","producttype":"0x0100","productid":"0x0201","type":"Smoke Alarm Sensor","name":"","loc":""} 2019-12-02 19:37:53.227 info: zwave.0 Update zwave.0.NODE27 2019-12-02 19:37:53.297 info: zwave.0 node ready nodeID: 31, nodeInfo: {"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGWR111 Walli Roller Shutter","producttype":"0x1d01","productid":"0x1000","type":"Window Covering Endpoint Aware","name":"","loc":""} 2019-12-02 19:37:53.297 info: zwave.0 Update zwave.0.NODE31 2019-12-02 19:37:53.382 info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Instance_2:_Switch_2 = undefined, index = 0, comClass = 37, instance = 2 2019-12-02 19:37:53.390 info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Instance_2:_Protection = undefined, index = 0, comClass = 117, instance = 2 2019-12-02 19:37:53.392 info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Instance_3:_Switch_3 = undefined, index = 0, comClass = 37, instance = 3 2019-12-02 19:37:53.393 info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Instance_3:_Protection = undefined, index = 0, comClass = 117, instance = 3 2019-12-02 19:37:53.394 info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Instance_4:_Switch_4 = undefined, index = 0, comClass = 37, instance = 4 2019-12-02 19:37:53.395 info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Instance_4:_Protection = undefined, index = 0, comClass = 117, instance = 4 2019-12-02 19:37:53.396 info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Instance_5:_Switch_5 = undefined, index = 0, comClass = 37, instance = 5 2019-12-02 19:37:53.397 info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Instance_5:_Protection = undefined, index = 0, comClass = 117, instance = 5Das OZW_log.txt wird bei jedem Neustart neu erstellt. Das er die manufacturer_specific.xml nicht nachladen und dort speichern kann, ist vermutlich auch nicht korrekt?:
2019-12-02 19:36:35.271 Always, OpenZwave Version 1.6-953-g79663e1e-dirty Starting Up 2019-12-02 19:36:35.282 Info, Loading Localization File /usr/local/etc/openzwave/Localization.xml 2019-12-02 19:36:35.284 Info, Loaded /usr/local/etc/openzwave/Localization.xml With Revision 8 2019-12-02 19:36:35.285 Always, Using Language Localization 2019-12-02 19:36:35.287 Info, Loading NotificationCCTypes File /usr/local/etc/openzwave/NotificationCCTypes.xml 2019-12-02 19:36:35.288 Info, Loaded /usr/local/etc/openzwave/NotificationCCTypes.xml With Revision 9 2019-12-02 19:36:35.290 Info, Loading SensorMultiLevelCCTypes File /usr/local/etc/openzwave/SensorMultiLevelCCTypes.xml 2019-12-02 19:36:35.290 Info, Loaded /usr/local/etc/openzwave/SensorMultiLevelCCTypes.xml With Revision 3 2019-12-02 19:36:35.290 Info, Setting Up Provided Network Key for Secure Communications 2019-12-02 19:36:35.307 Info, Manufacturer_Specific.xml file Revision is 56 2019-12-02 19:36:35.676 Info, Product name collision: FGR223 Roller Shutter Controller 3 type 303 id 1000 manufacturerid 10f, collides with FGRM223 Roller Shutter Controller 3, type 303 id 1000 manufacturerid 10f 2019-12-02 19:36:35.900 Info, Product name collision: ED2.0 Meter Adapter type 0 id 0 manufacturerid 128, collides with ED2.0 Meter Adapter, type 0 id 0 manufacturerid 128 2019-12-02 19:36:35.900 Info, Product name collision: ED2.0 Display type 128 id 0 manufacturerid 128, collides with ED2.0 Display, type 128 id 0 manufacturerid 128 *** 2019-12-02 19:36:36.032 Info, Product name collision: ZW500D 500W In-Wall Preset Dimmer Switch type 102 id 201 manufacturerid 11a, collides with ZW500D 500W In-Wall Preset Dimmer Switch, type 102 id 201 manufacturerid 11a 2019-12-02 19:36:36.032 Info, Product name collision: ZW15RM Plus 15A TR Smart Meter Duplex Receptacle type 111 id 105 manufacturerid 11a, collides with ZW15RM Plus 15A TR Smart Meter Duplex Receptacle, type 111 id 105 manufacturerid 11a 2019-12-02 19:36:36.073 Info, Queuing Lookup on mfs.db.openzwave.com for Node 0 2019-12-02 19:36:36.074 Info, Opening controller /dev/ttyACM0 2019-12-02 19:36:36.074 Info, Trying to open serial port /dev/ttyACM0 (attempt 1) 2019-12-02 19:36:36.074 Info, Starting DNSThread 2019-12-02 19:36:36.074 Info, mgr, Added driver for controller /dev/ttyACM0 2019-12-02 19:36:36.074 Info, Timer: thread starting 2019-12-02 19:36:36.074 Detail, Timer: waiting with timeout -1 ms 2019-12-02 19:36:36.074 Info, LookupTxT Checking mfs.db.openzwave.com 2019-12-02 19:36:36.075 Info, Lookup for mfs.db.openzwave.com returned 59 2019-12-02 19:36:36.077 Info, Serial port /dev/ttyACM0 opened (attempt 1) 2019-12-02 19:36:36.077 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9 2019-12-02 19:36:36.077 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc 2019-12-02 19:36:36.077 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9 2019-12-02 19:36:36.077 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb 2019-12-02 19:36:36.077 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa 2019-12-02 19:36:36.077 Warning, Config Revision of ManufacturerSpecific Database is out of date 2019-12-02 19:36:36.077 Info, Queuing download for http://download.db.openzwave.com/mfs.xml 2019-12-02 19:36:36.085 Warning, File Removal failed: /usr/local/etc/openzwave/manufacturer_specific.xml 2019-12-02 19:36:36.085 Warning, File Transfer Failed. Could not Rotate Existing File: /usr/local/etc/openzwave/manufacturer_specific.xml 2019-12-02 19:36:36.085 Warning, Can't download ManufacturerSpecifix.xml Config file 2019-12-02 19:36:36.085 Info, ManufacturerSpecificDB Initialized 2019-12-02 19:36:36.085 Detail, Notification: User Alert - Manufacturer_specific.xml out of Date 2019-12-02 19:36:36.085 Detail, Notification: A Config File Failed to download 2019-12-02 19:36:36.085 Detail, Notification: ManufacturerSpecificDB Ready 2019-12-02 19:36:36.085 Detail, 2019-12-02 19:36:36.086 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9 2019-12-02 19:36:36.086 Info, contrlr, Encrypted Flag is 0 2019-12-02 19:36:36.088 Detail, contrlr, Received: 0x01, 0x10, 0x01, 0x15, 0x5a, 0x2d, 0x57, 0x61, 0x76, 0x65, 0x20, 0x36, 0x2e, 0x30, 0x32, 0x00, 0x01, 0x92 2019-12-02 19:36:36.088 Detail, 2019-12-02 19:36:36.088 Info, contrlr, Received reply to FUNC_ID_ZW_GET_VERSION: 2019-12-02 19:36:36.088 Info, contrlr, Static Controller library, version Z-Wave 6.02 2019-12-02 19:36:36.088 Detail, contrlr, Expected reply was received 2019-12-02 19:36:36.088 Detail, contrlr, Message transaction complete *** 2019-12-02 19:36:36.321 Info, Node003, (50 - COMMAND_CLASS_METER) - Compatibility Flags: 2019-12-02 19:36:36.321 Info, Node003, (50 - COMMAND_CLASS_METER) - State Flags: 2019-12-02 19:36:36.321 Info, Node003, CCVersion: 3 2019-12-02 19:36:36.321 Info, Node003, InNif: true 2019-12-02 19:36:36.321 Info, Node003, StaticRequests: 2 2019-12-02 19:36:36.321 Warning, Localization::ReadXMLVIDHelp: Error in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/../../ozwcache_0xe58b19ca.xml at line 436 - No Help Entry for CommandClass 50, ValueID: 0 (-1): (null) (Lang: ) 2019-12-02 19:36:36.321 Warning, Localization::ReadXMLVIDHelp: Error in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/../../ozwcache_0xe58b19ca.xml at line 439 - No Help Entry for CommandClass 50, ValueID: 2 (-1): (null) (Lang: ) 2019-12-02 19:36:36.321 Warning, Localization::ReadXMLVIDHelp: Error in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/../../ozwcache_0xe58b19ca.xml at line 442 - No Help Entry for CommandClass 50, ValueID: 4 (-1): (null) (Lang: ) 2019-12-02 19:36:36.321 Warning, Localization::ReadXMLVIDHelp: Error in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/../../ozwcache_0xe58b19ca.xml at line 445 - No Help Entry for CommandClass 50, ValueID: 5 (-1): (null) (Lang: ) 2019-12-02 19:36:36.321 Warning, Localization::ReadXMLVIDHelp: Error in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/../../ozwcache_0xe58b19ca.xml at line 448 - No Help Entry for CommandClass 50, ValueID: 6 (-1): (null) (Lang: ) 2019-12-02 19:36:36.321 Warning, Localization::ReadXMLVIDHelp: Error in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/../../ozwcache_0xe58b19ca.xml at line 451 - No Help Entry for CommandClass 50, ValueID: 256 (-1): (null) (Lang: ) 2019-12-02 19:36:36.321 Warning, Localization::ReadXMLVIDHelp: Error in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/../../ozwcache_0xe58b19ca.xml at line 454 - No Help Entry for CommandClass 50, ValueID: 257 (-1): (null) (Lang: ) 2019-12-02 19:36:36.321 Info, Node003, (90 - COMMAND_CLASS_DEVICE_RESET_LOCALLY) - Compatibility Flags: 2019-12-02 19:36:36.321 Info, Node003, (90 - COMMAND_CLASS_DEVICE_RESET_LOCALLY) - State Flags: 2019-12-02 19:36:36.321 Info, Node003, InNif: true 2019-12-02 19:36:36.321 Info, Node003, StaticRequests: 4 *** 2019-12-02 19:36:36.326 Info, Node008, CCVersion: 4 2019-12-02 19:36:36.326 Info, Node008, InNif: true 2019-12-02 19:36:36.326 Info, Node008, StaticRequests: 0 2019-12-02 19:36:36.326 Warning, Value size is invalid (0). Only 1, 2 & 4 supported for node 8, class 0x71, instance 1, index 6 2019-12-02 19:36:36.326 Info, Node008, (114 - COMMAND_CLASS_MANUFACTURER_SPECIFIC) - Compatibility Flags: 2019-12-02 19:36:36.326 Info, Node008, (114 - COMMAND_CLASS_MANUFACTURER_SPECIFIC) - State Flags: 2019-12-02 19:36:36.326 Info, Node008, CCVersion: 2 2019-12-02 19:36:36.326 Info, Node008, InNif: true 2019-12-02 19:36:36.326 Info, Node008, StaticRequests: 0 *** -
@smudu said in Test Adapter z-wave v1.6.x:
Was Z-Wave betrifft, bin ich mir nicht mehr sicher ob der Wechsel zu ioBroker die richtige Entscheidung war...
Ich habe am Wochende das Upgrade von 1.7.0 auf 1.7.2 durchgeführt. Aber eigentlich ist es nur schlimmer geworden.
Das beim Wechsel von 1.4.x auf 1.6.x alle relevanten DPs sich ändern muss man wohl so hinnehmen. Das sollte m.E. präsenter drauf hingewiesen werden.
Dann heißt es auf Github "On first run, the Adapter needs "some" time, to calculate all..." Das stimmt so auch nicht ganz. Fast alle Batterie-betriebenen Geräte wachen per Default nur alle 24 Stunden auf. Ich habe alleine 12 Fensterkontakte, die sich aus ioBroker-Sicht bis zum WAKEUP "tot" stellen, also bis zu 24 Stunden kein Fenster offen melden.Das kann ich bei meinen Geräten nicht bestätigen. Melden die Geräte laut dem ozw log denn diesen Status?
Mit dem Update auf 1.7.2 führt der Reboot des Raspi oder auch nur ein einfaches "Info aktualisieren" nun dazu, dass der Z-Wave Adapter wieder alle Nodes neu scannt.
Das neue Scannen ist bei jedem Start des Adapters der Fall, so wie bei allen mir bekannten z-wave Implementierungen. Info aktualisieren macht das aber nur beim node.
Ansonsten ist mir noch aufgefallen, dass die Datenpunkte unter Configuration der jeweiligen Nodes anscheinend die Defaults des Herstellers sind und nicht das was tatsächlich konfiguriert ist. Demnach müssten alle meine Kontakte u.a. die Temperatur in Fahrenheit ausgeben. Auch eine 6-fach Steckdose, die ja immer erreichbar ist, hat nach dem erneuten Scan meine Einstellungen in den Datenpunkten wieder vergessen/zeigt den Default an.
Vermutlich nicht vergessen (das Gerät speichert es selber), aber dann stimmt die Anzeige nicht. Da wäre ein bug report gut.
Einige Geräte/Datenpunkte werden nicht korrekt übernommen(?). Z.B. ein Fibaro Walli Rolladenschalter:
"states": { "0": "Roller blind", "1": "Venetian blind", "2": "roller blind with built-in driver", "3": "roller blind with built-in driver (impulse)" }In der zugehörigen openzwave.xml:
<Value genre="config" index="151" label="Operating mode" size="1" type="list" value="1"> <Help>This parameter allows adjusting operation according to the connected device.</Help> <Item label="Roller blind" value="1"/> <Item label="Venetian blind" value="2"/> <Item label="roller blind with built-in driver" value="5"/> <Item label="roller blind with built-in driver (impulse)" value="6"/> </Value>Vermutlich ein bug. Auch da wäre ein GitHub issue sinnvoll.
Wenn der Z-Wave Adapter neu startet braucht er auch immer mehrere "Anläufe" bis sich berappelt (Nein, ich war nicht zu ungeduldig):
2019-12-02 19:34:43.225 info: zwave.0 List of ports: [{"comName":"/dev/ttyACM0"},{"comName":"/dev/ttyAMA0"}] 2019-12-02 19:34:57.909 info: zwave.0 Execute refreshNodeInfo for 15 2019-12-02 19:34:58.179 info: zwave.0 node removed: 15 2019-12-02 19:34:58.258 info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Config_File_Revision = undefined, index = 1, comClass = 114, instance = 1 2019-12-02 19:34:58.260 info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Loaded_Config_Revision = undefined, index = 0, comClass = 114, instance = 1 2019-12-02 19:34:58.262 info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.Power_delta = undefined, index = 0, comClass = 112, instance = 1 2019-12-02 19:34:58.263 info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.No_communication_light = undefined, index = 1, comClass = 112, instance = 1 2019-12-02 19:34:58.264 info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.Room_color = undefined, index = 2, comClass = 112, instance = 1 2019-12-02 19:34:58.265 info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.Power_on_relay = undefined, index = 3, comClass = 112, instance = 1 2019-12-02 19:34:58.266 info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.LED_on_network_error = undefined, index = 4, comClass = 112, instance = 1 2019-12-02 19:34:58.305 info: zwave.0 State created: zwave.0.NODE15.VERSION.Library_Version = undefined, index = 0, comClass = 134, instance = 1 2019-12-02 19:34:58.317 info: zwave.0 State created: zwave.0.NODE15.VERSION.Protocol_Version = undefined, index = 1, comClass = 134, instance = 1 2019-12-02 19:34:58.366 error: Caught by controller[0]: terminate called after throwing an instance of 'OpenZWave::OZWException' 2019-12-02 19:34:58.367 error: Caught by controller[0]: what(): Manager.cpp:1514 - InvalidValueIDError (101) Msg: Invalid ValueID passed to GetValueLabelDas habe ich schon mal gesehen. Da ist ein falscher Wert in der openzwave config gespeichert. Was da normal hilft ist ein refresh dieses Node.
2019-12-02 19:34:58.367 warn: host.mdomu*** instance system.adapter.zwave.0 terminated due to SIGABRT
2019-12-02 19:34:58.367 error: host.mdomu*** instance system.adapter.zwave.0 terminated with code null ()
2019-12-02 19:34:58.367 info: host.mdomu*** Restart adapter system.adapter.zwave.0 because enabled
2019-12-02 19:35:28.403 info: host.mdomu*** instance system.adapter.zwave.0 started with pid 14993
2019-12-02 19:35:29.092 info: zwave.0 starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.zwave, node: v10.17.0
2019-12-02 19:35:33.609 info: zwave.0 scanning homeid=0xe58b19ca...
2019-12-02 19:35:33.611 info: zwave.0 driver ready: homeid = e58b19ca
2019-12-02 19:35:33.615 info: zwave.0 Update zwave.0.NODE1
2019-12-02 19:35:33.626 info: zwave.0 Update zwave.0.NODE2
2019-12-02 19:35:34.191 info: zwave.0 Update zwave.0.NODE30
2019-12-02 19:35:34.216 info: zwave.0 Update zwave.0.NODE31
2019-12-02 19:35:37.378 info: zwave.0 node ready nodeID: 1, nodeInfo: {"manufacturer":"Z-Wave.Me","manufacturerid":"0x0115","product":"ZME_UZB1 USB Stick","producttype":"0x0400","productid":"0x0001","type":"Static PC Controller","name":"","loc":""}
2019-12-02 19:35:37.379 info: zwave.0 Update zwave.0.NODE1
2019-12-02 19:35:37.533 info: zwave.0 State created: zwave.0.NODE15.SWITCH_ALL.Switch_All = undefined, index = 0, comClass = 39, instance = 1
2019-12-02 19:35:51.664 info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Latest_Available_Config_File_Revision = undefined, index = 2, comClass = 114, instance = 1
2019-12-02 19:35:51.670 info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Device_ID = undefined, index = 3, comClass = 114, instance = 1
2019-12-02 19:35:51.672 info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Serial_Number = undefined, index = 4, comClass = 114, instance = 1
2019-12-02 19:36:03.510 info: zwave.0 State created: zwave.0.NODE15.VERSION.Library_Version = undefined, index = 0, comClass = 134, instance = 1
2019-12-02 19:36:03.517 info: zwave.0 State created: zwave.0.NODE15.VERSION.Protocol_Version = undefined, index = 1, comClass = 134, instance = 1
2019-12-02 19:36:03.560 error: Caught by controller[0]: terminate called after throwing an instance of 'OpenZWave::OZWException'
2019-12-02 19:36:03.561 error: Caught by controller[0]: what(): Manager.cpp:1514 - InvalidValueIDError (101) Msg: Invalid ValueID passed to GetValueLabel
2019-12-02 19:36:03.561 warn: host.mdomu*** instance system.adapter.zwave.0 terminated due to SIGABRT
2019-12-02 19:36:03.561 error: host.mdomu*** instance system.adapter.zwave.0 terminated with code null ()
2019-12-02 19:36:03.562 info: host.mdomu*** Restart adapter system.adapter.zwave.0 because enabled
2019-12-02 19:36:33.591 info: host.mdomu*** instance system.adapter.zwave.0 started with pid 16274
2019-12-02 19:36:34.257 info: zwave.0 starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.zwave, node: v10.17.0
2019-12-02 19:36:36.414 info: zwave.0 scanning homeid=0xe58b19ca...
2019-12-02 19:36:36.416 info: zwave.0 driver ready: homeid = e58b19ca
2019-12-02 19:36:36.421 info: zwave.0 Update zwave.0.NODE1
2019-12-02 19:36:36.433 info: zwave.0 Update zwave.0.NODE2
2019-12-02 19:36:36.681 info: zwave.0 Update zwave.0.NODE30
2019-12-02 19:36:37.159 info: zwave.0 Update zwave.0.NODE31
2019-12-02 19:36:40.264 info: zwave.0 node ready nodeID: 1, nodeInfo: {"manufacturer":"Z-Wave.Me","manufacturerid":"0x0115","product":"ZME_UZB1 USB Stick","producttype":"0x0400","productid":"0x0001","type":"Static PC Controller","name":"","loc":""}
2019-12-02 19:36:40.265 info: zwave.0 Update zwave.0.NODE1
2019-12-02 19:37:05.662 info: zwave.0 State created: zwave.0.NODE15.VERSION.Protocol_Version = undefined, index = 1, comClass = 134, instance = 1
2019-12-02 19:37:05.669 info: zwave.0 State created: zwave.0.NODE15.VERSION.Application_Version = undefined, index = 2, comClass = 134, instance = 1
2019-12-02 19:37:05.671 info: zwave.0 State created: zwave.0.NODE15.INDICATOR.Indicator_1 = undefined, index = 0, comClass = 135, instance = 1
2019-12-02 19:37:05.673 info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Protection = undefined, index = 0, comClass = 117, instance = 1
2019-12-02 19:37:52.887 info: zwave.0 node ready nodeID: 3, nodeInfo: {"manufacturer":"Devolo home Control","manufacturerid":"0x0175","product":"Metering Plug MT02646","producttype":"0x0001","productid":"0x0011","type":"On/Off Power Switch","name":"","loc":""}
2019-12-02 19:37:52.889 info: zwave.0 Update zwave.0.NODE3
2019-12-02 19:37:52.957 info: zwave.0 node ready nodeID: 16, nodeInfo: {"manufacturer":"Popp & Co","manufacturerid":"0x0154","product":"Smoke Detector and Siren","producttype":"0x0100","productid":"0x0201","type":"Smoke Alarm Sensor","name":"","loc":""}
2019-12-02 19:37:52.957 info: zwave.0 Update zwave.0.NODE16
2019-12-02 19:37:53.057 info: zwave.0 node ready nodeID: 24, nodeInfo: {"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGS223 Double Relay","producttype":"0x0203","productid":"0x1000","type":"On/Off Power Switch","name":"","loc":""}
2019-12-02 19:37:53.058 info: zwave.0 Update zwave.0.NODE24
2019-12-02 19:37:53.153 info: zwave.0 node ready nodeID: 25, nodeInfo: {"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGS223 Double Relay","producttype":"0x0203","productid":"0x1000","type":"On/Off Power Switch","name":"","loc":""}
2019-12-02 19:37:53.154 info: zwave.0 Update zwave.0.NODE25
2019-12-02 19:37:53.226 info: zwave.0 node ready nodeID: 27, nodeInfo: {"manufacturer":"Popp & Co","manufacturerid":"0x0154","product":"Smoke Detector and Siren","producttype":"0x0100","productid":"0x0201","type":"Smoke Alarm Sensor","name":"","loc":""}
2019-12-02 19:37:53.227 info: zwave.0 Update zwave.0.NODE27
2019-12-02 19:37:53.297 info: zwave.0 node ready nodeID: 31, nodeInfo: {"manufacturer":"FIBARO System","manufacturerid":"0x010f","product":"FGWR111 Walli Roller Shutter","producttype":"0x1d01","productid":"0x1000","type":"Window Covering Endpoint Aware","name":"","loc":""}
2019-12-02 19:37:53.297 info: zwave.0 Update zwave.0.NODE31
2019-12-02 19:37:53.382 info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Instance_2:_Switch_2 = undefined, index = 0, comClass = 37, instance = 2
2019-12-02 19:37:53.390 info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Instance_2:_Protection = undefined, index = 0, comClass = 117, instance = 2
2019-12-02 19:37:53.392 info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Instance_3:_Switch_3 = undefined, index = 0, comClass = 37, instance = 3
2019-12-02 19:37:53.393 info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Instance_3:_Protection = undefined, index = 0, comClass = 117, instance = 3
2019-12-02 19:37:53.394 info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Instance_4:_Switch_4 = undefined, index = 0, comClass = 37, instance = 4
2019-12-02 19:37:53.395 info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Instance_4:_Protection = undefined, index = 0, comClass = 117, instance = 4
2019-12-02 19:37:53.396 info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Instance_5:_Switch_5 = undefined, index = 0, comClass = 37, instance = 5
2019-12-02 19:37:53.397 info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Instance_5:_Protection = undefined, index = 0, comClass = 117, instance = 5Das OZW_log.txt wird bei jedem Neustart neu erstellt. Das er die manufacturer_specific.xml nicht nachladen und dort speichern kann, ist vermutlich auch nicht korrekt?:Naja, wenn es bei dir in /usr/local gespeichert ist und der Adapter dort keinen Schreibzugriff hat? Ob man den download will oder nicht, ist aber eine persönliche Entscheidung, die Auslieferungsversion geht ja.
2019-12-02 19:36:35.271 Always, OpenZwave Version 1.6-953-g79663e1e-dirty Starting Up 2019-12-02 19:36:35.282 Info, Loading Localization File /usr/local/etc/openzwave/Localization.xml 2019-12-02 19:36:35.284 Info, Loaded /usr/local/etc/openzwave/Localization.xml With Revision 8 2019-12-02 19:36:35.285 Always, Using Language Localization 2019-12-02 19:36:35.287 Info, Loading NotificationCCTypes File /usr/local/etc/openzwave/NotificationCCTypes.xml 2019-12-02 19:36:35.288 Info, Loaded /usr/local/etc/openzwave/NotificationCCTypes.xml With Revision 9 2019-12-02 19:36:35.290 Info, Loading SensorMultiLevelCCTypes File /usr/local/etc/openzwave/SensorMultiLevelCCTypes.xml 2019-12-02 19:36:35.290 Info, Loaded /usr/local/etc/openzwave/SensorMultiLevelCCTypes.xml With Revision 3 2019-12-02 19:36:35.290 Info, Setting Up Provided Network Key for Secure Communications 2019-12-02 19:36:35.307 Info, Manufacturer_Specific.xml file Revision is 56 2019-12-02 19:36:35.676 Info, Product name collision: FGR223 Roller Shutter Controller 3 type 303 id 1000 manufacturerid 10f, collides with FGRM223 Roller Shutter Controller 3, type 303 id 1000 manufacturerid 10f 2019-12-02 19:36:35.900 Info, Product name collision: ED2.0 Meter Adapter type 0 id 0 manufacturerid 128, collides with ED2.0 Meter Adapter, type 0 id 0 manufacturerid 128 2019-12-02 19:36:35.900 Info, Product name collision: ED2.0 Display type 128 id 0 manufacturerid 128, collides with ED2.0 Display, type 128 id 0 manufacturerid 128 *** 2019-12-02 19:36:36.032 Info, Product name collision: ZW500D 500W In-Wall Preset Dimmer Switch type 102 id 201 manufacturerid 11a, collides with ZW500D 500W In-Wall Preset Dimmer Switch, type 102 id 201 manufacturerid 11a 2019-12-02 19:36:36.032 Info, Product name collision: ZW15RM Plus 15A TR Smart Meter Duplex Receptacle type 111 id 105 manufacturerid 11a, collides with ZW15RM Plus 15A TR Smart Meter Duplex Receptacle, type 111 id 105 manufacturerid 11a 2019-12-02 19:36:36.073 Info, Queuing Lookup on mfs.db.openzwave.com for Node 0 2019-12-02 19:36:36.074 Info, Opening controller /dev/ttyACM0 2019-12-02 19:36:36.074 Info, Trying to open serial port /dev/ttyACM0 (attempt 1) 2019-12-02 19:36:36.074 Info, Starting DNSThread 2019-12-02 19:36:36.074 Info, mgr, Added driver for controller /dev/ttyACM0 2019-12-02 19:36:36.074 Info, Timer: thread starting 2019-12-02 19:36:36.074 Detail, Timer: waiting with timeout -1 ms 2019-12-02 19:36:36.074 Info, LookupTxT Checking mfs.db.openzwave.com 2019-12-02 19:36:36.075 Info, Lookup for mfs.db.openzwave.com returned 59 2019-12-02 19:36:36.077 Info, Serial port /dev/ttyACM0 opened (attempt 1) 2019-12-02 19:36:36.077 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9 2019-12-02 19:36:36.077 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc 2019-12-02 19:36:36.077 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9 2019-12-02 19:36:36.077 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb 2019-12-02 19:36:36.077 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa 2019-12-02 19:36:36.077 Warning, Config Revision of ManufacturerSpecific Database is out of date 2019-12-02 19:36:36.077 Info, Queuing download for http://download.db.openzwave.com/mfs.xml 2019-12-02 19:36:36.085 Warning, File Removal failed: /usr/local/etc/openzwave/manufacturer_specific.xml 2019-12-02 19:36:36.085 Warning, File Transfer Failed. Could not Rotate Existing File: /usr/local/etc/openzwave/manufacturer_specific.xml 2019-12-02 19:36:36.085 Warning, Can't download ManufacturerSpecifix.xml Config file 2019-12-02 19:36:36.085 Info, ManufacturerSpecificDB Initialized 2019-12-02 19:36:36.085 Detail, Notification: User Alert - Manufacturer_specific.xml out of Date 2019-12-02 19:36:36.085 Detail, Notification: A Config File Failed to download 2019-12-02 19:36:36.085 Detail, Notification: ManufacturerSpecificDB Ready 2019-12-02 19:36:36.085 Detail, 2019-12-02 19:36:36.086 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9 2019-12-02 19:36:36.086 Info, contrlr, Encrypted Flag is 0 2019-12-02 19:36:36.088 Detail, contrlr, Received: 0x01, 0x10, 0x01, 0x15, 0x5a, 0x2d, 0x57, 0x61, 0x76, 0x65, 0x20, 0x36, 0x2e, 0x30, 0x32, 0x00, 0x01, 0x92 2019-12-02 19:36:36.088 Detail, 2019-12-02 19:36:36.088 Info, contrlr, Received reply to FUNC_ID_ZW_GET_VERSION: 2019-12-02 19:36:36.088 Info, contrlr, Static Controller library, version Z-Wave 6.02 2019-12-02 19:36:36.088 Detail, contrlr, Expected reply was received 2019-12-02 19:36:36.088 Detail, contrlr, Message transaction complete *** 2019-12-02 19:36:36.321 Info, Node003, (50 - COMMAND_CLASS_METER) - Compatibility Flags: 2019-12-02 19:36:36.321 Info, Node003, (50 - COMMAND_CLASS_METER) - State Flags: 2019-12-02 19:36:36.321 Info, Node003, CCVersion: 3 2019-12-02 19:36:36.321 Info, Node003, InNif: true 2019-12-02 19:36:36.321 Info, Node003, StaticRequests: 2 2019-12-02 19:36:36.321 Warning, Localization::ReadXMLVIDHelp: Error in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/../../ozwcache_0xe58b19ca.xml at line 436 - No Help Entry for CommandClass 50, ValueID: 0 (-1): (null) (Lang: ) 2019-12-02 19:36:36.321 Warning, Localization::ReadXMLVIDHelp: Error in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/../../ozwcache_0xe58b19ca.xml at line 439 - No Help Entry for CommandClass 50, ValueID: 2 (-1): (null) (Lang: ) 2019-12-02 19:36:36.321 Warning, Localization::ReadXMLVIDHelp: Error in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/../../ozwcache_0xe58b19ca.xml at line 442 - No Help Entry for CommandClass 50, ValueID: 4 (-1): (null) (Lang: ) 2019-12-02 19:36:36.321 Warning, Localization::ReadXMLVIDHelp: Error in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/../../ozwcache_0xe58b19ca.xml at line 445 - No Help Entry for CommandClass 50, ValueID: 5 (-1): (null) (Lang: ) 2019-12-02 19:36:36.321 Warning, Localization::ReadXMLVIDHelp: Error in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/../../ozwcache_0xe58b19ca.xml at line 448 - No Help Entry for CommandClass 50, ValueID: 6 (-1): (null) (Lang: ) 2019-12-02 19:36:36.321 Warning, Localization::ReadXMLVIDHelp: Error in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/../../ozwcache_0xe58b19ca.xml at line 451 - No Help Entry for CommandClass 50, ValueID: 256 (-1): (null) (Lang: ) 2019-12-02 19:36:36.321 Warning, Localization::ReadXMLVIDHelp: Error in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared/build/Release/../../ozwcache_0xe58b19ca.xml at line 454 - No Help Entry for CommandClass 50, ValueID: 257 (-1): (null) (Lang: ) 2019-12-02 19:36:36.321 Info, Node003, (90 - COMMAND_CLASS_DEVICE_RESET_LOCALLY) - Compatibility Flags: 2019-12-02 19:36:36.321 Info, Node003, (90 - COMMAND_CLASS_DEVICE_RESET_LOCALLY) - State Flags: 2019-12-02 19:36:36.321 Info, Node003, InNif: true 2019-12-02 19:36:36.321 Info, Node003, StaticRequests: 4 *** 2019-12-02 19:36:36.326 Info, Node008, CCVersion: 4 2019-12-02 19:36:36.326 Info, Node008, InNif: true 2019-12-02 19:36:36.326 Info, Node008, StaticRequests: 0 2019-12-02 19:36:36.326 Warning, Value size is invalid (0). Only 1, 2 & 4 supported for node 8, class 0x71, instance 1, index 6 2019-12-02 19:36:36.326 Info, Node008, (114 - COMMAND_CLASS_MANUFACTURER_SPECIFIC) - Compatibility Flags: 2019-12-02 19:36:36.326 Info, Node008, (114 - COMMAND_CLASS_MANUFACTURER_SPECIFIC) - State Flags: 2019-12-02 19:36:36.326 Info, Node008, CCVersion: 2 2019-12-02 19:36:36.326 Info, Node008, InNif: true 2019-12-02 19:36:36.326 Info, Node008, StaticRequests: 0 *** -
@smudu Darf ich fragen worauf die Z Wave vorher laufen hast lassen? War eigentlich auch immer am übleren, dass outzusourcen. Aber die aktuelle Beta läuft jetzt seit langem echt mal gut.
-
ich hab auch mehrfach umgestellt .. ja es ist nervig das die Objectnamen sich geändert haben (vor allem wenn man Grafen erstellt mit den Datenpunkten)
aber da können wir nix machen.. die Daten kommen so vom OZW.. ansonsten läft das Ding wie lange nicht mehr..
bin froh dass sich das einer angenommen hat..danke @cburghardt
