felixganzer / ioBroker.hyperion_ng

adapter for control hyperionng for iobroker
MIT License
4 stars 5 forks source link

Farbe Einschalten,beim Ausschalten anschließend Crash #2

Closed Cosmicbase closed 3 years ago

Cosmicbase commented 3 years ago

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '...'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.

Versions:

Einschalten einer Farbe klappt gut, aber bein ausschalten gibt es einen Crash und Adapter ist in ioBroker ROT.

Log

hyperion_ng.0 2021-01-26 13:56:47.513 error (9718) The state contains the forbidden properties HSL, RGB! hyperion_ng.0 2021-01-26 13:56:47.513 error (9718) Error: The state contains the forbidden properties HSL, RGB! at validateSetStateObjectArgument (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5848:23) at HyperionNg.s hyperion_ng.0 2021-01-26 13:56:47.510 error (9718) unhandled promise rejection: The state contains the forbidden properties HSL, RGB! hyperion_ng.0 2021-01-26 13:56:47.509 error (9718) 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().

felixganzer commented 3 years ago

Wie hast du denn die Farbe wieder ausgeschalten?

Cosmicbase commented 3 years ago

Die Farbe kann ich nur über die Hyperion App oder wenn ich Instanz deaktiviere ausschalten. Einen Effekt schalte ich mit clearAll aus. So sollte es auch mit Farben gehen. Die Farbe setze ich über hyperion_ng.0.general.control.setColorRGB ab.

Cosmicbase commented 3 years ago

Screenshot_20210127_221947_com android chrome

felixganzer commented 3 years ago

Ich kann diesen Fehler leider nicht rekonstruieren. Welche Hyperion Version hast du denn am laufen?

Cosmicbase commented 3 years ago

Hyperion 9 #1154. Ich habe es mit Hyperion 9 sowie auch mit diversen andren PRs probiert. Das einschalten, wechseln von Effekten und ausschalten geht. Es liegt wohl definitiv nicht an Hyperion. Sobald ich eine Farbe z.B. Blau einschalte sind die LEDs auch blau. Nur sehe im ioBroker das der Adapter dann rot ist. Sobald ich per Hyperion App wieder cleare startet der Adapter wieder automatisch.

Vielleicht willst du auch mit Hyperion 9 testen. Habe Raspbian OS und Hyperion 9 am laufen. Oben sind meine Daten hinterlegt.

Cosmicbase commented 3 years ago

Auch wenn ich den Farbwert unter Control schreibe bekomme ich die richtige Farbe, aber dann stürzt der Adapter ab. Und ganz klar. Ich will dein Projekt ebenso unterstützen wie das Hyperion Projekt. Und ich danke dir schon mal für deinen Adapter. 😊

Hier ein debug log.

