Test Adapter drops-weather 1.2.x

[mcm1957]

@Winni
Hast du den Browser manuell auf chromium gestellt? Da ist offensichtloich ein Tippfehler wo drinnen. Kannst du mal versuchen auf dem zweiten Ta explizit auf AUTOmatic zu stellen?

[Winni]

@mcm1957 hatte ich auch probiert und jetzt nochmal, leider das gleiche Ergebnis.

drops-weather.0
2025-03-20 08:09:08.394	info	terminating

drops-weather.0
2025-03-20 08:09:07.898	error	Cannot read properties of null (reading 'pages')

drops-weather.0
2025-03-20 08:09:07.897	error	TypeError: Cannot read properties of null (reading 'pages') at DropsWeather.destroyBrowser (/opt/iobroker/node_modules/iobroker.drops-weather/main.js:320:37) at DropsWeather.onUnload (/opt/iobroker/node_modules/iobroker.drops-weather/main.js:335:18) at DropsWeather.emit (node:events:524:28) at DropsWeather._stop (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:1171:16) at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:7166:20) at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/build/esm/lib/states/statesInRedisClient.js:291:37) at process.processImmediate (node:internal/timers:483:21)

drops-weather.0
2025-03-20 08:09:07.895	error	unhandled promise rejection: Cannot read properties of null (reading 'pages')

drops-weather.0
2025-03-20 08:09:07.894	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

drops-weather.0
2025-03-20 08:09:07.893	info	terminating

drops-weather.0
2025-03-20 08:09:07.892	info	Got terminate signal TERMINATE_YOURSELF

drops-weather.0
2025-03-20 08:09:07.864	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

drops-weather.0
2025-03-20 08:09:07.862	error	error launching browser undefined - Error: Failed to launch the browser process! undefined TROUBLESHOOTING: https://pptr.dev/troubleshooting

drops-weather.0
2025-03-20 08:09:07.826	info	browserPath set to puppeteer default

drops-weather.0
2025-03-20 08:09:07.825	info	browserMode set to automatic

drops-weather.0
2025-03-20 08:09:07.813	info	starting. Version 1.1.0 (non-npm: iobroker-community-adapters/ioBroker.drops-weather) in /opt/iobroker/node_modules/iobroker.drops-weather, node: v20.19.0, js-controller: 7.0.6

[mcm1957]

@winni
Kannst du bitte mal mit debug Level starten und das log posten?
Ist aber nicht prior - muss dann weg und kann erst nachher in Code schaun.

[Winni]

@mcm1957, ok

drops-weather.0
2025-03-20 08:50:23.836	error	Cannot read properties of null (reading 'pages')

drops-weather.0
2025-03-20 08:50:23.836	error	TypeError: Cannot read properties of null (reading 'pages') at DropsWeather.destroyBrowser (/opt/iobroker/node_modules/iobroker.drops-weather/main.js:320:37) at DropsWeather.onUnload (/opt/iobroker/node_modules/iobroker.drops-weather/main.js:335:18) at DropsWeather.emit (node:events:524:28) at DropsWeather._stop (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:1171:16) at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:7166:20) at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/build/esm/lib/states/statesInRedisClient.js:291:37) at process.processImmediate (node:internal/timers:483:21)

drops-weather.0
2025-03-20 08:50:23.834	error	unhandled promise rejection: Cannot read properties of null (reading 'pages')

drops-weather.0
2025-03-20 08:50:23.834	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

drops-weather.0
2025-03-20 08:50:23.832	info	terminating

drops-weather.0
2025-03-20 08:50:23.830	info	Got terminate signal TERMINATE_YOURSELF

drops-weather.0
2025-03-20 08:50:23.803	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

drops-weather.0
2025-03-20 08:50:23.801	error	error launching browser undefined - Error: Failed to launch the browser process! undefined TROUBLESHOOTING: https://pptr.dev/troubleshooting

drops-weather.0
2025-03-20 08:50:23.775	info	browserPath set to puppeteer default

drops-weather.0
2025-03-20 08:50:23.772	info	browserMode set to automatic

drops-weather.0
2025-03-20 08:50:23.760	info	starting. Version 1.1.0 (non-npm: iobroker-community-adapters/ioBroker.drops-weather) in /opt/iobroker/node_modules/iobroker.drops-weather, node: v20.19.0, js-controller: 7.0.6

