NEWS
Beta Test js-controller 3.0.x auf GitHub
-
@guergen sagte in Beta Test js-controller 3.0.x auf GitHub:
2020-04-20 16:37:14.377 - warn: upnp.0 (11152) State value to set is invalid for upnp.0.FRITZ!Box_7590_(UI).fritzbox.Alive: The state property "expire" has the wrong type "string" (should be "number")! 2020-04-20 16:37:14.377 - warn: upnp.0 (11152) This value will not be set in future versions. Please report this to the developer.2020-04-20 16:27:05.260 - warn: upnp.0 (11152) State value to set is invalid for upnp.0.Repeater310.fritzbox.Alive: The state property "expire" has the wrong type "string" (should be "number")! 2020-04-20 16:27:05.261 - warn: upnp.0 (11152) This value will not be set in future versions. Please report this to the developer.Habe die Fehler aus dem UPNP Adapter entfernt die Änderung der main.js findet Ihr hier:
https://github.com/Michael-Sauer/ioBroker.upnp@Michael-Sauer Installier vom tr-064 mal die 4.0.1
-
@guergen sagte in Beta Test js-controller 3.0.x auf GitHub:
2020-04-20 16:37:14.377 - warn: upnp.0 (11152) State value to set is invalid for upnp.0.FRITZ!Box_7590_(UI).fritzbox.Alive: The state property "expire" has the wrong type "string" (should be "number")! 2020-04-20 16:37:14.377 - warn: upnp.0 (11152) This value will not be set in future versions. Please report this to the developer.2020-04-20 16:27:05.260 - warn: upnp.0 (11152) State value to set is invalid for upnp.0.Repeater310.fritzbox.Alive: The state property "expire" has the wrong type "string" (should be "number")! 2020-04-20 16:27:05.261 - warn: upnp.0 (11152) This value will not be set in future versions. Please report this to the developer.Habe die Fehler aus dem UPNP Adapter entfernt die Änderung der main.js findet Ihr hier:
https://github.com/Michael-Sauer/ioBroker.upnp@Michael-Sauer Jupp... weg!
Danke! -
Halli Hallo an alle Euch fleissigen und treuen Tester,
das Wetter ist ja heute eh komisch, dann habt Ihr vllt spontan Zeit die 3.1. des js-controller mla kurz anzuschauen :-)
Es kam noch ein Feature dazu und daher haben wir (auch weil wir schon bei 3.0.20 waren) für als Vorbereitung für den Stable Release das ganze 3.1 zu nennen :-)Wir haben nach dem Release der 3.0.20 jetzt gesammelt und alles für den finalen Release finalisiert und auch Sentry hat die letzten paar Tage keine weiteren Meldungen mehr geschickt :-)
Changelog:
3.1.0 (2020-05-09) Release Elena
- (foxriver76) catch error on alias ids with empty objects
- (Apollon77) make sure promise rejections without error are not crashing the controller
- (bluefox) Add Controller messages to allow read and write controller base settings (iobroker.json); introduce adapter feature flag CONTROLLER_READWRITE_BASE_SETTINGS
- (Apollon77) handle edge case where hostName is not a string when sending messages (Sentry IOBROKER-ADMIN-B)
- (Apollon77) handle case where letsencrypt directory can not be created (Sentry IOBROKER-ADMIN-C/IOBROKER-WEB-B)
- (bluefox) add IDs to some log messages
- (foxriver76) fix some logging in objects lib
- (Apollon77) make sure to catch error when reading log directory (Sentry IOBROKER-JS-CONTROLLER-1F)
- (foxriver76) Make decrypt and encrypt methods available in adapter object for developers. System secret is read automatically soonly the value is passed to the function
- (AlCalzone) Add adapter exit code 13 (ADAPTER_REQUESTED_REBUILD) to also allow to tell js-controller to rebuild this adapter.
- (Apollon77) change logging for invalid readFile actions to debug because ca be triggered also by other cases then planned ones. Update objects lib
- (Apollon77) make sure command on cmdExec is a string (Sentry IOBROKER-JS-CONTROLLER-1H)
- (Apollon77) Check more cases for existence of variables before accessing them (Sentry IOBROKER-JS-CONTROLLER-E)
- (Apollon77) Add a node.js version check and output special error message if node.js version is not satisfied
- (AlCalzone) Add missing parameter
digestto crypto calls - (AlCalzone) further code optimizatons
- (AlCalzone) Allow reverse lookup of exit codes (exit code -> error name)
- (Apollon77) make sure Objects/States backup files are deleted correctly according to backup settings
- (foxriver76) Make sure default state value is only set if state is not existing also in setObject
- (foxriver76) check that alias is of type state when adding subscribing pattern
- (Apollon77) Make sure error are checked correctly (Sentry IOBROKER-JS-CONTROLLER-1N)
- (Apollon77) Inform about sentry activation if not configured on "iobroker setup first"
- (bluefox) implement maintenance mode for adapter methods
- (bluefox) store for binary states the binary flag in objects
- (Apollon77) update Plugin system
- (Apollon77) update Sentry plugin to respect all options to disable reporting including new disableDataReporting flag ( will be integrated into Admin later)
- (AlCalzone) Add Plugin CLI commands to enable/disable plugins
Es gelten die ganz Normalen "Installation vom GitHub Anweisungen aus dem ersten Post. Wenn Ihr nichts findet dann geht das heute Abend offiziell ins Latest Repository und in ein paar Tagen ins Stable.
Danke im Voraus für Eure Unterstützung.
Ingo
Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77
- Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
- Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
-
Halli Hallo an alle Euch fleissigen und treuen Tester,
das Wetter ist ja heute eh komisch, dann habt Ihr vllt spontan Zeit die 3.1. des js-controller mla kurz anzuschauen :-)
Es kam noch ein Feature dazu und daher haben wir (auch weil wir schon bei 3.0.20 waren) für als Vorbereitung für den Stable Release das ganze 3.1 zu nennen :-)Wir haben nach dem Release der 3.0.20 jetzt gesammelt und alles für den finalen Release finalisiert und auch Sentry hat die letzten paar Tage keine weiteren Meldungen mehr geschickt :-)
Changelog:
3.1.0 (2020-05-09) Release Elena
- (foxriver76) catch error on alias ids with empty objects
- (Apollon77) make sure promise rejections without error are not crashing the controller
- (bluefox) Add Controller messages to allow read and write controller base settings (iobroker.json); introduce adapter feature flag CONTROLLER_READWRITE_BASE_SETTINGS
- (Apollon77) handle edge case where hostName is not a string when sending messages (Sentry IOBROKER-ADMIN-B)
- (Apollon77) handle case where letsencrypt directory can not be created (Sentry IOBROKER-ADMIN-C/IOBROKER-WEB-B)
- (bluefox) add IDs to some log messages
- (foxriver76) fix some logging in objects lib
- (Apollon77) make sure to catch error when reading log directory (Sentry IOBROKER-JS-CONTROLLER-1F)
- (foxriver76) Make decrypt and encrypt methods available in adapter object for developers. System secret is read automatically soonly the value is passed to the function
- (AlCalzone) Add adapter exit code 13 (ADAPTER_REQUESTED_REBUILD) to also allow to tell js-controller to rebuild this adapter.
- (Apollon77) change logging for invalid readFile actions to debug because ca be triggered also by other cases then planned ones. Update objects lib
- (Apollon77) make sure command on cmdExec is a string (Sentry IOBROKER-JS-CONTROLLER-1H)
- (Apollon77) Check more cases for existence of variables before accessing them (Sentry IOBROKER-JS-CONTROLLER-E)
- (Apollon77) Add a node.js version check and output special error message if node.js version is not satisfied
- (AlCalzone) Add missing parameter
digestto crypto calls - (AlCalzone) further code optimizatons
- (AlCalzone) Allow reverse lookup of exit codes (exit code -> error name)
- (Apollon77) make sure Objects/States backup files are deleted correctly according to backup settings
- (foxriver76) Make sure default state value is only set if state is not existing also in setObject
- (foxriver76) check that alias is of type state when adding subscribing pattern
- (Apollon77) Make sure error are checked correctly (Sentry IOBROKER-JS-CONTROLLER-1N)
- (Apollon77) Inform about sentry activation if not configured on "iobroker setup first"
- (bluefox) implement maintenance mode for adapter methods
- (bluefox) store for binary states the binary flag in objects
- (Apollon77) update Plugin system
- (Apollon77) update Sentry plugin to respect all options to disable reporting including new disableDataReporting flag ( will be integrated into Admin later)
- (AlCalzone) Add Plugin CLI commands to enable/disable plugins
Es gelten die ganz Normalen "Installation vom GitHub Anweisungen aus dem ersten Post. Wenn Ihr nichts findet dann geht das heute Abend offiziell ins Latest Repository und in ein paar Tagen ins Stable.
Danke im Voraus für Eure Unterstützung.
Ingo
@apollon77
Sollte da nach dem Update nicht 3.1.0 stehen?jan@Beelink:/opt/iobroker$ npm install ioBroker/ioBroker.js-controller [sudo] Passwort für jan: > iobroker.js-controller@3.0.21 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.4 > iobroker.js-controller@3.0.21 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first object system.certificates updated The following notifications happened during sync: - Ignoring Directory "discovery.admin" because officially not created as meta object. Please remove directory! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.5 (node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.5: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/zigbee-herdsman-converters/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/zigbee-herdsman/node_modules/jest-haste-map/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.12 (node_modules/zigbee-herdsman/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.12: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) + iobroker.js-controller@3.0.21 updated 4 packages in 183.579s 44 packages are looking for funding run `npm fund` for details -
@apollon77
Sollte da nach dem Update nicht 3.1.0 stehen?jan@Beelink:/opt/iobroker$ npm install ioBroker/ioBroker.js-controller [sudo] Passwort für jan: > iobroker.js-controller@3.0.21 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.4 > iobroker.js-controller@3.0.21 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first object system.certificates updated The following notifications happened during sync: - Ignoring Directory "discovery.admin" because officially not created as meta object. Please remove directory! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.5 (node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.5: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/zigbee-herdsman-converters/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/zigbee-herdsman/node_modules/jest-haste-map/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.12 (node_modules/zigbee-herdsman/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.12: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) + iobroker.js-controller@3.0.21 updated 4 packages in 183.579s 44 packages are looking for funding run `npm fund` for details -
Halli Hallo an alle Euch fleissigen und treuen Tester,
das Wetter ist ja heute eh komisch, dann habt Ihr vllt spontan Zeit die 3.1. des js-controller mla kurz anzuschauen :-)
Es kam noch ein Feature dazu und daher haben wir (auch weil wir schon bei 3.0.20 waren) für als Vorbereitung für den Stable Release das ganze 3.1 zu nennen :-)Wir haben nach dem Release der 3.0.20 jetzt gesammelt und alles für den finalen Release finalisiert und auch Sentry hat die letzten paar Tage keine weiteren Meldungen mehr geschickt :-)
Changelog:
3.1.0 (2020-05-09) Release Elena
- (foxriver76) catch error on alias ids with empty objects
- (Apollon77) make sure promise rejections without error are not crashing the controller
- (bluefox) Add Controller messages to allow read and write controller base settings (iobroker.json); introduce adapter feature flag CONTROLLER_READWRITE_BASE_SETTINGS
- (Apollon77) handle edge case where hostName is not a string when sending messages (Sentry IOBROKER-ADMIN-B)
- (Apollon77) handle case where letsencrypt directory can not be created (Sentry IOBROKER-ADMIN-C/IOBROKER-WEB-B)
- (bluefox) add IDs to some log messages
- (foxriver76) fix some logging in objects lib
- (Apollon77) make sure to catch error when reading log directory (Sentry IOBROKER-JS-CONTROLLER-1F)
- (foxriver76) Make decrypt and encrypt methods available in adapter object for developers. System secret is read automatically soonly the value is passed to the function
- (AlCalzone) Add adapter exit code 13 (ADAPTER_REQUESTED_REBUILD) to also allow to tell js-controller to rebuild this adapter.
- (Apollon77) change logging for invalid readFile actions to debug because ca be triggered also by other cases then planned ones. Update objects lib
- (Apollon77) make sure command on cmdExec is a string (Sentry IOBROKER-JS-CONTROLLER-1H)
- (Apollon77) Check more cases for existence of variables before accessing them (Sentry IOBROKER-JS-CONTROLLER-E)
- (Apollon77) Add a node.js version check and output special error message if node.js version is not satisfied
- (AlCalzone) Add missing parameter
digestto crypto calls - (AlCalzone) further code optimizatons
- (AlCalzone) Allow reverse lookup of exit codes (exit code -> error name)
- (Apollon77) make sure Objects/States backup files are deleted correctly according to backup settings
- (foxriver76) Make sure default state value is only set if state is not existing also in setObject
- (foxriver76) check that alias is of type state when adding subscribing pattern
- (Apollon77) Make sure error are checked correctly (Sentry IOBROKER-JS-CONTROLLER-1N)
- (Apollon77) Inform about sentry activation if not configured on "iobroker setup first"
- (bluefox) implement maintenance mode for adapter methods
- (bluefox) store for binary states the binary flag in objects
- (Apollon77) update Plugin system
- (Apollon77) update Sentry plugin to respect all options to disable reporting including new disableDataReporting flag ( will be integrated into Admin later)
- (AlCalzone) Add Plugin CLI commands to enable/disable plugins
Es gelten die ganz Normalen "Installation vom GitHub Anweisungen aus dem ersten Post. Wenn Ihr nichts findet dann geht das heute Abend offiziell ins Latest Repository und in ein paar Tagen ins Stable.
Danke im Voraus für Eure Unterstützung.
Ingo
@apollon77 sagte in Beta Test js-controller 3.0.x auf GitHub:
Es gelten die ganz Normalen "Installation vom GitHub Anweisungen aus dem ersten Post. Wenn Ihr nichts findet dann geht das heute Abend offiziell ins Latest Repository und in ein paar Tagen ins Stable.
Hatte mich darauf bezogen und gedacht es wäre nun schon als npm verfügbar ;-)
-
Aha OK! Die 3.0.21 läuft bisher ohne Probleme!
-
@apollon77
Sollte da nach dem Update nicht 3.1.0 stehen?jan@Beelink:/opt/iobroker$ npm install ioBroker/ioBroker.js-controller [sudo] Passwort für jan: > iobroker.js-controller@3.0.21 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.4 > iobroker.js-controller@3.0.21 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first object system.certificates updated The following notifications happened during sync: - Ignoring Directory "discovery.admin" because officially not created as meta object. Please remove directory! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.5 (node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.5: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/zigbee-herdsman-converters/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/zigbee-herdsman/node_modules/jest-haste-map/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.12 (node_modules/zigbee-herdsman/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.12: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) + iobroker.js-controller@3.0.21 updated 4 packages in 183.579s 44 packages are looking for funding run `npm fund` for details -
@Jan1 Aahhh jetzt sehe ich was DU meinst ... warte mal ... mach nochmal das install ... die 3.0.21 war so "Intermediate". irgendwe at Du scheinbar nicht das allerneueste bekommen ... vllt warst Du zu schnell :-)
@apollon77
Ok, ich warte mal 5 Minuten und versuche es noch mal :-) -
Halli Hallo an alle Euch fleissigen und treuen Tester,
das Wetter ist ja heute eh komisch, dann habt Ihr vllt spontan Zeit die 3.1. des js-controller mla kurz anzuschauen :-)
Es kam noch ein Feature dazu und daher haben wir (auch weil wir schon bei 3.0.20 waren) für als Vorbereitung für den Stable Release das ganze 3.1 zu nennen :-)Wir haben nach dem Release der 3.0.20 jetzt gesammelt und alles für den finalen Release finalisiert und auch Sentry hat die letzten paar Tage keine weiteren Meldungen mehr geschickt :-)
Changelog:
3.1.0 (2020-05-09) Release Elena
- (foxriver76) catch error on alias ids with empty objects
- (Apollon77) make sure promise rejections without error are not crashing the controller
- (bluefox) Add Controller messages to allow read and write controller base settings (iobroker.json); introduce adapter feature flag CONTROLLER_READWRITE_BASE_SETTINGS
- (Apollon77) handle edge case where hostName is not a string when sending messages (Sentry IOBROKER-ADMIN-B)
- (Apollon77) handle case where letsencrypt directory can not be created (Sentry IOBROKER-ADMIN-C/IOBROKER-WEB-B)
- (bluefox) add IDs to some log messages
- (foxriver76) fix some logging in objects lib
- (Apollon77) make sure to catch error when reading log directory (Sentry IOBROKER-JS-CONTROLLER-1F)
- (foxriver76) Make decrypt and encrypt methods available in adapter object for developers. System secret is read automatically soonly the value is passed to the function
- (AlCalzone) Add adapter exit code 13 (ADAPTER_REQUESTED_REBUILD) to also allow to tell js-controller to rebuild this adapter.
- (Apollon77) change logging for invalid readFile actions to debug because ca be triggered also by other cases then planned ones. Update objects lib
- (Apollon77) make sure command on cmdExec is a string (Sentry IOBROKER-JS-CONTROLLER-1H)
- (Apollon77) Check more cases for existence of variables before accessing them (Sentry IOBROKER-JS-CONTROLLER-E)
- (Apollon77) Add a node.js version check and output special error message if node.js version is not satisfied
- (AlCalzone) Add missing parameter
digestto crypto calls - (AlCalzone) further code optimizatons
- (AlCalzone) Allow reverse lookup of exit codes (exit code -> error name)
- (Apollon77) make sure Objects/States backup files are deleted correctly according to backup settings
- (foxriver76) Make sure default state value is only set if state is not existing also in setObject
- (foxriver76) check that alias is of type state when adding subscribing pattern
- (Apollon77) Make sure error are checked correctly (Sentry IOBROKER-JS-CONTROLLER-1N)
- (Apollon77) Inform about sentry activation if not configured on "iobroker setup first"
- (bluefox) implement maintenance mode for adapter methods
- (bluefox) store for binary states the binary flag in objects
- (Apollon77) update Plugin system
- (Apollon77) update Sentry plugin to respect all options to disable reporting including new disableDataReporting flag ( will be integrated into Admin later)
- (AlCalzone) Add Plugin CLI commands to enable/disable plugins
Es gelten die ganz Normalen "Installation vom GitHub Anweisungen aus dem ersten Post. Wenn Ihr nichts findet dann geht das heute Abend offiziell ins Latest Repository und in ein paar Tagen ins Stable.
Danke im Voraus für Eure Unterstützung.
Ingo
pi@raspberrypi:~ $ iobroker version 3.0.21 pi@raspberrypi:~ $ nodejs -v v14.2.0Der amazon2-Adapter klemmt:
2020-05-09 13:47:46.526 - info: host.raspberrypi "system.adapter.alexa2.0" enabled 2020-05-09 13:47:46.599 - info: host.raspberrypi instance system.adapter.alexa2.0 started with pid 10253 2020-05-09 13:47:49.033 - info: alexa2.0 (10253) starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.2.0, js-controller: 3.0.21 2020-05-09 13:47:49.250 - info: alexa2.0 (10253) Proxy IP not set, use first network interface (192.168.178.50) instead 2020-05-09 13:47:50.092 - warn: alexa2.0 (10253) Exception: TypeError: Cannot read property 'end' of null 2020-05-09 13:47:50.095 - error: alexa2.0 (10253) uncaught exception: Cannot read property 'end' of null 2020-05-09 13:47:50.097 - error: alexa2.0 (10253) TypeError: Cannot read property 'end' of null at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/alexa-cookie2/alexa-cookie.js:110:36) at IncomingMessage.emit (events.js:327:22) at IncomingMessage.EventEmitter.emit (domain.js:485:12) at endReadableNT (_stream_readable.js:1225:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2020-05-09 13:47:50.142 - info: alexa2.0 (10253) terminating 2020-05-09 13:47:50.146 - info: alexa2.0 (10253) Terminated (NO_ERROR): Without reason 2020-05-09 13:47:50.648 - error: host.raspberrypi Caught by controller[0]: TypeError: Cannot read property 'end' of null 2020-05-09 13:47:50.649 - error: host.raspberrypi Caught by controller[0]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/alexa-cookie2/alexa-cookie.js:110:36) 2020-05-09 13:47:50.649 - error: host.raspberrypi Caught by controller[0]: at IncomingMessage.emit (events.js:327:22) 2020-05-09 13:47:50.649 - error: host.raspberrypi Caught by controller[0]: at IncomingMessage.EventEmitter.emit (domain.js:485:12) 2020-05-09 13:47:50.650 - error: host.raspberrypi Caught by controller[0]: at endReadableNT (_stream_readable.js:1225:12) 2020-05-09 13:47:50.650 - error: host.raspberrypi Caught by controller[0]: at processTicksAndRejections (internal/process/task_queues.js:84:21) 2020-05-09 13:47:50.651 - error: host.raspberrypi instance system.adapter.alexa2.0 terminated with code 1 (JS_CONTROLLER_STOPPED) -
pi@raspberrypi:~ $ iobroker version 3.0.21 pi@raspberrypi:~ $ nodejs -v v14.2.0Der amazon2-Adapter klemmt:
2020-05-09 13:47:46.526 - info: host.raspberrypi "system.adapter.alexa2.0" enabled 2020-05-09 13:47:46.599 - info: host.raspberrypi instance system.adapter.alexa2.0 started with pid 10253 2020-05-09 13:47:49.033 - info: alexa2.0 (10253) starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.2.0, js-controller: 3.0.21 2020-05-09 13:47:49.250 - info: alexa2.0 (10253) Proxy IP not set, use first network interface (192.168.178.50) instead 2020-05-09 13:47:50.092 - warn: alexa2.0 (10253) Exception: TypeError: Cannot read property 'end' of null 2020-05-09 13:47:50.095 - error: alexa2.0 (10253) uncaught exception: Cannot read property 'end' of null 2020-05-09 13:47:50.097 - error: alexa2.0 (10253) TypeError: Cannot read property 'end' of null at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/alexa-cookie2/alexa-cookie.js:110:36) at IncomingMessage.emit (events.js:327:22) at IncomingMessage.EventEmitter.emit (domain.js:485:12) at endReadableNT (_stream_readable.js:1225:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2020-05-09 13:47:50.142 - info: alexa2.0 (10253) terminating 2020-05-09 13:47:50.146 - info: alexa2.0 (10253) Terminated (NO_ERROR): Without reason 2020-05-09 13:47:50.648 - error: host.raspberrypi Caught by controller[0]: TypeError: Cannot read property 'end' of null 2020-05-09 13:47:50.649 - error: host.raspberrypi Caught by controller[0]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/alexa-cookie2/alexa-cookie.js:110:36) 2020-05-09 13:47:50.649 - error: host.raspberrypi Caught by controller[0]: at IncomingMessage.emit (events.js:327:22) 2020-05-09 13:47:50.649 - error: host.raspberrypi Caught by controller[0]: at IncomingMessage.EventEmitter.emit (domain.js:485:12) 2020-05-09 13:47:50.650 - error: host.raspberrypi Caught by controller[0]: at endReadableNT (_stream_readable.js:1225:12) 2020-05-09 13:47:50.650 - error: host.raspberrypi Caught by controller[0]: at processTicksAndRejections (internal/process/task_queues.js:84:21) 2020-05-09 13:47:50.651 - error: host.raspberrypi instance system.adapter.alexa2.0 terminated with code 1 (JS_CONTROLLER_STOPPED)@Thomas-Braun Alexa 2 liegt an nodejs 14 ... Du bist sehr experimentell unterwegs :-) Da ist was inkompatibel, kommt mit als nächstes. Aber nix mit controller zu tun
Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77
- Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
- Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
-
@Thomas-Braun Alexa 2 liegt an nodejs 14 ... Du bist sehr experimentell unterwegs :-) Da ist was inkompatibel, kommt mit als nächstes. Aber nix mit controller zu tun
@apollon77 Das weiß ich. Deswegen hatte ich die node-Version extra bekannt gegeben. Ich schnall mal flugs node 12 drauf...
Im Admin wird
Verfügbar: 3.0.20 Installiert: 3.0.21vermeldet.
-
@apollon77 Das weiß ich. Deswegen hatte ich die node-Version extra bekannt gegeben. Ich schnall mal flugs node 12 drauf...
Im Admin wird
Verfügbar: 3.0.20 Installiert: 3.0.21vermeldet.
@Thomas-Braun
Machs noch mal, jetzt ist 3.1 online ;-) -
Wie gesagt wer eine 3.0.21 bekommen hat bitte nochmal installieren, dann sollte eine 3.1.0 kommen
Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77
- Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
- Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
-
Wie gesagt wer eine 3.0.21 bekommen hat bitte nochmal installieren, dann sollte eine 3.1.0 kommen
@apollon77
IOBroker Start ohne Fehler im Log mit 3.1.0 :+1: -
Der unifi-Adapter kommt mit folgendem Fehler im Log:
unifi.0 2020-05-09 14:11:56.948 error (3567) Error: api.err.Invalid unifi.0 2020-05-09 14:11:56.037 debug (3567) Update started unifi.0 2020-05-09 14:11:56.036 debug (3567) Blacklisted WLANs: [] unifi.0 2020-05-09 14:11:56.036 debug (3567) Blacklisted networks: [] unifi.0 2020-05-09 14:11:56.036 debug (3567) Blacklisted health: [] unifi.0 2020-05-09 14:11:56.036 debug (3567) Blacklisted devices: [] unifi.0 2020-05-09 14:11:56.036 debug (3567) Blacklisted clients: [] unifi.0 2020-05-09 14:11:56.035 debug (3567) updateInterval = 60 unifi.0 2020-05-09 14:11:56.035 debug (3567) controller = 192.168.1.208:8443 unifi.0 2020-05-09 14:11:56.032 info (3567) Unifi adapter is ready unifi.0 2020-05-09 14:11:56.018 info (3567) starting. Version 0.5.0-beta.1 in /opt/iobroker/node_modules/iobroker.unifi, node: v12.16.3, js-controller: 3.1.0 unifi.0 2020-05-09 14:11:55.956 debug (3567) Plugin sentry Initialize Plugin (enabled=true) -
Wie gesagt wer eine 3.0.21 bekommen hat bitte nochmal installieren, dann sollte eine 3.1.0 kommen
pi@raspberrypi:~ $ iobroker version 3.1.0 pi@raspberrypi:~ $ nodejs -v v12.16.3alexa2:
Alexa startet jetzt.
tado:
Klemmt im Moment, da werde ich aber immer von deren Servern abgewiesen. Hatte das aber schon mit vorherigen Softwareständen. Hat wohl nicht mit dem controller zu tun.
ble:
Bei 'ble' musste ich die capabilities wieder manuell setzen. Wie immer bei node-Wechseln.Ansonsten so auf den ersten Blick alles i.O. , das logfile bleibt auch ruhig.
-
Wie gesagt wer eine 3.0.21 bekommen hat bitte nochmal installieren, dann sollte eine 3.1.0 kommen
2020-05-09 14:03:58.851 - warn: iot.0 (12964) Cannot initialize getImage: Error: The module '/opt/iobroker/node_modules/canvas/build/Release/canvas.node' was compiled against a different Node.js version using NODE_MODULE_VERSION 83. This version of Node.js requires NODE_MODULE_VERSION 72. Please try re-compiling or re-installing the module (for instance, using `npm rebuild` or `npm install`).canvas hatte ich mal selber gebaut. Das versuche ich jetzt mit einem rebuild gerade zu zupfen.
Sonst keine Auffälligkeiten im log.
Support us
795
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge