Test Adapter z-wave v1.6.x

[smudu]

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 = 5

Das 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
 ***

[cburghardt]

@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 GetValueLabel

Das 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 = 5

Das 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
 ***

[Stormbringer]

@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.

[arteck]

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

[smudu]

@Stormbringer
Das einfache zu erst: Ich komme von fhem

@cburghardt
Das mit dem Githib Issues kann ich machen.
Das mit dem Speichern der XML unter /usr/local... habe ich mir nicht ausgesucht und wäre mir ohne Fehlersuche auch nicht aufgefallen.

Vielleicht habe ich mich mißverständlich ausgedrückt. Das Scannen ist natürlich normal. Nur das ioBroker(openzave) bis zum nächsten WAKEUP einer Node keine Status Änderungen meldet, erwarte ich nur unter folgenden Bedingungen:

• Neuinstallation Adapter/Instanz
• Major Update wie von 1.4.x nach 1.6.x

Ich habe heute nochmals versucht das, mehr oder weniger erfolgreich, zu reproduzieren

• Neustart der Z-Wave Instanz > Ok
• Kompletter Neustart Raspi > Ok
• Info Aktualisieren bei Node 24 (Fibaro Doppelschalter) > Ok, die Instanz bleibt dabei grün/wird nicht neu gestartet!
  Laut Log werden auch nur die Datenpunkte für diese Node aktualisiert.
• Info Aktualisieren bei Node 15 (Greenwave 6-fach Steckdose) > Fehler
  Die Zwave Instanz startet drei mal neu und macht dabei ein Update aller Nodes. Warum aber neben Node 15 nur nochmals für Node 24 alle Datenpunkte aktualisiert werden erschließt sich mir nicht.
  Bei einer 6-fach Steckdose mit Messung kommt einiges an Datenpunkten zusammen, vielleicht ein Timeout Problem?

Was mir wichtig ist, dass die Fensterkontakte jetzt trotz der Neustarts immer noch ihren Status korrekt melden. Damit kann ich leben.

Für das OZW log muss ich mir noch was einfallen lassen. Es gibt kein logrotate und es wird bei jedem Neustart der Instanz neu erstellt
Falls das ioBroker Log irgendwie hilft (Info Aktualisieren bei Node 15):

