Warning and error message when instance is started

[UweSauter]

Hi again.

When starting an instance of ioBroker.resol (v1.0.0) with a VBus/Lan configuration and an attached (Cosmo Multi2)[https://www.cosmo-info.de/produkte/heizungstechnik/solartechnik/regelungen/regelung-multi-2] I get one warning and one error during startup:

• info | starting. Version 1.0.0 (non-npm: grizzelbee/ioBroker.resol) in /opt/iobroker/node_modules/iobroker.resol, node: v16.13.1, js-controller: 4.0.23
• info | Config seems to be valid for LAN or LAN-Gateway.
• info | TCP Connection via LAN to [192.168.55.224:7053] selected
• info | Waiting for Connection...
• info | Connection state changed to CONNECTING
• info | Connection established
• warn | [getJSONByResolId] Controller type not found in setup file.
• error | [generateDP] Error: TypeError: Cannot read properties of undefined (reading 'setup')

Once started the instance can read sensors as expected.
Is this normal?

ioBroker is at v4.0.23

[Grizzelbee]

warn | [getJSONByResolId] Controller type not found in setup file.
error | [generateDP] Error: TypeError: Cannot read properties of undefined (reading 'setup')

Is this normal?

Basically: Yes. This adapter is designed to support Resol-Controllers.
And to identify the actual controller a controller-ID is used. It makes sense, that Cosmo uses different IDs than Resol. But the Cosmo IDs are currently unknown to the adapter. Thats why this error occurs.
This ID is not really important for reading the values (thats why this part works) but if you like to control pumps or things like that, it's important. The various controllers support very different features.

To get that fixed please switch the adapter to debug loglevel, start it and post the log here. Your actual ID should be mentioned there and I can implement this feature than.

[UweSauter]

debug.resol.0.zip

This is the zipped HTML output.

[Grizzelbee]

V1.1.0 should fix your issue and add basic support for your controller.
But it's only basic support. Unfortunately I can't support all various controllers the same way. If you need more control of your controller you may need to do some investigation and configuration on your own. I'll only may be able to give you some hints.

[UweSauter]

With v1.1.0 new errors happen:

debug.resol.0.zip

[Grizzelbee]

Was a wrong file name. V1.1.1 should fix it.

[UweSauter]

Those two warnings still exist in 1.1.1:

[getJSONByResolId] Error: SyntaxError: Unexpected token / in JSON at position 832

[generateDP] Error: TypeError: Cannot read properties of undefined (reading 'setup')