NEWS
js-controller 5.0.x jetzt für alle User im STABLE!
-
Ich bin kein Entwickler, aber die aktuelle Version aus Latest (7.1.4) ist noch nicht fehlerfrei.
-
@ofbeqnpolkkl6mby5e13 wenn er den fehler gefixt hat warum hab ich ihn dann?
-
@fa-bio
Weil du 7.0.3 verwendest?
-
@ofbeqnpolkkl6mby5e13 ok, dann abwarten.
Werden die Scripte mit gesichert vom backitup Adapter?
-
Bei mir wurden die Skripte in der Nacht in der Kombination 5.0.12/7.0.3 gesichert.
-
@ofbeqnpolkkl6mby5e13 okay danke
-
@ofbeqnpolkkl6mby5e13 Ok, dann ist ja erst mal alles gut, Hauptsache die neusten Änderungen sind im Notfall nicht weg.
-
Hat jemand den linux-control mal getestet? Er scheint ja nicht mehr gepflegt zu werden, sieht für mich in GitHub ziemlich eindeutig aus. Aber funktioniert er denn unter 5.x?
-
@x4n70 sagte in js-controller 5.0.x jetzt für alle User im STABLE!:
Hat jemand den linux-control mal getestet? Er scheint ja nicht mehr gepflegt zu werden, sieht für mich in GitHub ziemlich eindeutig aus. Aber funktioniert er denn unter 5.x?
ja, läuft bei mir noch
-
@x4n70 sagte in js-controller 5.0.x jetzt für alle User im STABLE!:
Hat jemand den linux-control mal getestet? Er scheint ja nicht mehr gepflegt zu werden, sieht für mich in GitHub ziemlich eindeutig aus. Aber funktioniert er denn unter 5.x?
Läuft bei mir auch noch
-
seit dem Update kann ich die admin seite nicht mehr erreichen.
Die Seite bleibt weiß ohne Fehlermeldung.
der iob Befehl der vorher systemweit funktionierte führt jetzt immer hierzu:/opt/iobroker# iob fix iobroker fix Execute the installation fixer script, this updates your ioBroker installation Options: --help Show help [boolean] das hier führt zu: service iobroker status Failed to connect to bus: Connection refused
nach einem Reboot zeigt er mir die admin Oberfläche wieder an aber wieder soll ich den admin adapter auf 6.8.0 aktualisieren und WIEDER gibt der js-controller an er sei4.0.24 und ich müsse auf 5.0.12 aktualisieren...
iobroker stop
iobroker controller daemon is not running
root@iobroker:/opt/iobroker# service iobroker stop
root@iobroker:/opt/iobroker# iobroker fix
iobroker fixExecute the installation fixer script, this updates your ioBroker installation
Options:
--help Show help [boolean]
master:
CPU: 11,81 %
RAM: 64,7 %
Betriebszeit: 0h
Verfügbar: 5.0.12
Installiert: 4.0.24
Ereignisse: ⇥25 / ↦13
Plattform: linux
Betriebssystem: linux
Architektur: x64
CPUs: 1
Geschwindigkeit: 3600 MHz
Modell: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
RAM: 6 GB
System-Betriebszeit: 00:03:42
Node.js: v18.17.1
time: 1694769114715
timeOffset: -120
Adapter-Anzahl: 496
NPM: 9.6.7
Datenträgergröße: 88.5 GB
Freier Festplattenspeicher: 15.8 GB
Betriebszeit: 00:03:39
Aktive Instanzen: 30
Pfad: /opt/iobroker/
slave:
aspberrypi
0,13 %
72 %
3h
5.0.125.0.12
⇥0 / ↦13 -
@merowinger sagte in js-controller 5.0.x jetzt für alle User im STABLE!:
root@iobroker
Regel 1: Nie als root herumkaspern.
iob diag
sagt dazu?
-
@walter-white said in js-controller 5.0.x jetzt für alle User im STABLE!:
@ofbeqnpolkkl6mby5e13 offiziell gibt es den den ab wann?
Verfügbare Version:
7.0.3
Installierte Version:
7.0.3Die Version 7.1.4 von javascript sollte ab heute Nachmittag im stable zur Installation angeboten werden.
DANKE für eure Rückmeldung des Problems und der Lösung.
-
iob diag iobroker [command] Commands: iobroker setup Setup ioBroker iobroker start [all|<adapter>.<instance>] Starts the js-controller or a specified adapter instance iobroker stop [<adapter>.<instance>] stops the js-controller or a specified adapter instance iobroker restart [<adapter>.<instance>] Restarts js-controller or a specified adapter instance [aliases: r] iobroker debug <adapter>[.<instance>] Starts a Node.js debugging session for the adapter instance iobroker info Shows the host info iobroker logs [<adapter>] Monitor log iobroker add <adapter> [desiredNumber] Add instance of adapter [aliases: a] iobroker install <adapter> Installs a specified adapter [aliases: i] iobroker rebuild [<module>] Rebuild all native modules or path iobroker url <url> [<name>] Install adapter from specified url, e.g. GitHub iobroker del <adapter> Remove adapter and all instances from this host [aliases: delete] iobroker del <adapter>.<instance> Remove adapter instance [aliases: delete] iobroker update [<repositoryUrl>] Update repository and list adapters iobroker upgrade Upgrade management iobroker upload [all|<adapter>] Upload management [aliases: u] iobroker object Object management [aliases: o] iobroker state State management [aliases: s] iobroker message <adapter>[.instance] <command> [<message>] Send message to adapter instance/s iobroker list <type> [<filter>] List all entries, like objects iobroker chmod <mode> <file> Change file rights iobroker chown <user> <group> <file> Change file ownership iobroker touch <file> Touch file iobroker rm <file> Remove file iobroker file File management iobroker user User commands iobroker group group management iobroker host <hostname> Set host to given hostname iobroker set <adapter>.<instance> Change settings of adapter config iobroker license <license.file or license.text> Update license by given file iobroker cert Certificate management iobroker clean <yes> Clears all objects and states iobroker backup Create backup iobroker restore <backup name or path> Restore a specified backup iobroker validate <backup name or path> Validate a specified backup iobroker status [all|<adapter>.<instance>] Status of ioBroker or adapter instance [aliases: isrun] iobroker repo [<name>] Show repo information iobroker uuid Show uuid of the installation [aliases: id] iobroker unsetup Reset license, installation secret and language iobroker fix Execute the installation fixer script, this updates your ioBroker installation iobroker multihost Multihost management iobroker compact compact group management iobroker plugin Plugin management iobroker version [<adapter>] Show version of js-controller or specified adapter [aliases: v] Options: --help Show help [boolean]
Ist das hier aus dem service status evtl das Problem?
Sep 15 11:14:22 iobroker bash[3271]: /bin/sh: 1: hcitool: not found
Mod-Edit: Code/Log in Code Tags gepackt. Bitte benutzt die Code Tags Funktion -> </>
Hier gehts zur Hilfe.jetzt habe ich das js-controller update so zum drittel Mal durchgeführt...
von den iob Befehlen funktioniert jeder nur bei iob fix, zeigt er mir die Befehlsliste an...Sep 15 11:38:59 iobroker bash[21714]: at Module.require (node:internal/modules/cjs/loader:1143:19) { Sep 15 11:38:59 iobroker bash[21714]: code: 'MODULE_NOT_FOUND', Sep 15 11:38:59 iobroker bash[21714]: requireStack: [ Sep 15 11:38:59 iobroker bash[21714]: '/opt/iobroker/node_modules/iobroker.fritzbox/lib/utils.js', Sep 15 11:38:59 iobroker bash[21714]: '/opt/iobroker/node_modules/iobroker.fritzbox/main.js'
Jetzt habe ich wieder den crash. fritzbox adapter deinstalliert.
service iobroker stop und start durchgeführt...
jetzt kann ich wieder den admin adapter auf 6.8.0 upgraden und der js-controller ist auch wieder der 4er... -
Da ist deine Basis verfummelt...
root...
Mach einen separaten Thread auf. Da dann die Langfassung vom manuellen Aufruf rein:curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh
-
Aktualisierung der Liste erforderlicher Adapterupdates:
javascript 7.1.4 - stable verfügbar ab 15.9. nachmittags
enigma2 2.0.3 - nur via latest repository verfügbar
plenticore 2.3.0 - z.Z. nur im latest, stable in Planung -
@mcm57 sagte in js-controller 5.0.x jetzt für alle User im STABLE!:
@mcm57 said in js-controller 5.0.x jetzt für alle User im STABLE!:
@foxriver76
Ok
Wenn ihr keine Zeit habt kann ich am Abend release versuchenOk, der botvac hat weder release script noch github tests - Museumsstand was die Infrastruktur betrifft. Ich werd dann mal anfangen, kann aber auch noch nen Tag dauern bis ne saubere Release entsteht.
Wer will, kann zwischenzeitlich die GITHUB Version versuchen (übliches Disclaimer - at own risk + Backup). Der Code sollte an js-controller 5 angepasst sein. Er enthält allerdings auch ein paar weitere Änderungen die nicht ins README gefunden haben, da muss ich erst mal schaun ob da ne Info was geändert wurde extrahieren kann.
Funkt leider nicht
2023-09-15 12:00:23.203 - debug: botvac.0 (24567) Redis Objects: Use Redis connection: 10.0.0.227:9001 2023-09-15 12:00:23.246 - debug: botvac.0 (24567) Objects client ready ... initialize now 2023-09-15 12:00:23.249 - debug: botvac.0 (24567) Objects create System PubSub Client 2023-09-15 12:00:23.250 - debug: botvac.0 (24567) Objects create User PubSub Client 2023-09-15 12:00:23.317 - debug: botvac.0 (24567) Objects client initialize lua scripts 2023-09-15 12:00:23.323 - debug: botvac.0 (24567) Objects connected to redis: 10.0.0.227:9001 2023-09-15 12:00:23.360 - debug: botvac.0 (24567) Redis States: Use Redis connection: 10.0.0.227:9000 2023-09-15 12:00:23.381 - debug: botvac.0 (24567) States create System PubSub Client 2023-09-15 12:00:23.381 - debug: botvac.0 (24567) States create User PubSub Client 2023-09-15 12:00:23.469 - debug: botvac.0 (24567) States connected to redis: 10.0.0.227:9000 2023-09-15 12:00:23.700 - info: botvac.0 (24567) starting. Version 1.0.4 (non-npm: iobroker-community-adapters/ioBroker.botvac#331c3718f9b221f76efdec922ed38ba587c1d392) in /opt/iobroker/node_modules/iobroker.botvac, node: v18.17.1, js-controller: 5.0.12 2023-09-15 12:00:28.485 - info: botvac.0 (24567) devices found: 4 2023-09-15 12:00:28.719 - warn: botvac.0 (24567) Device"Erdgeschoss" with id: Erdgeschoss is not exists in cloud any more! 2023-09-15 12:00:28.984 - warn: botvac.0 (24567) Device"Erdgeschoss" with id: Erdgeschoss is not exists in cloud any more! 2023-09-15 12:00:28.985 - warn: botvac.0 (24567) Device"Turnverein Oben" with id: Turnverein Oben is not exists in cloud any more! 2023-09-15 12:00:29.209 - warn: botvac.0 (24567) Device"Erdgeschoss" with id: Erdgeschoss is not exists in cloud any more! 2023-09-15 12:00:29.209 - warn: botvac.0 (24567) Device"Keller" with id: Keller is not exists in cloud any more! 2023-09-15 12:00:29.210 - warn: botvac.0 (24567) Device"Turnverein Oben" with id: Turnverein Oben is not exists in cloud any more! 2023-09-15 12:00:30.373 - error: botvac.0 (24567) 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(). 2023-09-15 12:00:30.374 - error: botvac.0 (24567) unhandled promise rejection: undefined is not a valid state value 2023-09-15 12:00:30.376 - error: botvac.0 (24567) Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at AdapterClass._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5439:49) at AdapterClass.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5400:21) at /opt/iobroker/node_modules/iobroker.botvac/main.js:514:17 at Robot. (/opt/iobroker/node_modules/node-botvac/lib/robot.js:77:17) at /opt/iobroker/node_modules/node-botvac/lib/robot.js:610:17 at /opt/iobroker/node_modules/node-botvac/lib/api.js:40:45 at at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2023-09-15 12:00:30.376 - error: botvac.0 (24567) undefined is not a valid state value 2023-09-15 12:00:30.385 - info: botvac.0 (24567) terminating 2023-09-15 12:00:30.386 - warn: botvac.0 (24567) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-09-15 12:00:30.395 - warn: botvac.0 (24567) State value to set for "botvac.0.Turnverein Oben.commands.spotWidth" has value "0" less than min "100" 2023-09-15 12:00:30.398 - warn: botvac.0 (24567) State value to set for "botvac.0.Turnverein Oben.commands.spotHeight" has value "0" less than min "100" 2023-09-15 12:00:30.524 - debug: botvac.0 (24567) get schedule {"type":1,"enabled":true,"events":[{"day":0,"startTime":"04:00"},{"day":2,"startTime":"04:00"},{"day":4,"startTime":"04:00"},{"day":1,"startTime":"04:00"},{"day":3,"startTime":"04:00"},{"day":5,"startTime":"04:00"},{"day":6,"startTime":"04:00"}]} 2023-09-15 12:00:30.560 - error: botvac.0 (24567) 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(). 2023-09-15 12:00:30.560 - error: botvac.0 (24567) unhandled promise rejection: undefined is not a valid state value 2023-09-15 12:00:30.560 - error: botvac.0 (24567) Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at AdapterClass._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5439:49) at AdapterClass.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5400:21) at /opt/iobroker/node_modules/iobroker.botvac/main.js:514:17 at Robot. (/opt/iobroker/node_modules/node-botvac/lib/robot.js:77:17) at /opt/iobroker/node_modules/node-botvac/lib/robot.js:610:17 at /opt/iobroker/node_modules/node-botvac/lib/api.js:40:45 at at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2023-09-15 12:00:30.561 - error: botvac.0 (24567) undefined is not a valid state value 2023-09-15 12:00:30.577 - warn: botvac.0 (24567) State value to set for "botvac.0.Erdgeschoss.commands.spotWidth" has value "0" less than min "100" 2023-09-15 12:00:30.578 - warn: botvac.0 (24567) State value to set for "botvac.0.Erdgeschoss.commands.spotHeight" has value "0" less than min "100" 2023-09-15 12:00:30.586 - error: botvac.0 (24567) 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(). 2023-09-15 12:00:30.586 - error: botvac.0 (24567) unhandled promise rejection: undefined is not a valid state value 2023-09-15 12:00:30.587 - error: botvac.0 (24567) Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at AdapterClass._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5439:49) at AdapterClass.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5400:21) at /opt/iobroker/node_modules/iobroker.botvac/main.js:514:17 at Robot. (/opt/iobroker/node_modules/node-botvac/lib/robot.js:77:17) at /opt/iobroker/node_modules/node-botvac/lib/robot.js:610:17 at /opt/iobroker/node_modules/node-botvac/lib/api.js:40:45 at at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2023-09-15 12:00:30.587 - error: botvac.0 (24567) undefined is not a valid state value 2023-09-15 12:00:30.670 - warn: botvac.0 (24567) State value to set for "botvac.0.Obergeschoss.commands.spotWidth" has value "0" less than min "100" 2023-09-15 12:00:30.671 - warn: botvac.0 (24567) State value to set for "botvac.0.Obergeschoss.commands.spotHeight" has value "0" less than min "100" 2023-09-15 12:00:30.673 - debug: botvac.0 (24567) get schedule {"enabled":true,"events":[{"mode":2,"day":0,"startTime":"19:30","boundary":{"id":"a94e2a00-949e-4414-ab56-d506f2725d74","name":"Vorraum"},"mapId":"2022-10-03T15:30:57Z"},{"mode":2,"day":1,"startTime":"19:30","boundary":{"id":"a94e2a00-949e-4414-ab56-d506f2725d74","name":"Vorraum"},"mapId":"2022-10-03T15:30:57Z"},{"mode":2,"day":2,"startTime":"19:30","boundary":{"id":"a94e2a00-949e-4414-ab56-d506f2725d74","name":"Vorraum"},"mapId":"2022-10-03T15:30:57Z"},{"mode":2,"day":3,"startTime":"19:30","boundary":{"id":"a94e2a00-949e-4414-ab56-d506f2725d74","name":"Vorraum"},"mapId":"2022-10-03T15:30:57Z"},{"mode":2,"day":4,"startTime":"19:30","boundary":{"id":"a94e2a00-949e-4414-ab56-d506f2725d74","name":"Vorraum"},"mapId":"2022-10-03T15:30:57Z"},{"mode":2,"day":5,"startTime":"19:30","boundary":{"id":"a94e2a00-949e-4414-ab56-d506f2725d74","name":"Vorraum"},"mapId":"2022-10-03T15:30:57Z"},{"mode":2,"day":6,"startTime":"19:30","boundary":{"id":"a94e2a00-949e-4414-ab56-d506f2725d74","name":"Vorraum"},"mapId":"2022-10-03T15:30:57Z"}]} 2023-09-15 12:00:30.702 - debug: botvac.0 (24567) get schedule {"enabled":true,"events":[{"mode":2,"day":1,"startTime":"07:50"},{"mode":2,"day":2,"startTime":"07:50"},{"mode":2,"day":3,"startTime":"07:50"},{"mode":2,"day":4,"startTime":"07:50"},{"mode":2,"day":5,"startTime":"08:30"},{"mode":2,"day":6,"startTime":"09:30"}]} 2023-09-15 12:00:30.714 - debug: botvac.0 (24567) get schedule {"enabled":true,"events":[{"mode":2,"day":5,"startTime":"08:30","boundary":{"id":"7a60a658-82aa-4ef2-b2e5-bf6655c39f59","name":"Vorraum "},"mapId":"2021-11-01T08:33:05Z"},{"mode":2,"day":5,"startTime":"08:50","boundary":{"id":"7c8bb571-74aa-4150-8edd-bb46bf5939c9","name":"Bad Klo"},"mapId":"2021-11-01T08:33:05Z"},{"mode":2,"day":2,"startTime":"07:50"},{"mode":2,"day":3,"startTime":"07:50"},{"mode":2,"day":1,"startTime":"07:50","boundary":{"id":"7a60a658-82aa-4ef2-b2e5-bf6655c39f59","name":"Vorraum "},"mapId":"2021-11-01T08:33:05Z"},{"mode":2,"day":4,"startTime":"07:50","boundary":{"id":"7a60a658-82aa-4ef2-b2e5-bf6655c39f59","name":"Vorraum "},"mapId":"2021-11-01T08:33:05Z"},{"mode":2,"day":1,"startTime":"08:15","boundary":{"id":"7c8bb571-74aa-4150-8edd-bb46bf5939c9","name":"Bad Klo"},"mapId":"2021-11-01T08:33:05Z"},{"mode":2,"day":4,"startTime":"08:15","boundary":{"id":"7c8bb571-74aa-4150-8edd-bb46bf5939c9","name":"Bad Klo"},"mapId":"2021-11-01T08:33:05Z"},{"mode":2,"day":6,"startTime":"09:30"}]} 2023-09-15 12:00:30.832 - error: botvac.0 (24567) 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(). 2023-09-15 12:00:30.833 - error: botvac.0 (24567) unhandled promise rejection: undefined is not a valid state value 2023-09-15 12:00:30.833 - error: botvac.0 (24567) Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at AdapterClass._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5439:49) at AdapterClass.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5400:21) at /opt/iobroker/node_modules/iobroker.botvac/main.js:514:17 at Robot. (/opt/iobroker/node_modules/node-botvac/lib/robot.js:77:17) at /opt/iobroker/node_modules/node-botvac/lib/robot.js:610:17 at /opt/iobroker/node_modules/node-botvac/lib/api.js:40:45 at at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2023-09-15 12:00:30.834 - error: botvac.0 (24567) undefined is not a valid state value 2023-09-15 12:00:30.879 - warn: botvac.0 (24567) State value to set for "botvac.0.Keller.commands.spotWidth" has value "0" less than min "100" 2023-09-15 12:00:30.886 - info: botvac.0 (24567) terminating 2023-09-15 12:00:30.920 - warn: botvac.0 (24567) State value to set for "botvac.0.Keller.commands.spotHeight" has value "0" less than min "100" 2023-09-15 12:00:30.927 - warn: botvac.0 (24567) get state error: DB closed 2023-09-15 12:00:30.928 - warn: botvac.0 (24567) get state error: DB closed 2023-09-15 12:00:31.058 - error: host.VM-Slave instance system.adapter.botvac.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-09-15 12:00:31.061 - warn: host.VM-Slave Do not restart adapter system.adapter.botvac.0 because restart loop detected
-
@JohGre
OK und sorry,
Dann mach bitte ein neues Issue beim Adapter auf und erstell hier ggF einen eigenen Thread zum Thema botvac. Das ist definitiv ain Anpassungsproblem diese Uralt Adapters der leider schon länger keine Wartung mehr hatte.Hoff ich / jemand kann das fixen auch ohne die passende Hardware zu haben.
Aber wie gesagt - bitte in getrenntem Thread weiter behandeln (und diesn ggF hier verlinken). Das wird zu speziell hier.
DANKE
-
@mcm57 Zur Info
Habe gerade einen fork des community-Adapters gefunden der funktioniert. Vielleicht könnt ihr das zusammenlegen.https://github.com/PeterVoronov/ioBroker.botvac/tree/patch-1
zugehöriger Thread:
https://forum.iobroker.net/topic/44822/neato-botvac-adapter-further-development/45?_=1694772899628 -
@johgre
Danke für die Info; schaus mir an. Dieser Fork unterscheidet sich aber nur bei einer Variablen - nicht aber dort wo es jetzt bei dir gecrashed hat. Der Fix aus dem Fork kommt aber jedenfalls in die nächste Release.Aber bitte entweder im referenzierten Thread weiter oder einen neuen öffnen.
Danke