hyperion_ng.0 2021-01-28 18:12:49.084 info (4801) Connection closed
hyperion_ng.0 2021-01-28 18:11:49.113 info (4801) setup finished
hyperion_ng.0 2021-01-28 18:11:49.068 info (4801) create effects
hyperion_ng.0 2021-01-28 18:11:48.923 warn (4801) State "hyperion_ng.0.2.priorities.0-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.919 warn (4801) State "hyperion_ng.0.2.priorities.0-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.918 warn (4801) State "hyperion_ng.0.2.priorities.0-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.917 warn (4801) State "hyperion_ng.0.2.priorities.0-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.916 warn (4801) State "hyperion_ng.0.2.priorities.0-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.914 warn (4801) State "hyperion_ng.0.2.priorities.0-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.904 info (4801) read out priorities finished
hyperion_ng.0 2021-01-28 18:11:48.902 info (4801) create priorities
hyperion_ng.0 2021-01-28 18:11:48.651 warn (4801) State "hyperion_ng.0.1.priorities.0-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.650 warn (4801) State "hyperion_ng.0.1.priorities.0-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.649 warn (4801) State "hyperion_ng.0.1.priorities.0-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.649 warn (4801) State "hyperion_ng.0.1.priorities.0-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.645 warn (4801) State "hyperion_ng.0.1.priorities.0-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.644 warn (4801) State "hyperion_ng.0.1.priorities.0-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.629 info (4801) create priorities
hyperion_ng.0 2021-01-28 18:11:48.327 warn (4801) State "hyperion_ng.0.0.priorities.0-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.327 warn (4801) State "hyperion_ng.0.0.priorities.0-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.326 warn (4801) State "hyperion_ng.0.0.priorities.0-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.326 warn (4801) State "hyperion_ng.0.0.priorities.0-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.325 warn (4801) State "hyperion_ng.0.0.priorities.0-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.324 warn (4801) State "hyperion_ng.0.0.priorities.0-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:48.310 info (4801) create priorities
hyperion_ng.0 2021-01-28 18:11:48.018 info (4801) read out Adjustments finished
hyperion_ng.0 2021-01-28 18:11:47.540 info (4801) read out components finished
hyperion_ng.0 2021-01-28 18:11:46.856 info (4801) socket is connected
hyperion_ng.0 2021-01-28 18:11:46.661 info (4801) create Control Parameter
hyperion_ng.0 2021-01-28 18:11:46.614 info (4801) starting. Version 0.1.10 in /opt/iobroker/node_modules/iobroker.hyperion_ng, node: v14.15.1, js-controller: 3.2.12
hyperion_ng.0 2021-01-28 18:11:14.803 warn (4666) State "hyperion_ng.0.2.priorities.0-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.802 warn (4666) State "hyperion_ng.0.2.priorities.0-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.801 warn (4666) State "hyperion_ng.0.2.priorities.0-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.801 warn (4666) State "hyperion_ng.0.2.priorities.0-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.800 warn (4666) State "hyperion_ng.0.2.priorities.0-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.799 warn (4666) State "hyperion_ng.0.2.priorities.0-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.789 info (4666) read out priorities finished
hyperion_ng.0 2021-01-28 18:11:14.787 info (4666) create priorities
hyperion_ng.0 2021-01-28 18:11:14.592 warn (4666) State "hyperion_ng.0.1.priorities.0-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.591 warn (4666) State "hyperion_ng.0.1.priorities.0-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.591 warn (4666) State "hyperion_ng.0.1.priorities.0-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.590 warn (4666) State "hyperion_ng.0.1.priorities.0-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.589 warn (4666) State "hyperion_ng.0.1.priorities.0-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.588 warn (4666) State "hyperion_ng.0.1.priorities.0-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.528 info (4666) create priorities
hyperion_ng.0 2021-01-28 18:11:14.340 warn (4666) Terminated (UNCAUGHT_EXCEPTION): Without reason
hyperion_ng.0 2021-01-28 18:11:14.338 info (4666) terminating
hyperion_ng.0 2021-01-28 18:11:14.289 warn (4666) State "hyperion_ng.0.0.priorities.1-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.289 warn (4666) State "hyperion_ng.0.0.priorities.1-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.288 warn (4666) State "hyperion_ng.0.0.priorities.1-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.288 warn (4666) State "hyperion_ng.0.0.priorities.1-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.287 warn (4666) State "hyperion_ng.0.0.priorities.1-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.286 warn (4666) State "hyperion_ng.0.0.priorities.1-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.279 warn (4666) State "hyperion_ng.0.0.priorities.0-COLOR.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.278 warn (4666) State "hyperion_ng.0.0.priorities.0-COLOR.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.278 warn (4666) State "hyperion_ng.0.0.priorities.0-COLOR.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.277 warn (4666) State "hyperion_ng.0.0.priorities.0-COLOR.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.276 warn (4666) State "hyperion_ng.0.0.priorities.0-COLOR.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:14.259 error (4666) The state contains the forbidden properties HSL, RGB!
hyperion_ng.0 2021-01-28 18:11:14.259 error at processTimers (internal/timers.js:497:7)
hyperion_ng.0 2021-01-28 18:11:14.259 error at listOnTimeout (internal/timers.js:554:17)
hyperion_ng.0 2021-01-28 18:11:14.259 error at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.hyperion_ng/main.js:162:24)
hyperion_ng.0 2021-01-28 18:11:14.259 error at /opt/iobroker/node_modules/iobroker.hyperion_ng/main.js:211:37
hyperion_ng.0 2021-01-28 18:11:14.259 error at HyperionNg.setState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5935:21)
hyperion_ng.0 2021-01-28 18:11:14.259 error at validateSetStateObjectArgument (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5848:23)
hyperion_ng.0 2021-01-28 18:11:14.259 error (4666) Error: The state contains the forbidden properties HSL, RGB!
hyperion_ng.0 2021-01-28 18:11:14.254 error (4666) unhandled promise rejection: The state contains the forbidden properties HSL, RGB!
hyperion_ng.0 2021-01-28 18:11:14.254 error (4666) 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().
hyperion_ng.0 2021-01-28 18:11:14.249 info (4666) create priorities
hyperion_ng.0 2021-01-28 18:11:14.024 warn (4666) State "hyperion_ng.0." has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:00.155 info (4666) setup finished
hyperion_ng.0 2021-01-28 18:11:00.135 info (4666) create effects
hyperion_ng.0 2021-01-28 18:11:00.040 warn (4666) State "hyperion_ng.0.2.priorities.0-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:00.039 warn (4666) State "hyperion_ng.0.2.priorities.0-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:00.038 warn (4666) State "hyperion_ng.0.2.priorities.0-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:00.037 warn (4666) State "hyperion_ng.0.2.priorities.0-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:11:00.037 warn (4666) State "hyperion_ng.0.2.priorities.0-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:10:59.988 warn (4666) State "hyperion_ng.0.2.priorities.0-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:10:59.980 info (4666) read out priorities finished
hyperion_ng.0 2021-01-28 18:10:59.979 info (4666) create priorities
hyperion_ng.0 2021-01-28 18:10:59.730 warn (4666) State "hyperion_ng.0.1.priorities.0-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:10:59.730 warn (4666) State "hyperion_ng.0.1.priorities.0-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:10:59.729 warn (4666) State "hyperion_ng.0.1.priorities.0-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:10:59.728 warn (4666) State "hyperion_ng.0.1.priorities.0-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:10:59.727 warn (4666) State "hyperion_ng.0.1.priorities.0-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:10:59.725 warn (4666) State "hyperion_ng.0.1.priorities.0-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:10:59.719 info (4666) create priorities
hyperion_ng.0 2021-01-28 18:10:59.476 warn (4666) State "hyperion_ng.0.0.priorities.0-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:10:59.476 warn (4666) State "hyperion_ng.0.0.priorities.0-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:10:59.475 warn (4666) State "hyperion_ng.0.0.priorities.0-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:10:59.474 warn (4666) State "hyperion_ng.0.0.priorities.0-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:10:59.474 warn (4666) State "hyperion_ng.0.0.priorities.0-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:10:59.473 warn (4666) State "hyperion_ng.0.0.priorities.0-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:10:59.458 info (4666) create priorities
hyperion_ng.0 2021-01-28 18:10:59.170 info (4666) read out Adjustments finished
hyperion_ng.0 2021-01-28 18:10:58.704 info (4666) read out components finished
hyperion_ng.0 2021-01-28 18:10:57.993 info (4666) socket is connected
hyperion_ng.0 2021-01-28 18:10:57.798 info (4666) create Control Parameter
hyperion_ng.0 2021-01-28 18:10:57.766 info (4666) starting. Version 0.1.10 in /opt/iobroker/node_modules/iobroker.hyperion_ng, node: v14.15.1, js-controller: 3.2.12
hyperion_ng.0 2021-01-28 18:07:35.149 warn (4098) State "hyperion_ng.0.2.priorities.0-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:35.149 warn (4098) State "hyperion_ng.0.2.priorities.0-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:35.148 warn (4098) State "hyperion_ng.0.2.priorities.0-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:35.148 warn (4098) State "hyperion_ng.0.2.priorities.0-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:35.147 warn (4098) State "hyperion_ng.0.2.priorities.0-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:35.146 warn (4098) State "hyperion_ng.0.2.priorities.0-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:35.094 info (4098) read out priorities finished
hyperion_ng.0 2021-01-28 18:07:35.093 info (4098) create priorities
hyperion_ng.0 2021-01-28 18:07:34.894 warn (4098) State "hyperion_ng.0.1.priorities.0-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.893 warn (4098) State "hyperion_ng.0.1.priorities.0-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.893 warn (4098) State "hyperion_ng.0.1.priorities.0-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.892 warn (4098) State "hyperion_ng.0.1.priorities.0-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.890 warn (4098) State "hyperion_ng.0.1.priorities.0-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.890 warn (4098) State "hyperion_ng.0.1.priorities.0-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.878 info (4098) create priorities
hyperion_ng.0 2021-01-28 18:07:34.718 warn (4098) Terminated (UNCAUGHT_EXCEPTION): Without reason
hyperion_ng.0 2021-01-28 18:07:34.717 info (4098) terminating
hyperion_ng.0 2021-01-28 18:07:34.659 warn (4098) State "hyperion_ng.0.0.priorities.1-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.658 warn (4098) State "hyperion_ng.0.0.priorities.1-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.658 warn (4098) State "hyperion_ng.0.0.priorities.1-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.657 warn (4098) State "hyperion_ng.0.0.priorities.1-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.656 warn (4098) State "hyperion_ng.0.0.priorities.1-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.652 warn (4098) State "hyperion_ng.0.0.priorities.1-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.652 warn (4098) State "hyperion_ng.0.0.priorities.0-COLOR.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.651 warn (4098) State "hyperion_ng.0.0.priorities.0-COLOR.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.650 warn (4098) State "hyperion_ng.0.0.priorities.0-COLOR.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.649 warn (4098) State "hyperion_ng.0.0.priorities.0-COLOR.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.646 warn (4098) State "hyperion_ng.0.0.priorities.0-COLOR.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:34.631 error (4098) The state contains the forbidden properties HSL, RGB!
hyperion_ng.0 2021-01-28 18:07:34.630 error at processTimers (internal/timers.js:497:7)
hyperion_ng.0 2021-01-28 18:07:34.630 error at listOnTimeout (internal/timers.js:554:17)
hyperion_ng.0 2021-01-28 18:07:34.630 error at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.hyperion_ng/main.js:162:24)
hyperion_ng.0 2021-01-28 18:07:34.630 error at /opt/iobroker/node_modules/iobroker.hyperion_ng/main.js:211:37
hyperion_ng.0 2021-01-28 18:07:34.630 error at HyperionNg.setState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5935:21)
hyperion_ng.0 2021-01-28 18:07:34.630 error at validateSetStateObjectArgument (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5848:23)
hyperion_ng.0 2021-01-28 18:07:34.630 error (4098) Error: The state contains the forbidden properties HSL, RGB!
hyperion_ng.0 2021-01-28 18:07:34.626 error (4098) unhandled promise rejection: The state contains the forbidden properties HSL, RGB!
hyperion_ng.0 2021-01-28 18:07:34.625 error (4098) 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().
hyperion_ng.0 2021-01-28 18:07:34.621 info (4098) create priorities
hyperion_ng.0 2021-01-28 18:07:34.381 warn (4098) State "hyperion_ng.0." has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:22.113 info (4098) setup finished
hyperion_ng.0 2021-01-28 18:07:22.076 info (4098) create effects
hyperion_ng.0 2021-01-28 18:07:22.033 warn (4098) State "hyperion_ng.0.2.priorities.0-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:22.032 warn (4098) State "hyperion_ng.0.2.priorities.0-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:22.031 warn (4098) State "hyperion_ng.0.2.priorities.0-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:22.030 warn (4098) State "hyperion_ng.0.2.priorities.0-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:22.029 warn (4098) State "hyperion_ng.0.2.priorities.0-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:22.028 warn (4098) State "hyperion_ng.0.2.priorities.0-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:21.968 info (4098) read out priorities finished
hyperion_ng.0 2021-01-28 18:07:21.967 info (4098) create priorities
hyperion_ng.0 2021-01-28 18:07:21.763 warn (4098) State "hyperion_ng.0.1.priorities.0-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:21.762 warn (4098) State "hyperion_ng.0.1.priorities.0-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:21.761 warn (4098) State "hyperion_ng.0.1.priorities.0-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:21.760 warn (4098) State "hyperion_ng.0.1.priorities.0-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:21.759 warn (4098) State "hyperion_ng.0.1.priorities.0-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:21.757 warn (4098) State "hyperion_ng.0.1.priorities.0-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:21.751 info (4098) create priorities
hyperion_ng.0 2021-01-28 18:07:21.537 warn (4098) State "hyperion_ng.0.0.priorities.0-V4L.visible" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:21.537 warn (4098) State "hyperion_ng.0.0.priorities.0-V4L.priority" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:21.535 warn (4098) State "hyperion_ng.0.0.priorities.0-V4L.owner" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:21.535 warn (4098) State "hyperion_ng.0.0.priorities.0-V4L.origin" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:21.534 warn (4098) State "hyperion_ng.0.0.priorities.0-V4L.componentId" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:21.533 warn (4098) State "hyperion_ng.0.0.priorities.0-V4L.active" has no existing object, this might lead to an error in future versions
hyperion_ng.0 2021-01-28 18:07:21.524 info (4098) create priorities
hyperion_ng.0 2021-01-28 18:07:21.301 info (4098) read out Adjustments finished
hyperion_ng.0 2021-01-28 18:07:20.985 info (4098) read out components finished
hyperion_ng.0 2021-01-28 18:07:20.547 info (4098) socket is connected
hyperion_ng.0 2021-01-28 18:07:20.377 info (4098) create Control Parameter
hyperion_ng.0 2021-01-28 18:07:20.316 info (4098) starting. Version 0.1.10 in /opt/iobroker/node_modules/iobroker.hyperion_ng, node: v14.15.1, js-controller: 3.2.12
hyperion_ng.0 2021-01-28 18:06:47.925 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.925 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.924 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.924 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.923 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.923 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.923 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.923 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.922 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.922 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.922 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.921 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.921 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.921 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.921 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.920 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.920 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.920 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.916 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.915 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.915 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.915 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.914 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.914 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.914 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.913 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.913 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.913 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.913 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.912 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.912 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.911 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.911 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.911 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.910 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.910 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.909 warn (4019) get state error: DB closed
hyperion_ng.0 2021-01-28 18:06:47.909 warn (4019) get state error: DB closed
felixganzer commented 3 years ago

