Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. deconz - Lampen schalten sich ungewollt ein

    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

    deconz - Lampen schalten sich ungewollt ein

    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      meikelg last edited by

      Hallo deconz-Experten,

      Ich betreibe eine kleine Anzahl an Zigbee-fähigen Leuchtmitteln am deconz-Adapter. In der Regel steuere ich diese über yahka-Verknüpfungen bzw. über HmIP-Taster via blockly-Script.

      Alle paar Wochen, zu unterschiedlichen Zeiten, schaltet sich eine dieser Lampen ungewollt ein, und fast alle Lampen waren schon mal betroffen. Ich kann ausschließen, dass diese Events durch Nutzeraktivitäten getriggert werden. Heute Nacht war das Schlafzimmer betroffen. Ich habe vor ein paar Wochen das deconz- Logging auf debug umgestellt und sehe das folgende:

      2022-07-29 02:34:05.484  - debug: deconz.0 (4435) Websocket message: {"e":"changed","id":"6","r":"lights","state":{"alert":null,"bri":58,"colormode":"hs","ct":201,"effect":"none","hue":11352,"on":false,"reachable":true,"sat":71,"xy":[0.3484,0.3638]},"t":"event","uniqueid":"00:15:8d:00:04:20:1e:2f-01"}
      2022-07-29 02:34:05.484  - debug: deconz.0 (4435) Event has state-tag
      2022-07-29 02:34:05.511  - debug: deconz.0 (4435) alert: null
      2022-07-29 02:34:05.514  - debug: deconz.0 (4435) bri: 58
      2022-07-29 02:34:05.516  - debug: deconz.0 (4435) Websocket message: {"attr":{"id":"5","lastannounced":"2022-06-28T06:48:40Z","lastseen":"2022-07-29T00:34Z","manufacturername":"Paulmann Licht","modelid":"500.45","name":"Fensterlicht Wohnzimmer","swversion":"1400-0001","type":"Dimmable light","uniqueid":"00:15:8d:00:05:81:67:e5-01"},"e":"changed","id":"5","r":"lights","t":"event","uniqueid":"00:15:8d:00:05:81:67:e5-01"}
      2022-07-29 02:34:05.517  - debug: deconz.0 (4435) Event has attr-Tag
      2022-07-29 02:34:05.563  - debug: deconz.0 (4435) colormode: hs
      2022-07-29 02:34:05.609  - debug: deconz.0 (4435) ct: 201
      2022-07-29 02:34:05.653  - debug: deconz.0 (4435) effect: none
      2022-07-29 02:34:05.698  - debug: deconz.0 (4435) hue: 11352
      2022-07-29 02:34:05.745  - debug: deconz.0 (4435) on: false
      2022-07-29 02:34:05.789  - debug: deconz.0 (4435) reachable: true
      2022-07-29 02:34:05.833  - debug: deconz.0 (4435) sat: 71
      2022-07-29 02:34:05.877  - debug: deconz.0 (4435) xy: 0.3484,0.3638
      2022-07-29 02:34:06.537  - debug: deconz.0 (4435) Websocket message: {"attr":{"colorcapabilities":0,"ctmax":65279,"ctmin":0,"id":"6","lastannounced":"2022-07-29T00:34:05Z","lastseen":"2022-07-29T00:34Z","manufacturername":"Paulmann Licht","modelid":"500.49","name":"Wandlicht Schlafzimmer","swversion":"1400-0001","type":"Extended color light","uniqueid":"00:15:8d:00:04:20:1e:2f-01"},"e":"changed","id":"6","r":"lights","t":"event","uniqueid":"00:15:8d:00:04:20:1e:2f-01"}
      2022-07-29 02:34:06.538  - debug: deconz.0 (4435) Event has attr-Tag
      2022-07-29 02:34:06.555  - debug: deconz.0 (4435) Websocket message: {"e":"changed","id":"6","r":"lights","state":{"alert":null,"bri":58,"colormode":"hs","ct":201,"effect":"none","hue":11352,"on":true,"reachable":true,"sat":71,"xy":[0.3484,0.3638]},"t":"event","uniqueid":"00:15:8d:00:04:20:1e:2f-01"}
      2022-07-29 02:34:06.555  - debug: deconz.0 (4435) Event has state-tag
      2022-07-29 02:34:06.571  - debug: deconz.0 (4435) Websocket message: {"e":"changed","id":"65520","r":"groups","state":{"all_on":false,"any_on":true},"t":"event"}
      2022-07-29 02:34:06.582  - debug: deconz.0 (4435) Websocket message: {"e":"changed","id":"5","r":"groups","state":{"all_on":false,"any_on":true},"t":"event"}
      2022-07-29 02:34:06.586  - debug: deconz.0 (4435) alert: null
      2022-07-29 02:34:06.591  - debug: deconz.0 (4435) bri: 58
      2022-07-29 02:34:06.606  - debug: deconz.0 (4435) Code 200: Request succeded get group attributes 65520: {"action":{"alert":"none","bri":127,"colormode":"hs","ct":0,"effect":"none","hue":0,"on":false,"sat":127,"scene":null,"xy":[0,0]},"devicemembership":[],"etag":"a0f459d1057dbe6a48d818c316b2a66c","id":"65520","lights":["1","3","5","8","2","4","7","9","6"],"name":"All","scenes":[],"state":{"all_on":false,"any_on":true},"type":"LightGroup"}
      2022-07-29 02:34:06.608  - debug: deconz.0 (4435) colormode: hs
      2022-07-29 02:34:06.629  - debug: deconz.0 (4435) Code 200: Request succeded get group attributes 5: {"action":{"alert":"none","bri":127,"colormode":"hs","ct":0,"effect":"none","hue":0,"on":false,"sat":127,"scene":null,"xy":[0,0]},"devicemembership":[],"etag":"23d0ed578ea35e49993d565af90ffde4","id":"5","lights":["8","7","9","6"],"name":"Schlafzimmer","scenes":[],"state":{"all_on":false,"any_on":true},"type":"LightGroup"}
      2022-07-29 02:34:06.632  - debug: deconz.0 (4435) ct: 201
      2022-07-29 02:34:06.637  - debug: deconz.0 (4435) effect: none
      2022-07-29 02:34:06.685  - debug: deconz.0 (4435) hue: 11352
      2022-07-29 02:34:06.730  - debug: deconz.0 (4435) on: true
      2022-07-29 02:34:06.736  - debug: deconz.0 (4435) reachable: true
      2022-07-29 02:34:06.748  - debug: deconz.0 (4435) sat: 71
      2022-07-29 02:34:06.759  - debug: deconz.0 (4435) xy: 0.3484,0.3638
      
      

      Ich sehe hier zwei Events - das "Fensterlicht Wohnzimmer" war aus und blieb aus, das "Wandlicht Schlafzimmer" war aus und wurde eingeschaltet. Kann man hieraus irgendwie erkennen, was diese Events getriggert hat? Wenn nein, was kann ich noch tun, um diesem Phänomen auf den Grund zu gehen?

      Gruß
      Michael

      Jey Cee 1 Reply Last reply Reply Quote 0
      • Jey Cee
        Jey Cee Developer @meikelg last edited by

        @meikelg sagte in deconz - Lampen schalten sich ungewollt ein:

        Kann man hieraus irgendwie erkennen, was diese Events getriggert hat?

        Nein, man hätte eine Chance wenn man das ganze Log zum betreffenden Zeitpunkt hätte und nicht nur das vom deConz Adapter.

        M 1 Reply Last reply Reply Quote 0
        • M
          meikelg @Jey Cee last edited by

          @jey-cee Minuten vor und nach diesem Abschnitt sind im Log nur deconz.0-Einträge mit "Websocket message: {"attr" ...", die regulär alle paar Sekunden gelogt werden. Sonst rein gar nichts.

          Jey Cee 1 Reply Last reply Reply Quote 0
          • Jey Cee
            Jey Cee Developer @meikelg last edited by

            @meikelg dann bin ich mir ziemlich sicher das der Auslöser nicht ioBroker ist. Schau mal ob du logs von deConz/Phoscon finden kannst, vielleicht ist da was zu finden.

            M 1 Reply Last reply Reply Quote 0
            • M
              meikelg @Jey Cee last edited by

              @jey-cee deCONZ (läuft auf einem alten Raspberry) macht standardmäßig kaum Logging. Ich müsste erst mal rausfinden, mit welchen Logging-Einstellungen ich solche Events erfasse, ohne massiv Daten auf die SD-Karte zu schreiben. Das Problem tritt ja nur sehr unregelmäßig auf.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post

              Support us

              ioBroker
              Community Adapters
              Donate
              FAQ Cloud / IOT
              HowTo: Node.js-Update
              HowTo: Backup/Restore
              Downloads
              BLOG

              933
              Online

              31.9k
              Users

              80.1k
              Topics

              1.3m
              Posts

              deconz
              2
              5
              232
              Loading More Posts
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes
              Reply
              • Reply as topic
              Log in to reply
              Community
              Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
              The ioBroker Community 2014-2023
              logo