2019-12-04 09:41:15.589 - info: zwave.0 List of ports: [{"comName":"/dev/ttyACM0"},{"comName":"/dev/ttyAMA0"}]
2019-12-04 09:42:11.097 - info: zwave.0 Execute refreshNodeInfo for 15
2019-12-04 09:42:11.405 - info: zwave.0 node removed: 15
2019-12-04 09:42:11.582 - error: Caught by controller[0]: terminate called after throwing an instance of 'OpenZWave::OZWException'
2019-12-04 09:42:11.583 - error: Caught by controller[0]: what(): Manager.cpp:1514 - InvalidValueIDError (101) Msg: Invalid ValueID passed to GetValueLabel
2019-12-04 09:42:11.583 - warn: host.mdomus.*** instance system.adapter.zwave.0 terminated due to SIGABRT
2019-12-04 09:42:11.583 - error: host.mdomus.*** instance system.adapter.zwave.0 terminated with code null ()
2019-12-04 09:42:11.583 - info: host.mdomus.*** Restart adapter system.adapter.zwave.0 because enabled
2019-12-04 09:42:41.608 - info: host.mdomus.*** instance system.adapter.zwave.0 started with pid 23326
2019-12-04 09:42:42.289 - info: zwave.0 starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.zwave, node: v10.17.0
2019-12-04 09:42:44.380 - info: zwave.0 scanning homeid=0xe58b19ca...
2019-12-04 09:42:44.381 - info: zwave.0 driver ready: homeid = e58b19ca
2019-12-04 09:42:44.385 - info: zwave.0 Update zwave.0.NODE1
2019-12-04 09:42:44.397 - info: zwave.0 Update zwave.0.NODE2
2019-12-04 09:42:44.429 - info: zwave.0 Update zwave.0.NODE3
2019-12-04 09:42:44.454 - info: zwave.0 Update zwave.0.NODE8
2019-12-04 09:42:44.469 - info: zwave.0 Update zwave.0.NODE9
2019-12-04 09:42:44.482 - info: zwave.0 Update zwave.0.NODE10
2019-12-04 09:42:44.495 - info: zwave.0 Update zwave.0.NODE16
2019-12-04 09:42:44.787 - info: zwave.0 Update zwave.0.NODE17
2019-12-04 09:42:44.799 - info: zwave.0 Update zwave.0.NODE18
2019-12-04 09:42:44.814 - info: zwave.0 Update zwave.0.NODE19
2019-12-04 09:42:44.837 - info: zwave.0 Update zwave.0.NODE20
2019-12-04 09:42:44.892 - info: zwave.0 Update zwave.0.NODE21
2019-12-04 09:42:44.913 - info: zwave.0 Update zwave.0.NODE22
2019-12-04 09:42:44.927 - info: zwave.0 Update zwave.0.NODE23
2019-12-04 09:42:44.944 - info: zwave.0 Channel created: zwave.0.NODE24.SWITCH_ALL = Disabled, index = 0, comClass = 39, instance = 1
2019-12-04 09:42:44.945 - info: zwave.0 State created: zwave.0.NODE24.SWITCH_ALL.Switch_All = undefined, index = 0, comClass = 39, instance = 1
2019-12-04 09:42:44.949 - info: zwave.0 State created: zwave.0.NODE24.CENTRAL_SCENE.Scene_Reset_Timeout = undefined, index = 257, comClass = 91, instance = 1
2019-12-04 09:42:44.953 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = State saved at power failure, all outputs are set to previous state upon power restore, index = 9, comClass = 112, instance = 1
2019-12-04 09:42:44.954 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Saving_state_before_power_failure = undefined, index = 9, comClass = 112, instance = 1
2019-12-04 09:42:44.954 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = Standard operation, index = 10, comClass = 112, instance = 1
2019-12-04 09:42:44.955 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.First_channel_-_operating_mode = undefined, index = 10, comClass = 112, instance = 1
2019-12-04 09:42:44.955 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = Cancel mode and set target state, index = 11, comClass = 112, instance = 1
2019-12-04 09:42:44.956 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.First_channel_-_reaction_to_switch_for_delay/auto_ON/OFF_modes = undefined, index = 11, comClass = 112, instance = 1
2019-12-04 09:42:44.956 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 50, index = 12, comClass = 112, instance = 1
2019-12-04 09:42:44.957 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.First_channel_-_time_parameter_for_delay/auto_ON/OFF_modes = undefined, index = 12, comClass = 112, instance = 1
2019-12-04 09:42:44.957 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 5, index = 13, comClass = 112, instance = 1
2019-12-04 09:42:44.957 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.First_channel_-_pulse_time_for_flashing_mode = undefined, index = 13, comClass = 112, instance = 1
2019-12-04 09:42:44.958 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = Standard operation, index = 15, comClass = 112, instance = 1
2019-12-04 09:42:44.958 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Second_channel_-_operating_mode = undefined, index = 15, comClass = 112, instance = 1
2019-12-04 09:42:44.959 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = Cancel mode and set target state, index = 16, comClass = 112, instance = 1
2019-12-04 09:42:44.959 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Second_channel_-_reaction_to_switch_for_delay/auto_ON/OFF_modes = undefined, index = 16, comClass = 112, instance = 1
2019-12-04 09:42:44.959 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 50, index = 17, comClass = 112, instance = 1
2019-12-04 09:42:44.960 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Second_channel_-_time_parameter_for_delay/auto_ON/OFF_modes = undefined, index = 17, comClass = 112, instance = 1
2019-12-04 09:42:44.960 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 5, index = 18, comClass = 112, instance = 1
2019-12-04 09:42:44.960 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Second_channel_-_pulse_time_for_flashing_mode = undefined, index = 18, comClass = 112, instance = 1
2019-12-04 09:42:44.961 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = Toggle switch (device changes status when switch changes status), index = 20, comClass = 112, instance = 1
2019-12-04 09:42:44.961 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Switch_type = undefined, index = 20, comClass = 112, instance = 1
2019-12-04 09:42:44.962 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = Disabled, index = 21, comClass = 112, instance = 1
2019-12-04 09:42:44.962 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Flashing_mode_report = undefined, index = 21, comClass = 112, instance = 1
2019-12-04 09:42:44.963 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 15, index = 27, comClass = 112, instance = 1
2019-12-04 09:42:44.963 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Associations_in_Z-Wave_network_security_mode = undefined, index = 27, comClass = 112, instance = 1
2019-12-04 09:42:44.964 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 0, index = 28, comClass = 112, instance = 1
2019-12-04 09:42:44.964 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.S1_switch_-_scenes_sent = undefined, index = 28, comClass = 112, instance = 1
2019-12-04 09:42:44.965 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 0, index = 29, comClass = 112, instance = 1
2019-12-04 09:42:44.965 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.S2_switch_-_scenes_sent = undefined, index = 29, comClass = 112, instance = 1
2019-12-04 09:42:44.966 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 0, index = 30, comClass = 112, instance = 1
2019-12-04 09:42:44.966 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.S1_associations_sent_to_2nd_and_3rd_association_groups = undefined, index = 30, comClass = 112, instance = 1
2019-12-04 09:42:44.966 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 255, index = 31, comClass = 112, instance = 1
2019-12-04 09:42:44.967 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.S1_Switch_ON_value_sent_to_2nd_and_3rd_association_groups = undefined, index = 31, comClass = 112, instance = 1
2019-12-04 09:42:44.967 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 0, index = 32, comClass = 112, instance = 1
2019-12-04 09:42:44.967 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.S1_Switch_OFF_value_sent_to_2nd_and_3rd_association_groups = undefined, index = 32, comClass = 112, instance = 1
2019-12-04 09:42:44.968 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 99, index = 33, comClass = 112, instance = 1
2019-12-04 09:42:44.968 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.S1_Switch_Double_Click_value_sent_to_2nd_and_3rd_association_groups = undefined, index = 33, comClass = 112, instance = 1
2019-12-04 09:42:44.969 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 0, index = 35, comClass = 112, instance = 1
2019-12-04 09:42:44.969 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.S2_associations_sent_to_4th_and_5th_association_groups = undefined, index = 35, comClass = 112, instance = 1
2019-12-04 09:42:44.970 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 255, index = 36, comClass = 112, instance = 1
2019-12-04 09:42:44.970 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.S2_Switch_ON_value_sent_to_4th_and_5th_association_groups = undefined, index = 36, comClass = 112, instance = 1
2019-12-04 09:42:44.971 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 0, index = 37, comClass = 112, instance = 1
2019-12-04 09:42:44.972 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.S2_Switch_OFF_value_sent_to_4th_and_5th_association_groups = undefined, index = 37, comClass = 112, instance = 1
2019-12-04 09:42:44.973 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 99, index = 38, comClass = 112, instance = 1
2019-12-04 09:42:44.973 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.S2_Switch_Double_Click_value_sent_to_4th_and_5th_association_groups = undefined, index = 38, comClass = 112, instance = 1
2019-12-04 09:42:44.974 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = Flash, index = 40, comClass = 112, instance = 1
2019-12-04 09:42:44.974 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Reaction_to_General_Alarm = undefined, index = 40, comClass = 112, instance = 1
2019-12-04 09:42:44.975 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = Turn OFF, index = 41, comClass = 112, instance = 1
2019-12-04 09:42:44.976 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Reaction_to_Flood_Alarm = undefined, index = 41, comClass = 112, instance = 1
2019-12-04 09:42:44.977 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = Flash, index = 42, comClass = 112, instance = 1
2019-12-04 09:42:44.977 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Reaction_to_CO/CO2/Smoke_Alarm = undefined, index = 42, comClass = 112, instance = 1
2019-12-04 09:42:44.978 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = Turn On, index = 43, comClass = 112, instance = 1
2019-12-04 09:42:44.979 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Reaction_to_Heat_Alarm = undefined, index = 43, comClass = 112, instance = 1
2019-12-04 09:42:44.980 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 600, index = 44, comClass = 112, instance = 1
2019-12-04 09:42:44.981 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Flashing_alarm_duration = undefined, index = 44, comClass = 112, instance = 1
2019-12-04 09:42:44.982 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 20, index = 50, comClass = 112, instance = 1
2019-12-04 09:42:44.982 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.First_channel_-_power_reports = undefined, index = 50, comClass = 112, instance = 1
2019-12-04 09:42:44.983 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 10, index = 51, comClass = 112, instance = 1
2019-12-04 09:42:44.983 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.First_channel_-_minimal_time_between_power_reports = undefined, index = 51, comClass = 112, instance = 1
2019-12-04 09:42:44.984 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 100, index = 53, comClass = 112, instance = 1
2019-12-04 09:42:44.985 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.First_channel_-_energy_reports = undefined, index = 53, comClass = 112, instance = 1
2019-12-04 09:42:44.985 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 20, index = 54, comClass = 112, instance = 1
2019-12-04 09:42:44.986 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Second_Channel_-_power_reports = undefined, index = 54, comClass = 112, instance = 1
2019-12-04 09:42:44.987 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 10, index = 55, comClass = 112, instance = 1
2019-12-04 09:42:44.987 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Second_channel_-_minimal_time_between_power_reports = undefined, index = 55, comClass = 112, instance = 1
2019-12-04 09:42:44.988 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 100, index = 57, comClass = 112, instance = 1
2019-12-04 09:42:44.988 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Second_channel_-_energy_reports = undefined, index = 57, comClass = 112, instance = 1
2019-12-04 09:42:44.989 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 3600, index = 58, comClass = 112, instance = 1
2019-12-04 09:42:44.989 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Periodic_power_reports = undefined, index = 58, comClass = 112, instance = 1
2019-12-04 09:42:44.990 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = 3600, index = 59, comClass = 112, instance = 1
2019-12-04 09:42:44.991 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Periodic_energy_reports = undefined, index = 59, comClass = 112, instance = 1
2019-12-04 09:42:44.991 - info: zwave.0 Channel created: zwave.0.NODE24.CONFIGURATION = function inactive, index = 60, comClass = 112, instance = 1
2019-12-04 09:42:44.992 - info: zwave.0 State created: zwave.0.NODE24.CONFIGURATION.Measuring_energy_consumed_by_the_device_itself = undefined, index = 60, comClass = 112, instance = 1
2019-12-04 09:42:44.994 - info: zwave.0 State created: zwave.0.NODE24.MANUFACTURER_SPECIFIC.Loaded_Config_Revision = undefined, index = 0, comClass = 114, instance = 1
2019-12-04 09:42:44.994 - info: zwave.0 State created: zwave.0.NODE24.MANUFACTURER_SPECIFIC.Config_File_Revision = undefined, index = 1, comClass = 114, instance = 1
2019-12-04 09:42:44.995 - info: zwave.0 State created: zwave.0.NODE24.MANUFACTURER_SPECIFIC.Latest_Available_Config_File_Revision = undefined, index = 2, comClass = 114, instance = 1
2019-12-04 09:42:44.996 - info: zwave.0 State created: zwave.0.NODE24.MANUFACTURER_SPECIFIC.Device_ID = undefined, index = 3, comClass = 114, instance = 1
2019-12-04 09:42:45.001 - info: zwave.0 State created: zwave.0.NODE24.POWERLEVEL.Set_Powerlevel = undefined, index = 2, comClass = 115, instance = 1
2019-12-04 09:42:45.005 - info: zwave.0 State created: zwave.0.NODE24.POWERLEVEL.Test_Node = undefined, index = 3, comClass = 115, instance = 1
2019-12-04 09:42:45.006 - info: zwave.0 State created: zwave.0.NODE24.POWERLEVEL.Test_Powerlevel = undefined, index = 4, comClass = 115, instance = 1
2019-12-04 09:42:45.007 - info: zwave.0 State created: zwave.0.NODE24.POWERLEVEL.Frame_Count = undefined, index = 5, comClass = 115, instance = 1
2019-12-04 09:42:45.008 - info: zwave.0 State created: zwave.0.NODE24.POWERLEVEL.Test = undefined, index = 6, comClass = 115, instance = 1
2019-12-04 09:42:45.009 - info: zwave.0 State created: zwave.0.NODE24.POWERLEVEL.Report = undefined, index = 7, comClass = 115, instance = 1
2019-12-04 09:42:45.010 - info: zwave.0 State created: zwave.0.NODE24.POWERLEVEL.Test_Status = undefined, index = 8, comClass = 115, instance = 1
2019-12-04 09:42:45.017 - info: zwave.0 State created: zwave.0.NODE24.POWERLEVEL.Acked_Frames = undefined, index = 9, comClass = 115, instance = 1
2019-12-04 09:42:45.019 - info: zwave.0 Channel created: zwave.0.NODE24.SECURITY = false, index = 0, comClass = 152, instance = 1
2019-12-04 09:42:45.019 - info: zwave.0 State created: zwave.0.NODE24.SECURITY.Secured = undefined, index = 0, comClass = 152, instance = 1
2019-12-04 09:42:45.020 - info: zwave.0 Update zwave.0.NODE25
2019-12-04 09:42:45.046 - info: zwave.0 Update zwave.0.NODE26
2019-12-04 09:42:45.067 - info: zwave.0 Update zwave.0.NODE27
2019-12-04 09:42:45.075 - info: zwave.0 Update zwave.0.NODE28
2019-12-04 09:42:45.088 - info: zwave.0 Update zwave.0.NODE29
2019-12-04 09:42:45.097 - info: zwave.0 Update zwave.0.NODE30
2019-12-04 09:42:45.116 - info: zwave.0 Update zwave.0.NODE31
2019-12-04 09:42:48.274 - 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-04 09:42:48.275 - info: zwave.0 Update zwave.0.NODE1
2019-12-04 09:42:48.377 - info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Switch_1 = undefined, index = 0, comClass = 37, instance = 1
2019-12-04 09:42:48.379 - info: zwave.0 State created: zwave.0.NODE15.SWITCH_ALL.Switch_All = undefined, index = 0, comClass = 39, instance = 1
2019-12-04 09:43:01.638 - info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Loaded_Config_Revision = undefined, index = 0, comClass = 114, instance = 1
2019-12-04 09:43:01.643 - info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Config_File_Revision = undefined, index = 1, comClass = 114, instance = 1
2019-12-04 09:43:01.644 - info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Latest_Available_Config_File_Revision = undefined, index = 2, comClass = 114, instance = 1
2019-12-04 09:43:01.649 - info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Device_ID = undefined, index = 3, comClass = 114, instance = 1
2019-12-04 09:43:01.650 - info: zwave.0 State created: zwave.0.NODE15.MANUFACTURER_SPECIFIC.Serial_Number = undefined, index = 4, comClass = 114, instance = 1
2019-12-04 09:43:01.788 - info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.Power_delta = undefined, index = 0, comClass = 112, instance = 1
2019-12-04 09:43:01.790 - info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.No_communication_light = undefined, index = 1, comClass = 112, instance = 1
2019-12-04 09:43:01.791 - info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.Room_color = undefined, index = 2, comClass = 112, instance = 1
2019-12-04 09:43:01.794 - info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.Power_on_relay = undefined, index = 3, comClass = 112, instance = 1
2019-12-04 09:43:01.794 - info: zwave.0 State created: zwave.0.NODE15.CONFIGURATION.LED_on_network_error = undefined, index = 4, comClass = 112, instance = 1
2019-12-04 09:43:13.472 - info: zwave.0 State created: zwave.0.NODE15.VERSION.Library_Version = undefined, index = 0, comClass = 134, instance = 1
2019-12-04 09:43:13.476 - info: zwave.0 State created: zwave.0.NODE15.VERSION.Protocol_Version = undefined, index = 1, comClass = 134, instance = 1
2019-12-04 09:43:13.527 - error: Caught by controller[0]: terminate called after throwing an instance of 'OpenZWave::OZWException'
2019-12-04 09:43:13.527 - error: Caught by controller[0]: what(): Manager.cpp:1514 - InvalidValueIDError (101) Msg: Invalid ValueID passed to GetValueLabel
2019-12-04 09:43:13.528 - warn: host.mdomus.*** instance system.adapter.zwave.0 terminated due to SIGABRT
2019-12-04 09:43:13.528 - error: host.mdomus.*** instance system.adapter.zwave.0 terminated with code null ()
2019-12-04 09:43:13.528 - info: host.mdomus.*** Restart adapter system.adapter.zwave.0 because enabled
2019-12-04 09:43:43.555 - info: host.mdomus.*** instance system.adapter.zwave.0 started with pid 24638
2019-12-04 09:43:44.235 - info: zwave.0 starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.zwave, node: v10.17.0
2019-12-04 09:43:46.307 - info: zwave.0 scanning homeid=0xe58b19ca...
2019-12-04 09:43:46.310 - info: zwave.0 driver ready: homeid = e58b19ca
2019-12-04 09:43:46.313 - info: zwave.0 Update zwave.0.NODE1
2019-12-04 09:43:46.324 - info: zwave.0 Update zwave.0.NODE2
2019-12-04 09:43:46.361 - info: zwave.0 Update zwave.0.NODE3
2019-12-04 09:43:46.387 - info: zwave.0 Update zwave.0.NODE8
2019-12-04 09:43:46.411 - info: zwave.0 Update zwave.0.NODE9
2019-12-04 09:43:46.424 - info: zwave.0 Update zwave.0.NODE10
2019-12-04 09:43:46.443 - info: zwave.0 Update zwave.0.NODE16
2019-12-04 09:43:46.648 - info: zwave.0 Update zwave.0.NODE17
2019-12-04 09:43:46.669 - info: zwave.0 Update zwave.0.NODE18
2019-12-04 09:43:46.686 - info: zwave.0 Update zwave.0.NODE19
2019-12-04 09:43:46.699 - info: zwave.0 Update zwave.0.NODE20
2019-12-04 09:43:46.725 - info: zwave.0 Update zwave.0.NODE21
2019-12-04 09:43:46.738 - info: zwave.0 Update zwave.0.NODE22
2019-12-04 09:43:46.748 - info: zwave.0 Update zwave.0.NODE23
2019-12-04 09:43:46.783 - info: zwave.0 Update zwave.0.NODE25
2019-12-04 09:43:46.813 - info: zwave.0 Update zwave.0.NODE26
2019-12-04 09:43:46.826 - info: zwave.0 Update zwave.0.NODE27
2019-12-04 09:43:46.834 - info: zwave.0 Update zwave.0.NODE28
2019-12-04 09:43:46.847 - info: zwave.0 Update zwave.0.NODE29
2019-12-04 09:43:46.855 - info: zwave.0 Update zwave.0.NODE30
2019-12-04 09:43:46.868 - info: zwave.0 Update zwave.0.NODE31
2019-12-04 09:43:50.089 - 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-04 09:43:50.090 - info: zwave.0 Update zwave.0.NODE1
2019-12-04 09:44:15.723 - info: zwave.0 State created: zwave.0.NODE15.VERSION.Protocol_Version = undefined, index = 1, comClass = 134, instance = 1
2019-12-04 09:44:15.773 - error: Caught by controller[0]: terminate called after throwing an instance of 'OpenZWave::OZWException'
2019-12-04 09:44:15.774 - error: Caught by controller[0]: what(): Manager.cpp:1733 - InvalidValueIDError (101) Msg: Invalid ValueID passed to IsValueReadOnly
2019-12-04 09:44:15.774 - warn: host.mdomus.*** instance system.adapter.zwave.0 terminated due to SIGABRT
2019-12-04 09:44:15.774 - error: host.mdomus.*** instance system.adapter.zwave.0 terminated with code null ()
2019-12-04 09:44:15.774 - info: host.mdomus.*** Restart adapter system.adapter.zwave.0 because enabled
2019-12-04 09:44:45.798 - info: host.mdomus.*** instance system.adapter.zwave.0 started with pid 25817
2019-12-04 09:44:46.545 - info: zwave.0 starting. Version 1.7.2 in /opt/iobroker/node_modules/iobroker.zwave, node: v10.17.0
2019-12-04 09:44:48.802 - info: zwave.0 scanning homeid=0xe58b19ca...
2019-12-04 09:44:48.803 - info: zwave.0 driver ready: homeid = e58b19ca
2019-12-04 09:44:48.807 - info: zwave.0 Update zwave.0.NODE1
2019-12-04 09:44:48.819 - info: zwave.0 Update zwave.0.NODE2
2019-12-04 09:44:48.861 - info: zwave.0 Update zwave.0.NODE3
2019-12-04 09:44:48.888 - info: zwave.0 Update zwave.0.NODE8
2019-12-04 09:44:48.903 - info: zwave.0 Update zwave.0.NODE9
2019-12-04 09:44:48.917 - info: zwave.0 Update zwave.0.NODE10
2019-12-04 09:44:48.933 - info: zwave.0 Update zwave.0.NODE16
2019-12-04 09:44:48.941 - info: zwave.0 Update zwave.0.NODE17
2019-12-04 09:44:48.952 - info: zwave.0 Update zwave.0.NODE18
2019-12-04 09:44:49.222 - info: zwave.0 Update zwave.0.NODE19
2019-12-04 09:44:49.235 - info: zwave.0 Update zwave.0.NODE20
2019-12-04 09:44:49.249 - info: zwave.0 Update zwave.0.NODE21
2019-12-04 09:44:49.266 - info: zwave.0 Update zwave.0.NODE22
2019-12-04 09:44:49.303 - info: zwave.0 Update zwave.0.NODE23
2019-12-04 09:44:49.377 - info: zwave.0 Update zwave.0.NODE25
2019-12-04 09:44:49.407 - info: zwave.0 Update zwave.0.NODE26
2019-12-04 09:44:49.418 - info: zwave.0 Update zwave.0.NODE27
2019-12-04 09:44:49.427 - info: zwave.0 Update zwave.0.NODE28
2019-12-04 09:44:49.442 - info: zwave.0 Update zwave.0.NODE29
2019-12-04 09:44:49.451 - info: zwave.0 Update zwave.0.NODE30
2019-12-04 09:44:49.466 - info: zwave.0 Update zwave.0.NODE31
2019-12-04 09:44:52.483 - 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-04 09:44:52.484 - info: zwave.0 Update zwave.0.NODE1
2019-12-04 09:45:27.431 - info: zwave.0 State created: zwave.0.NODE15.VERSION.Application_Version = undefined, index = 2, comClass = 134, instance = 1
2019-12-04 09:46:14.939 - 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-04 09:46:14.941 - info: zwave.0 Update zwave.0.NODE3
2019-12-04 09:46:15.044 - 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-04 09:46:15.045 - info: zwave.0 Update zwave.0.NODE16
2019-12-04 09:46:15.138 - 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-04 09:46:15.232 - 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-04 09:46:15.233 - info: zwave.0 Update zwave.0.NODE25
2019-12-04 09:46:15.317 - 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-04 09:46:15.317 - info: zwave.0 Update zwave.0.NODE27
2019-12-04 09:46:15.413 - 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-04 09:46:15.413 - info: zwave.0 Update zwave.0.NODE31
2019-12-04 09:46:15.496 - info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Instance_2:_Switch_2 = undefined, index = 0, comClass = 37, instance = 2
2019-12-04 09:46:15.500 - info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Instance_2:_Protection = undefined, index = 0, comClass = 117, instance = 2
2019-12-04 09:46:15.502 - info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Instance_3:_Switch_3 = undefined, index = 0, comClass = 37, instance = 3
2019-12-04 09:46:15.504 - info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Instance_3:_Protection = undefined, index = 0, comClass = 117, instance = 3
2019-12-04 09:46:15.505 - info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Instance_4:_Switch_4 = undefined, index = 0, comClass = 37, instance = 4
2019-12-04 09:46:15.506 - info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Instance_4:_Protection = undefined, index = 0, comClass = 117, instance = 4
2019-12-04 09:46:15.506 - info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Instance_5:_Switch_5 = undefined, index = 0, comClass = 37, instance = 5
2019-12-04 09:46:15.507 - info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Instance_5:_Protection = undefined, index = 0, comClass = 117, instance = 5
2019-12-04 09:46:15.508 - info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Instance_6:_Switch_6 = undefined, index = 0, comClass = 37, instance = 6
2019-12-04 09:46:15.508 - info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Instance_6:_Protection = undefined, index = 0, comClass = 117, instance = 6
2019-12-04 09:46:15.559 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_1:_Electric_-_kWh_1 = undefined, index = 0, comClass = 50, instance = 1
2019-12-04 09:46:15.562 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_1:_Electric_-_W_1 = undefined, index = 2, comClass = 50, instance = 1
2019-12-04 09:46:15.563 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_1:_Exporting_1 = undefined, index = 256, comClass = 50, instance = 1
2019-12-04 09:46:15.564 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_1:_Reset = undefined, index = 257, comClass = 50, instance = 1
2019-12-04 09:46:15.589 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_2:_Electric_-_kWh_2 = undefined, index = 0, comClass = 50, instance = 2
2019-12-04 09:46:15.591 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_2:_Electric_-_W_2 = undefined, index = 2, comClass = 50, instance = 2
2019-12-04 09:46:15.592 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_2:_Exporting_2 = undefined, index = 256, comClass = 50, instance = 2
2019-12-04 09:46:15.593 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_2:_Reset = undefined, index = 257, comClass = 50, instance = 2
2019-12-04 09:46:15.625 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_3:_Electric_-_kWh_3 = undefined, index = 0, comClass = 50, instance = 3
2019-12-04 09:46:15.629 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_3:_Electric_-_W_3 = undefined, index = 2, comClass = 50, instance = 3
2019-12-04 09:46:15.631 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_3:_Exporting_3 = undefined, index = 256, comClass = 50, instance = 3
2019-12-04 09:46:15.631 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_3:_Reset = undefined, index = 257, comClass = 50, instance = 3
2019-12-04 09:46:15.665 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_4:_Electric_-_kWh_4 = undefined, index = 0, comClass = 50, instance = 4
2019-12-04 09:46:15.668 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_4:_Electric_-_W_4 = undefined, index = 2, comClass = 50, instance = 4
2019-12-04 09:46:15.671 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_4:_Exporting_4 = undefined, index = 256, comClass = 50, instance = 4
2019-12-04 09:46:15.672 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_4:_Reset = undefined, index = 257, comClass = 50, instance = 4
2019-12-04 09:46:15.709 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_5:_Electric_-_kWh_5 = undefined, index = 0, comClass = 50, instance = 5
2019-12-04 09:46:15.711 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_5:_Electric_-_W_5 = undefined, index = 2, comClass = 50, instance = 5
2019-12-04 09:46:15.712 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_5:_Exporting_5 = undefined, index = 256, comClass = 50, instance = 5
2019-12-04 09:46:15.713 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_5:_Reset = undefined, index = 257, comClass = 50, instance = 5
2019-12-04 09:46:15.750 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_6:_Electric_-_kWh_6 = undefined, index = 0, comClass = 50, instance = 6
2019-12-04 09:46:15.752 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_6:_Electric_-_W_6 = undefined, index = 2, comClass = 50, instance = 6
2019-12-04 09:46:15.753 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_6:_Exporting_6 = undefined, index = 256, comClass = 50, instance = 6
2019-12-04 09:46:15.754 - info: zwave.0 State created: zwave.0.NODE15.METER.Instance_6:_Reset = undefined, index = 257, comClass = 50, instance = 6
2019-12-04 09:46:16.113 - info: zwave.0 State created: zwave.0.NODE15.PROTECTION.Instance_1:_Protection = undefined, index = 0, comClass = 117, instance = 1
2019-12-04 09:46:16.356 - info: zwave.0 State created: zwave.0.NODE15.SWITCH_BINARY.Instance_1:_Switch_1 = undefined, index = 0, comClass = 37, instance = 1
2019-12-04 09:46:17.203 - info: zwave.0 node ready nodeID: 15, nodeInfo: {"manufacturer":"GreenWave Reality Inc","manufacturerid":"0x0099","product":"PowerNode 6 port","producttype":"0x0003","productid":"0x0004","type":"Binary Power Switch","name":"","loc":""}
2019-12-04 09:46:17.218 - info: zwave.0 Scan completed

