@homoran sagte in Test Adapter shuttercontrol v2.0.x:
oder willst du dynamisch die Beschattungshöhe der SC Konfiguration per Script ändern?
ja, so kann man das auch ausdrücken.
@homoran sagte in Test Adapter shuttercontrol v2.0.x:
oder willst du dynamisch die Beschattungshöhe der SC Konfiguration per Script ändern?
ja, so kann man das auch ausdrücken.
@homoran Danke für die Antwort, löst mein Problem aber nur indirekt (siehe Antwort an simatec)
@simatec Danke für die Antwort.
Das habe ich schon gesehen, aber das löst mein Problem nur indirekt.
Ich erkläre das Problem mal ausführlich:
Ich habe ein Fenster, auf dem im Sommer Blumen auf der Fensterbank stehen. Dann soll das Rollo auf z.B. max. 30% runterfahren. Im Winter sind die Blumen weg, dann soll das Rollo auf 100% fahren. Auch wenn man den Schalter "Alle Rollos runterfahren" drückt soll auf die entsprechende Höhe gefahren werden.
Wenn man den Datenpunkt in der Konfiguration (Rollladenhöhe beim Runterfahren) per Skript ändern könnte wäre das Problem ja schon gelöst. Ich habe aber keine Möglichkeit gefunden die Höhe per Skript zu ändern, bzw per Skript ein Rollo zu aktivieren/deaktivieren.
Ich hoffe mal das ich mein Problem so gut erklärt habe.
LG
webwalker2001
Hi zusammen,
besteht die Möglichkeit einzelne Rollos über einen Datenpunkt zu aktivieren/deaktivieren?
Habe keinen Datenpunkt gefunden.
Hintergrund ist das ich für ein Rollo 2 verschiedene Profile (Höhe beim zu fahren) benutzen möchte.
LG
webwalker2001
@rene55 Hi, danke für die Info. Nach löschen und neu installieren des Adapters stehen da auch Werte drin.
Klappt jetzt wieder alles.
Danke
LG
Webwalker2001
Hi zusammen,
bei mir werden in der Version 0.4.2 die Statistischen Datenpunkte (Täglicher Ertrag, gesamter Ertrag usw) nicht aktualisiert. Die Datenpunkte mit den aktuellen Werten schon. In der Version 0.4.0 klappt alles.
Hat noch Jemand das Problem?
Gruß
Webwalker2001
@rene55 Mein CPU-Load liegt so zwischen 35%-50%. RAM bei ca. 50%. Sollte eigentlich passen. Kann man den Timeout evtl. irgendwo einstellen?
lg
webwalker2001
@rene55 Hi, hier der log.
Aber wie gesagt, die Fehlermeldungen kommen nur manchmal. Hab noch nicht den Zusammenhang herausgefunden.
solarmanpv.0 2022-11-10 22:54:39.800 debug [onReady] started: solarmanpv.0
solarmanpv.02 022-11-10 22:54:39.731 info starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.solarmanpv, node: v16.18.1, js-controller: 4.0.23
solarmanpv.0 2022-11-10 22:54:43.223 info Terminated (ADAPTER_REQUESTED_TERMINATION): Everything done. Going to terminate till next schedule
solarmanpv.0 2022-11-10 22:54:43.221 debug [onReady] finished - stopping instance
solarmanpv.0 2022-11-10 22:54:42.834 debug [getDeviceData] Device ID >: 217801816 and Device SN >: 2205037328
solarmanpv.0 2022-11-10 22:54:42.546 debug [initializeInverter] InverterTyp: MICRO_INVERTER
solarmanpv.0 2022-11-10 22:54:42.545 debug [initializeInverter] StationID >: 2633791
solarmanpv.0 2022-11-10 22:54:39.800 debug [onReady] started: solarmanpv.0
solarmanpv.0 2022-11-10 22:54:39.731 info starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.solarmanpv, node: v16.18.1, js-controller: 4.0.23
solarmanpv.0 2022-11-10 22:54:39.800 debug [onReady] started: solarmanpv.0
solarmanpv.0 2022-11-10 22:54:39.731 info starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.solarmanpv, node: v16.18.1, js-controller: 4.0.23
solarmanpv.0 2022-11-10 22:54:39.800 debug [onReady] started: solarmanpv.0
solarmanpv.0 2022-11-10 22:54:39.731 info starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.solarmanpv, node: v16.18.1, js-controller: 4.0.23
solarmanpv.0 2022-11-10 22:54:39.800 debug [onReady] started: solarmanpv.0
solarmanpv.0 2022-11-10 22:54:39.731 info starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.solarmanpv, node: v16.18.1, js-controller: 4.0.23
solarmanpv.0 2022-11-10 22:54:38.613 debug States connected to redis: 127.0.0.1:9000
solarmanpv.0 2022-11-10 22:54:38.380 debug States create User PubSub Client
solarmanpv.0 2022-11-10 22:54:38.376 debug States create System PubSub Client
solarmanpv.0 2022-11-10 22:54:38.289 debug Redis States: Use Redis connection: 127.0.0.1:9000
solarmanpv.0 2022-11-10 22:54:38.150 debug Objects connected to redis: 127.0.0.1:9001
solarmanpv.0 2022-11-10 22:54:38.060 debug Objects client initialize lua scripts
solarmanpv.0 2022-11-10 22:54:37.837 debug Objects create User PubSub Client
solarmanpv.0 2022-11-10 22:54:37.835 debug Objects create System PubSub Client
solarmanpv.0 2022-11-10 22:54:37.827 debug Objects client ready ... initialize now
solarmanpv.0 2022-11-10 22:54:37.718 debug Redis Objects: Use Redis connection: 127.0.0.1:9001
lg
Webwalker2001
Hallo in die Runde,
ich bekomme ab und zu folgende Fehlermeldungen:
solarmanpv.0 2022-11-08 08:00:11.819 error DB closed
solarmanpv.0 2022-11-08 08:00:11.818 error Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:301:12)
solarmanpv.0 2022-11-08 08:00:11.818 error unhandled promise rejection: DB closed
solarmanpv.0 2022-11-08 08:00:11.817 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().
solarmanpv.0 2022-11-08 08:00:11.815 error DB closed
solarmanpv.0 2022-11-08 08:00:11.815 error Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:301:12)
solarmanpv.0 2022-11-08 08:00:11.814 error unhandled promise rejection: DB closed
solarmanpv.0 2022-11-08 08:00:11.813 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().
solarmanpv.0 2022-11-08 08:00:11.809 error DB closed
solarmanpv.0 2022-11-08 08:00:11.808 error Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:301:12)
solarmanpv.0 2022-11-08 08:00:11.806 error unhandled promise rejection: DB closed
solarmanpv.0 2022-11-08 08:00:11.805 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().
solarmanpv.0 2022-11-08 08:00:11.804 error DB closed
solarmanpv.0 2022-11-08 08:00:11.802 error Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:301:12)
solarmanpv.0 2022-11-08 08:00:11.801 error unhandled promise rejection: DB closed
solarmanpv.0 2022-11-08 08:00:11.798 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().
solarmanpv.0 2022-11-08 08:00:11.794 error DB closed
solarmanpv.0 2022-11-08 08:00:11.793 error Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:301:12)
solarmanpv.0 2022-11-08 08:00:11.792 error unhandled promise rejection: DB closed
solarmanpv.0 2022-11-08 08:00:11.791 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().
solarmanpv.0 2022-11-08 08:00:11.786 error DB closed
solarmanpv.0 2022-11-08 08:00:11.785 error Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:301:12)
solarmanpv.0 2022-11-08 08:00:11.780 error unhandled promise rejection: DB closed
solarmanpv.0 2022-11-08 08:00:11.779 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().
solarmanpv.0 2022-11-08 08:00:11.776 error DB closed
Scheint aber sonst zu laufen.
Mein System:
RasPi4 mit 4GB
Node.js v16.18.1
NPM 8.19.2
Admin v6.2.23
LG
webwalker2001
Systemdata | Bitte Ausfüllen |
---|---|
Hardwaresystem: | Pi4 |
Arbeitsspeicher: | 4GB |
Festplattenart: | SSD |
Betriebssystem: | Ubuntu |
Node-Version: | 12.22.8 |
Nodejs-Version: | 12.22.8 |
Admin-Version: | 5.2.3 |
NPM-Version: | 6.14.15 |
Installationsart: | Skript |
Hallo zusammen,
ich bekomme sporatisch folgende Fehlermeldung:
time-switch.0 2021-12-25 02:00:33.168 info starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.time-switch, node: v12.22.8, js-controller: 3.3.22
host.iobroker 2021-12-25 02:00:00.772 error instance system.adapter.time-switch.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
time-switch.0 2021-12-25 02:00:00.103 warn Terminated (UNCAUGHT_EXCEPTION): Without reason
time-switch.0 2021-12-25 02:00:00.102 info terminating
time-switch.0 2021-12-25 02:00:00.100 info cleaning everything up...
time-switch.0 2021-12-25 02:00:00.038 error Trigger TimeTrigger {id=TimeTriggerForAstroTrigger:0, hour=16, minute=30, weekdays=[4]} is not registered.
time-switch.0 2021-12-25 02:00:00.037 error Error: Trigger TimeTrigger {id=TimeTriggerForAstroTrigger:0, hour=16, minute=30, weekdays=[4]} is not registered. at TimeTriggerScheduler.unregister (/opt/iobroker/node_modules/iobroker.time-switch/build/scheduler/TimeTriggerScheduler.js:34:19) at /opt/iobroker/node_modules/iobroker.time-switch/build/scheduler/AstroTriggerScheduler.js:25:73 at Array.forEach (<anonymous>) at Object.execute (/opt/iobroker/node_modules/iobroker.time-switch/build/scheduler/AstroTriggerScheduler.js:25:32) at Job.job (/opt/iobroker/node_modules/iobroker.time-switch/build/scheduler/TimeTriggerScheduler.js:22:33) at Job.invoke (/opt/iobroker/node_modules/node-schedule/lib/schedule.js:175:17) at /opt/iobroker/node_modules/node-schedule/lib/schedule.js:555:26 at Timeout._onTimeout (/opt/iobroker/node_modules/node-schedule/lib/schedule.js:512:7) at listOnTimeout (internal/timers.js:554:17) at processTimers (internal/timers.js:497:7)
time-switch.0 2021-12-25 02:00:00.029 error uncaught exception: Trigger TimeTrigger {id=TimeTriggerForAstroTrigger:0, hour=16, minute=30, weekdays=[4]} is not registered.
Wenn ich den Adapter neu starte kommt aber kein Fehler.
Ist das ein Bug oder hab ich was falsch eingestellt?
Gruß
Webwalker2001