NEWS
Probleme nach ZWave Update mit ZME_WALLC-S
ioBroker Allgemein
69
Beiträge
8
Kommentatoren
5.5k
Aufrufe
9
Watching
-
Ich habe eine Datei OZW_Log.txt in /opt/iobroker/node_modules/iobroker.zwave/node_modules/openzwave-shared gefunden:
Aktuell ist die leer.
Nach umstellen des Z-Wave Logs auf debug laufen die Meldungen der stromgebundenen Nodes ein.
scan completed; die Datei ist immer noch 0 Bytes groß.
Ein manuell erzeugter NIF taucht nicht im normalen log des iobrokers auf.
Nach dem dritten oder vierten abschicken des NIF kommen jetzt Meldungen von Node 5 im iobroker log an.
In CENTRAL_SCENE stehen immer noch zwei Einträge drin; Scene_Count_1 und Scene_Reset_TimeoutIm iobroker Log steht zum Taster (ID 5):
zwave.0 2019-11-06 19:31:56.152 debug node5: node sleep zwave.0 2019-11-06 19:31:55.738 debug value changed: 9 comClass: 50 value: {"value_id":"9-50-3-256","node_id":9,"class_id":50,"type":"bool","genre":"user","instance":3,"index":256,"label":"Instance 3: Exporting","units":"","help":"","read zwave.0 2019-11-06 19:31:55.735 debug value changed: 9 comClass: 50 value: {"value_id":"9-50-3-2","node_id":9,"class_id":50,"type":"decimal","genre":"user","instance":3,"index":2,"label":"Instance 3: Electric - W","units":"W","help":"","r zwave.0 2019-11-06 19:31:51.851 debug node5: timeout zwave.0 2019-11-06 19:31:45.875 debug value changed: 14 comClass: 49 value: {"value_id":"14-49-1-3","node_id":14,"class_id":49,"type":"decimal","genre":"user","instance":1,"index":3,"label":"Illuminance","units":"Lux","help":"Luminance Se zwave.0 2019-11-06 19:31:41.849 debug node5: timeout zwave.0 2019-11-06 19:31:31.868 info State created: zwave.0.NODE5.WAKE_UP.Wake-up_Interval_Step = undefined, index = 4, comClass = 132, instance = 1 zwave.0 2019-11-06 19:31:31.868 debug value added: nodeID: 5 comClass: 132 value: {"value_id":"5-132-1-4","node_id":5,"class_id":132,"type":"int","genre":"system","instance":1,"index":4,"label":"Wake-up Interval Step","units":"Seconds","h zwave.0 2019-11-06 19:31:31.868 info State created: zwave.0.NODE5.WAKE_UP.Default_Wake-up_Interval = undefined, index = 3, comClass = 132, instance = 1 zwave.0 2019-11-06 19:31:31.868 debug value added: nodeID: 5 comClass: 132 value: {"value_id":"5-132-1-3","node_id":5,"class_id":132,"type":"int","genre":"system","instance":1,"index":3,"label":"Default Wake-up Interval","units":"Seconds" zwave.0 2019-11-06 19:31:31.868 info State created: zwave.0.NODE5.WAKE_UP.Maximum_Wake-up_Interval = undefined, index = 2, comClass = 132, instance = 1 zwave.0 2019-11-06 19:31:31.868 debug value added: nodeID: 5 comClass: 132 value: {"value_id":"5-132-1-2","node_id":5,"class_id":132,"type":"int","genre":"system","instance":1,"index":2,"label":"Maximum Wake-up Interval","units":"Seconds" zwave.0 2019-11-06 19:31:31.868 info State created: zwave.0.NODE5.WAKE_UP.Minimum_Wake-up_Interval = undefined, index = 1, comClass = 132, instance = 1 zwave.0 2019-11-06 19:31:31.868 debug value added: nodeID: 5 comClass: 132 value: {"value_id":"5-132-1-1","node_id":5,"class_id":132,"type":"int","genre":"system","instance":1,"index":1,"label":"Minimum Wake-up Interval","units":"Seconds" zwave.0 2019-11-06 19:31:30.618 debug node5: timeout zwave.0 2019-11-06 19:31:20.686 info State created: zwave.0.NODE5.SCENE_ACTIVATION.Duration_1 = undefined, index = 1, comClass = 43, instance = 1 zwave.0 2019-11-06 19:31:20.686 info Channel created: zwave.0.NODE5.SCENE_ACTIVATION = 0, index = 1, comClass = 43, instance = 1 zwave.0 2019-11-06 19:31:20.686 debug value added: nodeID: 5 comClass: 43 value: {"value_id":"5-43-1-1","node_id":5,"class_id":43,"type":"int","genre":"user","instance":1,"index":1,"label":"Duration","units":"","help":"","read_only":true, zwave.0 2019-11-06 19:31:20.686 info State created: zwave.0.NODE5.SCENE_ACTIVATION.Scene_1 = undefined, index = 0, comClass = 43, instance = 1 zwave.0 2019-11-06 19:31:20.686 info Channel created: zwave.0.NODE5.SCENE_ACTIVATION = 0, index = 0, comClass = 43, instance = 1 zwave.0 2019-11-06 19:31:20.685 debug value added: nodeID: 5 comClass: 43 value: {"value_id":"5-43-1-0","node_id":5,"class_id":43,"type":"int","genre":"user","instance":1,"index":0,"label":"Scene","units":"","help":"","read_only":true,"wr zwave.0 2019-11-06 19:31:20.685 info State created: zwave.0.NODE5.SWITCH_ALL.Switch_All = undefined, index = 0, comClass = 39, instance = 1 zwave.0 2019-11-06 19:31:20.685 info Channel created: zwave.0.NODE5.SWITCH_ALL = Disabled, index = 0, comClass = 39, instance = 1 zwave.0 2019-11-06 19:31:20.685 debug value added: nodeID: 5 comClass: 39 value: {"value_id":"5-39-1-0","node_id":5,"class_id":39,"type":"list","genre":"system","instance":1,"index":0,"label":"Switch All","units":"","help":"Switch All Dev zwave.0 2019-11-06 19:31:20.685 info State created: zwave.0.NODE5.SWITCH_MULTILEVEL.Start_Level = undefined, index = 4, comClass = 38, instance = 1 zwave.0 2019-11-06 19:31:20.685 info Channel created: zwave.0.NODE5.SWITCH_MULTILEVEL = 0, index = 4, comClass = 38, instance = 1 zwave.0 2019-11-06 19:31:20.685 debug value added: nodeID: 5 comClass: 38 value: {"value_id":"5-38-1-4","node_id":5,"class_id":38,"type":"byte","genre":"system","instance":1,"index":4,"label":"Start Level","units":"","help":"Start Level w zwave.0 2019-11-06 19:31:20.685 info State created: zwave.0.NODE5.SWITCH_MULTILEVEL.Ignore_Start_Level = undefined, index = 3, comClass = 38, instance = 1 zwave.0 2019-11-06 19:31:20.685 info Channel created: zwave.0.NODE5.SWITCH_MULTILEVEL = true, index = 3, comClass = 38, instance = 1 zwave.0 2019-11-06 19:31:20.685 debug value added: nodeID: 5 comClass: 38 value: {"value_id":"5-38-1-3","node_id":5,"class_id":38,"type":"bool","genre":"system","instance":1,"index":3,"label":"Ignore Start Level","units":"","help":"Ignore zwave.0 2019-11-06 19:31:20.685 info State created: zwave.0.NODE5.SWITCH_MULTILEVEL.Dim_1 = undefined, index = 2, comClass = 38, instance = 1 zwave.0 2019-11-06 19:31:20.685 info Channel created: zwave.0.NODE5.SWITCH_MULTILEVEL = undefined, index = 2, comClass = 38, instance = 1 zwave.0 2019-11-06 19:31:20.685 debug value added: nodeID: 5 comClass: 38 value: {"value_id":"5-38-1-2","node_id":5,"class_id":38,"type":"button","genre":"user","instance":1,"index":2,"label":"Dim","units":"","help":"Decrease the Brightne zwave.0 2019-11-06 19:31:20.685 info State created: zwave.0.NODE5.SWITCH_MULTILEVEL.Bright_1 = undefined, index = 1, comClass = 38, instance = 1 zwave.0 2019-11-06 19:31:20.685 info Channel created: zwave.0.NODE5.SWITCH_MULTILEVEL = undefined, index = 1, comClass = 38, instance = 1 zwave.0 2019-11-06 19:31:20.685 debug value added: nodeID: 5 comClass: 38 value: {"value_id":"5-38-1-1","node_id":5,"class_id":38,"type":"button","genre":"user","instance":1,"index":1,"label":"Bright","units":"","help":"Increase the Brigh zwave.0 2019-11-06 19:31:20.685 info State created: zwave.0.NODE5.SWITCH_MULTILEVEL.Level_1 = undefined, index = 0, comClass = 38, instance = 1 zwave.0 2019-11-06 19:31:20.685 info Channel created: zwave.0.NODE5.SWITCH_MULTILEVEL = 0, index = 0, comClass = 38, instance = 1 zwave.0 2019-11-06 19:31:20.685 debug value added: nodeID: 5 comClass: 38 value: {"value_id":"5-38-1-0","node_id":5,"class_id":38,"type":"byte","genre":"user","instance":1,"index":0,"label":"Level","units":"","help":"The Current Level of zwave.0 2019-11-06 19:31:20.685 info State created: zwave.0.NODE5.VERSION.Application_Version = undefined, index = 2, comClass = 134, instance = 1 zwave.0 2019-11-06 19:31:20.685 info Channel created: zwave.0.NODE5.VERSION = Unknown, index = 2, comClass = 134, instance = 1 zwave.0 2019-11-06 19:31:20.685 debug value added: nodeID: 5 comClass: 134 value: {"value_id":"5-134-1-2","node_id":5,"class_id":134,"type":"string","genre":"system","instance":1,"index":2,"label":"Application Version","units":"","help":" zwave.0 2019-11-06 19:31:20.685 info State created: zwave.0.NODE5.VERSION.Protocol_Version = undefined, index = 1, comClass = 134, instance = 1 zwave.0 2019-11-06 19:31:20.685 info Channel created: zwave.0.NODE5.VERSION = Unknown, index = 1, comClass = 134, instance = 1 zwave.0 2019-11-06 19:31:20.685 debug value added: nodeID: 5 comClass: 134 value: {"value_id":"5-134-1-1","node_id":5,"class_id":134,"type":"string","genre":"system","instance":1,"index":1,"label":"Protocol Version","units":"","help":"Z-W zwave.0 2019-11-06 19:31:20.685 info State created: zwave.0.NODE5.VERSION.Library_Version = undefined, index = 0, comClass = 134, instance = 1 zwave.0 2019-11-06 19:31:20.685 info Channel created: zwave.0.NODE5.VERSION = Unknown, index = 0, comClass = 134, instance = 1 zwave.0 2019-11-06 19:31:20.685 debug value added: nodeID: 5 comClass: 134 value: {"value_id":"5-134-1-0","node_id":5,"class_id":134,"type":"string","genre":"system","instance":1,"index":0,"label":"Library Version","units":"","help":"Z-Wa zwave.0 2019-11-06 19:31:20.685 info State created: zwave.0.NODE5.POWERLEVEL.Acked_Frames = undefined, index = 9, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.685 info Channel created: zwave.0.NODE5.POWERLEVEL = 0, index = 9, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.685 debug value added: nodeID: 5 comClass: 115 value: {"value_id":"5-115-1-9","node_id":5,"class_id":115,"type":"short","genre":"system","instance":1,"index":9,"label":"Acked Frames","units":"","help":"Number o zwave.0 2019-11-06 19:31:20.684 info State created: zwave.0.NODE5.POWERLEVEL.Test_Status = undefined, index = 8, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 info Channel created: zwave.0.NODE5.POWERLEVEL = Failed, index = 8, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 debug value added: nodeID: 5 comClass: 115 value: {"value_id":"5-115-1-8","node_id":5,"class_id":115,"type":"list","genre":"system","instance":1,"index":8,"label":"Test Status","units":"","help":"The Curren zwave.0 2019-11-06 19:31:20.684 info State created: zwave.0.NODE5.POWERLEVEL.Report = undefined, index = 7, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 info Channel created: zwave.0.NODE5.POWERLEVEL = undefined, index = 7, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 debug value added: nodeID: 5 comClass: 115 value: {"value_id":"5-115-1-7","node_id":5,"class_id":115,"type":"button","genre":"system","instance":1,"index":7,"label":"Report","units":"","help":"Get the resul zwave.0 2019-11-06 19:31:20.684 info State created: zwave.0.NODE5.POWERLEVEL.Test = undefined, index = 6, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 info Channel created: zwave.0.NODE5.POWERLEVEL = undefined, index = 6, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 debug value added: nodeID: 5 comClass: 115 value: {"value_id":"5-115-1-6","node_id":5,"class_id":115,"type":"button","genre":"system","instance":1,"index":6,"label":"Test","units":"","help":"Perform a Power zwave.0 2019-11-06 19:31:20.684 info State created: zwave.0.NODE5.POWERLEVEL.Frame_Count = undefined, index = 5, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 info Channel created: zwave.0.NODE5.POWERLEVEL = 0, index = 5, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 debug value added: nodeID: 5 comClass: 115 value: {"value_id":"5-115-1-5","node_id":5,"class_id":115,"type":"short","genre":"system","instance":1,"index":5,"label":"Frame Count","units":"","help":"How Many zwave.0 2019-11-06 19:31:20.684 info State created: zwave.0.NODE5.POWERLEVEL.Test_Powerlevel = undefined, index = 4, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 info Channel created: zwave.0.NODE5.POWERLEVEL = Normal, index = 4, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 debug value added: nodeID: 5 comClass: 115 value: {"value_id":"5-115-1-4","node_id":5,"class_id":115,"type":"list","genre":"system","instance":1,"index":4,"label":"Test Powerlevel","units":"dB","help":"Powe zwave.0 2019-11-06 19:31:20.684 info State created: zwave.0.NODE5.POWERLEVEL.Test_Node = undefined, index = 3, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 info Channel created: zwave.0.NODE5.POWERLEVEL = 0, index = 3, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 debug value added: nodeID: 5 comClass: 115 value: {"value_id":"5-115-1-3","node_id":5,"class_id":115,"type":"byte","genre":"system","instance":1,"index":3,"label":"Test Node","units":"","help":"Node to Perf zwave.0 2019-11-06 19:31:20.684 info State created: zwave.0.NODE5.POWERLEVEL.Set_Powerlevel = undefined, index = 2, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 info Channel created: zwave.0.NODE5.POWERLEVEL = undefined, index = 2, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 debug value added: nodeID: 5 comClass: 115 value: {"value_id":"5-115-1-2","node_id":5,"class_id":115,"type":"button","genre":"system","instance":1,"index":2,"label":"Set Powerlevel","units":"","help":"Apply zwave.0 2019-11-06 19:31:20.684 info State created: zwave.0.NODE5.POWERLEVEL.Timeout = undefined, index = 1, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 info Channel created: zwave.0.NODE5.POWERLEVEL = 0, index = 1, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 debug value added: nodeID: 5 comClass: 115 value: {"value_id":"5-115-1-1","node_id":5,"class_id":115,"type":"byte","genre":"system","instance":1,"index":1,"label":"Timeout","units":"seconds","help":"Timeout zwave.0 2019-11-06 19:31:20.684 info State created: zwave.0.NODE5.POWERLEVEL.Powerlevel = undefined, index = 0, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 info Channel created: zwave.0.NODE5.POWERLEVEL = Normal, index = 0, comClass = 115, instance = 1 zwave.0 2019-11-06 19:31:20.684 debug value added: nodeID: 5 comClass: 115 value: {"value_id":"5-115-1-0","node_id":5,"class_id":115,"type":"list","genre":"system","instance":1,"index":0,"label":"Powerlevel","units":"dB","help":"Output RF zwave.0 2019-11-06 19:31:20.684 info State created: zwave.0.NODE5.CENTRAL_SCENE.Scene_Reset_Timeout = undefined, index = 257, comClass = 91, instance = 1 zwave.0 2019-11-06 19:31:20.684 info Channel created: zwave.0.NODE5.CENTRAL_SCENE = 1000, index = 257, comClass = 91, instance = 1 zwave.0 2019-11-06 19:31:20.684 debug value added: nodeID: 5 comClass: 91 value: {"value_id":"5-91-1-257","node_id":5,"class_id":91,"type":"int","genre":"config","instance":1,"index":257,"label":"Scene Reset Timeout","units":"","help":"", zwave.0 2019-11-06 19:31:20.684 info State created: zwave.0.NODE5.CENTRAL_SCENE.Scene_Count_1 = undefined, index = 256, comClass = 91, instance = 1 zwave.0 2019-11-06 19:31:20.683 info Channel created: zwave.0.NODE5.CENTRAL_SCENE = 0, index = 256, comClass = 91, instance = 1 zwave.0 2019-11-06 19:31:20.683 debug value added: nodeID: 5 comClass: 91 value: {"value_id":"5-91-1-256","node_id":5,"class_id":91,"type":"int","genre":"user","instance":1,"index":256,"label":"Scene Count","units":"","help":"","read_only zwave.0 2019-11-06 19:31:20.683 info State created: zwave.0.NODE5.BATTERY.Battery_Level_1 = undefined, index = 0, comClass = 128, instance = 1 zwave.0 2019-11-06 19:31:20.683 info Channel created: zwave.0.NODE5.BATTERY = 100, index = 0, comClass = 128, instance = 1 zwave.0 2019-11-06 19:31:20.683 debug value added: nodeID: 5 comClass: 128 value: {"value_id":"5-128-1-0","node_id":5,"class_id":128,"type":"byte","genre":"user","instance":1,"index":0,"label":"Battery Level","units":"%","help":"Current B zwave.0 2019-11-06 19:31:20.683 info State created: zwave.0.NODE5.ZWAVE_PLUS_INFO.UserIcon = undefined, index = 2, comClass = 94, instance = 1 zwave.0 2019-11-06 19:31:20.683 info Channel created: zwave.0.NODE5.ZWAVE_PLUS_INFO = 0, index = 2, comClass = 94, instance = 1 zwave.0 2019-11-06 19:31:20.683 debug value added: nodeID: 5 comClass: 94 value: {"value_id":"5-94-1-2","node_id":5,"class_id":94,"type":"short","genre":"system","instance":1,"index":2,"label":"UserIcon","units":"","help":"Icon File to us zwave.0 2019-11-06 19:31:20.683 info State created: zwave.0.NODE5.ZWAVE_PLUS_INFO.InstallerIcon = undefined, index = 1, comClass = 94, instance = 1 zwave.0 2019-11-06 19:31:20.683 info Channel created: zwave.0.NODE5.ZWAVE_PLUS_INFO = 0, index = 1, comClass = 94, instance = 1 zwave.0 2019-11-06 19:31:20.683 debug value added: nodeID: 5 comClass: 94 value: {"value_id":"5-94-1-1","node_id":5,"class_id":94,"type":"short","genre":"system","instance":1,"index":1,"label":"InstallerIcon","units":"","help":"Icon File zwave.0 2019-11-06 19:31:20.683 info State created: zwave.0.NODE5.ZWAVE_PLUS_INFO.ZWave+_Version = undefined, index = 0, comClass = 94, instance = 1 zwave.0 2019-11-06 19:31:20.683 info Channel created: zwave.0.NODE5.ZWAVE_PLUS_INFO = 0, index = 0, comClass = 94, instance = 1 zwave.0 2019-11-06 19:31:20.682 debug value added: nodeID: 5 comClass: 94 value: {"value_id":"5-94-1-0","node_id":5,"class_id":94,"type":"byte","genre":"system","instance":1,"index":0,"label":"ZWave+ Version","units":"","help":"ZWave+ Ver zwave.0 2019-11-06 19:31:20.465 debug value changed: 5 comClass: 114 value: {"value_id":"5-114-1-2","node_id":5,"class_id":114,"type":"int","genre":"system","instance":1,"index":2,"label":"Latest Available Config File Revision","units":"" zwave.0 2019-11-06 19:31:20.373 info Create new device: zwave.0.NODE5[Popp & Co 009303 Battery Wall Controller] zwave.0 2019-11-06 19:31:20.372 debug node naming nodeID: 5 nodeinfo: {"manufacturer":"Popp & Co","manufacturerid":"0x0154","product":"009303 Battery Wall Controller","producttype":"0x0100","productid":"0x0101","type":"Basic Wall Controll zwave.0 2019-11-06 19:31:20.372 info State created: zwave.0.NODE5.CONFIGURATION.Send_unsolicited_Battery_Report_on_Wake_Up = undefined, index = 30, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.372 info Channel created: zwave.0.NODE5.CONFIGURATION = To same node as wake up notification (Default), index = 30, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.372 debug value added: nodeID: 5 comClass: 112 value: {"value_id":"5-112-1-30","node_id":5,"class_id":112,"type":"list","genre":"config","instance":1,"index":30,"label":"Send unsolicited Battery Report on Wake zwave.0 2019-11-06 19:31:20.372 info State created: zwave.0.NODE5.CONFIGURATION.Blocks_wakeup_even_when_wakeup_interval_is_set = undefined, index = 25, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.372 info Channel created: zwave.0.NODE5.CONFIGURATION = Wakeup is possible if configured accordingly. (Default), index = 25, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.371 debug value added: nodeID: 5 comClass: 112 value: {"value_id":"5-112-1-25","node_id":5,"class_id":112,"type":"list","genre":"config","instance":1,"index":25,"label":"Blocks wakeup even when wakeup interval zwave.0 2019-11-06 19:31:20.371 info State created: zwave.0.NODE5.CONFIGURATION.Invert_buttons = undefined, index = 22, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.371 info Channel created: zwave.0.NODE5.CONFIGURATION = No (default), index = 22, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.371 debug value added: nodeID: 5 comClass: 112 value: {"value_id":"5-112-1-22","node_id":5,"class_id":112,"type":"list","genre":"config","instance":1,"index":22,"label":"Invert buttons","units":"","help":"","re zwave.0 2019-11-06 19:31:20.371 info State created: zwave.0.NODE5.CONFIGURATION.Send_the_following_Switch_All_commands = undefined, index = 21, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.371 info Channel created: zwave.0.NODE5.CONFIGURATION = Switch off only (Default), index = 21, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.371 debug value added: nodeID: 5 comClass: 112 value: {"value_id":"5-112-1-21","node_id":5,"class_id":112,"type":"list","genre":"config","instance":1,"index":21,"label":"Send the following Switch All commands", zwave.0 2019-11-06 19:31:20.370 info State created: zwave.0.NODE5.CONFIGURATION.Command_to_Control_Group_D = undefined, index = 14, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.370 info Channel created: zwave.0.NODE5.CONFIGURATION = Central Scene to Gateway (Default), index = 14, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.370 debug value added: nodeID: 5 comClass: 112 value: {"value_id":"5-112-1-14","node_id":5,"class_id":112,"type":"list","genre":"config","instance":1,"index":14,"label":"Command to Control Group D","units":""," zwave.0 2019-11-06 19:31:20.370 info State created: zwave.0.NODE5.CONFIGURATION.Command_to_Control_Group_C = undefined, index = 13, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.370 info Channel created: zwave.0.NODE5.CONFIGURATION = Central Scene to Gateway (Default), index = 13, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.370 debug value added: nodeID: 5 comClass: 112 value: {"value_id":"5-112-1-13","node_id":5,"class_id":112,"type":"list","genre":"config","instance":1,"index":13,"label":"Command to Control Group C","units":""," zwave.0 2019-11-06 19:31:20.369 info State created: zwave.0.NODE5.CONFIGURATION.Command_to_Control_Group_B = undefined, index = 12, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.369 info Channel created: zwave.0.NODE5.CONFIGURATION = Central Scene to Gateway (Default), index = 12, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.369 debug value added: nodeID: 5 comClass: 112 value: {"value_id":"5-112-1-12","node_id":5,"class_id":112,"type":"list","genre":"config","instance":1,"index":12,"label":"Command to Control Group B","units":""," zwave.0 2019-11-06 19:31:20.369 info State created: zwave.0.NODE5.CONFIGURATION.Command_to_Control_Group_A = undefined, index = 11, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.369 info Channel created: zwave.0.NODE5.CONFIGURATION = Central Scene to Gateway (Default), index = 11, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.369 debug value added: nodeID: 5 comClass: 112 value: {"value_id":"5-112-1-11","node_id":5,"class_id":112,"type":"list","genre":"config","instance":1,"index":11,"label":"Command to Control Group A","units":""," zwave.0 2019-11-06 19:31:20.368 info State created: zwave.0.NODE5.CONFIGURATION.Button_2_and_4_pair_mode = undefined, index = 2, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.368 info Channel created: zwave.0.NODE5.CONFIGURATION = In pair without double clicks (Default), index = 2, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.368 debug value added: nodeID: 5 comClass: 112 value: {"value_id":"5-112-1-2","node_id":5,"class_id":112,"type":"list","genre":"config","instance":1,"index":2,"label":"Button 2 and 4 pair mode","units":"","help zwave.0 2019-11-06 19:31:20.368 info State created: zwave.0.NODE5.CONFIGURATION.Button_1_and_3_pair_mode = undefined, index = 1, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.368 info Channel created: zwave.0.NODE5.CONFIGURATION = In pair without double clicks (Default), index = 1, comClass = 112, instance = 1 zwave.0 2019-11-06 19:31:20.368 debug value added: nodeID: 5 comClass: 112 value: {"value_id":"5-112-1-1","node_id":5,"class_id":112,"type":"list","genre":"config","instance":1,"index":1,"label":"Button 1 and 3 pair mode","units":"","help zwave.0 2019-11-06 19:31:20.367 debug value changed: 5 comClass: 114 value: {"value_id":"5-114-1-0","node_id":5,"class_id":114,"type":"int","genre":"system","instance":1,"index":0,"label":"Loaded Config Revision","units":"","help":"Revisi zwave.0 2019-11-06 19:31:20.364 debug value changed: 5 comClass: 114 value: {"value_id":"5-114-1-1","node_id":5,"class_id":114,"type":"int","genre":"system","instance":1,"index":1,"label":"Config File Revision","units":"","help":"Revision zwave.0 2019-11-06 19:31:15.157 info State created: zwave.0.NODE5.MANUFACTURER_SPECIFIC.Serial_Number = undefined, index = 4, comClass = 114, instance = 1 zwave.0 2019-11-06 19:31:15.157 info Channel created: zwave.0.NODE5.MANUFACTURER_SPECIFIC = , index = 4, comClass = 114, instance = 1 zwave.0 2019-11-06 19:31:15.156 debug value added: nodeID: 5 comClass: 114 value: {"value_id":"5-114-1-4","node_id":5,"class_id":114,"type":"string","genre":"system","instance":1,"index":4,"label":"Serial Number","units":"","help":"Device zwave.0 2019-11-06 19:31:15.156 info State created: zwave.0.NODE5.MANUFACTURER_SPECIFIC.Device_ID = undefined, index = 3, comClass = 114, instance = 1 zwave.0 2019-11-06 19:31:15.156 info Channel created: zwave.0.NODE5.MANUFACTURER_SPECIFIC = , index = 3, comClass = 114, instance = 1 zwave.0 2019-11-06 19:31:15.156 debug value added: nodeID: 5 comClass: 114 value: {"value_id":"5-114-1-3","node_id":5,"class_id":114,"type":"string","genre":"system","instance":1,"index":3,"label":"Device ID","units":"","help":"Manufactur zwave.0 2019-11-06 19:31:15.156 info State created: zwave.0.NODE5.MANUFACTURER_SPECIFIC.Latest_Available_Config_File_Revision = undefined, index = 2, comClass = 114, instance = 1 zwave.0 2019-11-06 19:31:15.156 info Channel created: zwave.0.NODE5.MANUFACTURER_SPECIFIC = 0, index = 2, comClass = 114, instance = 1 zwave.0 2019-11-06 19:31:15.156 debug value added: nodeID: 5 comClass: 114 value: {"value_id":"5-114-1-2","node_id":5,"class_id":114,"type":"int","genre":"system","instance":1,"index":2,"label":"Latest Available Config File Revision","uni zwave.0 2019-11-06 19:31:15.156 info State created: zwave.0.NODE5.MANUFACTURER_SPECIFIC.Config_File_Revision = undefined, index = 1, comClass = 114, instance = 1 zwave.0 2019-11-06 19:31:15.156 info Channel created: zwave.0.NODE5.MANUFACTURER_SPECIFIC = 0, index = 1, comClass = 114, instance = 1 zwave.0 2019-11-06 19:31:15.156 debug value added: nodeID: 5 comClass: 114 value: {"value_id":"5-114-1-1","node_id":5,"class_id":114,"type":"int","genre":"system","instance":1,"index":1,"label":"Config File Revision","units":"","help":"Re zwave.0 2019-11-06 19:31:15.156 info State created: zwave.0.NODE5.MANUFACTURER_SPECIFIC.Loaded_Config_Revision = undefined, index = 0, comClass = 114, instance = 1 zwave.0 2019-11-06 19:31:15.155 info Channel created: zwave.0.NODE5.MANUFACTURER_SPECIFIC = 0, index = 0, comClass = 114, instance = 1 zwave.0 2019-11-06 19:31:15.155 debug value added: nodeID: 5 comClass: 114 value: {"value_id":"5-114-1-0","node_id":5,"class_id":114,"type":"int","genre":"system","instance":1,"index":0,"label":"Loaded Config Revision","units":"","help":" zwave.0 2019-11-06 19:31:15.153 debug value changed: 5 comClass: 132 value: {"value_id":"5-132-1-0","node_id":5,"class_id":132,"type":"int","genre":"system","instance":1,"index":0,"label":"Wake-up Interval","units":"Seconds","help":"How o zwave.0 2019-11-06 19:31:14.764 debug node5: node awake zwave.0 2019-11-06 19:31:04.335 debug node5: node sleep zwave.0 2019-11-06 19:31:02.743 debug value changed: 9 comClass: 50 value: {"value_id":"9-50-3-256","node_id":9,"class_id":50,"type":"bool","genre":"user","instance":3,"index":256,"label":"Instance 3: Exporting","units":"","help":"","read zwave.0 2019-11-06 19:31:02.739 debug value changed: 9 comClass: 50 value: {"value_id":"9-50-3-2","node_id":9,"class_id":50,"type":"decimal","genre":"user","instance":3,"index":2,"label":"Instance 3: Electric - W","units":"W","help":"","r zwave.0 2019-11-06 19:31:01.222 info State created: zwave.0.NODE5.WAKE_UP.Wake-up_Interval = undefined, index = 0, comClass = 132, instance = 1 zwave.0 2019-11-06 19:31:01.222 info Channel created: zwave.0.NODE5.WAKE_UP = 604800, index = 0, comClass = 132, instance = 1 zwave.0 2019-11-06 19:31:01.218 debug value changed: 5 comClass: 132 value: {"value_id":"5-132-1-0","node_id":5,"class_id":132,"type":"int","genre":"system","instance":1,"index":0,"label":"Wake-up Interval","units":"Seconds","help":"How o zwave.0 2019-11-06 19:31:00.157 debug node5: node awake zwave.0 2019-11-06 19:30:52.708 debug value changed: 14 comClass: 49 value: {"value_id":"14-49-1-3","node_id":14,"class_id":49,"type":"decimal","genre":"user","instance":1,"index":3,"label":"Illuminance","units":"Lux","help":"Luminance Se zwave.0 2019-11-06 19:30:35.748 debug value changed: 9 comClass: 50 value: {"value_id":"9-50-2-256","node_id":9,"class_id":50,"type":"bool","genre":"user","instance":2,"index":256,"label":"Instance 2: Exporting","units":"","help":"","read zwave.0 2019-11-06 19:30:35.747 debug value changed: 9 comClass: 50 value: {"value_id":"9-50-2-2","node_id":9,"class_id":50,"type":"decimal","genre":"user","instance":2,"index":2,"label":"Instance 2: Electric - W","units":"W","help":"","r zwave.0 2019-11-06 19:30:33.691 debug node5: node sleep zwave.0 2019-11-06 19:30:30.765 debug value changed: 9 comClass: 50 value: {"value_id":"9-50-3-256","node_id":9,"class_id":50,"type":"bool","genre":"user","instance":3,"index":256,"label":"Instance 3: Exporting","units":"","help":"","read zwave.0 2019-11-06 19:30:30.761 debug value changed: 9 comClass: 50 value: {"value_id":"9-50-3-2","node_id":9,"class_id":50,"type":"decimal","genre":"user","instance":3,"index":2,"label":"Instance 3: Electric - W","units":"W","help":"","r zwave.0 2019-11-06 19:30:29.436 debug node5: node awake zwave.0 2019-11-06 19:30:17.751 debug value changed: 9 comClass: 50 value: {"value_id":"9-50-2-256","node_id":9,"class_id":50,"type":"bool","genre":"user","instance":2,"index":256,"label":"Instance 2: Exporting","units":"","help":"","read zwave.0 2019-11-06 19:30:17.751 debug value changed: 9 comClass: 50 value: {"value_id":"9-50-2-2","node_id":9,"class_id":50,"type":"decimal","genre":"user","instance":2,"index":2,"label":"Instance 2: Electric - W","units":"W","help":"","r zwave.0 2019-11-06 19:29:49.749 debug value changed: 9 comClass: 50 value: {"value_id":"9-50-3-256","node_id":9,"class_id":50,"type":"bool","genre":"user","instance":3,"index":256,"label":"Instance 3: Exporting","units":"","help":"","read zwave.0 2019-11-06 19:29:49.749 debug value changed: 9 comClass: 50 value: {"value_id":"9-50-3-2","node_id":9,"class_id":50,"type":"decimal","genre":"user","instance":3,"index":2,"label":"Instance 3: Electric - W","units":"W","help":"","r zwave.0 2019-11-06 19:29:46.647 debug node5: node sleep zwave.0 2019-11-06 19:29:46.646 debug node5: nop zwave.0 2019-11-06 19:29:45.752 debug value changed: 9 comClass: 50 value: {"value_id":"9-50-3-256","node_id":9,"class_id":50,"type":"bool","genre":"user","instance":3,"index":256,"label":"Instance 3: Exporting","units":"","help":"","read zwave.0 2019-11-06 19:29:45.750 debug value changed: 9 comClass: 50 value: {"value_id":"9-50-3-2","node_id":9,"class_id":50,"type":"decimal","genre":"user","instance":3,"index":2,"label":"Instance 3: Electric - W","units":"W","help":"","r zwave.0 2019-11-06 19:29:42.527 debug value added: nodeID: 5 comClass: 32 value: {"value_id":"5-32-1-0","node_id":5,"class_id":32,"type":"byte","genre":"basic","instance":1,"index":0,"label":"Basic","units":"","help":"Basic status of the zwave.0 2019-11-06 19:29:42.527 debug value added: nodeID: 5 comClass: 132 value: {"value_id":"5-132-1-0","node_id":5,"class_id":132,"type":"int","genre":"system","instance":1,"index":0,"label":"Wake-up Interval","units":"Seconds","help": zwave.0 2019-11-06 19:29:42.526 info Update zwave.0.NODE5 zwave.0 2019-11-06 19:29:42.526 debug node added for 5 found zwave.0 2019-11-06 19:29:42.526 info node removed: 5 zwave.0 2019-11-06 19:29:42.526 debug value removed: 5 comClass: 132 instance: 1 index: 0 zwave.0 2019-11-06 19:29:42.526 debug value removed: 5 comClass: 32 instance: 1 index: 0 zwave.0 2019-11-06 19:29:42.526 debug sendTo "refreshNodeInfo" to system.adapter.admin.0 from system.adapter.zwave.0 zwave.0 2019-11-06 19:29:42.525 info Execute refreshNodeInfo for 5zwave.0 2019-11-06 19:17:40.801 info starting. Version 1.6.3 in /opt/iobroker/node_modules/iobroker.zwave, node: v10.17.0 host.rockpro64 2019-11-06 19:17:39.968 info instance system.adapter.zwave.0 started with pid 7538 host.rockpro64 2019-11-06 19:17:39.599 info instance system.adapter.zwave.0 terminated with code null ()Die OZW Loddatei bleibt leer. :-(
Ist die Adapter Installation doch noch nicht so sauber und stabil, wie ich dachte?immerhin habe ich anscheinend das Logging Problem gelöst - ich glaube, vor der eben erfolgten Neuinstallation von Adapter und Instanz, hat der Haken für das ZWave-Logging gefehlt. Kann ich jetzt nicht mehr mit Sicherheit sagen.
Die Installation ist sauber durchgelaufen.
Die Anforderung von "info aktualisieren" unterstützt von einem manuellen Absenden des NIF am Taster bringt mich wieder dahin, wo ich vorher auch schon war - zu CENTRAL_SCENE.Scene_Count_1 und CENTRAL_SCENE.Scene_Reset_Timeout
Mehr ist da nach wie vor nicht.Immerhin kommen jetzt Infos vom Taster im iobroker an.
Im Log findet sich2019-11-07 19:30:54.529 Info, Node005, Received Central Scene set from node 5: scene id=4 with key Attribute 0. Sending event notification. 2019-11-07 19:30:54.529 Warning, Node005, No ValueID created for Scene 4 2019-11-07 19:30:54.529 Warning, Node005, CommandClass COMMAND_CLASS_CENTRAL_SCENE HandlerMsg Returned False 2019-11-07 19:31:03.204 Detail, Node005, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x5b, 0x03, 0x06, 0x00, 0x04, 0xaa 2019-11-07 19:31:03.205 Detail, 2019-11-07 19:31:03.205 Info, Node005, Received Central Scene set from node 5: scene id=4 with key Attribute 0. Sending event notification. 2019-11-07 19:31:03.205 Warning, Node005, No ValueID created for Scene 4 2019-11-07 19:31:03.205 Warning, Node005, CommandClass COMMAND_CLASS_CENTRAL_SCENE HandlerMsg Returned False 2019-11-07 19:31:07.124 Detail, Node005, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x5b, 0x03, 0x07, 0x00, 0x03, 0xac 2019-11-07 19:31:07.124 Detail, 2019-11-07 19:31:07.124 Info, Node005, Received Central Scene set from node 5: scene id=3 with key Attribute 0. Sending event notification. 2019-11-07 19:31:07.125 Warning, Node005, No ValueID created for Scene 3 2019-11-07 19:31:07.125 Warning, Node005, CommandClass COMMAND_CLASS_CENTRAL_SCENE HandlerMsg Returned FalseIch lese daraus, das bei unterschiedlichen genutzten Tastern (es sind insgesamt vier auf dem zme_wallc-s verbaut) diese Information im System ankommt, aber nicht korrekt wegsortiert werden kann, weil die ValueID fehlt.
Wie kann ich das los werden?
-
immerhin habe ich anscheinend das Logging Problem gelöst - ich glaube, vor der eben erfolgten Neuinstallation von Adapter und Instanz, hat der Haken für das ZWave-Logging gefehlt. Kann ich jetzt nicht mehr mit Sicherheit sagen.
Die Installation ist sauber durchgelaufen.
Die Anforderung von "info aktualisieren" unterstützt von einem manuellen Absenden des NIF am Taster bringt mich wieder dahin, wo ich vorher auch schon war - zu CENTRAL_SCENE.Scene_Count_1 und CENTRAL_SCENE.Scene_Reset_Timeout
Mehr ist da nach wie vor nicht.Immerhin kommen jetzt Infos vom Taster im iobroker an.
Im Log findet sich2019-11-07 19:30:54.529 Info, Node005, Received Central Scene set from node 5: scene id=4 with key Attribute 0. Sending event notification. 2019-11-07 19:30:54.529 Warning, Node005, No ValueID created for Scene 4 2019-11-07 19:30:54.529 Warning, Node005, CommandClass COMMAND_CLASS_CENTRAL_SCENE HandlerMsg Returned False 2019-11-07 19:31:03.204 Detail, Node005, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x5b, 0x03, 0x06, 0x00, 0x04, 0xaa 2019-11-07 19:31:03.205 Detail, 2019-11-07 19:31:03.205 Info, Node005, Received Central Scene set from node 5: scene id=4 with key Attribute 0. Sending event notification. 2019-11-07 19:31:03.205 Warning, Node005, No ValueID created for Scene 4 2019-11-07 19:31:03.205 Warning, Node005, CommandClass COMMAND_CLASS_CENTRAL_SCENE HandlerMsg Returned False 2019-11-07 19:31:07.124 Detail, Node005, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x5b, 0x03, 0x07, 0x00, 0x03, 0xac 2019-11-07 19:31:07.124 Detail, 2019-11-07 19:31:07.124 Info, Node005, Received Central Scene set from node 5: scene id=3 with key Attribute 0. Sending event notification. 2019-11-07 19:31:07.125 Warning, Node005, No ValueID created for Scene 3 2019-11-07 19:31:07.125 Warning, Node005, CommandClass COMMAND_CLASS_CENTRAL_SCENE HandlerMsg Returned FalseIch lese daraus, das bei unterschiedlichen genutzten Tastern (es sind insgesamt vier auf dem zme_wallc-s verbaut) diese Information im System ankommt, aber nicht korrekt wegsortiert werden kann, weil die ValueID fehlt.
Wie kann ich das los werden?
-
Hat keiner eine Idee? Das Problem besteht immer noch.
Kann ein Update auf die 1.7 Version helfen?
Gruß
Andreas -
@arteck hab ich dann mal gemacht; Problem mit den ZME_WALLC-S ist nicht besser geworden.
Außerdem ist eine Meldung über vulnerabilites aufgelaufen (Zeile 3), die ich nicht weg bekommen. Muss ich?iobroker 2019-11-12 20:47:59.810 info got /opt/iobroker/node_modules/iobroker.zwave/admin iobroker 2019-11-12 20:47:59.699 info run `npm audit fix` to fix them, or `npm audit` for details iobroker 2019-11-12 20:47:59.699 info found 80 vulnerabilities (49 low, 31 high) iobroker 2019-11-12 20:47:59.699 info removed 5 packages, updated 1 package and audited 8206 packages in 31.441s iobroker 2019-11-12 20:47:59.699 info + iobroker.zwave@1.7.0 iobroker 2019-11-12 20:47:59.699 info npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperatu iobroker 2019-11-12 20:47:57.551 info ---> find /usr/local/etc/ -name 'manufacturer_specific.xml' -exec grep -H 'Revision="52"' '{}' \; 2>/dev/null iobroker 2019-11-12 20:47:57.550 info manufacturer_specific.xml found in /usr/local/etc/openzwave/manufacturer_specific.xml iobroker 2019-11-12 20:47:57.495 info ---> find /usr/local/etc/ -name 'manufacturer_specific.xml' 2>/dev/null iobroker 2019-11-12 20:47:57.166 info > node lib/preinstall.js iobroker 2019-11-12 20:47:57.166 info > iobroker.zwave@1.7.0 preinstall /opt/iobroker/node_modules/iobroker.zwave iobroker 2019-11-12 20:47:26.935 info npm install https://github.com/ioBroker/ioBroker.zwave/tarball/master --production --save --prefix "/opt/iobroker" (System call) iobroker 2019-11-12 20:47:26.270 info install https://github.com/ioBroker/ioBroker.zwave/tarball/master iobroker 2019-11-12 20:47:25.713 info url "https://github.com/ioBroker/ioBroker.zwave/tarball/master" zwave --debug -
@arteck hab ich dann mal gemacht; Problem mit den ZME_WALLC-S ist nicht besser geworden.
Außerdem ist eine Meldung über vulnerabilites aufgelaufen (Zeile 3), die ich nicht weg bekommen. Muss ich?iobroker 2019-11-12 20:47:59.810 info got /opt/iobroker/node_modules/iobroker.zwave/admin iobroker 2019-11-12 20:47:59.699 info run `npm audit fix` to fix them, or `npm audit` for details iobroker 2019-11-12 20:47:59.699 info found 80 vulnerabilities (49 low, 31 high) iobroker 2019-11-12 20:47:59.699 info removed 5 packages, updated 1 package and audited 8206 packages in 31.441s iobroker 2019-11-12 20:47:59.699 info + iobroker.zwave@1.7.0 iobroker 2019-11-12 20:47:59.699 info npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperatu iobroker 2019-11-12 20:47:57.551 info ---> find /usr/local/etc/ -name 'manufacturer_specific.xml' -exec grep -H 'Revision="52"' '{}' \; 2>/dev/null iobroker 2019-11-12 20:47:57.550 info manufacturer_specific.xml found in /usr/local/etc/openzwave/manufacturer_specific.xml iobroker 2019-11-12 20:47:57.495 info ---> find /usr/local/etc/ -name 'manufacturer_specific.xml' 2>/dev/null iobroker 2019-11-12 20:47:57.166 info > node lib/preinstall.js iobroker 2019-11-12 20:47:57.166 info > iobroker.zwave@1.7.0 preinstall /opt/iobroker/node_modules/iobroker.zwave iobroker 2019-11-12 20:47:26.935 info npm install https://github.com/ioBroker/ioBroker.zwave/tarball/master --production --save --prefix "/opt/iobroker" (System call) iobroker 2019-11-12 20:47:26.270 info install https://github.com/ioBroker/ioBroker.zwave/tarball/master iobroker 2019-11-12 20:47:25.713 info url "https://github.com/ioBroker/ioBroker.zwave/tarball/master" zwave --debug@SirHenri noch ein zwei Sachen, die Auffallen
- Meldung aus dem log:
zwave.0 2019-11-12 21:28:15.550 error Unknown command: getNumberOfInstancesist öfter nacheinander im log zu finden - problematisch?
Zum Anderen ist in den Abbildungen zu den adapter settings z.B. auf
https://www.npmjs.com/package/iobroker.zwave
die Möglichkeit abgebildet bei "Force objects re-init" einen Haken zu setzten - den gibt's bei mir nicht
-
@SirHenri noch ein zwei Sachen, die Auffallen
- Meldung aus dem log:
zwave.0 2019-11-12 21:28:15.550 error Unknown command: getNumberOfInstancesist öfter nacheinander im log zu finden - problematisch?
Zum Anderen ist in den Abbildungen zu den adapter settings z.B. auf
https://www.npmjs.com/package/iobroker.zwave
die Möglichkeit abgebildet bei "Force objects re-init" einen Haken zu setzten - den gibt's bei mir nicht
@SirHenri Alles noch mal auf Anfang;
Instanz gelöscht; Adapter gelöscht
Installation der 1.7.0 aus dem Git
Adapter startet nicht sauber:host.rockpro64 2019-11-14 07:16:17.512 info Restart adapter system.adapter.zwave.0 because enabled host.rockpro64 2019-11-14 07:16:17.512 error instance system.adapter.zwave.0 terminated with code null () host.rockpro64 2019-11-14 07:16:17.511 warn instance system.adapter.zwave.0 terminated due to SIGSEGV host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Decoder.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Manager.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.zwave/main.js:536:51) host.rockpro64 2019-11-14 07:16:17.510 error Caught by controller[0]: at JSON.parse (<anonymous>) host.rockpro64 2019-11-14 07:16:17.509 error Caught by controller[0]: SyntaxError: Unexpected end of JSON input zwave.0 2019-11-14 07:16:16.506 error SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.zwave/main.js:536:51) at Socket.onack (/opt/iobroker/node_m zwave.0 2019-11-14 07:16:16.503 error uncaught exception: Unexpected end of JSON input zwave.0 2019-11-14 07:16:14.745 info starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.zwave, node: v10.17.0vulnerabilities (49 low, 31 high) bestehen weiter
interessanter Weise sieht die Geräteübersicht anders aus, als bei der letzten 1.7. Installation
Ampel bestenfalls gelb
:thinking_face: -
@SirHenri Alles noch mal auf Anfang;
Instanz gelöscht; Adapter gelöscht
Installation der 1.7.0 aus dem Git
Adapter startet nicht sauber:host.rockpro64 2019-11-14 07:16:17.512 info Restart adapter system.adapter.zwave.0 because enabled host.rockpro64 2019-11-14 07:16:17.512 error instance system.adapter.zwave.0 terminated with code null () host.rockpro64 2019-11-14 07:16:17.511 warn instance system.adapter.zwave.0 terminated due to SIGSEGV host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Decoder.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Manager.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9) host.rockpro64 2019-11-14 07:16:17.511 error Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.zwave/main.js:536:51) host.rockpro64 2019-11-14 07:16:17.510 error Caught by controller[0]: at JSON.parse (<anonymous>) host.rockpro64 2019-11-14 07:16:17.509 error Caught by controller[0]: SyntaxError: Unexpected end of JSON input zwave.0 2019-11-14 07:16:16.506 error SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.zwave/main.js:536:51) at Socket.onack (/opt/iobroker/node_m zwave.0 2019-11-14 07:16:16.503 error uncaught exception: Unexpected end of JSON input zwave.0 2019-11-14 07:16:14.745 info starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.zwave, node: v10.17.0vulnerabilities (49 low, 31 high) bestehen weiter
interessanter Weise sieht die Geräteübersicht anders aus, als bei der letzten 1.7. Installation
Ampel bestenfalls gelb
:thinking_face:@SirHenri das könnte ein Bug sein, dazu bräuchte ich bitte einen GitHub Eintrag
-
@SirHenri noch ein zwei Sachen, die Auffallen
- Meldung aus dem log:
zwave.0 2019-11-12 21:28:15.550 error Unknown command: getNumberOfInstancesist öfter nacheinander im log zu finden - problematisch?
Zum Anderen ist in den Abbildungen zu den adapter settings z.B. auf
https://www.npmjs.com/package/iobroker.zwave
die Möglichkeit abgebildet bei "Force objects re-init" einen Haken zu setzten - den gibt's bei mir nicht
@SirHenri said in Probleme nach ZWave Update mit ZME_WALLC-S:
ist öfter nacheinander im log zu finden - problematisch?
Da passt die Version des Admin Frontend nicht mit dem Backend zusammen. Der Adapter wurde nicht korrekt installiert.
Zum Anderen ist in den Abbildungen zu den adapter settings z.B. auf
https://www.npmjs.com/package/iobroker.zwave
die Möglichkeit abgebildet bei "Force objects re-init" einen Haken zu setzten - den gibt's bei mir nichtKann man ignorieren, ist noch eine alte Abbildung.
-
@SirHenri das könnte ein Bug sein, dazu bräuchte ich bitte einen GitHub Eintrag
@cburghardt mach ich gerne fertig, habe ich aber noch nie gemacht
muss jetzt erst mal los, melde mich heute Nachmittag - und werde dann wohl erst mal ein Account im Git anlegen?
-
@SirHenri das könnte ein Bug sein, dazu bräuchte ich bitte einen GitHub Eintrag
@cburghardt ist erledigt
-
@cburghardt ist erledigt
Ich wollte mal einen Zwischenstand mitteilen - das Problem besteht weiter.
Da die Version 1.7.1 bei mir immer noch Fehler erzeugt, bin ich zurück auf die 1.6. Den Tatster hatte ich 3x aus dem System vollständig raus (in beiden Adapterversionen; er hat 3x eine neue ID bekommen). In allen drei Versuchen habe ich nur die schon beschriebenen states erzeugt bekommen.
Weitere Veränderungen: neue Batterie, USB Dongle mit Verlängerung versorgt, um evt. Abschirmung direkt am Rechner auszuschließen.
Der Abstand zwischen Dongle und Taster beträgt bei Inklusion Exklusion ca. 1,5m.
Das Log sieht so aus, als wenn der Taster sich zu früh schlafen legt. Kann ich das unterbinden?
Hat irgendjemand eine Idee, welche(n) weiteren Parameter ich verändern kann?2019-11-21 12:16:50.585 Info, Node021, Response RTT 2289 Average Response RTT 1980 2019-11-21 12:16:50.585 Info, Node021, Opening config param file /usr/local/etc/openzwave/popp/009303.xml 2019-11-21 12:16:50.589 Info, Node021, (112 - COMMAND_CLASS_CONFIGURATION) - Compatibility Flags: 2019-11-21 12:16:50.589 Info, Node021, (112 - COMMAND_CLASS_CONFIGURATION) - State Flags: 2019-11-21 12:16:50.589 Info, Node021, CCVersion: 1 2019-11-21 12:16:50.589 Info, Node021, InNif: true 2019-11-21 12:16:50.589 Info, Node021, StaticRequests: 5 2019-11-21 12:16:50.590 Warning, Missing default list value or vindex from xml configuration: node 21, class 0x70, instance 1, index 21 2019-11-21 12:16:50.590 Warning, Missing default list value or vindex from xml configuration: node 21, class 0x70, instance 1, index 22 2019-11-21 12:16:50.591 Info, Node021, (133 - COMMAND_CLASS_ASSOCIATION) - Compatibility Flags: 2019-11-21 12:16:50.591 Info, Node021, (133 - COMMAND_CLASS_ASSOCIATION) - State Flags: 2019-11-21 12:16:50.591 Info, Node021, CCVersion: 1 2019-11-21 12:16:50.591 Info, Node021, InNif: true 2019-11-21 12:16:50.591 Info, Node021, StaticRequests: 7 2019-11-21 12:16:50.592 Info, Node021, Received manufacturer specific report from node 21: Manufacturer=Popp & Co, Product=009303 Battery Wall Controller 2019-11-21 12:16:50.592 Info, Node021, Node Identity Codes: 0154:0100:0101 2019-11-21 12:16:50.592 Detail, Node021, Notification: Group 2019-11-21 12:16:50.592 Detail, Node021, Notification: Group 2019-11-21 12:16:50.593 Detail, Node021, Notification: Group 2019-11-21 12:16:50.593 Detail, Node021, Notification: Group 2019-11-21 12:16:50.593 Detail, Node021, Notification: Group 2019-11-21 12:16:50.593 Detail, Node021, Notification: NodeNaming 2019-11-21 12:16:58.296 Error, Node021, ERROR: Dropping command, expected response not received after 1 attempt(s) 2019-11-21 12:16:58.296 Detail, Node021, Removing current message 2019-11-21 12:16:58.297 Detail, Node021, Notification: Notification - TimeOut 2019-11-21 12:16:58.297 Detail, 2019-11-21 12:16:58.297 Info, Node021, Sending (Query) message (Callback ID=0x40, Expected Reply=0x04) - MultiInstanceCmd_Get (Node=21): 0x01, 0x0a, 0x00, 0x13, 0x15, 0x03, 0x60, 0x04, 0x26, 0x25, 0x40, 0xd7 2019-11-21 12:16:58.297 Info, Node021, Encrypted Flag is 0 2019-11-21 12:16:58.306 Detail, Node021, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8 2019-11-21 12:16:58.307 Detail, Node021, ZW_SEND_DATA delivered to Z-Wave stack 2019-11-21 12:16:58.491 Detail, Node021, Received: 0x01, 0x07, 0x00, 0x13, 0x40, 0x00, 0x00, 0x13, 0xb8 2019-11-21 12:16:58.491 Detail, Node021, ZW_SEND_DATA Request with callback ID 0x40 received (expected 0x40) 2019-11-21 12:16:58.491 Info, Node021, Request RTT 193 Average Request RTT 112 2019-11-21 12:16:58.491 Detail, Node021, Expected callbackId was received 2019-11-21 12:17:08.298 Error, Node021, ERROR: Dropping command, expected response not received after 1 attempt(s) 2019-11-21 12:17:08.299 Detail, Node021, Removing current message 2019-11-21 12:17:08.299 Detail, Node021, Notification: Notification - TimeOut 2019-11-21 12:17:08.299 Detail, 2019-11-21 12:17:08.299 Info, Node021, Sending (Query) message (Callback ID=0x41, Expected Reply=0x04) - MultiInstanceCmd_Get (Node=21): 0x01, 0x0a, 0x00, 0x13, 0x15, 0x03, 0x60, 0x04, 0x27, 0x25, 0x41, 0xd7 2019-11-21 12:17:08.299 Info, Node021, Encrypted Flag is 0 2019-11-21 12:17:08.307 Detail, Node021, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8 2019-11-21 12:17:08.308 Detail, Node021, ZW_SEND_DATA delivered to Z-Wave stack 2019-11-21 12:17:08.482 Detail, Node021, Received: 0x01, 0x07, 0x00, 0x13, 0x41, 0x00, 0x00, 0x12, 0xb8 2019-11-21 12:17:08.483 Detail, Node021, ZW_SEND_DATA Request with callback ID 0x41 received (expected 0x41) 2019-11-21 12:17:08.483 Info, Node021, Request RTT 183 Average Request RTT 147 2019-11-21 12:17:08.483 Detail, Node021, Expected callbackId was received 2019-11-21 12:17:18.300 Error, Node021, ERROR: Dropping command, expected response not received after 1 attempt(s) 2019-11-21 12:17:18.300 Detail, Node021, Removing current message 2019-11-21 12:17:18.300 Detail, Node021, Notification: Notification - TimeOut 2019-11-21 12:17:18.300 Detail, 2019-11-21 12:17:18.300 Info, Node021, Sending (Query) message (Callback ID=0x42, Expected Reply=0x04) - MultiInstanceCmd_Get (Node=21): 0x01, 0x0a, 0x00, 0x13, 0x15, 0x03, 0x60, 0x04, 0x2b, 0x25, 0x42, 0xd8 2019-11-21 12:17:18.301 Info, Node021, Encrypted Flag is 0 2019-11-21 12:17:18.309 Detail, Node021, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8 2019-11-21 12:17:18.309 Detail, Node021, ZW_SEND_DATA delivered to Z-Wave stack 2019-11-21 12:17:22.716 Detail, Node021, Received: 0x01, 0x07, 0x00, 0x13, 0x42, 0x01, 0x01, 0xb9, 0x10 2019-11-21 12:17:22.717 Detail, Node021, ZW_SEND_DATA Request with callback ID 0x42 received (expected 0x42) 2019-11-21 12:17:22.717 Info, Node021, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep. 2019-11-21 12:17:22.717 Info, Node021, Node 21 has been marked as asleep 2019-11-21 12:17:22.717 Info, Node021, Node not responding - moving message -
Ich wollte mal einen Zwischenstand mitteilen - das Problem besteht weiter.
Da die Version 1.7.1 bei mir immer noch Fehler erzeugt, bin ich zurück auf die 1.6. Den Tatster hatte ich 3x aus dem System vollständig raus (in beiden Adapterversionen; er hat 3x eine neue ID bekommen). In allen drei Versuchen habe ich nur die schon beschriebenen states erzeugt bekommen.
Weitere Veränderungen: neue Batterie, USB Dongle mit Verlängerung versorgt, um evt. Abschirmung direkt am Rechner auszuschließen.
Der Abstand zwischen Dongle und Taster beträgt bei Inklusion Exklusion ca. 1,5m.
Das Log sieht so aus, als wenn der Taster sich zu früh schlafen legt. Kann ich das unterbinden?
Hat irgendjemand eine Idee, welche(n) weiteren Parameter ich verändern kann?2019-11-21 12:16:50.585 Info, Node021, Response RTT 2289 Average Response RTT 1980 2019-11-21 12:16:50.585 Info, Node021, Opening config param file /usr/local/etc/openzwave/popp/009303.xml 2019-11-21 12:16:50.589 Info, Node021, (112 - COMMAND_CLASS_CONFIGURATION) - Compatibility Flags: 2019-11-21 12:16:50.589 Info, Node021, (112 - COMMAND_CLASS_CONFIGURATION) - State Flags: 2019-11-21 12:16:50.589 Info, Node021, CCVersion: 1 2019-11-21 12:16:50.589 Info, Node021, InNif: true 2019-11-21 12:16:50.589 Info, Node021, StaticRequests: 5 2019-11-21 12:16:50.590 Warning, Missing default list value or vindex from xml configuration: node 21, class 0x70, instance 1, index 21 2019-11-21 12:16:50.590 Warning, Missing default list value or vindex from xml configuration: node 21, class 0x70, instance 1, index 22 2019-11-21 12:16:50.591 Info, Node021, (133 - COMMAND_CLASS_ASSOCIATION) - Compatibility Flags: 2019-11-21 12:16:50.591 Info, Node021, (133 - COMMAND_CLASS_ASSOCIATION) - State Flags: 2019-11-21 12:16:50.591 Info, Node021, CCVersion: 1 2019-11-21 12:16:50.591 Info, Node021, InNif: true 2019-11-21 12:16:50.591 Info, Node021, StaticRequests: 7 2019-11-21 12:16:50.592 Info, Node021, Received manufacturer specific report from node 21: Manufacturer=Popp & Co, Product=009303 Battery Wall Controller 2019-11-21 12:16:50.592 Info, Node021, Node Identity Codes: 0154:0100:0101 2019-11-21 12:16:50.592 Detail, Node021, Notification: Group 2019-11-21 12:16:50.592 Detail, Node021, Notification: Group 2019-11-21 12:16:50.593 Detail, Node021, Notification: Group 2019-11-21 12:16:50.593 Detail, Node021, Notification: Group 2019-11-21 12:16:50.593 Detail, Node021, Notification: Group 2019-11-21 12:16:50.593 Detail, Node021, Notification: NodeNaming 2019-11-21 12:16:58.296 Error, Node021, ERROR: Dropping command, expected response not received after 1 attempt(s) 2019-11-21 12:16:58.296 Detail, Node021, Removing current message 2019-11-21 12:16:58.297 Detail, Node021, Notification: Notification - TimeOut 2019-11-21 12:16:58.297 Detail, 2019-11-21 12:16:58.297 Info, Node021, Sending (Query) message (Callback ID=0x40, Expected Reply=0x04) - MultiInstanceCmd_Get (Node=21): 0x01, 0x0a, 0x00, 0x13, 0x15, 0x03, 0x60, 0x04, 0x26, 0x25, 0x40, 0xd7 2019-11-21 12:16:58.297 Info, Node021, Encrypted Flag is 0 2019-11-21 12:16:58.306 Detail, Node021, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8 2019-11-21 12:16:58.307 Detail, Node021, ZW_SEND_DATA delivered to Z-Wave stack 2019-11-21 12:16:58.491 Detail, Node021, Received: 0x01, 0x07, 0x00, 0x13, 0x40, 0x00, 0x00, 0x13, 0xb8 2019-11-21 12:16:58.491 Detail, Node021, ZW_SEND_DATA Request with callback ID 0x40 received (expected 0x40) 2019-11-21 12:16:58.491 Info, Node021, Request RTT 193 Average Request RTT 112 2019-11-21 12:16:58.491 Detail, Node021, Expected callbackId was received 2019-11-21 12:17:08.298 Error, Node021, ERROR: Dropping command, expected response not received after 1 attempt(s) 2019-11-21 12:17:08.299 Detail, Node021, Removing current message 2019-11-21 12:17:08.299 Detail, Node021, Notification: Notification - TimeOut 2019-11-21 12:17:08.299 Detail, 2019-11-21 12:17:08.299 Info, Node021, Sending (Query) message (Callback ID=0x41, Expected Reply=0x04) - MultiInstanceCmd_Get (Node=21): 0x01, 0x0a, 0x00, 0x13, 0x15, 0x03, 0x60, 0x04, 0x27, 0x25, 0x41, 0xd7 2019-11-21 12:17:08.299 Info, Node021, Encrypted Flag is 0 2019-11-21 12:17:08.307 Detail, Node021, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8 2019-11-21 12:17:08.308 Detail, Node021, ZW_SEND_DATA delivered to Z-Wave stack 2019-11-21 12:17:08.482 Detail, Node021, Received: 0x01, 0x07, 0x00, 0x13, 0x41, 0x00, 0x00, 0x12, 0xb8 2019-11-21 12:17:08.483 Detail, Node021, ZW_SEND_DATA Request with callback ID 0x41 received (expected 0x41) 2019-11-21 12:17:08.483 Info, Node021, Request RTT 183 Average Request RTT 147 2019-11-21 12:17:08.483 Detail, Node021, Expected callbackId was received 2019-11-21 12:17:18.300 Error, Node021, ERROR: Dropping command, expected response not received after 1 attempt(s) 2019-11-21 12:17:18.300 Detail, Node021, Removing current message 2019-11-21 12:17:18.300 Detail, Node021, Notification: Notification - TimeOut 2019-11-21 12:17:18.300 Detail, 2019-11-21 12:17:18.300 Info, Node021, Sending (Query) message (Callback ID=0x42, Expected Reply=0x04) - MultiInstanceCmd_Get (Node=21): 0x01, 0x0a, 0x00, 0x13, 0x15, 0x03, 0x60, 0x04, 0x2b, 0x25, 0x42, 0xd8 2019-11-21 12:17:18.301 Info, Node021, Encrypted Flag is 0 2019-11-21 12:17:18.309 Detail, Node021, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8 2019-11-21 12:17:18.309 Detail, Node021, ZW_SEND_DATA delivered to Z-Wave stack 2019-11-21 12:17:22.716 Detail, Node021, Received: 0x01, 0x07, 0x00, 0x13, 0x42, 0x01, 0x01, 0xb9, 0x10 2019-11-21 12:17:22.717 Detail, Node021, ZW_SEND_DATA Request with callback ID 0x42 received (expected 0x42) 2019-11-21 12:17:22.717 Info, Node021, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep. 2019-11-21 12:17:22.717 Info, Node021, Node 21 has been marked as asleep 2019-11-21 12:17:22.717 Info, Node021, Node not responding - moving message@SirHenri der Fehler der Version 1.7.1 wurde nun gefixt, er ist aktuell aber nur in der GitHub Version behoben.
Wegen dem Wallplug würde ich mal bei openzwave nachfragen, da scheint es ein Kommunikationsproblem zu geben. -
@SirHenri der Fehler der Version 1.7.1 wurde nun gefixt, er ist aktuell aber nur in der GitHub Version behoben.
Wegen dem Wallplug würde ich mal bei openzwave nachfragen, da scheint es ein Kommunikationsproblem zu geben.@cburghardt vielen Dank für die Benachrichtigung, hatte den Fix schon im Github gesehen.
Parallel zu diesem Text installiere ich die 1.7.1 noch mal.
Die Kommunikation ist seit dem Update auf die 1.6 sowie "besonders". Neben dem nicht mehr funktionierendem Taster (der ja mindestens bei einem weiteren Hersteller auch auftritt) hat sich auch bei meinen Bewegungsmeldern (3x Steinel IS 140-2) merkwürdiges Verhalten eingebürgert.
Bei Update auf die 1.6 laufen die Meldungen über detektierte Bewegung nicht mehr als Einbruchsalarm auf, sondern im Bereich "Home_Security_1" - meinetwegen. Beim Einrichten des Adapters gibt's die aber nicht zwingend (kann sein, dass das noch Verbindungsprobleme sind), mit Aktualiserung der Informationen sind sie dann irgenwann da. Ab einem Zeitpunkt, den ich nicht mehr genau benennen kann, gibt es nun Home_Security_1 und..._2; die Bwegung wird in _2 angemeldet. Nach Veränderung der Skripte wieder alles gut - bis zu dem Zeitpunkt gestern abend, oder heute Nacht, bei dem sich die BewMelder gedacht haben, es wäre eine gute Idee, die Bewegung wieder in Home_Security_1 zu melden...
Das Skript werde ich wohl nicht zurück schreiben, sondern ab sofort beide Kanäle (_1 und _2) abfragen. Ist aber irgendwie unbefriedigend.Welchen Wechsel hat es bei dem hinterlegten OZW Modul gegeben? Damit ich das für einen möglichen Eintrag dort mit angeben kann.
Die Installation der 1.7.1 und das Erzeugen der Instanz sind hier auch sauber durchgelaufen. Ein Fehler beim Scannen der Nodes ist aufgelaufen. Node 16 ist der BewMelder, der am weitesten weg hängt. Ich update die Informationen gerade, hier sind nämlich auch wieder nur die States für/um Home_Security_1 aufgelaufen.
host.rockpro64 2019-11-25 16:32:49.313 info Restart adapter system.adapter.zwave.0 because enabled host.rockpro64 2019-11-25 16:32:49.312 info instance system.adapter.zwave.0 terminated with code NaN () host.rockpro64 2019-11-25 16:32:49.311 warn instance system.adapter.zwave.0 terminated due to SIGABRT host.rockpro64 2019-11-25 16:32:49.310 error Caught by controller[0]: what(): Manager.cpp:1514 - InvalidValueIDError (101) Msg: Invalid ValueID passed to GetValueLabel host.rockpro64 2019-11-25 16:32:49.308 error Caught by controller[0]: terminate called after throwing an instance of 'OpenZWave::OZWException' web.0 2019-11-25 16:32:47.823 info (1709) ==>Connected system.user.admin from ::ffff:192.168.178.201 zwave.0 2019-11-25 16:32:43.723 info (14003) State created: zwave.0.NODE16.SENSOR_MULTILEVEL.Illuminance_1 = undefined, index = 3, comClass = 49, instance = 1 zwave.0 2019-11-25 16:32:43.721 info (14003) Channel created: zwave.0.NODE16.SENSOR_MULTILEVEL = 2, index = 3, comClass = 49, instance = 1 zwave.0 2019-11-25 16:32:43.719 info (14003) State created: zwave.0.NODE16.SENSOR_MULTILEVEL.Illuminance_1 = undefined, index = 3, comClass = 49, instance = 1"Info aktualisieren" startet bei mir im Moment keine Prozesse (Zeile bei der Geräteübersicht wird nicht kurz blau und die Auswahl bleibt auch auf "Info aktualisieren" stehen) - Ampel ist auch 3x rot...
Vielen Dank für Eure Arbeit
-
@cburghardt vielen Dank für die Benachrichtigung, hatte den Fix schon im Github gesehen.
Parallel zu diesem Text installiere ich die 1.7.1 noch mal.
Die Kommunikation ist seit dem Update auf die 1.6 sowie "besonders". Neben dem nicht mehr funktionierendem Taster (der ja mindestens bei einem weiteren Hersteller auch auftritt) hat sich auch bei meinen Bewegungsmeldern (3x Steinel IS 140-2) merkwürdiges Verhalten eingebürgert.
Bei Update auf die 1.6 laufen die Meldungen über detektierte Bewegung nicht mehr als Einbruchsalarm auf, sondern im Bereich "Home_Security_1" - meinetwegen. Beim Einrichten des Adapters gibt's die aber nicht zwingend (kann sein, dass das noch Verbindungsprobleme sind), mit Aktualiserung der Informationen sind sie dann irgenwann da. Ab einem Zeitpunkt, den ich nicht mehr genau benennen kann, gibt es nun Home_Security_1 und..._2; die Bwegung wird in _2 angemeldet. Nach Veränderung der Skripte wieder alles gut - bis zu dem Zeitpunkt gestern abend, oder heute Nacht, bei dem sich die BewMelder gedacht haben, es wäre eine gute Idee, die Bewegung wieder in Home_Security_1 zu melden...
Das Skript werde ich wohl nicht zurück schreiben, sondern ab sofort beide Kanäle (_1 und _2) abfragen. Ist aber irgendwie unbefriedigend.Welchen Wechsel hat es bei dem hinterlegten OZW Modul gegeben? Damit ich das für einen möglichen Eintrag dort mit angeben kann.
Die Installation der 1.7.1 und das Erzeugen der Instanz sind hier auch sauber durchgelaufen. Ein Fehler beim Scannen der Nodes ist aufgelaufen. Node 16 ist der BewMelder, der am weitesten weg hängt. Ich update die Informationen gerade, hier sind nämlich auch wieder nur die States für/um Home_Security_1 aufgelaufen.
host.rockpro64 2019-11-25 16:32:49.313 info Restart adapter system.adapter.zwave.0 because enabled host.rockpro64 2019-11-25 16:32:49.312 info instance system.adapter.zwave.0 terminated with code NaN () host.rockpro64 2019-11-25 16:32:49.311 warn instance system.adapter.zwave.0 terminated due to SIGABRT host.rockpro64 2019-11-25 16:32:49.310 error Caught by controller[0]: what(): Manager.cpp:1514 - InvalidValueIDError (101) Msg: Invalid ValueID passed to GetValueLabel host.rockpro64 2019-11-25 16:32:49.308 error Caught by controller[0]: terminate called after throwing an instance of 'OpenZWave::OZWException' web.0 2019-11-25 16:32:47.823 info (1709) ==>Connected system.user.admin from ::ffff:192.168.178.201 zwave.0 2019-11-25 16:32:43.723 info (14003) State created: zwave.0.NODE16.SENSOR_MULTILEVEL.Illuminance_1 = undefined, index = 3, comClass = 49, instance = 1 zwave.0 2019-11-25 16:32:43.721 info (14003) Channel created: zwave.0.NODE16.SENSOR_MULTILEVEL = 2, index = 3, comClass = 49, instance = 1 zwave.0 2019-11-25 16:32:43.719 info (14003) State created: zwave.0.NODE16.SENSOR_MULTILEVEL.Illuminance_1 = undefined, index = 3, comClass = 49, instance = 1"Info aktualisieren" startet bei mir im Moment keine Prozesse (Zeile bei der Geräteübersicht wird nicht kurz blau und die Auswahl bleibt auch auf "Info aktualisieren" stehen) - Ampel ist auch 3x rot...
Vielen Dank für Eure Arbeit
-
@cburghardt vielen Dank für die Benachrichtigung, hatte den Fix schon im Github gesehen.
Parallel zu diesem Text installiere ich die 1.7.1 noch mal.
Die Kommunikation ist seit dem Update auf die 1.6 sowie "besonders". Neben dem nicht mehr funktionierendem Taster (der ja mindestens bei einem weiteren Hersteller auch auftritt) hat sich auch bei meinen Bewegungsmeldern (3x Steinel IS 140-2) merkwürdiges Verhalten eingebürgert.
Bei Update auf die 1.6 laufen die Meldungen über detektierte Bewegung nicht mehr als Einbruchsalarm auf, sondern im Bereich "Home_Security_1" - meinetwegen. Beim Einrichten des Adapters gibt's die aber nicht zwingend (kann sein, dass das noch Verbindungsprobleme sind), mit Aktualiserung der Informationen sind sie dann irgenwann da. Ab einem Zeitpunkt, den ich nicht mehr genau benennen kann, gibt es nun Home_Security_1 und..._2; die Bwegung wird in _2 angemeldet. Nach Veränderung der Skripte wieder alles gut - bis zu dem Zeitpunkt gestern abend, oder heute Nacht, bei dem sich die BewMelder gedacht haben, es wäre eine gute Idee, die Bewegung wieder in Home_Security_1 zu melden...
Das Skript werde ich wohl nicht zurück schreiben, sondern ab sofort beide Kanäle (_1 und _2) abfragen. Ist aber irgendwie unbefriedigend.Welchen Wechsel hat es bei dem hinterlegten OZW Modul gegeben? Damit ich das für einen möglichen Eintrag dort mit angeben kann.
Die Installation der 1.7.1 und das Erzeugen der Instanz sind hier auch sauber durchgelaufen. Ein Fehler beim Scannen der Nodes ist aufgelaufen. Node 16 ist der BewMelder, der am weitesten weg hängt. Ich update die Informationen gerade, hier sind nämlich auch wieder nur die States für/um Home_Security_1 aufgelaufen.
host.rockpro64 2019-11-25 16:32:49.313 info Restart adapter system.adapter.zwave.0 because enabled host.rockpro64 2019-11-25 16:32:49.312 info instance system.adapter.zwave.0 terminated with code NaN () host.rockpro64 2019-11-25 16:32:49.311 warn instance system.adapter.zwave.0 terminated due to SIGABRT host.rockpro64 2019-11-25 16:32:49.310 error Caught by controller[0]: what(): Manager.cpp:1514 - InvalidValueIDError (101) Msg: Invalid ValueID passed to GetValueLabel host.rockpro64 2019-11-25 16:32:49.308 error Caught by controller[0]: terminate called after throwing an instance of 'OpenZWave::OZWException' web.0 2019-11-25 16:32:47.823 info (1709) ==>Connected system.user.admin from ::ffff:192.168.178.201 zwave.0 2019-11-25 16:32:43.723 info (14003) State created: zwave.0.NODE16.SENSOR_MULTILEVEL.Illuminance_1 = undefined, index = 3, comClass = 49, instance = 1 zwave.0 2019-11-25 16:32:43.721 info (14003) Channel created: zwave.0.NODE16.SENSOR_MULTILEVEL = 2, index = 3, comClass = 49, instance = 1 zwave.0 2019-11-25 16:32:43.719 info (14003) State created: zwave.0.NODE16.SENSOR_MULTILEVEL.Illuminance_1 = undefined, index = 3, comClass = 49, instance = 1"Info aktualisieren" startet bei mir im Moment keine Prozesse (Zeile bei der Geräteübersicht wird nicht kurz blau und die Auswahl bleibt auch auf "Info aktualisieren" stehen) - Ampel ist auch 3x rot...
Vielen Dank für Eure Arbeit
@SirHenri der Fehler oben deutet auf falsche Informationen in dem openzwave Cache hin. Das wird normal durch das Info aktualisieren behoben.
-
@SirHenri der Fehler der Version 1.7.1 wurde nun gefixt, er ist aktuell aber nur in der GitHub Version behoben.
Wegen dem Wallplug würde ich mal bei openzwave nachfragen, da scheint es ein Kommunikationsproblem zu geben. -
@cburghardt @SirHenri v1.7.2 ist jetzt auf npm
-
@AlCalzone hab s einmal mit einem Update probiert, danach Instanz und Adapter raus und von Null wieder neu - der Adapter behauptet in der Adapteransicht weiterhin eine 1.7.1 zu sein
788
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge