UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[apollon77]

Ok,die 4.0.4 sollte im Repo sein und funktioniert. Ich habe die Anleitung oben aktualisiert, da ggf "Fehler" ausgegeben werden die ok sind und am Update liegen.

[JohGre]

Habe mich auch getraut und gleich das Produktivssystem mit einem Slave gehoben (4.0.4). Upgrade war problemlos und keine Fehler.
:+1: :+1: :clap:

[lonsimbt]

@apollon77

Update auf 4.04 ist via

iobroker upgrade self

problemlos durchgelaufen. System läuft.

Gruß Marco

[e-i-k-e]

Meine Master habe ich auch über iobroker upgrade self auf 4.0.4 gebracht.

Testweise hebe ich einen meine Slaves auch auf die aktuelle Version hoch gezogen.

Hier funktioniert anschließend der rpi2 Adapter nicht.

javascript.5	2022-02-06 12:47:59.873	info	(21150) Sets unsupported
rpi2.5	2022-02-06 12:47:57.476	error	(21169) cannot use GPIO: TypeError: Cannot read property 'setMode' of null
rpi2.5	2022-02-06 12:47:57.470	error	the module (for instance, using `npm rebuild` or `npm install`).
rpi2.5	2022-02-06 12:47:57.470	error	NODE_MODULE_VERSION 83. Please try re-compiling or re-installing
rpi2.5	2022-02-06 12:47:57.470	error	NODE_MODULE_VERSION 72. This version of Node.js requires
rpi2.5	2022-02-06 12:47:57.470	error	was compiled against a different Node.js version using
rpi2.5	2022-02-06 12:47:57.470	error	(21169) Cannot initialize GPIO: Error: The module '/opt/iobroker/node_modules/epoll/build/Release/epoll.node'
rpi2.5	2022-02-06 12:47:55.156	info	(21169) starting. Version 1.2.0 in /opt/iobroker/node_modules/iobroker.rpi2, node: v14.18.2, js-controller: 4.0.4
rpi2.5	2022-02-06 12:47:54.305	info	(21169) Sets unsupported
rpi2.5	2022-02-06 12:47:54.303	info	(21169) Sets unsupported
rpi2.5	2022-02-06 12:47:54.301	info	(21169) Sets unsupported
rpi2.5	2022-02-06 12:47:54.295	info	(21169) Sets unsupported
host.raspberrypi-display5	2022-02-06 12:47:49.324	info	instance system.adapter.rpi2.5 started with pid 21169
host.raspberrypi-display5	2022-02-06 12:47:46.955	info	instance system.adapter.javascript.5 started with pid 21150
host.raspberrypi-display5	2022-02-06 12:47:43.713	info	starting 2 instances
host.raspberrypi-display5	2022-02-06 12:47:43.579	info	91 instances found
host.raspberrypi-display5	2022-02-06 12:47:39.465	info	Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
host.raspberrypi-display5	2022-02-06 12:47:39.441	info	added notifications configuration of host
host.raspberrypi-display5	2022-02-06 12:47:39.397	info	Node.js version has changed from unknown to 14.18.2
host.raspberrypi-display5	2022-02-06 12:47:39.370	info	connected to Objects and States
host.raspberrypi-display5	2022-02-06 12:47:37.963	info	Sets unsupported
host.raspberrypi-display5	2022-02-06 12:47:37.962	info	Sets unsupported
host.raspberrypi-display5	2022-02-06 12:47:37.960	info	Sets unsupported
host.raspberrypi-display5	2022-02-06 12:47:37.958	info	Sets unsupported
host.raspberrypi-display5	2022-02-06 12:47:37.224	info	ip addresses: 192.168.3.114 fe80::5f2b:268f:852e:cb99
host.raspberrypi-display5	2022-02-06 12:47:37.220	info	hostname: raspberrypi-display5, node: v14.18.2
host.raspberrypi-display5	2022-02-06 12:47:37.219	info	Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
host.raspberrypi-display5	2022-02-06 12:47:37.208	info	iobroker.js-controller version 4.0.4 js-controller starting
host.raspberrypi-display5	2022-02-06 12:43:55.858	info	terminated