[arteck]

so für alle..

das wird nix.. wir müssen den auf cron umstellen..

ich bitte um Geduld

[mcm1957]

@arteck said in Test Adapter drops-weather 1.1.x:

so für alle..

das wird nix.. wir müssen den auf cron umstellen..

ich bitte um Geduld

@arteck
Ich nehm an du meinst damit umstellen auf scheduled adapter.
Machst du das? Oder brauchts du Support? (wobei ich nicht bös bin wenn du das machst, bin eh ausgelastet).

[mcm1957]

@winni said in Test Adapter drops-weather 1.1.x:

@mcm1957, ok

drops-weather.0
2025-03-20 08:50:23.836	error	Cannot read properties of null (reading 'pages')

drops-weather.0
2025-03-20 08:50:23.836	error	TypeError: Cannot read properties of null (reading 'pages') at DropsWeather.destroyBrowser (/opt/iobroker/node_modules/iobroker.drops-weather/main.js:320:37) at DropsWeather.onUnload (/opt/iobroker/node_modules/iobroker.drops-weather/main.js:335:18) at DropsWeather.emit (node:events:524:28) at DropsWeather._stop (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:1171:16) at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:7166:20) at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/build/esm/lib/states/statesInRedisClient.js:291:37) at process.processImmediate (node:internal/timers:483:21)

drops-weather.0
2025-03-20 08:50:23.834	error	unhandled promise rejection: Cannot read properties of null (reading 'pages')

drops-weather.0
2025-03-20 08:50:23.834	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

drops-weather.0
2025-03-20 08:50:23.832	info	terminating

drops-weather.0
2025-03-20 08:50:23.830	info	Got terminate signal TERMINATE_YOURSELF

drops-weather.0
2025-03-20 08:50:23.803	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

drops-weather.0
2025-03-20 08:50:23.801	error	error launching browser undefined - Error: Failed to launch the browser process! undefined TROUBLESHOOTING: https://pptr.dev/troubleshooting

drops-weather.0
2025-03-20 08:50:23.775	info	browserPath set to puppeteer default

drops-weather.0
2025-03-20 08:50:23.772	info	browserMode set to automatic

drops-weather.0
2025-03-20 08:50:23.760	info	starting. Version 1.1.0 (non-npm: iobroker-community-adapters/ioBroker.drops-weather) in /opt/iobroker/node_modules/iobroker.drops-weather, node: v20.19.0, js-controller: 7.0.6

Hmm - das ist aber nicht DEBUG Level log

[Neuschwansteini]

@arteck

um's Choas kompletty zu machen, es gibt auch noch Fetch...
https://www.zenrows.com/blog/axios-vs-got-vs-fetch#which-is-best

Ihr seit schon hartnaeckig, das muss man sagen! geht nicht - gibts net..

[Winni]

@mcm1957 meinst du so?

1
Zeit
info
Nachricht

host.raspberrypi
2025-03-20 15:03:02.764	info	instance system.adapter.drops-weather.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

host.raspberrypi
2025-03-20 15:03:02.233	info	stopInstance system.adapter.drops-weather.0 send kill signal

drops-weather.0
2025-03-20 15:03:02.229	error	Cannot read properties of null (reading 'pages')

drops-weather.0
2025-03-20 15:03:02.228	error	TypeError: Cannot read properties of null (reading 'pages') at DropsWeather.destroyBrowser (/opt/iobroker/node_modules/iobroker.drops-weather/main.js:320:37) at DropsWeather.onUnload (/opt/iobroker/node_modules/iobroker.drops-weather/main.js:335:18) at DropsWeather.emit (node:events:524:28) at DropsWeather._stop (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:1171:16) at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:7166:20) at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/build/esm/lib/states/statesInRedisClient.js:291:37) at process.processImmediate (node:internal/timers:483:21)

drops-weather.0
2025-03-20 15:03:02.226	error	unhandled promise rejection: Cannot read properties of null (reading 'pages')

drops-weather.0
2025-03-20 15:03:02.222	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

host.raspberrypi
2025-03-20 15:03:02.211	info	stopInstance system.adapter.drops-weather.0 (force=false, process=true)

host.raspberrypi
2025-03-20 15:03:02.209	info	"system.adapter.drops-weather.0" disabled

