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!

• WARNING: No news entry for current version exists in io-package.json, no rollback in Admin possible!

• WARNING: titleLang is not existing in io-package.json. Please add

• Bitte admin/index.html entfernen wenn Admin2 support nicht vorhanden ist

• io-package bitte "common.restartAdapters" raus wenn kein widget drin ist

• io-package bitte "common.license " dazu mit der Lizenzangabe

• io-package in native bitte alle Parameter mit den Default-Werten rein nehmen

• Im Code gehen alle Posts an eine statische IP?? Soll das so sein?

• Bitte beim anlegen von Objekten nicht setObject sondern setObjectNotExists nutzen ODER statische Objekte in der io-package unter "instanceObjects" anlegen

• Objekte Role "EZR" ist keine erlaubte ioBroker Rollenangabe. Siehe hier: https://github.com/ioBroker/ioBroker/blob/master/doc/STATE_ROLES.md Bitte ROllen der Datenpunkte korrekt setzen

Danke

Hello,

i really love that alpha 2 adapter, but my third alpha 2 instance doesn´t show any values of the connected heat areas. The rest is filled with information (like Device or Programs) and the information there is right. But heat areas only deliver null values.

This is the info from one of the base units:

HW 01
SW 02.17
LAN 02.14
WEB 02.10

Guten Tag,
ich bin auf folgenden reproduzierbaren Fehler gestoßen, der im Endeffekt dazu führt, dass die Steuerung der Fußbodenheizung (EZR-Manager) nicht mehr erreichbar ist:

2021-11-12 06:46:27.422 - info: javascript.0 (18879) script.js.common.Heizung.HeizungAnHomeOffice: Auf Grund HomeOffice wurde im Büro, Flur & Wohnzimmer das Wochenend-Programm (P0) eingestellt.
2021-11-12 06:46:27.659 - info: whatsapp-cmb.0 (18245) Send Auf Grund HomeOffice wurde im Büro, Flur & Wohnzimmer das Wochenend-Programm (P0) eingestellt. to +49175123456
2021-11-12 06:46:33.058 - info: alpha2.0 (18145) Fehler XML-Parsen: Error: Invalid character in tag name
Line: 343
Column: 8
Char:
2021-11-12 06:47:19.119 - info: alpha2.0 (18145) Fehler beim Herunterladen: Error: connect EHOSTUNREACH 192.168.10.191:80
2021-11-12 06:47:31.276 - info: alpha2.0 (18145) Fehler beim Herunterladen: Error: connect EHOSTUNREACH 192.168.10.191:80
2021-11-12 06:48:03.596 - info: alpha2.0 (18145) Fehler beim Herunterladen: Error: connect EHOSTUNREACH 192.168.10.191:80
2021-11-12 06:48:33.596 - info: alpha2.0 (18145) Fehler beim Herunterladen: Error: connect EHOSTUNREACH 192.168.10.191:80
2021-11-12 06:49:03.606 - info: alpha2.0 (18145) Fehler beim Herunterladen: Error: connect EHOSTUNREACH 192.168.10.191:80
2021-11-12 06:49:33.596 - info: alpha2.0 (18145) Fehler beim Herunterladen: Error: connect EHOSTUNREACH 192.168.10.191:80

Das Problem tritt immer dann auf, wenn ich versuche die drei Objekte alpha2.0.HEATAREA.3.PROGRAM_WEEK, alpha2.0.HEATAREA.4.PROGRAM_WEEK und alpha2.0.HEATAREA.5.PROGRAM_WEEK gleichzeitig mittels Blockly zu steuern.
Ich habe mich bei meinen Tests zwar bisher nur auf die Objekte ...PROGRAM_WEEK beschränkt, bin mir aber nicht sicher inwiefern es sich hier um ein generelles Problem handelt. Ist die Steuerung mehrerer Objekte gleichzeitig mittels Blockly möglich? Bzw. wird eine XML-Datei, die mehrere Änderungen beinhaltet korrekt erstellt?