Edit:

pi@raspberrypi-display5:/opt/iobroker $ iobroker rebuild rpi2.5 --install
Path argument needs to be an absolute path!

[Chaot]

@apollon77 Update ist problemlos durchgelaufen.
Der Ubuntu Adapter stürzt ab, aber der ist sowieso eine Datenleiche und wird meinerseits nicht mehr benötigt.

Mein erster Eindruck ist, dass die Admin Oberfläche irgendwie flüssiger laüft. Gerade beim Scrollen durch die Objekte hatte ich vorher deutliche Verzögerung. Ich hatte das eigentlich auf meinen Browser und System zurückgeführt, aber das schien doch vom ioBroker zu kommen.

[paul53]

@e-i-k-e sagte:

pi@raspberrypi-display5:/opt/iobroker $ iobroker rebuild rpi2.5 --install

Versuche

iobroker rebuild rpi2 --install

[e-i-k-e]

@paul53

Klappt leider nicht.

pi@raspberrypi-display5:/opt/iobroker $ iobroker rebuild rpi2 --install
Path argument needs to be an absolute path!
pi@raspberrypi-display5:/opt/iobroker $ cd
pi@raspberrypi-display5:~ $ iobroker rebuild rpi2 --install
Path argument needs to be an absolute path!

Edit: Auf einem anderen Slave mit 3.3.22 klappt der Befehl wie gewohnt.

pi@raspberrypi-display2:/opt/iobroker $ iobroker rebuild rpi2.2 --install       npm install --loglevel error --production (System call1) in "/opt/iobroker/node_modules/iobroker.rpi2"

Rebuild rpi2.2 done

[UweRLP]

Auch hier, ein Windows 10 x64 System, hat das Upgrade auf die 4.0.4 erfolgreich geklappt.
Danke

Es gab die im ersten Post angeküdigten Fehlermeldungen aber es läuft soweit ich bisher sehen konnte.
Der yamaha und deconz Adapter bringen nun WARN Meldungen, denke aber das muß im Adapter gefixt werden.

yamaha.0
	2022-02-06 13:30:25.803	warn	This object will not be created in future versions. Please report this to the developer.
yamaha.0
	2022-02-06 13:30:25.803	warn	Object yamaha.0.powerAllZones is invalid: obj.common.min has an invalid type! Expected "number", received "boolean"
yamaha.0
	2022-02-06 13:30:25.801	warn	This object will not be created in future versions. Please report this to the developer.
yamaha.0
	2022-02-06 13:30:25.801	warn	Object yamaha.0.zone4 is invalid: obj.common.min has an invalid type! Expected "number", received "boolean"
yamaha.0
	2022-02-06 13:30:25.800	warn	This object will not be created in future versions. Please report this to the developer.
yamaha.0
	2022-02-06 13:30:25.799	warn	Object yamaha.0.zone3 is invalid: obj.common.min has an invalid type! Expected "number", received "boolean"
yamaha.0
	2022-02-06 13:30:25.798	warn	This object will not be created in future versions. Please report this to the developer.
yamaha.0
	2022-02-06 13:30:25.798	warn	Object yamaha.0.zone2 is invalid: obj.common.min has an invalid type! Expected "number", received "boolean"
yamaha.0
	2022-02-06 13:30:25.796	warn	This object will not be created in future versions. Please report this to the developer.

deconz.0
	2022-02-06 13:31:23.405	warn	This object will not be created in future versions. Please report this to the developer.
deconz.0
	2022-02-06 13:31:23.405	warn	Object Lights.17.xy is invalid: Default value has to be stringified but received type "object"
deconz.0
	2022-02-06 13:31:23.347	warn	This object will not be created in future versions. Please report this to the developer.
deconz.0
	2022-02-06 13:31:23.347	warn	Object Lights.15.xy is invalid: Default value has to be stringified but received type "object"