[arteck]

@smudu sagte in Test Adapter z-wave v1.6.x:

2019-12-04 09:44:15.723 - info: zwave.0 State created: zwave.0.NODE15.VERSION.Protocol_Version = undefined, index = 1, comClass = 134, instance = 1
2019-12-04 09:44:15.773 - error: Caught by controller[0]: terminate called after throwing an instance of 'OpenZWave::OZWException'
2019-12-04 09:44:15.774 - error: Caught by controller[0]: what(): Manager.cpp:1733 - InvalidValueIDError (101) Msg: Invalid ValueID passed to IsValueReadOnly
2019-12-04 09:44:15.774 - warn: host.mdomus.*** instance system.adapter.zwave.0 terminated due to SIGABRT

das problem scheint mit dem NODE15 zusamenzuhängen

hmm.. was passiert wenn du das Node15 exludierst und neu einbindest ??

[smudu]

@arteck
Wäre eine Option zu testen.
Ist dann allerdings ein "Projekt" für die Feiertage. Wenn sich zwangsläufig die Node ID ändert, zerlegt's mir Scripte, iQontrol und iot/Alexa.

[cburghardt]

@smudu said in Test Adapter z-wave v1.6.x:

Ich habe heute nochmals versucht das, mehr oder weniger erfolgreich, zu reproduzieren

