ich habe den Masterkurs von Matthias Kleine von Hausautomatisierung gekauft, finde das gut erklärt.
NEWS
Best posts made by Spidermike
-
RE: Lange Ladezeit vom iobroker
-
RE: Lange Ladezeit vom iobroker
@glasfaser sagte in Lange Ladezeit vom iobroker:
@spidermike sagte in Lange Ladezeit vom iobroker:
momentan läuft der raspi wie sau, richtig schnell
Na ... dann erstmal bis morgen .... sieht ja schon gut aus .
Ich danke Dir und ich melde mich morgen wenn ich von der Maloche zu hause bin
-
RE: Lange Ladezeit vom iobroker
Aber ich finde eure Hilfe auch sehr gut, und die Zeit die ihr dafür investiert.
super Leute
Latest posts made by Spidermike
-
RE: Plenticore Adapter startet nicht nach Aktualisierung
@mcm57
ok danke, leider kenn ich mich mit Github nicht aus.
Ich hoffe der Entwickler des Adapters schaut mal danach.
Gruß
-
RE: Plenticore Adapter startet nicht nach Aktualisierung
@mcm57
Möchte das Thema nochmal aufgreifen.
Habe auch den Plenticore Adapter auf 2.3.1
Bekomme regelmässig warnmeldung im Protokoll.
gibt es dafür eine Lösung?
Gruß
-
RE: ioBroker extrem langsam
@homoran sagte in ioBroker extrem langsam:
@Spidermike
das sind ja mehrere Einträge innerhalb einer Millisekunde.ich kann da nichts zuordnen, nur
@spidermike sagte in ioBroker extrem langsam:
Growatt._setState
bleibt es wenn du den Adapter deaktivierst?
es war kurz nach einen neustart befehl "sudo reboot" weil nur dadurch bebomme ich dann relativ schnellen zugriff auf den iobroker
-
RE: ioBroker extrem langsam
@thomas-braun sagte in ioBroker extrem langsam:
iob logs --watch | uniq
Hallo
konnte mich erst jetzt wieder melden, sorry.
hier die Auswertung
2023-10-21 11:35:54.551 - error: host.raspberrypi4-iobroker Caught by controller[15]: 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(). The promise rejected with the reason: 2023-10-21 11:35:54.551 - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed 2023-10-21 11:35:54.551 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2023-10-21 11:35:54.551 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2023-10-21 11:35:54.551 - error: host.raspberrypi4-iobroker Caught by controller[15]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) 2023-10-21 11:35:54.551 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34) 2023-10-21 11:35:54.551 - error: host.raspberrypi4-iobroker Caught by controller[15]: at runNextTicks (node:internal/process/task_queues:60:5) 2023-10-21 11:35:54.551 - error: host.raspberrypi4-iobroker Caught by controller[15]: at processImmediate (node:internal/timers:447:9) 2023-10-21 11:35:54.551 - error: host.raspberrypi4-iobroker Caught by controller[15]: 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(). The promise rejected with the reason: 2023-10-21 11:35:54.551 - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed 2023-10-21 11:35:54.551 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2023-10-21 11:35:54.552 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2023-10-21 11:35:54.552 - error: host.raspberrypi4-iobroker Caught by controller[15]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) 2023-10-21 11:35:54.552 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34) 2023-10-21 11:35:54.552 - error: host.raspberrypi4-iobroker Caught by controller[15]: at runNextTicks (node:internal/process/task_queues:60:5) 2023-10-21 11:35:54.552 - error: host.raspberrypi4-iobroker Caught by controller[15]: at processImmediate (node:internal/timers:447:9) 2023-10-21 11:35:54.552 - error: host.raspberrypi4-iobroker Caught by controller[15]: 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(). The promise rejected with the reason: 2023-10-21 11:35:54.552 - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed 2023-10-21 11:35:54.552 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2023-10-21 11:35:54.552 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2023-10-21 11:35:54.552 - error: host.raspberrypi4-iobroker Caught by controller[15]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) 2023-10-21 11:35:54.552 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34) 2023-10-21 11:35:54.552 - error: host.raspberrypi4-iobroker Caught by controller[15]: at runNextTicks (node:internal/process/task_queues:60:5) 2023-10-21 11:35:54.553 - error: host.raspberrypi4-iobroker Caught by controller[15]: at processImmediate (node:internal/timers:447:9) 2023-10-21 11:35:54.553 - error: host.raspberrypi4-iobroker Caught by controller[15]: 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(). The promise rejected with the reason: 2023-10-21 11:35:54.553 - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed 2023-10-21 11:35:54.553 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2023-10-21 11:35:54.553 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2023-10-21 11:35:54.553 - error: host.raspberrypi4-iobroker Caught by controller[15]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) 2023-10-21 11:35:54.553 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34) 2023-10-21 11:35:54.553 - error: host.raspberrypi4-iobroker Caught by controller[15]: at runNextTicks (node:internal/process/task_queues:60:5) 2023-10-21 11:35:54.553 - error: host.raspberrypi4-iobroker Caught by controller[15]: at processImmediate (node:internal/timers:447:9) 2023-10-21 11:35:54.553 - error: host.raspberrypi4-iobroker Caught by controller[15]: 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(). The promise rejected with the reason: 2023-10-21 11:35:54.553 - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed 2023-10-21 11:35:54.553 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2023-10-21 11:35:54.554 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2023-10-21 11:35:54.554 - error: host.raspberrypi4-iobroker Caught by controller[15]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) 2023-10-21 11:35:54.554 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34) 2023-10-21 11:35:54.554 - error: host.raspberrypi4-iobroker Caught by controller[15]: at runNextTicks (node:internal/process/task_queues:60:5) 2023-10-21 11:35:54.554 - error: host.raspberrypi4-iobroker Caught by controller[15]: at processImmediate (node:internal/timers:447:9) 2023-10-21 11:35:54.554 - error: host.raspberrypi4-iobroker Caught by controller[15]: 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(). The promise rejected with the reason: 2023-10-21 11:35:54.554 - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed 2023-10-21 11:35:54.554 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2023-10-21 11:35:54.554 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2023-10-21 11:35:54.554 - error: host.raspberrypi4-iobroker Caught by controller[15]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) 2023-10-21 11:35:54.554 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34) 2023-10-21 11:35:54.554 - error: host.raspberrypi4-iobroker Caught by controller[15]: at runNextTicks (node:internal/process/task_queues:60:5) 2023-10-21 11:35:54.555 - error: host.raspberrypi4-iobroker Caught by controller[15]: at processImmediate (node:internal/timers:447:9) 2023-10-21 11:35:54.555 - error: host.raspberrypi4-iobroker Caught by controller[15]: 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(). The promise rejected with the reason: 2023-10-21 11:35:54.555 - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed 2023-10-21 11:35:54.555 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2023-10-21 11:35:54.555 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2023-10-21 11:35:54.555 - error: host.raspberrypi4-iobroker Caught by controller[15]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) 2023-10-21 11:35:54.555 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34) 2023-10-21 11:35:54.555 - error: host.raspberrypi4-iobroker Caught by controller[15]: at runNextTicks (node:internal/process/task_queues:60:5) 2023-10-21 11:35:54.555 - error: host.raspberrypi4-iobroker Caught by controller[15]: at processImmediate (node:internal/timers:447:9) 2023-10-21 11:35:54.555 - error: host.raspberrypi4-iobroker Caught by controller[15]: 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(). The promise rejected with the reason: 2023-10-21 11:35:54.555 - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed 2023-10-21 11:35:54.555 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2023-10-21 11:35:54.556 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2023-10-21 11:35:54.556 - error: host.raspberrypi4-iobroker Caught by controller[15]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) 2023-10-21 11:35:54.556 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34) 2023-10-21 11:35:54.556 - error: host.raspberrypi4-iobroker Caught by controller[15]: at runNextTicks (node:internal/process/task_queues:60:5) 2023-10-21 11:35:54.556 - error: host.raspberrypi4-iobroker Caught by controller[15]: at processImmediate (node:internal/timers:447:9) 2023-10-21 11:35:54.556 - error: host.raspberrypi4-iobroker Caught by controller[15]: 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(). The promise rejected with the reason: 2023-10-21 11:35:54.556 - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed 2023-10-21 11:35:54.556 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2023-10-21 11:35:54.556 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2023-10-21 11:35:54.556 - error: host.raspberrypi4-iobroker Caught by controller[15]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) 2023-10-21 11:35:54.557 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Growatt._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7711:34) 2023-10-21 11:35:54.557 - error: host.raspberrypi4-iobroker Caught by controller[15]: at runNextTicks (node:internal/process/task_queues:60:5) 2023-10-21 11:35:54.557 - error: host.raspberrypi4-iobroker Caught by controller[15]: at processImmediate (node:internal/timers:447:9) 2023-10-21 11:35:54.557 - error: host.raspberrypi4-iobroker Caught by controller[15]: 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(). The promise rejected with the reason: 2023-10-21 11:35:54.557 - error: host.raspberrypi4-iobroker Caught by controller[15]: Error: DB closed 2023-10-21 11:35:54.557 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2023-10-21 11:35:54.557 - error: host.raspberrypi4-iobroker Caught by controller[15]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2023-10-21 11:35:54.557 - error: host.raspberrypi4-iobroker Caught by controller[15]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
das ist nur ein kleiner Ausug, bekomme es nicht alles in eine Nachricht
da scheint noch mehr probleme zu geben -
RE: ioBroker extrem langsam
@homoran sagte in ioBroker extrem langsam:
@spidermike sagte in ioBroker extrem langsam:
ok verstehe,
nicht falsch verstehen!!
@spidermike sagte in ioBroker extrem langsam:
weil ich einfach keine Zeit dafür habe.
das war es was ich andeutete.
Ein wenig Zeit findet sich immer.und hier hilft dir jeder gerne. Dann geht's noch schneller
klar für Euch ist das alles einfach weil ihr jeden Tag damit zu tun habt. Ich mache das nebebei zu meinen Job (bin selbstständig) ich bin so schon über 12 Std am arbeiten. egal
ich bin ja auch dankbar das es Euch gibt aber diese Hinweise "Ein wenig Zeit findet sich immer" hilft mir nicht.
Wenn man eine Familie mit zwei Kindern und Job hat dann ist die Zeit das größte Problem. Ich glaube da brauche nicht weiter darüber zu schreiben, wer in der gleichen Sitution ist weiß was ich meine.
ok lassen wir das Thema, ich schaue mal wie es mit mit meinen problemen weiter geht.Danke an Euch und gute Nacht
-
RE: ioBroker extrem langsam
@homoran sagte in ioBroker extrem langsam:
@spidermike sagte in ioBroker extrem langsam:
ich bin über 50 jahre alt.
soo jung war ich auch irgend wann mal.
@spidermike sagte in ioBroker extrem langsam:
Und hab ehrlich gesagt nicht die Zeit mich Stundenlang hinzusetzen um alles im Forum oder Internet zu suchen
willnicht kannnicht?
@spidermike sagte in ioBroker extrem langsam:
da stellt du mich wieder vor Herrausforderungen,
einfach lesen und Bildchen gucken
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1ok verstehe,
ich bin zu blöd für mein alter und habe keine Lust (willnicht kannnicht) um zu lesen und Bildchen zu gucken weil ich einfach keine Zeit dafür habe.aber trotzdem danke ich Dir @Thomas-Braun für Deine Hilfe bei meinen Problemen
Gruß Maik -
RE: ioBroker extrem langsam
@thomas-braun sagte in ioBroker extrem langsam:
Vor allen Dingen klatscht der im Milisekundenbereich auf den Bauch.
Das dürfte auch die Load verursachen. Ist aber was für einen eigenen Thread.
Da dann bitte keine bunten Bildchens sondern Textauszüge aus dem Terminal.da stellt du mich wieder vor Herrausforderungen,
ich bin über 50 jahre alt. Stehe jeden Tag um 5 Uhr auf und gehe arbeiten von 6 Uhr bis 15 Uhr (nichts zu tun mit dem hier) bin um 16 Uhr zuhause.
Ich bin einfach auf Eure Hilfe angewiesen denn ich verstehe ehrlich gesagt fast null was ihr hier alles leistet. (Honig ums Maul)
Ich bin wirklich froh das ihr mir helft,
Also bitte ich um rücksicht wenn ich nerve und doppelt nachfagen muss wie und was. Und hab ehrlich gesagt nicht die Zeit mich Stundenlang hinzusetzen um alles im Forum oder Internet zu suchen und zu lesen um es dann eh nicht zu verstehen.Sorry Leute, bin sehr dankbar für Eure Hilfe
Gruß Maik
-
RE: ioBroker extrem langsam
aber dieser adapter bringt mir sehr oft fehlermeldungen im Protokoll.
Aber ich denke das ist hier dann die falsche Stelle um das Problem zu diskutieren -
RE: ioBroker extrem langsam
@dp20eic sagte in ioBroker extrem langsam:
@spidermike sagte in ioBroker extrem langsam:
2023-10-16 19:20:55.065 - info: javascript.0 (1166) script.js.Warmwasser_.Test_2: Einspeisung: 0Netz-Bezug: 1005Heiz-Stufe: 0Boilertemp: 43.8
Moin,
da spuckt ein Skript, alle Sekunde was aus, das ist sicherlich so nicht gewollt, was machst Du da, das kann auch dazu führen, dass Du einen erhöhten Load hast, also dass Dein System sich langsamer anfühlt.
VG
BerndMoin,
das Script (zumindest das depug output) lief nur zu diesen Zeitpunkt schalte das Protokoll nur zu wenn ich schauen will was passiert.
Ich teste das Script momentan und schaue ob die Werte und schaltungen stimmen wie es soll.
Ist PV Überschuss zum schalten von 2 Heizstäben. Ist einer andere Sache im Forum unter Blockly Script in Diskussion.