Fix for invalid jsonConfig message

[mattreim]

warn: admin.0 (822) deconz has an invalid jsonConfig: [{"instancePath":"/items/_instruction/darkStyle","schemaPath":"#/properties/items/patternProperties/%5E.%2B/properties/darkStyle/type","keyword":"type","params":{"type":"string"},"message":"must be string"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"else"},"message":"must match \"else\" schema"}]

Nothing has changed in terms of optics.

[mattreim]

Now I've tried so much that the adapter no longer works.

[mattreim]

@Jey-Cee Unfortunately, the adapter no longer works at all when reinstalled. Now I have reinstalled my system and it does not connect to deConz. Downgrading to an older version also doesn't work because the "index_m.html" cannot be found.

[Jey-Cee]

Try an upload of adapter files. Turn on Expert mode, go to Adapter tab, hit the 3 dot button on deConz card and then the arrow up button.

[mattreim]

With an installation of a restore (index_m/io-package) and then an update it works.

[mattreim]

There are no errors in the log because it doesn't connect.

[Jey-Cee]

Which js-controller is running on your host?

[mattreim]

Node.js: v20.17.0
NPM: 10.8.2
js-controller: 6.0.11

[mattreim]

Could it be that “bridge” is no longer connected? Just an idea since port and websocket appear in main.js (with native values).

[Jey-Cee]

Hm on my productive system the adapter works.
On my test system and the productive system is nodejs 22 installed.
I have to test if this is the problem.

[mattreim]

It's clearly a reinstallation problem.

[Jey-Cee]

Check 1.6.2

[mattreim]

It now finds the deConz version and creates the object structure but it still doesn't show me connected.

It doesn't update either.

[mattreim]

I think it's because of the other "results.native...".

[Jey-Cee]

Can you point to a soecific line in code?

[mattreim]

ioBroker.deconz/main.js

Line 513 in 64aebd4

if (results.native.ipaddress === undefined) {

ioBroker.deconz/main.js

Line 517 in 64aebd4

if (results.native.port === "" || results.native.port === null) {

ioBroker.deconz/main.js

Line 524 in 64aebd4

if (results.native.user === "" || results.native.user === null) {

ioBroker.deconz/main.js

Line 700 in 64aebd4

host = results !== null && results.native.ipaddress !== undefined ? results.native.ipaddress : null;

ioBroker.deconz/main.js

Line 701 in 64aebd4

port = results !== null && results.native.websocketport !== undefined ? results.native.websocketport : 443;

ioBroker.deconz/main.js

Line 702 in 64aebd4

user = results !== null && results.native.user !== undefined ? results.native.user : null;

ioBroker.deconz/main.js

Line 884 in 64aebd4

ip = results.native.ipaddress;

ioBroker.deconz/main.js

Line 885 in 64aebd4

port = results.native.port;

ioBroker.deconz/main.js

Line 886 in 64aebd4

user = results.native.user;

I hope it was all of them.

[Jey-Cee]

Thx. I hope thats all. V1.6.3 is published.

[mattreim]

Now it can be installed again without any problems. Thanks

[mattreim]

Two notes, you should delete the versions that don't work and the invalid jsonConfig error will still exist.

[mattreim]

But otherwise everything is fine.

[mattreim]

@Jey-Cee I think websocketport should be here.

ioBroker.deconz/main.js

Line 688 in 0c279f1

const port = adapter.config.port ? adapter.config.websocketport : 443;

[Jey-Cee]

We can close this as it is a bug in the schema of darkStyle.
#ioBroker/adapter-react-v5#443