Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta)

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.6k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.1k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    2.9k

Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta)

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
391 Beiträge 39 Kommentatoren 67.6k Aufrufe 38 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • apollon77A apollon77

    @palm_maniac sagte in Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta):

    Außerdem habe ich wohl den Auslöser für das Eigenleben des Lichts gefunden. Mir ist aufgefallen, dass das Treppenlicht 2mal unter Smart-Devices auftauchte mit allen Datenpunkten für RGB Beleuchtung. Das hätte so aber nicht sein dürfen, denn ich hatte dieses Licht garnicht per IOT-Adapter an Alexa übergeben. Also habe ich mir nochmal die Konfig in WLED angeschaut und gesehen, dass dort die Alexa-Unterstützung aktiviert war. Problem erkannt, Problem gebannt.

    Warum es plötzlich was tut wenn nichts gesteuert wird ist dennoch strange

    Palm_ManiacP Offline
    Palm_ManiacP Offline
    Palm_Maniac
    schrieb am zuletzt editiert von
    #152

    @apollon77 sagte in Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta):

    @palm_maniac sagte in Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta):

    Außerdem habe ich wohl den Auslöser für das Eigenleben des Lichts gefunden. Mir ist aufgefallen, dass das Treppenlicht 2mal unter Smart-Devices auftauchte mit allen Datenpunkten für RGB Beleuchtung. Das hätte so aber nicht sein dürfen, denn ich hatte dieses Licht garnicht per IOT-Adapter an Alexa übergeben. Also habe ich mir nochmal die Konfig in WLED angeschaut und gesehen, dass dort die Alexa-Unterstützung aktiviert war. Problem erkannt, Problem gebannt.

    Warum es plötzlich was tut wenn nichts gesteuert wird ist dennoch strange

    Ja, zumal diese Datenpunkte in keinem Skript Verwendung finden.

    1 Antwort Letzte Antwort
    0
    • DiginixD Diginix

      @apollon77 Und mir ist die 3.17.1 eben nach einer Sprachausgabe mittels announcement auf allen Echos mit diesen Meldungen abgestürzt:

      2022-07-12 16:55:01.488 - warn: alexa2.0 (649312) Exception: TypeError: value.replace(...).replaceAll is not a function
      2022-07-12 16:55:01.493 - error: alexa2.0 (649312) uncaught exception: value.replace(...).replaceAll is not a function
      2022-07-12 16:55:01.494 - error: alexa2.0 (649312) TypeError: value.replace(...).replaceAll is not a function
          at /opt/iobroker/node_modules/iobroker.alexa2/main.js:2220:98
          at Array.forEach (<anonymous>)
          at /opt/iobroker/node_modules/iobroker.alexa2/main.js:2216:67
          at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.alexa2/main.js:2211:65)
          at processImmediate (internal/timers.js:466:21)
      2022-07-12 16:55:01.494 - error: alexa2.0 (649312) value.replace(...).replaceAll is not a function
      2022-07-12 16:55:01.512 - info: alexa2.0 (649312) terminating
      2022-07-12 16:55:01.513 - warn: alexa2.0 (649312) Terminated (UNCAUGHT_EXCEPTION): Without reason
      2022-07-12 16:55:02.080 - error: host.iobroker Caught by controller[0]: TypeError: value.replace(...).replaceAll is not a function
      2022-07-12 16:55:02.083 - error: host.iobroker Caught by controller[0]:     at /opt/iobroker/node_modules/iobroker.alexa2/main.js:2220:98
      2022-07-12 16:55:02.083 - error: host.iobroker Caught by controller[0]:     at Array.forEach (<anonymous>)
      2022-07-12 16:55:02.083 - error: host.iobroker Caught by controller[0]:     at /opt/iobroker/node_modules/iobroker.alexa2/main.js:2216:67
      2022-07-12 16:55:02.083 - error: host.iobroker Caught by controller[0]:     at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.alexa2/main.js:2211:65)
      2022-07-12 16:55:02.083 - error: host.iobroker Caught by controller[0]:     at processImmediate (internal/timers.js:466:21)
      2022-07-12 16:55:02.084 - error: host.iobroker instance system.adapter.alexa2.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
      2022-07-12 16:55:33.964 - info: alexa2.0 (652182) starting. Version 3.17.1 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.20.0, js-controller: 4.0.23
      2022-07-12 16:55:34.205 - info: alexa2.0 (652182) Update History Interval is too low, set to 112s
      2022-07-12 16:55:34.206 - info: alexa2.0 (652182) Update Device State Interval is too low, set to 112s
      2022-07-12 16:55:39.181 - info: alexa2.0 (652182) Alexa-Push-Connection (macDms = true) established. Disable Polling
      2022-07-12 16:56:37.755 - info: alexa2.0 (652182) Subscribing to states...
      

      announcement funktioniert auch nicht mehr, weder mit "volume;text" noch mit nur "text". Dabei stürzt die Instanz immer ab. Die 3.17.2 ist aber auch unbrauchbar durch die loopenden Logmeldungen zu falschen Datentypen. ;-)

      Also erstmal zurück zur 3.17.0.

      apollon77A Offline
      apollon77A Offline
      apollon77
      schrieb am zuletzt editiert von
      #153

      @diginix Den hab ich auf Sentry gesehen. Fix kommt heute abend

      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
      1 Antwort Letzte Antwort
      0
      • sigi234S sigi234

        @apollon77

        Seit 3.17.2 kommt ständig das im Log:

        alexa2.0
        2022-07-12 16:07:02.169	info	State value to set for "alexa2.0.Smart-Home-Devices.2bd3a32a-2769-44db-a7ae-87040ae0b9e9.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:07:02.169	info	State value to set for "alexa2.0.Smart-Home-Devices.4a7f3111-5f34-41c6-999d-97445497dd54.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:07:02.169	info	State value to set for "alexa2.0.Smart-Home-Devices.178c8295-8aca-4daa-9cc6-70319e3c42a8.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:07:02.169	info	State value to set for "alexa2.0.Smart-Home-Devices.baff13c0-c230-4a18-bc02-c75d89feb91b.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:07:02.168	info	State value to set for "alexa2.0.Smart-Home-Devices.d1edb1fa-f9cd-490e-8e18-4f9aba2bfa6b.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:07:02.168	info	State value to set for "alexa2.0.Smart-Home-Devices.0b11288f-36c0-49f4-9370-fa23a5e501fa.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:07:02.167	info	State value to set for "alexa2.0.Smart-Home-Devices.bbd84bcd-a37a-4213-b9e0-3fa66a805c4a.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:07:02.167	info	State value to set for "alexa2.0.Smart-Home-Devices.441edae9-3f8a-4ed6-8cc3-72ff8d179d72.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:07:02.166	info	State value to set for "alexa2.0.Smart-Home-Devices.bbcaed7a-20bf-4573-979d-ea5e6eb15903.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:07:02.166	info	State value to set for "alexa2.0.Smart-Home-Devices.8e5548cf-ab6b-462a-8f5b-153ef3e7cd33.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:07:02.165	info	State value to set for "alexa2.0.Smart-Home-Devices.f05454b0-f034-485e-beb6-b2ebc3fe60ac.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:53.282	info	State value to set for "alexa2.0.Smart-Home-Devices.2bd3a32a-2769-44db-a7ae-87040ae0b9e9.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:53.282	info	State value to set for "alexa2.0.Smart-Home-Devices.4a7f3111-5f34-41c6-999d-97445497dd54.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:53.282	info	State value to set for "alexa2.0.Smart-Home-Devices.178c8295-8aca-4daa-9cc6-70319e3c42a8.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:53.282	info	State value to set for "alexa2.0.Smart-Home-Devices.baff13c0-c230-4a18-bc02-c75d89feb91b.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:53.282	info	State value to set for "alexa2.0.Smart-Home-Devices.d1edb1fa-f9cd-490e-8e18-4f9aba2bfa6b.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:53.282	info	State value to set for "alexa2.0.Smart-Home-Devices.0b11288f-36c0-49f4-9370-fa23a5e501fa.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:53.281	info	State value to set for "alexa2.0.Smart-Home-Devices.bbd84bcd-a37a-4213-b9e0-3fa66a805c4a.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:53.280	info	State value to set for "alexa2.0.Smart-Home-Devices.441edae9-3f8a-4ed6-8cc3-72ff8d179d72.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:53.280	info	State value to set for "alexa2.0.Smart-Home-Devices.bbcaed7a-20bf-4573-979d-ea5e6eb15903.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:53.280	info	State value to set for "alexa2.0.Smart-Home-Devices.8e5548cf-ab6b-462a-8f5b-153ef3e7cd33.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:53.279	info	State value to set for "alexa2.0.Smart-Home-Devices.f05454b0-f034-485e-beb6-b2ebc3fe60ac.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:47.495	info	State value to set for "alexa2.0.Smart-Home-Devices.2bd3a32a-2769-44db-a7ae-87040ae0b9e9.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:47.495	info	State value to set for "alexa2.0.Smart-Home-Devices.4a7f3111-5f34-41c6-999d-97445497dd54.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:47.495	info	State value to set for "alexa2.0.Smart-Home-Devices.178c8295-8aca-4daa-9cc6-70319e3c42a8.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:47.495	info	State value to set for "alexa2.0.Smart-Home-Devices.baff13c0-c230-4a18-bc02-c75d89feb91b.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:47.494	info	State value to set for "alexa2.0.Smart-Home-Devices.d1edb1fa-f9cd-490e-8e18-4f9aba2bfa6b.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:47.494	info	State value to set for "alexa2.0.Smart-Home-Devices.0b11288f-36c0-49f4-9370-fa23a5e501fa.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:47.494	info	State value to set for "alexa2.0.Smart-Home-Devices.bbd84bcd-a37a-4213-b9e0-3fa66a805c4a.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:47.493	info	State value to set for "alexa2.0.Smart-Home-Devices.441edae9-3f8a-4ed6-8cc3-72ff8d179d72.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:47.492	info	State value to set for "alexa2.0.Smart-Home-Devices.bbcaed7a-20bf-4573-979d-ea5e6eb15903.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:47.492	info	State value to set for "alexa2.0.Smart-Home-Devices.8e5548cf-ab6b-462a-8f5b-153ef3e7cd33.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:47.492	info	State value to set for "alexa2.0.Smart-Home-Devices.f05454b0-f034-485e-beb6-b2ebc3fe60ac.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:41.563	info	State value to set for "alexa2.0.Smart-Home-Devices.2bd3a32a-2769-44db-a7ae-87040ae0b9e9.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:41.563	info	State value to set for "alexa2.0.Smart-Home-Devices.4a7f3111-5f34-41c6-999d-97445497dd54.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:41.563	info	State value to set for "alexa2.0.Smart-Home-Devices.178c8295-8aca-4daa-9cc6-70319e3c42a8.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:41.562	info	State value to set for "alexa2.0.Smart-Home-Devices.baff13c0-c230-4a18-bc02-c75d89feb91b.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:41.561	info	State value to set for "alexa2.0.Smart-Home-Devices.d1edb1fa-f9cd-490e-8e18-4f9aba2bfa6b.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:41.560	info	State value to set for "alexa2.0.Smart-Home-Devices.0b11288f-36c0-49f4-9370-fa23a5e501fa.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:41.560	info	State value to set for "alexa2.0.Smart-Home-Devices.bbd84bcd-a37a-4213-b9e0-3fa66a805c4a.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:41.559	info	State value to set for "alexa2.0.Smart-Home-Devices.441edae9-3f8a-4ed6-8cc3-72ff8d179d72.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:41.556	info	State value to set for "alexa2.0.Smart-Home-Devices.bbcaed7a-20bf-4573-979d-ea5e6eb15903.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:41.556	info	State value to set for "alexa2.0.Smart-Home-Devices.8e5548cf-ab6b-462a-8f5b-153ef3e7cd33.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:41.555	info	State value to set for "alexa2.0.Smart-Home-Devices.f05454b0-f034-485e-beb6-b2ebc3fe60ac.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:32.514	info	State value to set for "alexa2.0.Smart-Home-Devices.2bd3a32a-2769-44db-a7ae-87040ae0b9e9.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:32.513	info	State value to set for "alexa2.0.Smart-Home-Devices.4a7f3111-5f34-41c6-999d-97445497dd54.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:32.513	info	State value to set for "alexa2.0.Smart-Home-Devices.178c8295-8aca-4daa-9cc6-70319e3c42a8.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:32.513	info	State value to set for "alexa2.0.Smart-Home-Devices.baff13c0-c230-4a18-bc02-c75d89feb91b.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:32.513	info	State value to set for "alexa2.0.Smart-Home-Devices.d1edb1fa-f9cd-490e-8e18-4f9aba2bfa6b.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:32.512	info	State value to set for "alexa2.0.Smart-Home-Devices.0b11288f-36c0-49f4-9370-fa23a5e501fa.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:32.512	info	State value to set for "alexa2.0.Smart-Home-Devices.bbd84bcd-a37a-4213-b9e0-3fa66a805c4a.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:32.512	info	State value to set for "alexa2.0.Smart-Home-Devices.441edae9-3f8a-4ed6-8cc3-72ff8d179d72.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:32.510	info	State value to set for "alexa2.0.Smart-Home-Devices.bbcaed7a-20bf-4573-979d-ea5e6eb15903.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:32.510	info	State value to set for "alexa2.0.Smart-Home-Devices.8e5548cf-ab6b-462a-8f5b-153ef3e7cd33.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:32.510	info	State value to set for "alexa2.0.Smart-Home-Devices.f05454b0-f034-485e-beb6-b2ebc3fe60ac.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:26.767	info	State value to set for "alexa2.0.Smart-Home-Devices.2bd3a32a-2769-44db-a7ae-87040ae0b9e9.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:26.767	info	State value to set for "alexa2.0.Smart-Home-Devices.4a7f3111-5f34-41c6-999d-97445497dd54.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:26.766	info	State value to set for "alexa2.0.Smart-Home-Devices.178c8295-8aca-4daa-9cc6-70319e3c42a8.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:26.766	info	State value to set for "alexa2.0.Smart-Home-Devices.baff13c0-c230-4a18-bc02-c75d89feb91b.connectivity-reason" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:26.764	info	State value to set for "alexa2.0.Smart-Home-Devices.d1edb1fa-f9cd-490e-8e18-4f9aba2bfa6b.colorRgb" has to be type "string" but received type "object"
        
        alexa2.0
        2022-07-12 16:06:26.759	info	State value to set for "alexa2.0.Smart-Home-Devices.0b11288f-36c0-49f4-9370-fa23a5e501fa.connectivity-reason" has to be type "string" but received type "object"
        

        Smart-Home-Devices.2bd3a32a-2769-44db-a7ae-87040ae0b9e9.connectivity-reason

        Screenshot (5001).png Screenshot (5002).png

        alexa2.0.Smart-Home-Devices.d1edb1fa-f9cd-490e-8e18-4f9aba2bfa6b.colorRgb (Hue lightstrip Küche)

        Screenshot (5003).png Screenshot (5004).png

        apollon77A Offline
        apollon77A Offline
        apollon77
        schrieb am zuletzt editiert von
        #154

        @sigi234 Hab schon ne vermutung. Fix heute abend

        Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

        • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
        • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
        Thomas BraunT sigi234S 2 Antworten Letzte Antwort
        0
        • apollon77A apollon77

          @sigi234 Hab schon ne vermutung. Fix heute abend

          Thomas BraunT Online
          Thomas BraunT Online
          Thomas Braun
          Most Active
          schrieb am zuletzt editiert von
          #155

          @apollon77

          Das muss aber im Diff von

          alexa2.git#0fd8690ca77e16285030ebbcdbce49b4c56f99a8 ist wieder leise im Log.

          zum Release 3.17.2 zu finden sein.
          Die quasselt mich nämlich auch im Log zu:

          2022-07-12 18:15:30.770  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.4acc0e22-bfb9-4e3e-bdfe-bea4f3912910.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.771  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.d7d81c77-a50c-41cb-9c3a-0450992ae160.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.773  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.f3c8b652-2523-4cd9-b7da-2b125e973bb6.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.773  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.4e18554e-e6fe-4771-8f4e-12fc640761db.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.774  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.d359aeb1-03f5-4cde-9071-179a5924f7fa.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.775  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.0f9cec35-b064-4598-923d-963b29af18b8.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.776  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.7cd146f6-aac1-4b01-98e6-3167447f9e70.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.777  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.ca41d22b-884b-4be1-aa28-ced702d9f694.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.778  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.98257657-55fe-4a59-96ee-bcbb24ee9bc8.colorRgb" has to be type "string" but received type "object"
          2022-07-12 18:15:30.814  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.98257657-55fe-4a59-96ee-bcbb24ee9bc8.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.815  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.3c24ecd2-b792-4d5f-9c25-75d7cf57a574.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.816  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.fb3ea3ff-cbdf-423a-9186-11da242e2947.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.816  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.dff78664-0a39-4ee4-aa2b-a9a8e0d7ba31.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.817  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.8bc3f37a-58a8-4d46-82e8-4d84dd10121c.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.817  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.39be3920-5d21-4742-9453-25790bcc07f5.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.818  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.e134e20d-ae41-4394-b4c7-1504ae3e4831.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.818  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.10d02cfd-be52-46a6-84ed-fcaae8db99b7.colorRgb" has to be type "string" but received type "object"
          2022-07-12 18:15:30.819  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.10d02cfd-be52-46a6-84ed-fcaae8db99b7.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.820  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.5144a434-eee6-42db-a91b-3b5df7b712e5.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.820  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.3a8fa5bf-7037-4806-aecf-fea3af6070a4.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.821  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.c77e7be4-86da-4595-8223-5ceb6b50254b.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.821  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.4967049f-b2b6-42a5-a0fc-825172dad02a.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.822  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.e7ea8a09-6582-480b-a6a6-935cbbe3275e.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.823  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.81de86f1-23b0-49f6-b5d0-402c197dcba0.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.823  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.6c714265-c3e0-450a-b7e0-5acf25326e57.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.824  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.48f3f6f6-a74c-4daa-97a3-32766f03e5b1.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.824  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.141b1d14-9591-4d28-bd03-698cd0cfd970.batteryLevel" has to be type "number" but received type "object"
          2022-07-12 18:15:30.825  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.141b1d14-9591-4d28-bd03-698cd0cfd970.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.825  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.60099b70-c2d2-46b7-b14d-77acc53e04f9.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.827  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.a3ab3c77-6751-458f-a7d5-0871e996c700.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.828  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.5d479e97-6965-4780-98d1-5438ccbc2371.colorRgb" has to be type "string" but received type "object"
          2022-07-12 18:15:30.829  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.5d479e97-6965-4780-98d1-5438ccbc2371.connectivity-reason" has to be type "string" but received type "object"
          2022-07-12 18:15:30.829  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.30d44a62-ba23-4a51-a417-d4215f8e6336.connectivity-reason" has to be type "string" but received type "object"
          

          Linux-Werkzeugkasten:
          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
          NodeJS Fixer Skript:
          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

          M 1 Antwort Letzte Antwort
          0
          • Thomas BraunT Thomas Braun

            @apollon77

            Das muss aber im Diff von

            alexa2.git#0fd8690ca77e16285030ebbcdbce49b4c56f99a8 ist wieder leise im Log.

            zum Release 3.17.2 zu finden sein.
            Die quasselt mich nämlich auch im Log zu:

            2022-07-12 18:15:30.770  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.4acc0e22-bfb9-4e3e-bdfe-bea4f3912910.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.771  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.d7d81c77-a50c-41cb-9c3a-0450992ae160.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.773  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.f3c8b652-2523-4cd9-b7da-2b125e973bb6.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.773  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.4e18554e-e6fe-4771-8f4e-12fc640761db.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.774  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.d359aeb1-03f5-4cde-9071-179a5924f7fa.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.775  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.0f9cec35-b064-4598-923d-963b29af18b8.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.776  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.7cd146f6-aac1-4b01-98e6-3167447f9e70.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.777  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.ca41d22b-884b-4be1-aa28-ced702d9f694.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.778  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.98257657-55fe-4a59-96ee-bcbb24ee9bc8.colorRgb" has to be type "string" but received type "object"
            2022-07-12 18:15:30.814  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.98257657-55fe-4a59-96ee-bcbb24ee9bc8.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.815  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.3c24ecd2-b792-4d5f-9c25-75d7cf57a574.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.816  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.fb3ea3ff-cbdf-423a-9186-11da242e2947.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.816  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.dff78664-0a39-4ee4-aa2b-a9a8e0d7ba31.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.817  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.8bc3f37a-58a8-4d46-82e8-4d84dd10121c.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.817  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.39be3920-5d21-4742-9453-25790bcc07f5.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.818  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.e134e20d-ae41-4394-b4c7-1504ae3e4831.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.818  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.10d02cfd-be52-46a6-84ed-fcaae8db99b7.colorRgb" has to be type "string" but received type "object"
            2022-07-12 18:15:30.819  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.10d02cfd-be52-46a6-84ed-fcaae8db99b7.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.820  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.5144a434-eee6-42db-a91b-3b5df7b712e5.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.820  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.3a8fa5bf-7037-4806-aecf-fea3af6070a4.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.821  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.c77e7be4-86da-4595-8223-5ceb6b50254b.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.821  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.4967049f-b2b6-42a5-a0fc-825172dad02a.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.822  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.e7ea8a09-6582-480b-a6a6-935cbbe3275e.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.823  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.81de86f1-23b0-49f6-b5d0-402c197dcba0.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.823  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.6c714265-c3e0-450a-b7e0-5acf25326e57.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.824  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.48f3f6f6-a74c-4daa-97a3-32766f03e5b1.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.824  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.141b1d14-9591-4d28-bd03-698cd0cfd970.batteryLevel" has to be type "number" but received type "object"
            2022-07-12 18:15:30.825  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.141b1d14-9591-4d28-bd03-698cd0cfd970.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.825  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.60099b70-c2d2-46b7-b14d-77acc53e04f9.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.827  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.a3ab3c77-6751-458f-a7d5-0871e996c700.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.828  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.5d479e97-6965-4780-98d1-5438ccbc2371.colorRgb" has to be type "string" but received type "object"
            2022-07-12 18:15:30.829  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.5d479e97-6965-4780-98d1-5438ccbc2371.connectivity-reason" has to be type "string" but received type "object"
            2022-07-12 18:15:30.829  - info: alexa2.0 (74962) State value to set for "alexa2.0.Smart-Home-Devices.30d44a62-ba23-4a51-a417-d4215f8e6336.connectivity-reason" has to be type "string" but received type "object"
            
            M Offline
            M Offline
            Megawaldi
            schrieb am zuletzt editiert von
            #156

            @apollon77
            Hier das selbe Problem mit dem zugespamtem Log.

            Thomas BraunT 1 Antwort Letzte Antwort
            0
            • M Megawaldi

              @apollon77
              Hier das selbe Problem mit dem zugespamtem Log.

              Thomas BraunT Online
              Thomas BraunT Online
              Thomas Braun
              Most Active
              schrieb am zuletzt editiert von
              #157

              @megawaldi Setz das LogLevel auf 'Warning / Hinweis'.

              Linux-Werkzeugkasten:
              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
              NodeJS Fixer Skript:
              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

              M 1 Antwort Letzte Antwort
              0
              • Thomas BraunT Thomas Braun

                @megawaldi Setz das LogLevel auf 'Warning / Hinweis'.

                M Offline
                M Offline
                Megawaldi
                schrieb am zuletzt editiert von
                #158

                @thomas-braun
                schon erledigt. Aber trotzdem Danke für den Tip. 😉

                Thomas BraunT 1 Antwort Letzte Antwort
                0
                • M Megawaldi

                  @thomas-braun
                  schon erledigt. Aber trotzdem Danke für den Tip. 😉

                  Thomas BraunT Online
                  Thomas BraunT Online
                  Thomas Braun
                  Most Active
                  schrieb am zuletzt editiert von
                  #159

                  @megawaldi Danke für den #metoo-Beitrag. :-D

                  Linux-Werkzeugkasten:
                  https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                  NodeJS Fixer Skript:
                  https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                  iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                  M 1 Antwort Letzte Antwort
                  0
                  • Thomas BraunT Thomas Braun

                    @megawaldi Danke für den #metoo-Beitrag. :-D

                    M Offline
                    M Offline
                    Megawaldi
                    schrieb am zuletzt editiert von
                    #160

                    @thomas-braun
                    Wollte nur nicht da jemand denkt es liegt an dir Thomas...

                    1 Antwort Letzte Antwort
                    0
                    • apollon77A Offline
                      apollon77A Offline
                      apollon77
                      schrieb am zuletzt editiert von
                      #161

                      @Diginix @sigi234 Version 3.17.3 mit Fix ist auf dem Weg

                      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                      1 Antwort Letzte Antwort
                      3
                      • apollon77A apollon77

                        @sigi234 Hab schon ne vermutung. Fix heute abend

                        sigi234S Online
                        sigi234S Online
                        sigi234
                        Forum Testing Most Active
                        schrieb am zuletzt editiert von
                        #162

                        @apollon77 sagte in Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta):

                        @sigi234 Hab schon ne vermutung. Fix heute abend

                        Log wieder Ok, Danke für den Fix. :+1:

                        Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                        Immer Daten sichern!

                        apollon77A 1 Antwort Letzte Antwort
                        1
                        • sigi234S sigi234

                          @apollon77 sagte in Alexa2 Adapter 3.13/3.14/3.15/3.16/3.17 (Beta):

                          @sigi234 Hab schon ne vermutung. Fix heute abend

                          Log wieder Ok, Danke für den Fix. :+1:

                          apollon77A Offline
                          apollon77A Offline
                          apollon77
                          schrieb am zuletzt editiert von
                          #163

                          @sigi234 danke für die Bestätigung. Die Werte sind auch korrekt?! Vor allem bei den States die vorher angemeckert wurden?

                          Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                          • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                          • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                          1 Antwort Letzte Antwort
                          0
                          • apollon77A Offline
                            apollon77A Offline
                            apollon77
                            schrieb am zuletzt editiert von
                            #164

                            3.17.4 ist auf dem Weg mit einem weiteren Bugfix:

                            Es war nicht möglich die Query Intervalle für Smart-Home Devices, generellen State und Configuration auf 0 zu setzen aka zu deaktivieren.

                            Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                            • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                            • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                            DiginixD 1 Antwort Letzte Antwort
                            0
                            • apollon77A apollon77

                              3.17.4 ist auf dem Weg mit einem weiteren Bugfix:

                              Es war nicht möglich die Query Intervalle für Smart-Home Devices, generellen State und Configuration auf 0 zu setzen aka zu deaktivieren.

                              DiginixD Offline
                              DiginixD Offline
                              Diginix
                              schrieb am zuletzt editiert von
                              #165

                              @apollon77 Aus der iob Facebook Gruppe:

                              5d824679-9601-4b55-a3c0-e5190c20dece-image.png

                              ..:: So long! Tom ::..

                              NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB

                              1 Antwort Letzte Antwort
                              0
                              • apollon77A Offline
                                apollon77A Offline
                                apollon77
                                schrieb am zuletzt editiert von apollon77
                                #166

                                Naja ich sags mal so ... es gab einen Bug ... Alle schnellstens auf die 3.17.4 updaten!!!

                                Admin-Notify ist geschaltet um alle user daraf hinzuweisen. Im Forum ist auch ab gleich eine Headline

                                Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                DiginixD 1 Antwort Letzte Antwort
                                0
                                • apollon77A apollon77

                                  Naja ich sags mal so ... es gab einen Bug ... Alle schnellstens auf die 3.17.4 updaten!!!

                                  Admin-Notify ist geschaltet um alle user daraf hinzuweisen. Im Forum ist auch ab gleich eine Headline

                                  DiginixD Offline
                                  DiginixD Offline
                                  Diginix
                                  schrieb am zuletzt editiert von
                                  #167

                                  @apollon77 Der Facebook User ist aber auf 3.14.0.

                                  ..:: So long! Tom ::..

                                  NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB

                                  apollon77A 1 Antwort Letzte Antwort
                                  0
                                  • DiginixD Diginix

                                    @apollon77 Der Facebook User ist aber auf 3.14.0.

                                    apollon77A Offline
                                    apollon77A Offline
                                    apollon77
                                    schrieb am zuletzt editiert von
                                    #168

                                    @diginix Ok, da hats wohl mein changelog zerbröselt ... ab 3.14 ist "böse". Fixe kommunikatoon

                                    Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                    • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                    • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                    MyzerATM 1 Antwort Letzte Antwort
                                    0
                                    • apollon77A apollon77

                                      @diginix Ok, da hats wohl mein changelog zerbröselt ... ab 3.14 ist "böse". Fixe kommunikatoon

                                      MyzerATM Offline
                                      MyzerATM Offline
                                      MyzerAT
                                      schrieb am zuletzt editiert von MyzerAT
                                      #169

                                      @apollon77

                                      habe seit heute selbiges problem, habe dann auf 3.17.4 update gemacht und seither bekomme ich keine smart home devices unter objekte mehr angezeigt

                                      1841ee1d-feb5-47f8-aad5-56ecbbe48d06-grafik.png

                                      habe schon alles durch an tipps was ich gefunden habe.

                                      Instanz komplett gelöscht
                                      iobrokeriot skill in der handy app de und wieder aktiviert
                                      mehrere neustarts

                                      lg Rudi

                                      Master Debian 12 (Wien)
                                      Intel NUC6CAYH 16GB RAM, 500 GB SSD & auf Proxmox 8. 7. als VM

                                      Slave Debian 12. (TULLN) --> OpenVPN to Vienna
                                      Intel NUC6CAYH 16GB RAM, 500 GB SSD & auf Proxmox 8.7. als VM

                                      Node 20.19.0
                                      Nodejs 20.19.0
                                      npm 10.8.2
                                      js-controller 7.0.6

                                      1 Antwort Letzte Antwort
                                      0
                                      • ? Offline
                                        ? Offline
                                        Ein ehemaliger Benutzer
                                        schrieb am zuletzt editiert von Ein ehemaliger Benutzer
                                        #170

                                        @myzerat Hast du in der Config des Adapters ( Achtung hat sich einiges geaendert! ) auch das Sync der Smarthome Devices aktiviert?

                                        MyzerATM 1 Antwort Letzte Antwort
                                        0
                                        • ? Ein ehemaliger Benutzer

                                          @myzerat Hast du in der Config des Adapters ( Achtung hat sich einiges geaendert! ) auch das Sync der Smarthome Devices aktiviert?

                                          MyzerATM Offline
                                          MyzerATM Offline
                                          MyzerAT
                                          schrieb am zuletzt editiert von
                                          #171

                                          @ilovegym

                                          wo sollte das sein ?

                                          lg Rudi

                                          Master Debian 12 (Wien)
                                          Intel NUC6CAYH 16GB RAM, 500 GB SSD & auf Proxmox 8. 7. als VM

                                          Slave Debian 12. (TULLN) --> OpenVPN to Vienna
                                          Intel NUC6CAYH 16GB RAM, 500 GB SSD & auf Proxmox 8.7. als VM

                                          Node 20.19.0
                                          Nodejs 20.19.0
                                          npm 10.8.2
                                          js-controller 7.0.6

                                          ? 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

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

                                          797

                                          Online

                                          32.4k

                                          Benutzer

                                          81.5k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe