Update System iobroker failed

[crunchip]

@tiger sagte in Update System iobroker failed:

don't remember if socketio is used but it was installed.

Not currently, you can switch and test it or use pure web sockets

[mickym]

@tiger sagte in Update System iobroker failed:

@mickym
So... if I'm understanding well...
I've to let like that without copy the directory...
install the new node of Alexa...
and made a new programmation?

as i wanted to have an installation up to date... if it's your recommandation... i'll do like that...

Yes my recommendation is to do not copy the old stuff. Edit your package.json and delete the line in the dependencies section which refers to the old- alexa node. Run npm install hopefully without errors. Activate in the node red adapter configuration that you use the pallet manager and install a different node. Then you need to rework all alexa flows

[Homoran]

@tiger sagte in Update System iobroker failed:

Zigbee, probably same, I've to pair everything

i don't use zigbee and therefore I'm very sorry if there is a pitfall too.
But @Thomas-Braun may know wether there will be a solution.

[Tiger]

@mickym said in Update System iobroker failed:

package.json

ok I'll do it...
but, how do you edit the package.json?

[Tiger]

@homoran

No it seems everything is working well...
Zigbee and Rfxcom... good news...

[Tiger]

@crunchip

it seems it's due to my version of iobroker.admin...

I thing we'll be able to solve it after upgrading system...

2022-08-16 18:10:28.357	error	startInstance system.adapter.web.0 Adapter dependency not fulfilled on any host: required adapter "admin" has wrong version. Installed "4.0.10", required ">=5.1.0"!

[crunchip]

@tiger I do not understand all the problems, that was a backup with the backitup adapter? Why admin 4

[Homoran]

@crunchip sagte in Update System iobroker failed:

that was a backup with the backitup adapter?

no manually by iobroker backup

the admin had been downgraded by the restore

[crunchip]

@homoran

@tiger sagte in Update System iobroker failed:

Vis installed
Backup with --force done...
ADmin version has beenn downgrade to 4.0 as before...

Why
itself or through backup

@tiger sagte in Update System iobroker failed:

Installed "4.0.10", required ">=5.1.0"

then do the upgrade

[mickym]

@tiger sagte in Update System iobroker failed:

@mickym said in Update System iobroker failed:

package.json

ok I'll do it...
but, how do you edit the package.json?

Goto directory

cd /opt/iobroker/iobroker-data/node-red
nano package.json

If a message occurs that file is write protected then use

sudo nano package.json

Search for the reference of the alexa node. CTRL + k should delete line. I’m typing on my mobile so you need to look at the bottom describing the short-cuts. CTRL + x to
exit and confirm to write.

Ensure that you run npm install in the directory /opt/iobroker/iobroker-data/node-red. After you started the Node Red Adapter using the pallet manager, remove all alexa nodes from your flows and update your nodes within the pallet manager, if updates are available. This should be done on a regular base. Keep your system up to date to avoid surprises like this.

[Homoran]

@crunchip sagte in Update System iobroker failed:

through backup

as I understood

[Tiger]

@mickym

I made by another way as i've not a lot of node to install and needed.
I installed node manually,
Now I'm trying to find the correct alexa node...
moreover The boolean-logic that was installed don't work now... I had a AND node, that works good... now don't work...

So I'm truing to find these two solution.

node-red is correctly connect to My LOGO !8 from siemens

Regards

[Tiger]

@mickym

Alexa works... and boolean now too...

So I'm going to made all as before with the new node...

See you all after that to upgrade my system !

[Tiger]

@mickym

Don't know why,
Was trying to add other functionnality that doesn't work with node amazon

and connexion lost

message in the log file are like that

node-red.0	2022-08-16 21:00:26.108	info	(8145) node-red exited with 1
node-red.0	2022-08-16 21:00:25.642	warn	(8145) 16 Aug 21:00:25 - [warn] Projects disabled : editorTheme.projects.enabled=false
node-red.0	2022-08-16 21:00:21.074	warn	(8145) (node:8183) [DEP0128] DeprecationWarning: Invalid 'main' field in '/opt/iobroker/node_modules/@node-red/editor-client/package.json' of './lib/index.js'. Please either fix that or report it to t
node-red.0	2022-08-16 21:00:21.067	warn	(8145) 16 Aug 21:00:21 - [warn] server.httpadminauth-deprecated
node-red.0	2022-08-16 21:00:19.544	info	(8145) Starting node-red: --max-old-space-size=2048 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js

[mickym]

@tiger I cant help you with alexa - as I personally do not use it. The only node - which I help for support was this node:
node-red-contrib-virtual-smart-home. The message which you log are specific to nodes that you have installed.

[Tiger]

@mickym
how can i solved it?
as i can't access to node-red now...
when trying to open node-red message appear

This site is not accessible
192.168.1.16 don't allow the connexion

[mickym]

@tiger Try to start node-red in secure mode - then the flows do not start and you can delete all alexa stuff.

[Tiger]

@mickym

ok now.
With your node-red-contrib-virtual-smart-home, it works with alexa?

[mickym]

@tiger As I said - I have no alexa - however when users used it they had good experience .
https://flows.nodered.org/node/node-red-contrib-virtual-smart-home
You need to register it.

But to be honest - if there are only problems with alexa and the other flows work - you may should ask for help from users who work with alexa. So if all your other nodes work - then you should open a separate thread to solve your alexa issues.

[Tiger]

@mickym
node-red is only for alexa...
all other node are for the programmation of alexa.

I had register, connect...

but you are right, I think we can continue to upgrade and i will solve the problem of node-red after