Das Problem kann umgangen werden, indem die Steuerung der Objekte im Blockly nicht gleichzeitig erfolgt, sondern die Verzögerung aktiviert wird. Auf Verdacht habe ich die Verzögerung größer als die "Polling Time" (Instanzeinstellungen 30 Sek.) gewählt, da meinem Verständnis nach dann eine XML erzeugt wird, in der zunächst ein Objekt gesteuert wird. Diese XML wird dann verarbeitet (gepollt) und erst im Anschluss wird durch das Blockly das nächste Objekt gesteuert und eine neue XML erzeugt, die wiederum beim nächsten Polling-Intervall verarbeitet wird. Auf diese Weise scheinen die XML-Dateien fehlerfrei verarbeitet zu werden und zu funktionieren.
Zur Info hier mein Blockly mit aktivierter Verzögerung:

Mit dieser Vorgehensweiße kommt es zu keinen Fehlermeldungen und v.a. bleibt die Steuerung (EZR-Manager) weiterhin erreichbar und stürzt nicht ab.

Ich vermute, man müsste sich die XML-Datei anschauen, die geschrieben wird, wenn mehrere Objekte gleichzeitig geändert werden. Falls ich diesbezüglich Input liefern könnte, bitte ich um Erläuterung der Vorgehensweiße (wie kann ich sehen, was an die Steuereinheit geschickt wird?) und bin natürlich gerne bereit mich weiter einzubringen.

Würde mich freuen, wenn sich jemand mit mehr Hintergrundwissen der Sache annimmt, vielen Dank vorab!

Infos zu meinem System:
Raspberry Pi 4
NODE.JS V12.22.1
NPM 6.14.12
Adapter Version 1.0.3

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!

Hello,

when I set T_Target in Iobroker, the temperature will be overided by the next Update.

For Example:

When the target temperature is 21° and I override it by Iobroker with 25°, the Adapter will override it again with 21° by next actualisation.

Like here: https://github.com/foxriver76/ioBroker.denon/blob/master/io-package.json#L128

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/Eisbaeeer/ioBroker.alpha2

• [E140] width and height of logo are not equal
• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.alpha2"
• [E802] No topics found in the repository. Please go to "https://github.com/Eisbaeeer/ioBroker.alpha2" and press "Manage topics"
• [E605] No actual year found in copyright. Please add "Copyright (c) 2019 Eisbaeeer [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2019 Eisbaeeer [email protected]" at the start of LICENSE

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

• [W113] Adapter should support compact mode

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

Hallo,
wollte mal nachfragen, ob es möglich wäre, noch den Status der Heizungspumpe (Devices.Device.PUMP_OUTPUT.PUMP_ISACTIVE) abzufragen? Würde mir extrem das Leben erleichtern.
Vielen Dank im Voraus!

After adapter configuration, the values appears for the device settings, but heatareas are leaving blank. I can manually set the value for T_HEAT_DAY and the the value is correcly written to the EZ-Manager.

Thanks for this adapter!!!

Greez, Markus

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/Eisbaeeer/ioBroker.alpha2

• [E106] Title should not have word "adapter" in the name. It is clear, that this is adapter. Now: {"en":"Möhlenhoff Alpha2 heat-control adapter","de":"Möhlenhoff Alpha2 Fußbodenheizungsregler Adapter"}
• [E106] Title should not have word "adapter" in the name. It is clear, that this is adapter. Now: {"en":"Möhlenhoff Alpha2 heat-control adapter","de":"Möhlenhoff Alpha2 Fußbodenheizungsregler Adapter"}
• [E504] found setInterval in "main.js, but no clearInterval detected

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

• [W505] setTimeout found in "main.js", but no clearTimeout detected
• [W801] .npmignore not found

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

I need 3 instances of Alpha2 adapter, because of 3 different EZRs i want to control. In 1st and 2nd instance everything is alright, but in 3rd instance i don´t get any values in the heatarea objects. Maybe a hardcoded indexing problem?

Thanks for looking into it, because i really appreciate the effort you already put into the adapter eisbaeeer.