drops-weather.0
2025-03-20 15:03:02.167	error	error launching browser undefined - Error: Failed to launch the browser process! undefined TROUBLESHOOTING: https://pptr.dev/troubleshooting

host.raspberrypi
2025-03-20 15:03:00.760	info	instance system.adapter.drops-weather.0 in version "1.1.0" (non-npm: iobroker-community-adapters/ioBroker.drops-weather) started with pid 125172

host.raspberrypi
2025-03-20 15:03:00.092	info	"system.adapter.drops-weather.0" enabled

[mcm1957]

@winni
Hmmm - eigentlich sollten da DEBUG Meldungen stehen. Hast du den LOG Level in der Instanz auf debug gestellt?

Aber da @arteck sowieso plant auch scheduled umzustellen (damit hoffentlich dann die Zombieprozesse / Speicherfresser bereinigt werden) können wir diese Analyse auch mal nach hinten schieben.

Den Fehler bei manuelle Auswahl (chromkum-browser) hab ich schon gefunden, war ein Typo in jsonConfig.json. Hab dafür aber keine neue Release erstell da zuerst die Änderung von arteck stabilisiert sein sollten. Danke für das Rückmelden

[Winni]

@mcm1957 so hatte ich das eingestellt.

[Homoran]

@winni sagte in Test Adapter drops-weather 1.1.x:

so hatte ich das eingestellt.

dann zeigt das log nur Errors

bitte auf debug umstellen

[Winni]

@homoran jetzt so:

host.raspberrypi

2025-03-20 15:49:41.016	info	instance system.adapter.drops-weather.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

host.raspberrypi
2025-03-20 15:49:40.497	info	stopInstance system.adapter.drops-weather.0 send kill signal

drops-weather.0
2025-03-20 15:49:40.494	error	Cannot read properties of null (reading 'pages')

drops-weather.0
2025-03-20 15:49:40.494	error	TypeError: Cannot read properties of null (reading 'pages') at DropsWeather.destroyBrowser (/opt/iobroker/node_modules/iobroker.drops-weather/main.js:320:37) at DropsWeather.onUnload (/opt/iobroker/node_modules/iobroker.drops-weather/main.js:335:18) at DropsWeather.emit (node:events:524:28) at DropsWeather._stop (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:1171:16) at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:7166:20) at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/build/esm/lib/states/statesInRedisClient.js:291:37) at process.processImmediate (node:internal/timers:483:21)

drops-weather.0
2025-03-20 15:49:40.492	error	unhandled promise rejection: Cannot read properties of null (reading 'pages')

drops-weather.0
2025-03-20 15:49:40.492	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

drops-weather.0
2025-03-20 15:49:40.491	info	terminating

drops-weather.0
2025-03-20 15:49:40.490	debug	destroy browser

drops-weather.0
2025-03-20 15:49:40.489	info	Got terminate signal TERMINATE_YOURSELF

host.raspberrypi
2025-03-20 15:49:40.486	info	stopInstance system.adapter.drops-weather.0 (force=false, process=true)

host.raspberrypi
2025-03-20 15:49:40.486	info	"system.adapter.drops-weather.0" disabled

drops-weather.0
2025-03-20 15:49:40.442	debug	de

drops-weather.0
2025-03-20 15:49:40.434	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

drops-weather.0
2025-03-20 15:49:40.433	error	error launching browser undefined - Error: Failed to launch the browser process! undefined TROUBLESHOOTING: https://pptr.dev/troubleshooting

drops-weather.0
2025-03-20 15:49:40.413	debug	getting system language

drops-weather.0
2025-03-20 15:49:40.412	info	browserPath set to puppeteer default

drops-weather.0
2025-03-20 15:49:40.412	info	browserMode set to automatic

drops-weather.0
2025-03-20 15:49:40.401	info	starting. Version 1.1.0 (non-npm: iobroker-community-adapters/ioBroker.drops-weather) in /opt/iobroker/node_modules/iobroker.drops-weather, node: v20.19.0, js-controller: 7.0.6

[Homoran]

@winni sagte in Test Adapter drops-weather 1.1.x:

jetzt so:

wie geht das denn ??
debug und error?

[Winni]

@homoran keine Ahnung, aber jetzt steht da nur noch debug, vielleicht war ich zu schnell..

[Homoran]