Ich würde mal so spontan sagen, dass die js-controller Version, welche du verwendest so strikt ist, dass er ein paar Objekte nicht mehr zulässt, was mit der älteren Version nur als Warnung markiert wurde.

Cosmicbase commented 3 years ago

OK das bedeutet ein downgrade? Welche Version nutzt du? Und funktionieren auch das verstellen der Helligkeit? Ich meine zu wissen das die Farben sich ein und ausschalten ließen. Nach einem Update.. Scheinbar auch jscontroller das Problem.

felixganzer commented 3 years ago

ich habe den 3.1.6 aus dem stable. Bei mir geht alles.

Cosmicbase commented 3 years ago

ich habe den 3.1.6 aus dem stable. Bei mir geht alles.

Ich habe 2 Raspi im Host. Muss ich dann alle 2 auf 3.1.6 downgraden?

felixganzer commented 3 years ago

Ja keine ahnung. Ist nur eine Vermutung

Cosmicbase commented 3 years ago

Ja keine ahnung. Ist nur eine Vermutung

Ich probiere es aus und teste weiter. Ist eine Kompatibilität zu neueren js Controller in Zukunft gewährleistet oder müsste ich auf 3.1.6 bleiben?

Nachtrag: mit js-controller 3.1.6 lassen sich Farben wieder schalten. Danke👍☺️

