iobroker Shutdown/Start unter Windows
-
@gaspode said in Alpha Test js-controller Kiera (v6.0):
Ich hab jetzt nochmal ein wenig rum probiert. Ich hab die Meldung auch mit dem aktuellen JS-Controller, wenn ich "kurz" zuvor ioBroker gestoppt habe und "gleich" wieder starte. Ist mir noch nie aufgefallen. Node.js Prozesse gibt es zu dieser Zeit allerdings keine mehr.
Ich tippe drauf, dass da was beim Shutdown unsauber abläuft und beim Start nicht wirklich bereinigt wird. Es betrifft (bei mir) ja nicht alle Adapter.
Um 11:22 hab ich das System runtergefahren. Dabei wurde von 3 Adaptern (admin, backitup und notification manager) ein "unsauberer" shutdown mit nachfolgendem Restart gelogged.
Und genau diese 3 Adapter haben beim Start ab 11:37 einen already running error gemeldet.@foxriver76
Hast du da eine Idee dazu? Kann ich / wir da was testen um es weiter einzugrenzen?
Auch wenn wahrscheinlich kein neues js-controlelr 6 issue ist könnte man es ev mit dem js-controller 6 fixen. Ist aber in jedem Fall eher cosmetic.Übrigends: Der js-controller logged scheinbar nicht, dass er den Befehl zum stoppen bekommen hat. Wär m.e. sinnvoll das im Log zu haben. Ich schreib dazu einen Feature Issue.
v6.17.11 22 69 Log-Größe: 26.8 KB 1 Zeit debug Nachricht admin.0 2024-05-24 11:42:36.689 info ==> Connected system.user.admin from ::1 discovery.0 2024-05-24 11:38:26.404 info starting. Version 4.2.0 in C:/ioBroker/node_modules/iobroker.discovery, node: v20.13.1, js-controller: 6.0.1-alpha.0-20240523-1d3cb759c host.Envy 2024-05-24 11:38:24.894 info instance system.adapter.discovery.0 started with pid 23076 notification-manager.0 2024-05-24 11:38:18.271 info Starting notification manager ... notification-manager.0 2024-05-24 11:38:18.260 info starting. Version 1.1.2 in C:/ioBroker/node_modules/iobroker.notification-manager, node: v20.13.1, js-controller: 6.0.1-alpha.0-20240523-1d3cb759c host.Envy 2024-05-24 11:38:16.979 info instance system.adapter.notification-manager.0 started with pid 11636 backitup.0 2024-05-24 11:38:15.504 info [iobroker] backup will be activated at 02:40 every 1 day(s) backitup.0 2024-05-24 11:38:15.456 info starting. Version 2.10.11 in C:/ioBroker/node_modules/iobroker.backitup, node: v20.13.1, js-controller: 6.0.1-alpha.0-20240523-1d3cb759c admin.0 2024-05-24 11:38:13.322 info Use link "http://127.0.0.1:8081" to configure. admin.0 2024-05-24 11:38:13.322 info http server listening on port 8081 admin.0 2024-05-24 11:38:13.320 info socket.io server listening on port 8081 host.Envy 2024-05-24 11:38:13.302 info instance system.adapter.backitup.0 started with pid 1460 admin.0 2024-05-24 11:38:13.023 info received all objects admin.0 2024-05-24 11:38:12.213 info requesting all objects admin.0 2024-05-24 11:38:12.192 info starting. Version 6.17.11 in C:/ioBroker/node_modules/iobroker.admin, node: v20.13.1, js-controller: 6.0.1-alpha.0-20240523-1d3cb759c host.Envy 2024-05-24 11:38:10.024 info instance system.adapter.admin.0 started with pid 8660 host.Envy 2024-05-24 11:37:56.430 info instance system.adapter.ical.1 terminated with code 0 (NO_ERROR) ical.1 2024-05-24 11:37:55.908 info Terminated (NO_ERROR): Without reason host.Envy 2024-05-24 11:37:54.547 info Restart adapter system.adapter.discovery.0 because enabled host.Envy 2024-05-24 11:37:54.547 error instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) discovery.0 2024-05-24 11:37:54.012 warn Terminated (ADAPTER_ALREADY_RUNNING): Without reason discovery.0 2024-05-24 11:37:54.011 error discovery.0 already running host.Envy 2024-05-24 11:37:52.741 info instance system.adapter.discovery.0 started with pid 10408 ical.1 2024-05-24 11:37:50.889 info All calenders could not be processed, Do not clean up events ical.1 2024-05-24 11:37:50.888 warn Error reading "http://11111.ics": Cannot read URL: "http://11111.ics" ical.1 2024-05-24 11:37:50.888 warn Error reading from URL "http://11111.ics" ical.1 2024-05-24 11:37:50.661 info starting. Version 1.15.0 in C:/ioBroker/node_modules/iobroker.ical, node: v20.13.1, js-controller: 6.0.1-alpha.0-20240523-1d3cb759c host.Envy 2024-05-24 11:37:48.837 info instance system.adapter.ical.1 started with pid 16528 host.Envy 2024-05-24 11:37:48.829 info instance scheduled system.adapter.ical.1 0,4 0,30 * * * * host.Envy 2024-05-24 11:37:46.671 info Restart adapter system.adapter.notification-manager.0 because enabled host.Envy 2024-05-24 11:37:46.670 error instance system.adapter.notification-manager.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) notification-manager.0 2024-05-24 11:37:46.126 warn Terminated (ADAPTER_ALREADY_RUNNING): Without reason notification-manager.0 2024-05-24 11:37:46.124 error notification-manager.0 already running host.Envy 2024-05-24 11:37:44.776 info instance system.adapter.notification-manager.0 started with pid 14436 host.Envy 2024-05-24 11:37:42.774 info Restart adapter system.adapter.backitup.0 because enabled host.Envy 2024-05-24 11:37:42.774 error instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) backitup.0 2024-05-24 11:37:42.250 warn Terminated (ADAPTER_ALREADY_RUNNING): Without reason backitup.0 2024-05-24 11:37:42.249 error backitup.0 already running host.Envy 2024-05-24 11:37:40.733 info instance system.adapter.backitup.0 started with pid 19664 host.Envy 2024-05-24 11:37:39.629 info Restart adapter system.adapter.admin.0 because enabled host.Envy 2024-05-24 11:37:39.629 error instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) admin.0 2024-05-24 11:37:39.056 warn Terminated (ADAPTER_ALREADY_RUNNING): Without reason admin.0 2024-05-24 11:37:39.054 error admin.0 already running host.Envy 2024-05-24 11:37:36.798 info Some obsolete host states deleted. host.Envy 2024-05-24 11:37:36.795 info Delete state "system.host.Envy.versions.npmNewestNext" host.Envy 2024-05-24 11:37:36.791 info Delete state "system.host.Envy.versions.npmNewest" host.Envy 2024-05-24 11:37:36.787 info Delete state "system.host.Envy.versions.npmCurrent" host.Envy 2024-05-24 11:37:36.781 info instance system.adapter.admin.0 started with pid 12684 host.Envy 2024-05-24 11:37:36.774 info Delete state "system.host.Envy.versions.nodeNewestNext" host.Envy 2024-05-24 11:37:36.766 info Delete state "system.host.Envy.versions.nodeNewest" host.Envy 2024-05-24 11:37:36.728 info Delete state "system.host.Envy.versions.nodeCurrent" host.Envy 2024-05-24 11:37:36.419 info starting 5 instances host.Envy 2024-05-24 11:37:36.404 info 17 instances found host.Envy 2024-05-24 11:37:35.648 info added notifications configuration of host host.Envy 2024-05-24 11:37:35.632 info connected to Objects and States host.Envy 2024-05-24 11:37:35.136 info ip addresses: 10.17.2.100 fe80::3089:3ca1:e684:7494 10.17.2.16 host.Envy 2024-05-24 11:37:35.136 info hostname: Envy, node: v20.13.1 host.Envy 2024-05-24 11:37:35.136 info Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker host.Envy 2024-05-24 11:37:35.133 info iobroker.js-controller version 6.0.1 js-controller starting host.Envy 2024-05-24 11:22:35.097 info Restart adapter system.adapter.notification-manager.0 because enabled host.Envy 2024-05-24 11:22:35.097 error instance system.adapter.notification-manager.0 terminated with code 4294967295 () host.Envy 2024-05-24 11:22:34.914 info Restart adapter system.adapter.backitup.0 because enabled host.Envy 2024-05-24 11:22:34.914 error instance system.adapter.backitup.0 terminated with code 4294967295 () host.Envy 2024-05-24 11:22:34.733 info Restart adapter system.adapter.admin.0 because enabled host.Envy 2024-05-24 11:22:34.732 error instance system.adapter.admin.0 terminated with code 4294967295 () -
@mcm1957 sagte in Alpha Test js-controller Kiera (v6.0):
Und genau diese 3 Adapter haben beim Start ab 11:37 einen already running error gemeldet.
Bei mir sind es einige mehr. War aber immer schon so. Beruhigt sich nach einiger Zeit wieder. Bis zum Neustart eben.
host.SmartHome 2024-05-24 11:58:49.508 error instance system.adapter.upnp.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:58:41.067 error instance system.adapter.vis-inventwo.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:58:37.231 error instance system.adapter.sayit.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:58:25.628 error instance system.adapter.ecovacs-deebot.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:58:22.100 error instance system.adapter.vis-2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:58:16.992 error instance system.adapter.parser.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:58:13.106 error instance system.adapter.tapo.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:58:09.359 error instance system.adapter.pollenflug.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:58:05.571 error instance system.adapter.musiccast.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:58:01.679 error instance system.adapter.web.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:57:57.194 error instance system.adapter.iot.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:57:53.440 error instance system.adapter.jarvis.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:57:49.746 error instance system.adapter.fb-checkpresence.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:57:45.893 error instance system.adapter.weather-warnings.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:57:42.774 error instance system.adapter.alarm.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:57:32.892 error instance system.adapter.socketio.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:57:29.354 error instance system.adapter.ws.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:57:24.995 error instance system.adapter.web.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:57:17.208 error instance system.adapter.snmp.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:57:12.895 error instance system.adapter.lgtv.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:57:05.988 error instance system.adapter.meross.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:56:57.522 error instance system.adapter.cloud.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:56:50.507 error instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:56:45.626 error instance system.adapter.yamaha.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:56:42.406 error instance system.adapter.tr-064.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:56:37.747 error instance system.adapter.hm-rpc.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:56:32.874 error instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:56:28.974 error instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:56:24.950 error instance system.adapter.hue.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:56:20.873 error instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:56:16.888 error instance system.adapter.email.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:56:13.251 error instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:56:09.200 error instance system.adapter.history.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:56:05.239 error instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.SmartHome 2024-05-24 11:55:52.252 error instance system.adapter.vis-inventwo.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:52.143 error instance system.adapter.sayit.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:52.042 error instance system.adapter.ecovacs-deebot.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:51.928 error instance system.adapter.vis-2.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:51.827 error instance system.adapter.parser.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:51.724 error instance system.adapter.tapo.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:51.540 error instance system.adapter.pollenflug.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:51.400 error instance system.adapter.musiccast.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:51.300 error instance system.adapter.web.1 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:51.182 error instance system.adapter.iot.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:51.081 error instance system.adapter.jarvis.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:50.961 error instance system.adapter.fb-checkpresence.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:50.853 error instance system.adapter.weather-warnings.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:50.752 error instance system.adapter.alarm.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:50.652 error instance system.adapter.socketio.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:50.553 error instance system.adapter.ws.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:50.447 error instance system.adapter.web.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:50.347 error instance system.adapter.snmp.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:50.250 error instance system.adapter.lgtv.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:50.149 error instance system.adapter.meross.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:50.050 error instance system.adapter.cloud.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:49.944 error instance system.adapter.alexa2.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:49.825 error instance system.adapter.yamaha.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:49.697 error instance system.adapter.tr-064.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:49.576 error instance system.adapter.hm-rpc.1 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:49.471 error instance system.adapter.hm-rega.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:49.363 error instance system.adapter.hm-rpc.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:49.226 error instance system.adapter.hue.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:49.091 error instance system.adapter.backitup.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:48.983 error instance system.adapter.email.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:48.883 error instance system.adapter.javascript.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:48.747 error instance system.adapter.history.0 terminated with code 4294967295 () host.SmartHome 2024-05-24 11:55:48.583 error instance system.adapter.admin.0 terminated with code 4294967295 () -
@mcm1957 sagte in Alpha Test js-controller Kiera (v6.0):
@sigi234
OK, aber auch diese haben einen "ungewöhnlichen" Existstatus beim Beenden.Jupp, hat wahrscheinlich nix mit js-controller Kiera zu tun, ev. sollte man das abtrennen in einen Neuen Beitrag?
-
@sigi234 said in Alpha Test js-controller Kiera (v6.0):
@mcm1957 sagte in Alpha Test js-controller Kiera (v6.0):
@sigi234
OK, aber auch diese haben einen "ungewöhnlichen" Existstatus beim Beenden.Jupp, hat wahrscheinlich nix mit js-controller Kiera zu tun, ev. sollte man das abtrennen in einen Neuen Beitrag?
Jaein.
Warten wir mal ab ob / was @Foxriver76 sagt. Wenn es ein js-controller Problem ist kann es ev. auch hier bleiben. Wenn wir mehr Suchdiskussion brauchen ists ev. extra besser. Aber im Prinzip ist im Moment wahrscheinlich alles geschrieben bis wer der den betreffenden Code gut kennt sagen kann was da los ist bzw. zu suchen wäre. Ist jedenfalls kein Einzelfall. -
@mcm1957 said in Alpha Test js-controller Kiera (v6.0):
Ich tippe drauf, dass da was beim Shutdown unsauber abläuft und beim Start nicht wirklich bereinigt wird. Es betrifft (bei mir) ja nicht alle Adapter.
Hmm, ich denke immer noch, dass da grundsätzlich was krumm ist unter Windows.
Versuch(t) mal folgendes bei gestartetem ioBroker:iob stop iob status iob status iob startBei mir antwortet "iob status" Nummer 1 "iobroker is running on this host.", obwohl keinerlei Node.js-Prozess auf dem Rechner läuft. Aufruf Nummer 2 liefert "iobroker is not running on this host.", wie es sein soll. Der nächste Start erfolgt dann bei mir sauber OHNE diese ADAPTER_ALREADY_RUNNING Meldungen.
2024-05-24 13:05:28.210 - [32minfo[39m: host.SmartHome5 iobroker.js-controller version 6.0.1 js-controller starting 2024-05-24 13:05:28.211 - [32minfo[39m: host.SmartHome5 Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-05-24 13:05:28.211 - [32minfo[39m: host.SmartHome5 hostname: SmartHome5, node: v20.13.1 2024-05-24 13:05:28.211 - [32minfo[39m: host.SmartHome5 ip addresses: XXXXXXXXXXXXXXXXXXXXXXX 2024-05-24 13:05:28.335 - [32minfo[39m: host.SmartHome5 connected to Objects and States 2024-05-24 13:05:28.339 - [32minfo[39m: host.SmartHome5 added notifications configuration of host 2024-05-24 13:05:28.478 - [32minfo[39m: host.SmartHome5 4 instances found 2024-05-24 13:05:28.479 - [32minfo[39m: host.SmartHome5 starting 3 instances 2024-05-24 13:05:28.543 - [32minfo[39m: host.SmartHome5 Delete state "system.host.SmartHome5.versions.nodeCurrent" 2024-05-24 13:05:28.548 - [32minfo[39m: host.SmartHome5 Delete state "system.host.SmartHome5.versions.nodeNewest" 2024-05-24 13:05:28.558 - [32minfo[39m: host.SmartHome5 instance system.adapter.admin.0 started with pid 31324 2024-05-24 13:05:28.559 - [32minfo[39m: host.SmartHome5 Delete state "system.host.SmartHome5.versions.nodeNewestNext" 2024-05-24 13:05:28.560 - [32minfo[39m: host.SmartHome5 Delete state "system.host.SmartHome5.versions.npmCurrent" 2024-05-24 13:05:28.561 - [32minfo[39m: host.SmartHome5 Delete state "system.host.SmartHome5.versions.npmNewest" 2024-05-24 13:05:28.562 - [32minfo[39m: host.SmartHome5 Delete state "system.host.SmartHome5.versions.npmNewestNext" 2024-05-24 13:05:28.562 - [32minfo[39m: host.SmartHome5 Some obsolete host states deleted. 2024-05-24 13:05:29.331 - [32minfo[39m: admin.0 (31324) starting. Version 6.13.16 in C:/ioBroker/SmartHome5/node_modules/iobroker.admin, node: v20.13.1, js-controller: 6.0.1-alpha.0-20240523-1d3cb759c 2024-05-24 13:05:29.343 - [32minfo[39m: admin.0 (31324) requesting all objects 2024-05-24 13:05:29.479 - [32minfo[39m: admin.0 (31324) received all objects 2024-05-24 13:05:29.523 - [32minfo[39m: admin.0 (31324) socket.io server listening on port 8191 2024-05-24 13:05:29.523 - [32minfo[39m: admin.0 (31324) http server listening on port 8191 2024-05-24 13:05:29.523 - [32minfo[39m: admin.0 (31324) Use link "http://127.0.0.1:8191" to configure. 2024-05-24 13:05:32.566 - [32minfo[39m: host.SmartHome5 instance system.adapter.backitup.0 started with pid 36456 2024-05-24 13:05:33.240 - [32minfo[39m: backitup.0 (36456) starting. Version 2.11.0 in C:/ioBroker/SmartHome5/node_modules/iobroker.backitup, node: v20.13.1, js-controller: 6.0.1-alpha.0-20240523-1d3cb759c 2024-05-24 13:05:33.261 - [32minfo[39m: backitup.0 (36456) [iobroker] backup will be activated at 02:48 every 1 day(s) 2024-05-24 13:05:36.571 - [32minfo[39m: host.SmartHome5 instance system.adapter.discovery.0 started with pid 32412 2024-05-24 13:05:37.209 - [32minfo[39m: discovery.0 (32412) starting. Version 4.4.0 in C:/ioBroker/SmartHome5/node_modules/iobroker.discovery, node: v20.13.1, js-controller: 6.0.1-alpha.0-20240523-1d3cb759cDas verhält sich bei mir gleich mit Controller 5 und 6. also evtl. doch abtrennen, um das hier übersichtlicher zu halten?
-
@gaspode sagte in Alpha Test js-controller Kiera (v6.0):
evtl. doch abtrennen
wenn gewünscht, bitte Link zum ersten abzutrennenden Post.
Danke
-
@homoran said in Alpha Test js-controller Kiera (v6.0):
wenn gewünscht, bitte Link zum ersten abzutrennenden Post.
Lass uns mal warten, ob und was @foxriver76 dazu meint.
Betroffen sind diese Beiträge:
https://forum.iobroker.net/post/1162260
https://forum.iobroker.net/post/1162264
https://forum.iobroker.net/post/1162266
https://forum.iobroker.net/post/1162267
https://forum.iobroker.net/post/1162311
https://forum.iobroker.net/post/1162316
https://forum.iobroker.net/post/1162317
https://forum.iobroker.net/post/1162327
https://forum.iobroker.net/post/1162329
https://forum.iobroker.net/post/1162355 -
-
@gaspode Danke fpr die Liste, hat aber leider beim selektieren nicht geholfen, wenn ich im Auswahlmenü bin.
ich hoffe ich habe alles und nicht zu viel.
wie immer
ggf. provisorischen Threadtitel anpassen -
@homoran said in iobroker Shutdown unter Windowe:
ich hoffe ich habe alles und nicht zu viel.
Sieht gut aus, Danke.
-
Falscher Thread
-
-- obsoleter Text ---
-
Hier geht es weiter:
https://forum.iobroker.net/topic/75829@Homoran
Ich denke, dieser Thread hier kann geschlossen werden. Wärst du so nett? Danke.
-
@gaspode erledigt!
