Javascripts update 5.7 - scripts lost...?

[Thomas Braun]

@erwinberlin

JS

is not a valid entry. Either put the correct full path to your skripts or leave it empty.

[erwinberlin]

@thomas-braun
Leaving it empty does not result in my scripts appearing again.

And the back up issue still exists. Backups are stored on the file server and can be read. However, when decompressing there seems to be an issue. Could be rights or location. Right now I am searching for the javascript folder.

[Thomas Braun]

@erwinberlin

How do you create backups and how do you put the backup files back into your system?

[erwinberlin]

@thomas-braun
backups to a synology (SMB3.0). Restoring on a clean install works fine.

[Thomas Braun]

@erwinberlin sagte in Javascripts update 5.7 - scripts lost...?:

Restoring on a clean install works fine.

Why don't you do this then?

[erwinberlin]

@thomas-braun
that is a last resort option. It is weird that the javascript update breaks the system.

[Thomas Braun]

@erwinberlin sagte in Javascripts update 5.7 - scripts lost...?:

It is weird that the javascript update breaks the system.

I think it's your faulty setup of the mirror directory.

[erwinberlin]

@thomas-braun that may well be faulty. Now the question is how to fix it.

[Thomas Braun]

@erwinberlin

iobroker stop
iobroker fix
iobroker start

Then pull back in your javaskript-Backup:

[erwinberlin]

@thomas-braun I did that already. Unfortunately, it does not help.

[erwinberlin]

So I ended up doing a full clean install RPI4 3Gb with Bullseye 64 bit. Restoring worked for adapters and javascript; zigbee and history both came with errors:
{"errno":-1,"code":"EPERM","syscall":"utime","path":"/opt/iobroker/backups/tmpScripts/"}
Still it all worked, so it is just a finding.

[erwinberlin]

My solution (which I did tried 4x today) is to do a clean install. And then do the following in this order:

1. restore history, java scripts and zigbee data
2. install VIS via the adapters
3. do an ioBroker restore

And then the history data is still missing unfortunately. at least the system is up and running again in 10 mins. Did it 4x to get the Tuya devices to connect. unfortunately to no avail... (separate thread)

BTW I changed from RPI to docker on Ubuntu server running on a Fujitsu Futro s740 with 8Gb and 128Gb SSD. That is a bit more stable and flexible than the RPi system.