Incompatible with Node.js v18.17.1

[Byolock]

I've updated my Node.js version to v18.17.1 and after that I'm now getting the Error :

Rebuild for adapter system.adapter.egigeozone.0 not successful in 3 tries. Adapter will not be restarted again. Please execute "npm install --production" in adapter directory manually.

and a warning saying EgiGeoZone was build for an older version of NodeJS:

adapter "egigeozone" seems to be installed for a different version of Node.js. Trying to rebuild it... 3 attempt

[Apollon77]

Please provide the full log

[Domme33]

I have got the same Problem.

info | iobroker npm-rebuild: Rebuilding native modules ...
info | iobroker rebuild
warn | adapter "egigeozone" seems to be installed for a different version of Node.js. Trying to rebuild it... 1 attempt
info | system.adapter.egigeozone.0 will be rebuilt
info | Adapter system.adapter.egigeozone.0 needs rebuild and will be restarted afterwards.
execute "npm install --production" in adapter directory manually.
error | Caught by controller[0]: Node.js v18.17.1
error | Caught by controller[0]: }
error | Caught by controller[0]: ]
error | Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.egigeozone/main.js'
error | Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.egigeozone/lib/utils.js',
error | Caught by controller[0]: requireStack: [
error | Caught by controller[0]: code: 'MODULE_NOT_FOUND',
error | Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19) {
error | Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12)
error | Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32)
error | Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
error | Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1256:14)
error | Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.egigeozone/lib/utils.js:59:25)
error | Caught by controller[0]: at require (node:internal/modules/cjs/helpers:121:18)
error | Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19)
error | Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:922:27)
error | Caught by controller[0]: at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
error | Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.egigeozone/main.js
error | Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.egigeozone/lib/utils.js
error | Caught by controller[0]: Require stack:
error | Caught by controller[0]: Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js'
error | Caught by controller[0]: ^
error | Caught by controller[0]: throw err;
error | Caught by controller[0]: node:internal/modules/cjs/loader:1080
info | instance system.adapter.egigeozone.0 started with pid 560

[Apollon77]

This has nothing todo with the nodejhs version, it is the js.controller ... or to be more exact: https://github.com/BasGo/ioBroker.egigeozone/blob/master/package.json#L22 adapter-core needs to be at least a "last 2,x version" and not 1.x ... This dependency needs to be updated at least

[Domme33]

nodejs and js.controller are on the newest version. How can i update the adapter-core?

[Apollon77]

The adapter devloper needs to do this

[bastiaux]

So, there will be no other solution to run the adapter on the newest js.controller until the devloper will update the adapter-core, which still didn't happend, right?

[obakuhl]

As the original developer @BasGo no longer actively maintains the adapter, what are the options @Apollon77 for those who have used this adapter?
It is clear that the adapter core needs to be reworked. This adapter is not listed in the list of incompatible adapters, it should be adjusted or at least highlighted.
As of today the only way to continue using this adapter would be a roll-back of the js.controller.

[mcm1957]

As the original Maintainer did not take the now madatory measure to ensure a migration to iobroker-community-adapters an easy migration is not possible.

One possibility will be a fork / renaming of the adapter. I will note this at my todo list. As I cannot perform any tests would you be available as an alpha tester ?

But in any case - this might not occure with the next days ...

@Apollon77
FYI

[obakuhl]

@mcm1957 Thanks for your quick feedback. Sure I am available for such tests.

[mcm1957]

see #15