Neustart der Z-Wave Instanz > Ok
Kompletter Neustart Raspi > Ok
Info Aktualisieren bei Node 24 (Fibaro Doppelschalter) > Ok, die Instanz bleibt dabei grün/wird nicht neu gestartet!
Laut Log werden auch nur die Datenpunkte für diese Node aktualisiert.
Info Aktualisieren bei Node 15 (Greenwave 6-fach Steckdose) > Fehler
Die Zwave Instanz startet drei mal neu und macht dabei ein Update aller Nodes. Warum aber neben Node 15 nur nochmals für Node 24 alle Datenpunkte aktualisiert werden erschließt sich mir nicht.

Wie gesagt: bei der node sind fehlerhafte Daten in dem openzwave XML file, in diesem Fall eine falsche ValueId. openzwave wirft nen Fehler. openzwave-shared kann damit leider nicht umgehen und Crasht. Folge: der adapter startet komplett neu.
Lösung: probiere es mit einem refresh der betroffenen node. Im Härtefall exkludieren und neu inkludieren. Ist nervig (ich weiß), aber da sind mir die Hände aus Adapter-Sicht gebunden.

Bei einer 6-fach Steckdose mit Messung kommt einiges an Datenpunkten zusammen, vielleicht ein Timeout Problem?

Was mir wichtig ist, dass die Fensterkontakte jetzt trotz der Neustarts immer noch ihren Status korrekt melden. Damit kann ich leben.
Für das OZW log muss ich mir noch was einfallen lassen. Es gibt kein logrotate und es wird bei jedem Neustart der Instanz neu erstellt

