you have not provided a custom_m.html so please setsupportsCustoms to false!
Originally posted by @Apollon77 in ioBroker/ioBroker.repositories#756 (comment)

{
    ...
    "common": {
        ...
        "supportCustoms": false,
        ...
    }
    ...
}

Think about update stable version to 1.5.4

Version: stable=1.5.1 (191 days old) => latest=1.5.4 (15 days old)
Installs: stable=58 (66.67%), latest=11 (12.64%), total=87

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!
Do not close this issue manually as a new issue will be created if condition for update still exists
@mcm1957 for evidence

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/ylabonte/ioBroker.procon-ip

• [E152] No common.dataSource found in io-package.json
• [E605] No actual year found in copyright. Please add "Copyright (c) 2021 Yannic Labonte [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2021 Yannic Labonte [email protected]" at the start of LICENSE

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

The current version 0.2 brings up an error within ioBroker log periodically.

Node.js v10.19.0
NPM 6.13.4

please make sure that onUnload also stops the timouts in get state service. unload currently is doing nothing. Else it will break the compact mode - did you ever tested the adapter in compact mode?
Originally posted by @Apollon77 in ioBroker/ioBroker.repositories#756 (comment)

I was not able to find the place where info channel and info.connection objects were created (https://github.com/ylabonte/ioBroker.procon-ip/blob/master/src/main.ts#L127) Plese add them to the instanceObjects in io-package... see e.g. tuya adapter or such
Originally posted by @Apollon77 in ioBroker/ioBroker.repositories#756 (comment)

Please remove duplicate changelog headers at README.md if time allows. (Most likely copy & Paste result :-) )

https://github.com/ylabonte/ioBroker.procon-ip/tree/master?tab=readme-ov-file#changelog-1

Version 1.2.1

My current instance shows always the label of the following element. For example relais 7 named as "Heat pump" within Procon-IP is also named "Heat Pump", but the text label shows the valua of the following relay 8. Same for sensors.

Can you reproduce this issue?

What is correct in this case?

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

Die Procon.IP Instanz verbindet sich nach dem Update nicht mehr mit der ProconIP Steuerung.

Unter der vorherigen Version lief es bis auf das Relay Umschalt Problem einwandfrei.

Die Procon Steuerung ist erreichbar und aktiv und Wurde neu gestartet.

Was könnte ich testen, damit das wieder klappt?

Think about update stable version to 1.5.1

Version: stable=1.4.0 (44 days old) => latest=1.5.1 (30 days old)
Installs: stable=41 (49.4%), latest=16 (19.28%), total=83

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!

We have detected that your adapter supports the compact mode. Please use the latest js-controller 2.0 and verify that everything works.

Some more information what is important to check can be found at ioBroker/ioBroker.js-controller#512

On questions please answer to the linked issue. Please close this issue after your test and add the version number that you have tested please as a comment.

Thank you for your support.

you added the code to use Auto Adapter encryot/decrypt but you did not provided "encryptedNative" array with the fieldnames in io-package, so most likely there will be NO encryption at all! (changing this will break itfor your users potentially!) Additionally when you do it that way make sure to rename your "own" encrypt/decrypt methods in index_m.ht,l - else they conflict with the ones also build in in Admin
Originally posted by @Apollon77 in ioBroker/ioBroker.repositories#756 (comment)

Dear Adapter developer,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

Please also have a look at https://github.com/ioBroker/ioBroker.repositories#development-and-coding-best-practices
Originally posted by @Apollon77 in ioBroker/ioBroker.repositories#756 (comment)

This is a general adapter refactoring regarding ioBroker's coding best practices referenced above.

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/ylabonte/ioBroker.procon-ip

• [E605] No actual year found in copyright. Please add "Copyright (c) 2020 Yannic Labonte [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2020 Yannic Labonte [email protected]" at the start of LICENSE

I have also found warnings that may be fixed if possible.

• [W400] Cannot find "procon-ip" in latest repository

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

Hallo yannic,

gibt es wegen der Fehlermeldungen was neues?
Besteht ja schon länger, oder soll die Log-Ausgabe weiterhin mit error eingestellt bleiben um die Log- Datei nicht komplett "zuzuspamen" ;-) ?
Hab im Controller-Forum auch nochmal geschrieben, da ist irgendwie Stillstand.

procon-ip.0 | 2021-04-18 11:23:31.385 | warn | (1588) State "procon-ip.0.temperatures.1.offset" has no existing object, this might lead to an error in future versions
procon-ip.0 | 2021-04-18 11:23:31.384 | warn | (1588) State "procon-ip.0.temperatures.1.id" has no existing object, this might lead to an error in future versions
procon-ip.0 | 2021-04-18 11:23:31.383 | warn | (1588) State "procon-ip.0.analog.4.categoryId" has no existing object, this might lead to an error in future versions
procon-ip.0 | 2021-04-18 11:23:31.383 | warn | (1588) State "procon-ip.0.analog.4.raw" has no existing object, this might lead to an error in future versions

... ... usw. usw. dürfte ja bekannt sein.

We saw your adapter and if it is ready please request that it is added to the repository. With this it becomes available for all users. Please consult https://github.com/ioBroker/ioBroker.repositories#add-a-new-adapter-to-the-latest-repository and the following sections for more details.
If you need help, contact us in the forum https://forum.iobroker.net/ or in the developer chat https://github.com/iobroker-community-adapters/info .

Thank you for your support.

Think about adding version 1.3.3 to stable repository.

Version: stable=0.0.0 (0 days old) => latest=1.3.3 (30 days old)
Installs: stable=0 (0%), latest=16 (20.51%), total=78
Click to edit

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/ylabonte/ioBroker.procon-ip

• [E152] No common.dataSource found in io-package.json
• [E605] No actual year found in copyright. Please add "Copyright (c) 2021 Yannic Labonte [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2021 Yannic Labonte [email protected]" at the start of LICENSE

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Please do not use setObjectAsync (https://github.com/ylabonte/ioBroker.procon-ip/blob/master/src/main.ts#L257, also https://github.com/ylabonte/ioBroker.procon-ip/blob/master/src/main.ts#L351 ...) because this can lead to custom settings being removed in older js-controller versions. User setObjectNotExistsAsync please
Originally posted by @Apollon77 in ioBroker/ioBroker.repositories#756 (comment)