Ingo Fischer

I can only repeat: The logline is just a logline ... For me it more looks like that maybe dev-server support for scheduled instances might not be there?? Nortmally scheduled...

This is also an issue of devc-server. It seems to me that the "shutdown" could be too fast sometimes and then alive is set also on next start but shouldn't...

Controller 4.0 should normally detect the needed capabilities to set automatically when he updates the capabilties... We made sure this happens correctly ... there was an "in between version" of...

which js-controller ist used?

the node capabilities need to be set anew ... so iob fix should be executed

``` TypeError: Cannot read property 'hostname' of undefined File "/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js", line 686, col 52, in BackupRestore._restoreAfterStop restore.config ? restore.config.system.hostname || hostname : hostname, File "/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js", line 1118, col 49, in...

seems like iun this case "restore.config.system" is not existing

ANd does the chart mean that you switched off debug logging or seq logging at all ?

@PeterVoronov Whats the seq config? Can You please copy that part out of iobroker-data/iobroker.json? especially interesting is the "Loglevel" setting there. is it empty or set to anything?

@PeterVoronov Would you up for a bit testing? ;-) We do da deepClone of the log object in https://github.com/ioBroker/ioBroker.js-controller/blob/master/packages/common/src/lib/common/logger.ts#L96 (buut in general for all loglevels) ... One idea would be...