Warum brauchst du das log? Das ist nur zum debugging und sollte normal ausgeschaltet sein.

[maloross]

Falls meine Frage nicht im richtigen Thread ist, bitte verschieben.

Ist vorgesehen, eine Backup-Funktion des Controllers einzubauen?

[arteck]

@maloross wie ne backup funktion ?? der Stick mekrt sich die Nodes und lat den baut der Adapter die Geräteliste auf.. was willst du da mit einem Backup.. zieh den stick ab pack den woanders rein und die Geräte laufen an diesem

[maloross]

@arteck und wenn der Stick mal defekt ist? Es geht mir darum, die Daten des Sticks auf ein baugleiches Gerät übertragen zu können.

[arteck]

@maloross ist mir nicht bekannt das es gehen würde/sollte

[maloross]

@arteck ```
Die Z-Wave.Me Lösung
Alle Z-Wave-Controller von Z-Wave.Me und seinen OEM-Partner, bieten eine Z-Wave-Netzwerk Backup-und Restore-Funktion, um dieses Problem zu überwinden.
Die Firmware im USB Stick der Gateway-Hardware bietet eine Erweiterung, die das Klonen eines vorhandenen Controller in ein neues Gerät ermöglicht. Die Z-Wave Expert-UI zeigt diese Erweiterung als eine Funktionen der Hardware (Zum Netzwerk – Controller-Info Unterteil, ZMERestore (0xF3))

[arteck]

@maloross na dann hast du dein backup den du anlegen kannst.. da musst du selber aktiv werden..da bestmmt nicht ALLE so funktionieren werden und es keine globale Lösung für gibt

[maloross]

@arteck bisher habe ich diese Funktion nicht gefunden, es gab keine Software zum Stick.

[cburghardt]

@maloross es gibt keine generische Schnittstelle zum backup der controller. Der Aeon hat beispielsweise ein eigenes Windows Tool zur Sicherung. Somit wird der z-wave Adapter so etwas auch nicht unterstützen können.

[maloross]

@cburghardt ok danke für die Info, also hier müsste dann eine spezifische Software des Herstellers diese Aufgabe übernehmen.
Da hier so fleißig gebastelt wird und ihr so viele Funktionen einbaut, hatte ich angenommen, sowas würde auch gehen.

[AlCalzone]

Es gibt Methoden im Z-Wave Standard zur Controller-Replikation. Wie genau die funktionieren, und ob die in OZW implementiert sind, weiß ich allerdings nicht.

[easybeat]

Ich habe Heute nochmal einen Versuch unternommen meinen ZWave Adapter von 1.3.1 auf 1.6.3 upzudaten. Das Update wurde zwar durchgeführt. Jedoch erhalte ich jetzt eine Fehlermeldung:

Danach konnte ich auch nicht mehr zurück auf 1.3.1

Ausserdem habe ich weiter unten gelesen, dass sich die Datenpunkte ab 1.4.x ändern. Ist dem wirklich so? Ich habe über 40 Zwave Geräte und müsste dann in meiner Logik alle anpassen...da bleib ich wohl lieber einfach auf 1.3.1

Hat irgend jemand Ansatzpunkte wie ich das Problem lösen kann?

Danke und Gruss
Beat

[AlCalzone]

@easybeat sagte in Test Adapter z-wave v1.6.x:

Hat irgend jemand Ansatzpunkte wie ich das Problem lösen kann?

Ja, steht in der Adapter-README beschrieben: https://github.com/iobroker/iobroker.zwave#known-issues