NEWS
Yahka schaltet nicht
-
Log file sagt?
-
@thomas-braun
im iobroker log steht nix vom yahka Adapter im Debug modus -
@robse Trotzdem posten.
Adapter Neustart, Ausgaben posten -
-
Keine Screenshots, Auszüge aus dem Log file in CodeTags hier rein posten.
-
2021-09-06 21:58:10.589 - [32minfo[39m: host.a4ddf15dc862 stopInstance system.adapter.yahka.0 (force=false, process=true) 2021-09-06 21:58:10.591 - [32minfo[39m: host.a4ddf15dc862 stopInstance system.adapter.yahka.0 send kill signal 2021-09-06 21:58:10.591 - [32minfo[39m: yahka.0 (12662) Got terminate signal TERMINATE_YOURSELF 2021-09-06 21:58:10.592 - [32minfo[39m: yahka.0 (12662) cleaning up ... 2021-09-06 21:58:10.592 - [32minfo[39m: yahka.0 (12662) cleaned up ... 2021-09-06 21:58:10.592 - [32minfo[39m: yahka.0 (12662) terminating 2021-09-06 21:58:10.592 - [32minfo[39m: yahka.0 (12662) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2021-09-06 21:58:11.112 - [32minfo[39m: host.a4ddf15dc862 instance system.adapter.yahka.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2021-09-06 21:58:11.113 - [32minfo[39m: node-red.0 (24781) State value to set for "0_userdata.0.Heizung_Leistung" has to be type "string" but received type "number" 2021-09-06 21:58:11.114 - [32minfo[39m: node-red.0 (24781) State value to set for "0_userdata.0.Heizung_Quelltemperatur_Eingang" has to be type "string" but received type "number" 2021-09-06 21:58:11.114 - [32minfo[39m: node-red.0 (24781) State value to set for "0_userdata.0.Heizung_Quelltemperatur_Ausgang" has to be type "string" but received type "number" 2021-09-06 21:58:13.604 - [32minfo[39m: host.a4ddf15dc862 instance system.adapter.yahka.0 started with pid 12779 2021-09-06 21:58:14.206 - [32minfo[39m: yahka.0 (12779) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.yahka, node: v12.22.5, js-controller: 3.3.15 2021-09-06 21:58:14.215 - [32minfo[39m: yahka.0 (12779) adapter ready, checking config 2021-09-06 21:58:14.218 - [32minfo[39m: yahka.0 (12779) adding Test Gerät with UUID: a95a1b70-1d0a-49ad-b5eb-2b392fb86145 2021-09-06 21:58:14.221 - [32minfo[39m: yahka.0 (12779) adding Büro Licht with UUID: 68404733-0ee7-4d39-8189-b8a42e2bb7ec 2021-09-06 21:58:14.221 - [32minfo[39m: yahka.0 (12779) adding Heizung Bad with UUID: d49eeda6-88b7-447b-b247-a344b4a47128 2021-09-06 21:58:14.222 - [32minfo[39m: yahka.0 (12779) adding Wohnzimmer Decke with UUID: 3e9c26a7-45f9-4d35-b2df-fdbb20358ed2 2021-09-06 21:58:14.222 - [32minfo[39m: yahka.0 (12779) adding Bodenlampe with UUID: cdfee335-ada1-4f9d-9805-e93cc3bb1340 2021-09-06 21:58:14.222 - [32minfo[39m: yahka.0 (12779) adding Stehlampe with UUID: 09378103-6ba9-4771-9dcf-95ff50333f98 2021-09-06 21:58:14.223 - [32minfo[39m: yahka.0 (12779) adding Test 2 with UUID: 0f0a1774-efa5-4e16-aead-c60c87cd8ebd 2021-09-06 21:58:14.223 - [32minfo[39m: yahka.0 (12779) publishing bridge HomeKit-iobroker on 0.0.0.0
-
Spielt da node-red noch mit rein?
-
Nein, das sind nur Log Einträge aus node-red, die zwischen, beenden und starten des Yahka Adapters kamen.
-
hat noch jemand eine Idee? Ich habe bereits eine neue iobroker Instanz aufgesetzt. Auch dort funktioniert yahka nicht
-
@thomas-braun hast du noch irgendeinen Tip für mich?
-
Von yahka hab ich keine Ahnung.