JS-Controller Update SOLVED

[ap2017]

I have two installations of ioBroker, both on Intel platform, actually I am transitioning from one to another. So, the older one just allowed me to update JS Controller to version 2.0.38, while the new one goes through update process, no error codes, but still displays old version in Hosts. And the way it shows Installed and Available versions is weird.

SOLUTION: My new controller was setup to default repository instead of latest. After change all updates went fine.

[Stabilostick]

@ap2017

Are both servers configured for the „latest“ version tree?

[ap2017]

@Stabilostick Yes they both configured for latest version tree. I will try to update the new server again and provide an update log.

[ap2017]

@Stabilostick Actually, the new server was set to "default" after changing to "latest" it shows JS-Controller Available 2.0.34 / Installed 2.0.34

[Stabilostick]

@ap2017

So, is your problem solved?

[ap2017]

@Stabilostick Almost! The old server shows controller 2.0.38 available, while the new one is 2.0.34 .

[Stabilostick]

@ap2017

The latest version for js-controller changes quit often because the developers want to transfer it in the stable branch. Lots of fixes in the last days.

[Sher02]

@Stabilostick Yes it does change very often. I often feel irritated. http://walmartone.fyi/

[krstaricuuh]

@Sher02 said in JS-Controller Update SOLVED:

@Stabilostick Yes it does change very often. I often feel irritated. https://www.tellthebell.one/

The old server shows controller 2.0.38 available, while the new one is 2.0.34.