felixganzer commented 3 years ago

Aus beruflicher Erfahrung kann ich nur raten, never touch a running system. Man sollte solange auf einer Version bleiben, bis ein upgrade nitwendig ist. ZB. Sicherheit oder benötigte features.

Ich werde natürlich bei Gelegenheit eine Kompatibilität herstellen.

Cosmicbase commented 3 years ago

Danke für deinen tollen Support. Und eine zukünftige Kompatibilität wäre echt super, alleine schon mal wegen anderen Adapter die evtl. auf neueren js-controller setzen.

Wäre auch schön wenn ich oder andere dies zuvor sehen könnten wie meinet wegen iobroker.hyperion.ng v 0.1.0 kompatibel bis js-controller 3.1.6 oder darüber.

Es könnte ja auch sein das jemand ein iobroker up to Date hat und feststellen müsste das dein Adapter gar nicht wunschgemäß funktioniert.

Danke nochmal☺️

Cosmicbase commented 3 years ago

Hallo Felix, ich muss leider nochmals den Fehler aufnehmen. Habe meinen js-controller wieder auf 3.2.12 geupdatet und leider wieder gleiches Phänomen. Sicherlich fragt sich warum ich wieder die Host update, aber das liegt auch an der Neugier ob das Adapter Update auch läuft. Bei 3.1.6 läufts wie es soll.

Den Log pack ich mal in eine txt Datei. log.txt

Nachtrag:

Nachdem ich den Adapter komplett deinstalliert habe und nochmal Neu installiert läuft er unter js-controller 3.2.12 so wie er soll. Scheinbar hatte das überschreiben des alten Adapters nicht richtig funktioniert.

Cosmicbase commented 3 years ago

Weitere Infos erhaltet ihr hier https://www.hyperion-project.org/threads/hyperion-ng-in-iobroker-einbinden-und-steuern.10498/.