NEWS
Hilfe bei buderus km 200 adapter
-
Hallo
ich habe 2 adapter km200 und .ems-esp.
IP stimmt Pw auch. Der Km200 verbindet sich nicht und der ems ist verbunden mit host und hat lebenzeeichen
jemand ne Idee
danke
-
@pooldiver sagte in Hilfe bei buderus km 200 adapter:
jemand ne Idee
Idee noch nicht, aber die wichtigste Information fehlt in der Kette der Screenshots.
Das Protokoll. Aber bitte nicht als Screenshot sondern als Text, in Code tags </>
da muss beim Versuch den Adapter zu starten etwas drin landen. Zur not den Adapter im Debug starten.
A.
-
@asgothian so was
ems-esp.1
2025-03-10 12:24:15.981 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
ems-esp.1
2025-03-10 12:24:15.979 info terminating
ems-esp.1
2025-03-10 12:24:15.976 info Got terminate signal TERMINATE_YOURSELF
host.raspberrypi
2025-03-10 12:24:15.971 info stopInstance system.adapter.ems-esp.1 (force=false, process=true)
javascript.0
2025-03-10 12:24:15.732 info script.js.Pool.WP_on_off: setStateDelayed(id=tuya.0.47033807a4e57ca59265. -
@pooldiver So in etwa. Aber bitte in Code tags packen. Und mehr Kontext. Diese Einträge stammen nicht von dem gewünschten Adapter. ggf. musst du den Adapter anhalten und nochmal starten damit er ins Log schreibt.
A. -
@asgothian 2 versuch
ems-esp.1 2025-03-10 14:19:13.774 error error reading km200 gateway information (wrong ip address) - stop km200 read ems-esp.1 2025-03-10 14:19:13.756 info no database instance selected for recordings ems-esp.1 2025-03-10 14:19:13.754 error API version V2 identified. V2 is not supported anymore ems-esp.1 2025-03-10 14:19:13.667 info starting. Version 1.21.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v18.17.1, js-controller: 7.0.6 host.raspberrypi 2025-03-10 14:19:10.975 info instance system.adapter.ems-esp.1 in version "1.21.0" started with pid 10181 host.raspberrypi 2025-03-10 14:19:06.735 info instance system.adapter.ems-esp.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.raspberrypi 2025-03-10 14:19:06.290 info Do not restart adapter system.adapter.km200.0 because desired by instance host.raspberrypi 2025-03-10 14:19:06.290 info instance system.adapter.km200.0 terminated by request of the instance itself and will not be restarted, before user restarts it. host.raspberrypi 2025-03-10 14:19:06.217 info stopInstance system.adapter.ems-esp.1 send kill signal ems-esp.1 2025-03-10 14:19:06.175 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason ems-esp.1 2025-03-10 14:19:06.173 info terminating ems-esp.1 2025-03-10 14:19:06.170 info Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2025-03-10 14:19:06.164 info stopInstance system.adapter.ems-esp.1 (force=false, process=true) km200.0 2025-03-10 14:19:06.040 info Adapter km200 initialization finished with 0 states. km200.0 2025-03-10 14:19:06.024 info Slow Interval=6 hours, Slow-List: km200.0 2025-03-10 14:19:06.024 info Fast Interval=2 min, Fast-List: km200.0 2025-03-10 14:19:06.023 info Interval=30 min, Norm-list: km200.0 2025-03-10 14:19:06.021 info KM200 found 0 states, get their values now. km200.0 2025-03-10 14:19:06.020 info Services found: 41 km200.0 2025-03-10 14:19:06.019 warn Did not get any Services from KLM200!: {} km200.0 2025-03-10 14:19:05.997 warn Skip service data of /system km200.0 2025-03-10 14:19:05.850 warn Skip service data of /solarCircuits km200.0 2025-03-10 14:19:05.716 info Terminated (ADAPTER_REQUESTED_TERMINATION): km200 Initialization Error:TypeError: Cannot read properties of undefined (reading '_subscribeForeignStates') at subscribeStates (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:6660:17) at /opt/iobroker/node_modules/@frankjoke/myadapter/myAdapter.js:830:111 at new Promise (<anonymous>) at /opt/iobroker/node_modules/@frankjoke/myadapter/myAdapter.js:830:20 at /opt/iobroker/node_modules/@frankjoke/myadapter/myAdapter.js:311:77 km200.0 2025-03-10 14:19:05.704 warn Skip service data of /recordings km200.0 2025-03-10 14:19:05.559 warn Skip service data of /notifications km200.0 2025-03-10 14:19:05.411 warn Skip service data of /heatSources km200.0 2025-03-10 14:19:05.264 warn Skip service data of /heatingCircuits km200.0 2025-03-10 14:19:05.118 warn Skip service data of /gateway km200.0 2025-03-10 14:19:04.969 warn Skip service data of /dhwCircuits km200.0 2025-03-10 14:19:04.819 info km200.0 address: http://http://192.168.1.75 km200.0 2025-03-10 14:19:04.815 warn Adapter will exit in latest 1 sec with code km200 Initialization Error:TypeError: Cannot read properties of undefined (reading '_subscribeForeignStates') at subscribeStates (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:6660:17) at /opt/iobroker/node_modules/@frankjoke/myadapter/myAdapter.js:830:111 at new Promise (<anonymous>) at /opt/iobroker/node_modules/@frankjoke/myadapter/myAdapter.js:830:20 at /opt/iobroker/node_modules/@frankjoke/myadapter/myAdapter.js:311:77! km200.0 2025-03-10 14:19:04.813 info Adapter disconnected and stopped with dostop(km200 Initialization Error:TypeError: Cannot read properties of undefined (reading '_subscribeForeignStates') at subscribeStates (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:6660:17) at /opt/iobroker/node_modules/@frankjoke/myadapter/myAdapter.js:830:111 at new Promise (<anonymous>) at /opt/iobroker/node_modules/@frankjoke/myadapter/myAdapter.js:830:20 at /opt/iobroker/node_modules/@frankjoke/myadapter/myAdapter.js:311:77) and callback(false) km200.0 2025-03-10 14:19:04.812 error km200 Initialization Error:TypeError: Cannot read properties of undefined (reading '_subscribeForeignStates') at subscribeStates (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:6660:17) at /opt/iobroker/node_modules/@frankjoke/myadapter/myAdapter.js:830:111 at new Promise (<anonymous>) at /opt/iobroker/node_modules/@frankjoke/myadapter/myAdapter.js:830:20 at /opt/iobroker/node_modules/@frankjoke/myadapter/myAdapter.js:311:77 km200.0 2025-03-10 14:19:04.705 info starting. Version 2.0.3 in /opt/iobroker/node_modules/iobroker.km200, node: v18.17.1, js-controller: 7.0.6 host.raspberrypi 2025-03-10 14:19:02.250 info instance system.adapter.km200.0 in version "2.0.3" started with pid 10166
-
@pooldiver sagte in Hilfe bei buderus km 200 adapter:
Aus dem Logging
km200.0 address: http://http://192.168.1.75
Das sieht komisch aus - anscheinend stellt der Adapter selbsttätig "http://" voran
Vielleicht mal hier die "nackte" IP-Adresse ohne vorangestelltes "http://" angeben...
-
@pooldiver sagte in Hilfe bei buderus km 200 adapter:
node: v18.17.1
Beobachtung am Rande:
Deine nodejs-Version ist abgesoffen. Bring das auf nodejs@20.iob nodejs-update 20
Vermutlich ist da aber auch noch mehr ranzig.
-
@thomas-braun In Github steht außerdem....
https://github.com/iobroker-community-adapters/ioBroker.km200
This adapter is DEPRECATED and will not be developed any further
Da reitet man ein totes Pferd ... (Seit Jul 2023)
-
@martinp sagte in Hilfe bei buderus km 200 adapter:
Da reitet man ein totes Pferd ...
Nicht nur eins.
Vermutlich liegt das tote Pferd im buster-Stall. -
@thomas-braun
Charakteristisch ist, dass @Pooldiver bei iobroker selber anscheinend im Beta Repository unterwegs ist ... aber da ein ziemlich abgehangene Version fährt...Aktuell:
EDIT - 7.4.21 ist doch nicht besonders alt:
-
Ergibt aber dennoch keinen Sinn. Denn was soll man da testen, wenn es schon längst aktuellere Versionen gibt?
-
Der Adapter .ioBroker.km200 ist DEPRECTED und ARCHIVED.
Aus dem README des km200:
This adapter is DEPRECATED and will not be developed any further
Currently there is no further development for this adapter planned. Please migrate to ioBroker.ems-esp adapter which is maintained. If you miss any features at ioBroker.ems-esp open an issue at that repository (https://github.com/tp1de/ioBroker.ems-esp/issues).IoBroker.km200 will stay available for some time, but keep in mind, that it will not be adapted to node 20 and upcoming js-controller v5.
Also vergiss und lösch den km200 Adapter und benutz den ems-esp der der dafür vorgesehne Nachfolger ist.
Offizieller Support Thread ist da:
https://forum.iobroker.net/topic/45862/neuer-adapter-ems-esp-für-bosch-heizungen -
Ich verwende weder den einen noch den anderen...
Du meintest vermutlich @Pooldiver -
@thomas-braun
Ja - sorry