Skip to content

ioBroker Allgemein

29.7k Topics 437.9k Posts
Integrationtsplattform für IoT

NEWS

  • Yahka Probleme

    8
    0 Votes
    8 Posts
    838 Views
    R
    @wendy2702 Das Log File vom Yahka Adapter habe ich inkl. der Installation mal angehangen und auch die Screenshots der Konfiguration. Habe jetzt für die Testinstallation erst einmal alles auf "Standard" gelassen. yahka.0 2023-03-12 16:54:59.787 debug [Licht Buero.On] set was initiated from ioBroker - exiting here yahka.0 2023-03-12 16:54:59.787 debug [Licht Buero.On] got a set event, hkValue: false yahka.0 2023-03-12 16:54:59.787 debug [Licht Buero.On] initializing homekit with value from ioBroker (false) to homekit as (0) yahka.0 2023-03-12 16:54:59.787 debug read state from ioBroker [knx.0.Licht.Schalten.Buero_Licht_Decke]: {"val":false,"ack":true,"ts":1678541219755,"q":0,"from":"system.adapter.knx.0","user":"system.user.admin","lc":1678541218825} yahka.0 2023-03-12 16:54:59.785 debug [Licht Buero.On] set was initiated from ioBroker - exiting here yahka.0 2023-03-12 16:54:59.785 debug [Licht Buero.On] got a set event, hkValue: false yahka.0 2023-03-12 16:54:59.785 debug [Licht Buero.On] forwarding value from ioBroker (0) to homekit as (0) yahka.0 2023-03-12 16:54:59.785 debug [Licht Buero.On] got a change notify event, ioValue: 0 yahka.0 2023-03-12 16:54:59.785 debug change event from ioBroker via [knx.0.Licht.Schalten.Buero_Licht_Decke]{"val":0,"ack":true,"ts":1678541219755,"q":0,"from":"system.adapter.knx.0","user":"system.user.admin","lc":1678541218825} yahka.0 2023-03-12 16:54:59.765 info publishing bridge Yahka-0 on 0.0.0.0 using ciao yahka.0 2023-03-12 16:54:59.765 debug reading state from ioBroker [knx.0.Licht.Schalten.Buero_Licht_Decke] yahka.0 2023-03-12 16:54:59.765 debug added subscription for: [state]knx.0.Licht.Schalten.Buero_Licht_Decke yahka.0 2023-03-12 16:54:59.763 debug [Licht Buero] adding Service Licht Buero yahka.0 2023-03-12 16:54:59.763 info adding Licht Buero with UUID: 05201c84-e5c1-46c7-916d-33d987baea9f yahka.0 2023-03-12 16:54:59.759 debug creating bridge yahka.0 2023-03-12 16:54:59.759 info adapter ready, checking config yahka.0 2023-03-12 16:54:59.748 info starting. Version 0.13.1 in /opt/iobroker/node_modules/iobroker.yahka, node: v16.19.1, js-controller: 4.0.24 yahka.0 2023-03-12 16:54:59.650 debug States connected to redis: 0.0.0.0:9000 yahka.0 2023-03-12 16:54:59.595 debug States create User PubSub Client yahka.0 2023-03-12 16:54:59.595 debug States create System PubSub Client yahka.0 2023-03-12 16:54:59.587 debug Redis States: Use Redis connection: 0.0.0.0:9000 yahka.0 2023-03-12 16:54:59.574 debug Objects connected to redis: 0.0.0.0:9001 yahka.0 2023-03-12 16:54:59.570 debug Objects client initialize lua scripts yahka.0 2023-03-12 16:54:59.570 info Sets unsupported yahka.0 2023-03-12 16:54:59.547 debug Objects create User PubSub Client yahka.0 2023-03-12 16:54:59.546 debug Objects create System PubSub Client yahka.0 2023-03-12 16:54:59.546 debug Objects client ready ... initialize now yahka.0 2023-03-12 16:54:59.530 debug Redis Objects: Use Redis connection: 0.0.0.0:9001 yahka.0 2023-03-12 16:54:55.242 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason yahka.0 2023-03-12 16:54:55.242 info terminating yahka.0 2023-03-12 16:54:55.242 info cleaned up ... yahka.0 2023-03-12 16:54:55.242 info cleaning up ... yahka.0 2023-03-12 16:54:55.242 info Got terminate signal TERMINATE_YOURSELF yahka.0 2023-03-12 16:53:15.277 debug [Licht Buero.On] forwarding value from ioBroker (false) to homekit as (0) yahka.0 2023-03-12 16:53:15.277 debug read state from ioBroker [knx.0.Licht.Schalten.Buero_Licht_Decke]: {"val":false,"ack":true,"ts":1678541219755,"q":0,"from":"system.adapter.knx.0","user":"system.user.admin","lc":1678541218825} yahka.0 2023-03-12 16:53:15.277 debug reading state from ioBroker [knx.0.Licht.Schalten.Buero_Licht_Decke] yahka.0 2023-03-12 16:53:15.276 debug [Licht Buero.On] got a get event yahka.0 2023-03-12 16:53:14.056 debug [Licht Buero.On] forwarding value from ioBroker (false) to homekit as (0) yahka.0 2023-03-12 16:53:14.056 debug read state from ioBroker [knx.0.Licht.Schalten.Buero_Licht_Decke]: {"val":false,"ack":true,"ts":1678541219755,"q":0,"from":"system.adapter.knx.0","user":"system.user.admin","lc":1678541218825} yahka.0 2023-03-12 16:53:14.055 debug reading state from ioBroker [knx.0.Licht.Schalten.Buero_Licht_Decke] yahka.0 2023-03-12 16:53:14.055 debug [Licht Buero.On] got a get event yahka.0 2023-03-12 16:52:49.168 debug [Licht Buero.On] set was initiated from ioBroker - exiting here yahka.0 2023-03-12 16:52:49.168 debug [Licht Buero.On] got a set event, hkValue: false yahka.0 2023-03-12 16:52:49.167 debug [Licht Buero.On] initializing homekit with value from ioBroker (false) to homekit as (0) yahka.0 2023-03-12 16:52:49.167 debug read state from ioBroker [knx.0.Licht.Schalten.Buero_Licht_Decke]: {"val":false,"ack":true,"ts":1678541219755,"q":0,"from":"system.adapter.knx.0","user":"system.user.admin","lc":1678541218825} yahka.0 2023-03-12 16:52:49.167 debug [Licht Buero.On] set was initiated from ioBroker - exiting here yahka.0 2023-03-12 16:52:49.167 debug [Licht Buero.On] got a set event, hkValue: false yahka.0 2023-03-12 16:52:49.167 debug [Licht Buero.On] forwarding value from ioBroker (0) to homekit as (0) yahka.0 2023-03-12 16:52:49.167 debug [Licht Buero.On] got a change notify event, ioValue: 0 yahka.0 2023-03-12 16:52:49.166 debug change event from ioBroker via [knx.0.Licht.Schalten.Buero_Licht_Decke]{"val":0,"ack":true,"ts":1678541219755,"q":0,"from":"system.adapter.knx.0","user":"system.user.admin","lc":1678541218825} yahka.0 2023-03-12 16:52:49.083 info publishing bridge Yahka-0 on 0.0.0.0 using ciao yahka.0 2023-03-12 16:52:49.083 debug reading state from ioBroker [knx.0.Licht.Schalten.Buero_Licht_Decke] yahka.0 2023-03-12 16:52:49.083 debug added subscription for: [state]knx.0.Licht.Schalten.Buero_Licht_Decke yahka.0 2023-03-12 16:52:49.081 debug [Licht Buero] adding Service Licht Buero yahka.0 2023-03-12 16:52:49.080 info adding Licht Buero with UUID: 05201c84-e5c1-46c7-916d-33d987baea9f yahka.0 2023-03-12 16:52:49.077 debug creating bridge yahka.0 2023-03-12 16:52:49.077 info adapter ready, checking config yahka.0 2023-03-12 16:52:49.065 info starting. Version 0.13.1 in /opt/iobroker/node_modules/iobroker.yahka, node: v16.19.1, js-controller: 4.0.24 yahka.0 2023-03-12 16:52:48.974 debug States connected to redis: 0.0.0.0:9000 yahka.0 2023-03-12 16:52:48.918 debug States create User PubSub Client yahka.0 2023-03-12 16:52:48.918 debug States create System PubSub Client yahka.0 2023-03-12 16:52:48.909 debug Redis States: Use Redis connection: 0.0.0.0:9000 yahka.0 2023-03-12 16:52:48.898 debug Objects connected to redis: 0.0.0.0:9001 yahka.0 2023-03-12 16:52:48.894 debug Objects client initialize lua scripts yahka.0 2023-03-12 16:52:48.893 info Sets unsupported yahka.0 2023-03-12 16:52:48.870 debug Objects create User PubSub Client yahka.0 2023-03-12 16:52:48.870 debug Objects create System PubSub Client yahka.0 2023-03-12 16:52:48.869 debug Objects client ready ... initialize now yahka.0 2023-03-12 16:52:48.854 debug Redis Objects: Use Redis connection: 0.0.0.0:9001 yahka.0 2023-03-12 16:52:44.535 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason yahka.0 2023-03-12 16:52:44.535 info terminating yahka.0 2023-03-12 16:52:44.534 info cleaned up ... yahka.0 2023-03-12 16:52:44.534 info cleaning up ... yahka.0 2023-03-12 16:52:44.534 info Got terminate signal TERMINATE_YOURSELF yahka.0 2023-03-12 16:51:50.480 info publishing bridge Yahka-0 on 0.0.0.0 using ciao yahka.0 2023-03-12 16:51:50.474 debug creating bridge yahka.0 2023-03-12 16:51:50.474 info adapter ready, checking config yahka.0 2023-03-12 16:51:50.462 info starting. Version 0.13.1 in /opt/iobroker/node_modules/iobroker.yahka, node: v16.19.1, js-controller: 4.0.24 yahka.0 2023-03-12 16:51:50.248 debug States connected to redis: 0.0.0.0:9000 yahka.0 2023-03-12 16:51:50.191 debug States create User PubSub Client yahka.0 2023-03-12 16:51:50.191 debug States create System PubSub Client yahka.0 2023-03-12 16:51:50.183 debug Redis States: Use Redis connection: 0.0.0.0:9000 yahka.0 2023-03-12 16:51:50.171 debug Objects connected to redis: 0.0.0.0:9001 yahka.0 2023-03-12 16:51:50.167 debug Objects client initialize lua scripts yahka.0 2023-03-12 16:51:50.167 info Sets unsupported yahka.0 2023-03-12 16:51:50.141 debug Objects create User PubSub Client yahka.0 2023-03-12 16:51:50.141 debug Objects create System PubSub Client yahka.0 2023-03-12 16:51:50.140 debug Objects client ready ... initialize now yahka.0 2023-03-12 16:51:50.123 debug Redis Objects: Use Redis connection: 0.0.0.0:9001 yahka.0 2023-03-12 16:51:44.605 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason yahka.0 2023-03-12 16:51:44.605 info terminating yahka.0 2023-03-12 16:51:44.605 info cleaned up ... yahka.0 2023-03-12 16:51:44.605 info cleaning up ... yahka.0 2023-03-12 16:51:44.604 info Got terminate signal TERMINATE_YOURSELF yahka.0 2023-03-12 16:51:36.659 info publishing bridge Yahka-0 on 0.0.0.0 using ciao yahka.0 2023-03-12 16:51:36.656 info adapter ready, checking config yahka.0 2023-03-12 16:51:36.643 info starting. Version 0.13.1 in /opt/iobroker/node_modules/iobroker.yahka, node: v16.19.1, js-controller: 4.0.24 yahka.0 2023-03-12 16:51:36.465 info Sets unsupported yahka.0 2023-03-12 16:51:32.142 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason yahka.0 2023-03-12 16:51:32.142 info terminating yahka.0 2023-03-12 16:51:32.141 info cleaned up ... yahka.0 2023-03-12 16:51:32.141 info cleaning up ... yahka.0 2023-03-12 16:51:32.141 info Got terminate signal TERMINATE_YOURSELF yahka.0 2023-03-12 16:51:32.022 info publishing bridge Yahka-0 on 0.0.0.0 using ciao yahka.0 2023-03-12 16:51:32.019 info first time initialization yahka.0 2023-03-12 16:51:32.018 info adapter ready, checking config yahka.0 2023-03-12 16:51:32.007 info starting. Version 0.13.1 in /opt/iobroker/node_modules/iobroker.yahka, node: v16.19.1, js-controller: 4.0.24 [image: 1678637058092-2023-03-12_17h02_34.png] [image: 1678637057866-2023-03-12_17h02_23.png] [image: 1678637057635-2023-03-12_17h00_57.png] MOD EDIT: LOG IN CODE TAGS GESETZT </>
  • SourceAnalytix Objektbaum nicht vorhanden

    7
    2
    0 Votes
    7 Posts
    504 Views
    HomoranH
    @ronniboy sagte in SourceAnalytix Objektbaum nicht vorhanden: man muss doch in der Basiseinstellung alle Felder ausfühll. und mal das log lesen. Wofür rackert es sich denn so ab?
  • Ubuntu 22.10 - falsche node Version?

    16
    0 Votes
    16 Posts
    412 Views
    Thomas BraunT
    @tholterhus sagte in Ubuntu 22.10 - falsche node Version?: die 18.x zu entfernen und auf die 16.x downzugraden. Kann man natürlich. Nennt sich apt pinning.
  • [gelöst] Adapter in den Instanzen oder in „Adapter“ löschen?

    8
    0 Votes
    8 Posts
    222 Views
    HomoranH
    @ben1983 sagte in Adapter in den Instanzen oder im Reiter Adapter löschen?: Hat alles gepasst. warum auch nicht?
  • Hama LED in Yahka

    1
    1
    0 Votes
    1 Posts
    61 Views
    No one has replied
  • Wechsel von Sonoff zu MQTT Adapter - Fehlende Objekte

    4
    3
    0 Votes
    4 Posts
    374 Views
    CodierknechtC
    @robson sagte in Wechsel von Sonoff zu MQTT Adapter - Fehlende Objekte: Das ist mir aktuell zu viel Arbeit und bleibe daher mit meinen Tasmota-Devices beim Sonoff-Adapter Darum packe ich - wo es möglich ist - Tasmota drauf. Aber manchmal geht's hat nicht ;-)
  • HUE Adapter -> Dimmer Switch

    Moved
    17
    0 Votes
    17 Posts
    4k Views
    D
    @michael2142 Das habe ich auch, wenn ich dem Switch keine Lampe oder Zone zu weisen. Ist dies allerdings bei HUE gemacht, bekomme ich die Ziffern als Code.
  • Datenhistorie für Shelly 3em

    Moved
    19
    0 Votes
    19 Posts
    1k Views
    HomoranH
    @andy-2 würdest du bitte den Threadtitel anpassen und nicht deinen letzten Post kopieren.
  • Frage zum Info-Adapter

    info-adapter 2. instanz master-slave
    1
    0 Votes
    1 Posts
    148 Views
    No one has replied
  • 0 Votes
    13 Posts
    1k Views
    O
    @arteck Muß ich da was tun? This object will not be created in future versions. Please report this to the developer.
  • gelöst! Alexa speak funktion funktioniert nicht via Skript

    10
    3
    0 Votes
    10 Posts
    821 Views
    R
    @djmarc75 sagte in Alexa speak funktion funktioniert nicht via Skript: @rebel85 Den Volume Block kannst Du Dir auch sparen indem Du im Feld vom SPEAK Block den Volumewert VOR den Text setzt: 30;Gute Nacht und schlaf gut. Danke für den tipp, werd ich gleich überall mal umändern
  • Warnmeldungen bei Adapterinstallation

    4
    0 Votes
    4 Posts
    413 Views
    Thomas BraunT
    @loverz iob stop iob fix iob start WARTEN iob diag
  • 0 Votes
    10 Posts
    665 Views
    R
    @apollon77 Super, danke!
  • backitup bricht bei sicherung zigbee2mqtt ab

    35
    1
    0 Votes
    35 Posts
    3k Views
    R
    @simatec Danke für Deine schnelle Hilfe. Und die rege Unterstützung aller Beteiligten, @arteck !
  • Deconz-Gui

    53
    0 Votes
    53 Posts
    6k Views
    G
    @thomas-braun ja das stimmt, hätte gerne was ausgelesen in der GUI, aber wenn es nicht geht dann ist das so. Danke dir für deine Hilfe!!!
  • 0 Votes
    5 Posts
    483 Views
    E
    Ich kann das Problem nicht lokalisieren. Was kann ich noch versuchen?
  • InfluxDB Werte in festem Intervall loggen

    2
    1
    0 Votes
    2 Posts
    359 Views
    michif100M
    @michif100 Wobei, wen nich hier in Influx die RAW Data anschaue, sieht es ja so aus, als ob die Werte nur alles 10 Sekunden kommen, oder? Aber warum dann nicht im 5 Sekunden Takt? [image: 1678545404975-scr-20230311-nugt.png]
  • Modbus Adapter Docker & Multihost

    2
    0 Votes
    2 Posts
    511 Views
    F
    -> Thema hat sich mit iob fix gelöst
  • Zugriff Auf Datenpunkte liefert keine Werte

    20
    0 Votes
    20 Posts
    2k Views
    HomoranH
    @tscho32 sagte in Zugriff Auf Datenpunkte liefert keine Werte: Ich habe exakt das selbe Problem wie du definitiv nicht! es ging um die ID Selector box! davon sehe ich bei dir nichts. Gar nichts.
  • VIS jqui - log: type "boolean" but received type "number"

    vis jqui
    9
    1
    0 Votes
    9 Posts
    471 Views
    M
    @bahnuhr Ich bin eben auch darüber gestolpert. Für mich scheint dieser Workaround zu helfen. Ich nehme tplJquiRadioList (jqui RadioButton List), und als Werte wahr/falsch (values":"true;false","texts":"an;aus"). Update: ich glaube das war Quatsch...

577

Online

32.9k

Users

83.0k

Topics

1.3m

Posts