@winni das log passt auf jeden Fall.
Da sollte jetzt alles für @mcm1957 drin sein

[Negalein]

@homoran sagte in Test Adapter drops-weather 1.1.x:

wie geht das denn ??

Screenshot gleich nach speichern gemacht.
Sobald der Adapter gestartet ist, steht da nur eins von denen.

[arteck]

so hab da mal was

https://github.com/iobroker-community-adapters/ioBroker.drops-weather

der adapter muss aber zuvor gelöscht werden (die id aus den einstellungen merken)
dann installieren
dann instanz hinzufügen
dann starten

es kann aber sein dass es paar zombie prozesse gibt .. also am besten den iobroker neu starten oder die prozesse killen
dann erst den adapter starten

sollte dann so aussehen

kommt so eine meldung im LOG

drops-weather.0
2025-03-20 20:12:31.879	error	drops-weather.0 already running

drops-weather.0
2025-03-20 20:12:31.882	warn	Terminated (ADAPTER_ALREADY_RUNNING): Without reason

host.iobroker
2025-03-20 20:12:32.436	error	instance system.adapter.drops-weather.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)

dann sind da noch prozesse am laufen die gekillt werden müssen.. oder iob neu starten

[Winni]

@arteck Hallo, funktioniert bei mir leider nicht. Habe den Adapter erst deinstalliert, iob gestoppt und neu gestartet. Dann den Adapter neu installiert. Hier der Log:

host.raspberrypi
2025-03-20 20:42:18.103	info	instance system.adapter.drops-weather.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

host.raspberrypi
2025-03-20 20:42:17.538	info	stopInstance canceled schedule system.adapter.drops-weather.0

host.raspberrypi
2025-03-20 20:42:17.538	info	stopInstance system.adapter.drops-weather.0 (force=false, process=true)

host.raspberrypi
2025-03-20 20:42:17.537	info	"system.adapter.drops-weather.0" disabled

drops-weather.0
2025-03-20 20:42:17.494	debug	de

drops-weather.0
2025-03-20 20:42:17.486	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

drops-weather.0
2025-03-20 20:42:17.485	error	error launching browser undefined - Error: Failed to launch the browser process! undefined TROUBLESHOOTING: https://pptr.dev/troubleshooting

drops-weather.0
2025-03-20 20:42:17.466	debug	getting system language

drops-weather.0
2025-03-20 20:42:17.466	info	browserPath set to puppeteer default

drops-weather.0
2025-03-20 20:42:17.465	info	browserMode set to automatic

drops-weather.0
2025-03-20 20:42:17.453	info	starting. Version 1.1.0 (non-npm: iobroker-community-adapters/ioBroker.drops-weather#df8b0a7231e71f2a89672d780c44b03675ed4dfe) in /opt/iobroker/node_modules/iobroker.drops-weather, node: v20.19.0, js-controller: 7.0.6

[mcm1957]

@arteck hat den Adapter dankenswerter Weise nochmals überarbeitet und auf schedule Betrieb umgestellt. Er startet jetzt alle 5 Minuten als neuer Prozess. Das Problem der Zobieprozesse sollte dadurch gelöst sein.

Der Adapter steht in dieser Version nun als 1.2.0 nun zurVerfügung (ab morgen im LATEST).

Bei Tests auf meine Pi4 in den letzen Tagen hat dieser "halbwegs" funktioniert. Das halbwegs bezieht sich darauf, dass der Adapter in nicht vorhersehbarere Weise updates durch ein Timeout verweigert - mal gehen die Update stundenlang gut, dann kommen wieder timeouts ohne unterbrechung... Die Ursache dafür ist zumindest mir derzeit nicht klar. Eine Vergrößerung des Timeouts von 10 auf 15s hat keine Verbesserung gebracht.

Ich stellen den Adapter trotzdem mal zum Testen bereit - viulleicht zeigt sich ja da dann ein klareres Bild. Oder @arteck hat noch eine Idee wie / wo "man" suchen könnte.

mcm1957

EDIT:
mcm1957 about a minute ago

ACHTUNG:

Bitte vor der Installation der 1.2.0 den Adapter DEINSTALLIEREN. Vorher bitte die locationID notieren.

Siehe: https://forum.iobroker.net/topic/80335/test-adapter-drops-weather-1-1-x/77