deconz.0
	2022-02-06 13:31:23.292	warn	This object will not be created in future versions. Please report this to the developer.
deconz.0
	2022-02-06 13:31:23.291	warn	Object Lights.14.xy is invalid: Default value has to be stringified but received type "object"
deconz.0
	2022-02-06 13:31:23.058	warn	This object will not be created in future versions. Please report this to the developer.
deconz.0
	2022-02-06 13:31:23.058	warn	Object Lights.13.xy is invalid: Default value has to be stringified but received type "object"
deconz.0
	2022-02-06 13:31:22.952	warn	This object will not be created in future versions. Please report this to the developer.
deconz.0
	2022-02-06 13:31:22.952	warn	Object Lights.12.xy is invalid: Default value has to be stringified but received type "object"
deconz.0
	2022-02-06 13:31:22.892	warn	This object will not be created in future versions. Please report this to the developer.
deconz.0
	2022-02-06 13:31:22.891	warn	Object Lights.11.xy is invalid: Default value has to be stringified but received type "object"
deconz.0
	2022-02-06 13:31:22.834	warn	This object will not be created in future versions. Please report this to the developer.
deconz.0
	2022-02-06 13:31:22.834	warn	Object Lights.10.xy is invalid: Default value has to be stringified but received type "object"
deconz.0
	2022-02-06 13:31:22.777	warn	This object will not be created in future versions. Please report this to the developer.
deconz.0
	2022-02-06 13:31:22.777	warn	Object Lights.9.xy is invalid: Default value has to be stringified but received type "object"
deconz.0
	2022-02-06 13:31:22.492	warn	This object will not be created in future versions. Please report this to the developer.
deconz.0
	2022-02-06 13:31:22.492	warn	Object Groups.26756.xy is invalid: Default value has to be stringified but received type "object"
deconz.0
	2022-02-06 13:31:22.487	warn	This object will not be created in future versions. Please report this to the developer.
deconz.0
	2022-02-06 13:31:22.487	warn	Object Groups.5.xy is invalid: Default value has to be stringified but received type "object"
deconz.0
	2022-02-06 13:31:22.486	warn	This object will not be created in future versions. Please report this to the developer.
deconz.0
	2022-02-06 13:31:22.486	warn	Object Groups.4.xy is invalid: Default value has to be stringified but received type "object"
deconz.0
	2022-02-06 13:31:22.486	warn	This object will not be created in future versions. Please report this to the developer.
deconz.0
	2022-02-06 13:31:22.486	warn	Object Groups.1.xy is invalid: Default value has to be stringified but received type "object"
deconz.0
	2022-02-06 13:31:22.485	warn	This object will not be created in future versions. Please report this to the developer.
deconz.0
	2022-02-06 13:31:22.485	warn	Object Groups.2.xy is invalid: Default value has to be stringified but received type "object" 

[paul53]

@e-i-k-e sagte: mit 3.3.22 klappt der Befehl wie gewohnt.

Changelog 4.0.0:

CLI command iob rebuild adaptername is no longer supported because of the new way of automatic rebuilds and some unwanted side effects

[UweRLP]

@uwerlp issues waren bei GitHub schon angelegt :-)

[e-i-k-e]

@paul53
Ach oaky! Das erklärt das natürlich.

Nur wie behebe ich den Fehler @apollon77 ?

[apollon77]

@e-i-k-e hi, hier muss der binäre Teil neu ge auth. werden. Hast du mal da volle log? An sich sollte er jetzt bis zu drei mal versuchen über rebuilds das zu fixen

[ice987]

ich hab' mich auch versucht mit dem
System: ioBroker.docker v6.0.0
und erhalte folgende Fehlermeldung:

