Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. smudu

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    S
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 15
    • Best 0
    • Groups 1

    smudu

    @smudu

    0
    Reputation
    29
    Profile views
    15
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    smudu Follow
    Starter

    Latest posts made by smudu

    • RE: D-Link DCH-Z110 (ZWave) Probleme

      Hallo item,
      ich habe 4 Stück die einwandfrei funktionieren.

      Ich gehe davon aus, dass du den Zwave2 Adapter verwendest?

      Wenn du nicht den Deckel abnehmen willst um den Wakeup-Taster manuell (mehrfach) zu drücken, solltest du mit min. 72 Stunden bis zum vollständigen Interview rechnen.
      Sofern du das Default-Intervall von 24 Stunden nicht geändert hattest.

      posted in ioBroker Allgemein
      S
      smudu
    • Radar2 - Merkwürdige Meldung unter Info

      „Bitte entfernen Sie den Eintrag ioBroker-Forum aus der Radar2-Überwachungskonfiguration.

      Der Radar2-Adapter enthält einen Standardeintrag, der das ioBroker-Forum überwacht. Bitte entfernen Sie diesen Eintrag ("Forum" genannt und verweist auf forum.iobroker.net) aus Ihrer Adapterkonfiguration, da dies einen großen, nicht benötigten Datenverkehr im Forum erzeugt.“

      Dieser Eintrag erscheint seit heute unter Info.

      Der Adapter läuft seit Monaten ohne Änderungen der Konfiguration. Das letzte Update (2.0.1) ist auch schon länger her.

      Ich finde in der Instanz keine Einstellung die das verursachen könnte?

      posted in ioBroker Allgemein
      S
      smudu
    • RE: Test Adapter Z-Wave 2 (v1.8.x)

      @cburghardt
      Danke für den Hinweis. Das war mir neu.

      Bei mir sind alle Geräte Z-Wave Plus.

      posted in Tester
      S
      smudu
    • RE: Test Adapter Z-Wave 2 (v1.8.x)

      @alcalzone
      danke für diesen Adapter. Der ist um Welten besser als die alte openzwave Version.

      Leider habe ich Probleme mit meinen Rolladenschaltern. Bis Version 1.7.x. wurde das immer besser, so dass ich mir noch 2 Stück gekauft hatte.
      Mit jeder 1.8.x Version wird es wieder etwas schlechter: Time-Out Fehler, Node dead, etc.
      Treiber-Timeouts und Sendeversuche erhöhen haben auch nichts gebracht.
      Die Rolladen selbst fahren an sich problemlos. Es gibt/gab ab und zu Ausrutscher die aber auch vom Adapter shuttercontrol kommen könnten.

      Könntest du dir das mal anschauen?

      Die Details:
      Fibaro Walli Roller Shutter (FGWREU-111)
      Node 31, 38 und 39 / Node 31 war der erste und hat eine ältere/unterschiedliche Firmware.
      Auffällig ist, dass während des Fahrens vermutlich permanent die aktuelle Rolladenhöhe in Prozent zurückgemeldet wird. Ich benutze den Adapter shuttercontrol der damit manchmal durcheinander kommt. Dort hatte ich schon eingestellt, dass die Rollos nacheinander statt gleichzeitig fahren.

      Im Log müsste der initiale Start des Adapters zu sehen sein mit Node 31 "Interview failed". Zwei weitere Versuche manuell angestossen über die Instanz. Für Node 31 und 39 jeweils ein kompletter Lauf hoch und wieder runter.

      Noch eine Verständnisfrage:
      Ich hatte schon mehrfach die Funktion Netzwerk heilen versucht. Wenn man das startet, wird das ja auch hinter den Nodes visualisiert. Ich habe allerdings auch einen ganzen Zoo von Batterie-Geräten wobei Wakeup auf max. alle 24 Stunden steht.
      Wenn man die Zwave-Instanz schließt und z.B. das Log öffnet, wird irgendwann der Status hinter den Nodes nicht mehr angezeigt. Nach dem Button "Netzwerk heilen" zu urteilen, ist der Vorgang selbst nach mehreren Tagen noch nicht abgeschlossen.
      Eigentlich müsste das doch spätestens dann durch sein, wenn alle Gerät ein Mal ein Wakeup gemacht haben?

      e58b19ca.json
      e58b19ca.values.jsonl
      zwave-11750.log

      posted in Tester
      S
      smudu
    • RE: Suche nach Z wave Roller Shutter

      @Esmax666
      Wo Licht ist ist auch Schatten. Eigentlich ist Z-Wave ja ein offenes System aber Fibaro legt in erster Linie Wert darauf, dass die Komponenten mit dem eigenen Smarthome-Center funktionieren.
      Für mich persönlich ist Fibaro immer die letzte Wahl.

      Ich habe mittlerweile drei Stück verbaut. Ich kann (und will auch nicht) aus baulichen Gründen nicht auf Module hinter Schaltern setzen.

      Wenn du noch den alten ZWave Adapter einsetzt, lass die Finger von den Walli's
      Beim ZWave2 Adapter laufen die Walli's seit 1.6.x zuverlässig. Mit der aktuellen Version (1.7.8) sind auch die letzten Time-Outs verschwunden.

      Ich habe auch den Adapter shuttercontrol im Einsatz. Funktioniert soweit zuverlässig. Die einzige Einschränkung ist das er unter den Objekten manchmal die falschen autoLevel und eigentlich immer autoState falsch anzeigt.

      Geschuldet ist das vermutlich der Tatsache das man die Datenpunkte current- und targetvalue hat. Während die Rollos fahren wird vom Walli permanent der aktuelle Stand in currentvalue zurück gemeldet.
      Wenn du was eigenes programmierst, würde ich darauf achten, dass du den currentvalue erst abfragst wenn das Rollo nicht mehr fährt.

      posted in Hardware
      S
      smudu
    • RE: Suche nach Z wave Roller Shutter

      @Esmax666
      Die Fibaro Walli Serie hast du schon gesehen?

      posted in Hardware
      S
      smudu
    • ioBroker <> fhem (ZWave) auf einem PI möglich?

      Meine Frustgrenze, was den originalen ZWave-Adapter betrifft ist mittlerweile mehr als überschritten.
      Ich habe gehofft, dass ich irgendwann nach den diversen Updates (aktuell 2.0.0.) mal Ruhe einkehrt und ich mich auf die Steuerungen/Skripte konzentrieren kann.
      Das sich durch Updates immer mal wieder die Benennung der Datenpunkten ändert und ich diverse Scripte und iQontrol anpassen muss, ist bei knapp 30 Geräten für mich ein NoGo.

      Den Zwave2-Adapter hatte ich testweise installiert. Aber auch hier ändert sich wieder die Bezeichnung der Datenpunkte, unterstützt noch nicht Security und braucht für In-/Exklusion noch den anderen ZWave-Adapter.

      Wenn ich also komplett bei Null anfangen muss, aber grundsätzlich bei ioBroker bleiben will, ist meine Überlegung:

      • Ich verwende die Alias-Funktion um die Schmerzen von Namensänderungen zu lindern.
      • Den fhem-Adapter um darüber die ZWave-Komponenten einzubinden.

      Kann man fhem und ioBroker parallel auf einem Pi betreiben?
      Hat jemand Erfahrungen ob das problemlos funktioniert?
      Oder fange ich mir wieder ganz andere Probleme ein?

      posted in ioBroker Allgemein
      S
      smudu
    • RE: welchen Z-Wave Stick?

      Bei mir geht der UZB1 problemlos durch zwei Stahlbetondecken.
      Im Gegensatz zum WLAN.

      Es gibt allerdings die Empfehlung den Stick über eine USB-Verlängerung statt direkt an Raspi/PC anzuschließen.
      Leider habe ich die Doku dazu auf die Schnelle nicht wieder gefunden.

      posted in Hardware
      S
      smudu
    • RE: Test Adapter z-wave v1.6.x

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

      posted in Tester
      S
      smudu
    • RE: Test Adapter z-wave v1.6.x

      @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
      
      posted in Tester
      S
      smudu
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
    The ioBroker Community 2014-2023
    logo