I am an automatic service from ioBroker that searches adapters and makes suggestions.

I noticed that your adapter is not integrated in the ioBroker.discovery. Using the Discovery adapter, ioBroker can automatically find devices or suggest services to the user for installation. If possible I would live to see your adapter added there.

Some adapters have already been added and you can use them as blueprints. See: https://github.com/ioBroker/ioBroker.discovery You need to fork this project and then create a PR for your adapter to be added.

Basically the plugins can do HTTP calls, UDP discovery, MDNS, UPNP and will iterate over all devices found by IP scan and check local serial ports. If you want you can also add new discovery methods but please try to do that with at least dependencies as possible.

Then create one file under lib/adapters for your adapter to implement the detection and proposal of an instance to the user.

On questions, the other developers will support in the forum or via GitHub issues too.

If no detection is possible, simply close this issue and I won't bother you again. ;-)

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

I frequently get the following errors, though the adapter is working as expected. You may have a look....
`
alpha2.0 | 2018-09-09 13:05:49.937 | info | Char: >
alpha2.0 | 2018-09-09 13:05:49.937 | info | Column: 11
alpha2.0 | 2018-09-09 13:05:49.937 | info | Line: 397
alpha2.0 | 2018-09-09 13:05:49.937 | info | Fehler XML-Parsen: Error: Unexpected close tag
alpha2.0 | 2018-09-09 13:03:49.829 | info | Char: >
alpha2.0 | 2018-09-09 13:03:49.829 | info | Column: 43
alpha2.0 | 2018-09-09 13:03:49.829 | info | Line: 107
alpha2.0 | 2018-09-09 13:03:49.829 | info | Fehler XML-Parsen: Error: Unexpected close tag
alpha2.0 | 2018-09-09 13:03:19.831 | info | Char: >
alpha2.0 | 2018-09-09 13:03:19.831 | info | Column: 68
alpha2.0 | 2018-09-09 13:03:19.831 | info | Line: 50
alpha2.0 | 2018-09-09 13:03:19.831 | info | Fehler XML-Parsen: Error: Unexpected close tag
alpha2.0 | 2018-09-09 12:53:49.683 | info | Char: >
alpha2.0 | 2018-09-09 12:53:49.683 | info | Column: 51
alpha2.0 | 2018-09-09 12:53:49.683 | info | Line: 249
alpha2.0 | 2018-09-09 12:53:49.683 | info | Fehler XML-Parsen: Error: Unexpected close tag
alpha2.0 | 2018-09-09 12:06:18.885 | info | Char: >
alpha2.0 | 2018-09-09 12:06:18.885 | info | Column: 68
alpha2.0 | 2018-09-09 12:06:18.885 | info | Line: 50
alpha2.0 | 2018-09-09 12:06:18.885 | info | Fehler XML-Parsen: Error: Unexpected close tag

`
Greetings,
Gregor

You can find a sutable example here: https://github.com/ioBroker/ioBroker.discovery/blob/master/lib/adapters/homepilot.js#L9

Just get http://'+ip+'/data/static.xml and detect some alpha2 specific data.

The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466

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/Eisbaeeer/ioBroker.alpha2

• [E106] Title should not have word "adapter" in the name. It is clear, that this is adapter. Now: {"en":"Möhlenhoff Alpha2 heat-control adapter","de":"Möhlenhoff Alpha2 Fußbodenheizungsregler Adapter"}
• [E106] Title should not have word "adapter" in the name. It is clear, that this is adapter. Now: {"en":"Möhlenhoff Alpha2 heat-control adapter","de":"Möhlenhoff Alpha2 Fußbodenheizungsregler Adapter"}
• [E504] found setInterval in "main.js, but no clearInterval detected

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

• [W505] setTimeout found in "main.js", but no clearTimeout detected
• [W801] .npmignore not found

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

Hallo Eisbaeeer,

ich hab das Problem das mir ioBroker ständig das meldet:

`

`

Kannst du damit was anfangen?
Das kam nach einem Update von ioBroker.

MfG

AcidSubway

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!

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.