root@iobroker-v600-testsystem7:/opt/iobroker# pkill -u iobroker
root@iobroker-v600-testsystem7:/opt/iobroker# iobroker update
Used repository: latest
hash unchanged, use cached sources
update done
Adapter    "admin"         : 5.2.3    , installed 5.1.25 [Updateable]
Controller "js-controller" : 4.0.4    , installed 3.3.21 [Updateable]
root@iobroker-v600-testsystem7:/opt/iobroker# iobroker upgrade self
Update js-controller from @3.3.21 to @4.0.4
NPM version: 6.14.16
npm install iobroker.js-controller@4.0.4 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
In file included from ../../nan/nan.h:58,
                 from ../src/unix_dgram.cc:5:
/opt/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793:7: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
  793 |       (node::addon_register_func) (regfunc),                          \
      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:827:3: note: in expansion of macro ‘NODE_MODULE_X’
  827 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
      |   ^~~~~~~~~~~~~
../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
  404 | NODE_MODULE(unix_dgram, Initialize)
      | ^~~~~~~~~~~
Server Objects 127.0.0.1:36016 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
Server States 127.0.0.1:45560 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
Server Objects 127.0.0.1:36016 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
Server States 127.0.0.1:45562 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
Server Objects 127.0.0.1:36016 Error from InMemDB: Error: Unknown LUA script load
Server Objects 127.0.0.1:36016 Error from InMemDB: Error: Unknown LUA script load
Server Objects 127.0.0.1:36016 Error from InMemDB: Error: Unknown LUA script load
Server Objects 127.0.0.1:36016 Error from InMemDB: Error: SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
Server Objects 127.0.0.1:36016 Error from InMemDB: Error: multi NOT SUPPORTED
Server Objects 127.0.0.1:36016 Error from InMemDB: Error: sadd NOT SUPPORTED
Server Objects 127.0.0.1:36016 Error from InMemDB: Error: exec NOT SUPPORTED
root@iobroker-v600-testsystem7:/opt/iobroker# iobroker upgrade

This upgrade of "admin" will introduce the following changes:
==========================================================================
-> 5.2.3:
Fixed error in `AutocompleteSendTo`
Fixed error in charts

-> 5.2.2:
Changed the minimal required js-controller version to 3.3.22 
Used web-socket library 8 (no node 10 support anymore)

-> 5.2.1:
Allow in expert mode the creation of states and channels in mqtt branch

-> 5.2.0:
Fix crash cases reported via sentry
Added support for multi-repositories

-> 5.1.29:
Fix crash cases reported via sentry
Added support for multi-repositories

-> 5.1.28:
Fixed discovery function
Fixed some GUI bugs
==========================================================================

Would you like to upgrade admin from @5.1.25 to @5.2.3 now? [(y)es, (n)o]: y
Update admin from @5.1.25 to @5.2.3
host.iobroker-v600-testsystem7 Adapter "system.adapter.admin.0" is stopped.
NPM version: 6.14.16
Installing iobroker.admin@5.2.3... (System call)
+ iobroker.admin@5.2.3
updated 7 packages in 32.186s

17 packages are looking for funding
  run `npm fund` for details

host.iobroker-v600-testsystem7 Adapter "system.adapter.admin.0" is started
Update "system.adapter.admin.0"
upload [14] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/admin.png admin.png image/png
upload [13] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/de/translations.json i18n/de/translations.json application/json
upload [12] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/en/translations.json i18n/en/translations.json application/json
upload [11] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/es/translations.json i18n/es/translations.json application/json
upload [10] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/fr/translations.json i18n/fr/translations.json application/json
upload [9] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/it/translations.json i18n/it/translations.json application/json
upload [8] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/nl/translations.json i18n/nl/translations.json application/json
upload [7] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
upload [6] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/pt/translations.json i18n/pt/translations.json application/json
upload [5] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/ru/translations.json i18n/ru/translations.json application/json
upload [4] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json
upload [3] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/index.html index.html text/html
upload [2] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/index_m.html index_m.html text/html
upload [1] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/jsonConfig.json jsonConfig.json application/json
upload [0] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/words.js words.js application/javascript
root@iobroker-v600-testsystem7:/opt/iobroker# iobroker start
Starting iobroker controller daemon...
iobroker controller daemon started. PID: 1425

ioBroker ist nicht zu erreichen

[apollon77]

@ice987 ok was steht im log? Ich Seherin den Ausgaben keine Fehler. Da ist an sich alles ok

[ice987]

@apollon77

der Restart vom Container ergibt nun:

--------------------------------------------------------------------------------
-------------------------     2022-02-06 15:04:25      -------------------------
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
-----                 Welcome to your ioBroker-container!                  -----
-----                    Startupscript is now running.                     -----
-----                          Please be patient!                          -----
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
-----                        Debugging information                         -----
-----                                                                      -----
-----                                System                                -----
-----                    arch:                x86_64                       -----
-----                                                                      -----
-----                             Docker-Image                             -----
-----                    image:               v6.0.0                       -----
-----                    build:               2021-12-17T03:48:21+00:00    -----
-----                                                                      -----
-----                               Versions                               -----
-----                    /opt/scripts/iobroker_startup.sh: line 48: /usr/bin/node: Operation not permitted
node:                                             -----
-----                    /usr/bin/env: ‘node’: Operation not permitted
npm:                                              -----
-----                                                                      -----
-----                                 ENV                                  -----
-----                    SETGID:              1000                         -----
-----                    SETUID:              1000                         -----
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
-----                  Step 1 of 5: Preparing container                   -----
--------------------------------------------------------------------------------
 
Nothing to do here.
 
--------------------------------------------------------------------------------
-----             Step 2 of 5: Detecting ioBroker installation             -----
--------------------------------------------------------------------------------
 
Existing installation of ioBroker detected in /opt/iobroker.
 
--------------------------------------------------------------------------------
-----             Step 3 of 5: Checking ioBroker installation              -----
--------------------------------------------------------------------------------
 
(Re)Setting folder permissions (This might take a while! Please be patient!)...
Done.
 
Fixing "sudo-bug" by replacing sudo in iobroker with gosu...
Done.
 
error: exec failed: operation not permitted
/opt/scripts/iobroker_startup.sh: line 199: [: !=: unary operator expected
--------------------------------------------------------------------------------
-----                Step 4 of 5: Applying special settings                -----
--------------------------------------------------------------------------------
 
Some adapters have special requirements/ settings which can be activated by the use of environment variables.
For more information take a look at readme.md on Github!
 
--------------------------------------------------------------------------------
-----                    Step 5 of 5: ioBroker startup                     -----
--------------------------------------------------------------------------------
 
Starting ioBroker...
 
error: exec failed: operation not permitted

[apollon77]

@chaot was ist denn de ubuntu Adapter? Und was gefällt ihm nicht?

[ste_glei]

@ice987
Ich hatte den gleichen log

iobroker fix

hat geholfen

[e-i-k-e]

@apollon77
Hallo,
anbei wie gewünscht die komplette log.
b04d2521-d6ec-46a9-ab5a-18d5ad80331e-iobroker.2022-02-06.log

[ice987]

@ste_glei
kann ich bestätigen:

iobroker fix

hilft und ioBroker läuft nun

[Chaot]

@apollon77 Das ist ne uralte Leiche die mitgelaufen ist.
https://github.com/Standarduser/ioBroker.ubuntu
Ist mir nie aufgefallen dass das noch aktiv ist.
Meinerseits bereits entsorgt, da überflüssig.
Ausgegebener Fehler:

ubuntu.0
2022-02-06 12:57:13.847	error	Cannot read property 'getObjectList' of undefined
ubuntu.0
2022-02-06 12:57:13.846	error	TypeError: Cannot read property 'getObjectList' of undefined at Object.ready (/opt/iobroker/node_modules/iobroker.ubuntu/main.js:35:25) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8225:68
ubuntu.0
2022-02-06 12:57:13.842	error	unhandled promise rejection: Cannot read property 'getObjectList' of undefined
ubuntu.0
2022-02-06 12:57:13.837	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().