Meine Sonnensensoren geben einen Fehler aus, ich kann aber keine Änderungen vornehmen. Der

log:

• Adapter version: 0.0.10
  Software alle aktuell !

After updating the Adapter is HP now Reporting Errors an fill the Log up.
Do we have a chance to suppress this? Or can we have a DP to control the responsible devices?
Maybe that's the case and I have not seen it.

homepilot20.0 | 2019-10-02 12:48:11.597 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:47:59.534 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:47:47.553 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:47:35.532 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:47:23.622 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:47:11.532 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:46:59.493 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:46:47.517 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:46:35.477 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:46:23.473 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:46:11.403 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:45:59.419 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:45:47.423 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:45:35.418 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:45:23.383 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:45:11.411 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:44:59.377 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:44:47.387 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:44:35.408 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:44:23.365 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:44:11.344 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:43:59.372 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:43:47.417 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:43:35.302 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:43:23.316 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:43:11.382 | warn | Homepilot Device 1010006 reports an error
homepilot20.0 | 2019-10-02 12:42:59.256 | warn | Homepilot Device 1010006 reports an error

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '...'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.

Versions:

• Adapter version:
• JS-Controller version:
• Node version:
• Operating system:

Additional context
Add any other context about the problem here.

Hallo leider habe ich bei deviceNumber "35000662" den Datenpunkt Slatposition nicht. Habe ich irgendwas übersehen?

Es wäre hilfreich, wenn man entweder einen Auslöser der Scene nicht nur als generellen Auslöser hätte, sondern auch mit der Option zB. Auslöser Sonne, Wind etc. und der Adapter prüft dann, ob alle Geräte die Automatik Sonne, Wind etc. auf true gesetzt sind. Geräte mit true werden ausgelöst, die mit false nicht.

Dies wäre eine Erweiterung der homepilot20.0.Scene.XXXX.execute Button.

Wäre das möglich?

I have many warnings in my log from the homepilot adapter. It really spams my log. Otherwise the adapter seems to work as it should.
I don't know, if there is any connection, but i noticed it not before i updated to admin 5 surface.
Homepilot-Adapter Version 0.0.29
Screenshot of my log:

also ich hab für die Devices, die ich habe, alle Auto-Funktionen eingabaut.
Sollten welche fehlen, bitte neue Issues aufmachen.
Danke

Originally posted by @homecineplexx in #21 (comment)

Hi Chris,

also ich hab Auf und Unterputzwickler. Die Aufputz sind mit Auto/Manu Attributes vorhanden, super Danke für die Erweiterung!
Der 1800 Unterputz (homepilot20.0.Actuator.1010000-16234511) nicht. Für mich nicht zeitkritisch, aber bei den Beschattungsgeräten ist AUTO MANU Umschaltung meines Erachtens interessant. Ich kann deinen Programmieraufwand überhaupt nicht einschätzen, aber falls es dir hilft: Ich denke der DP "AUTO_MODE_CFG" wäre für die meisten schon ausreichend, da ich niemanden kenne, der gezielt einzelne Automatiken schaltet, wohl aber Situationen wo ein Nutzer mal ein Gerät KOMPLETT aus der Automatik nimmt. Also falls das deinen Aufwand der Integration mindert. Für mich jetzt auch nicht zeitkritisch, kannst du beim nächsten Update mal mit integrieren.

Rollotron Comfort 1800: homepilot20.0.Actuator.1010000-16234511 hat bei mir keinen "Attributes"-Ordner
Rollotron Standard 2510 (1400): homepilot20.0.Actuator.1010035-14234511 hat die Attributes

Gruß Sven

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!

Hallo,
ist es möglich den Batteriestatus des z-wave Heizkörperstellantrieb 8433 im iobroker anzuzeigen?
bei dem neueren Modell Heizkörperstellantrieb 9433 wird dieser korrekt im iobroker angezeigt.

Grüße
René

Das Log ist voll von folgenden Meldungen, lässt sich das unterbinden?

homepilot20.0 | 2020-11-19 19:50:50.254 | warn | (1736) Scenes -> Cannot connect to Homepilot: {"statusCode":501,"body":"Not implemented for Bridge!","headers":{"server":"nginx/1.17.1","date":"Thu, 19 Nov 2020 18:50:50 GMT","content-type":"text/htm

Originally posted by @deus82ex in #22 (comment)

Hello,
I am at version 0.0.3
I can not find the scenes in the object's. Do I have to do something else?
thx

Hi,

i'm completely new to ioBroker and i would like to install your adapter to use my Rademacher homepilot. Is there a tutorial how to install it manually?

Thanks for your work!

latest Version 0.0.1
Node.js: v8.16.1
NPM: 6.4.1

Fehler im Log:

(8043) State value to set for "homepilot20.0.Actuator.2-14234511.did" has to be type "string" but received type "number"
(8043) State value to set for "homepilot20.0.Actuator.2-14234511.deviceGroup" has to be type "string" but received type "number"
(8043) State value to set for "homepilot20.0.Actuator.1-14234511.deviceGroup" has to be type "string" but received type "number"
(8043) State value to set for "homepilot20.0.Actuator.2-14234511.did" has to be type "string" but received type "number"
(8043) State value to set for "homepilot20.0.Actuator.2-14234511.deviceGroup" has to be type "string" but received type "number"
(8043) State value to set for "homepilot20.0.Actuator.1-14234511.deviceGroup" has to be type "string" but received type "number"
(8043) State value to set for "homepilot20.0.Actuator.2-14234511.did" has to be type "string" but received type "number"
(8043) State value to set for "homepilot20.0.Actuator.2-14234511.deviceGroup" has to be type "string" but received type "number"
(8043) State value to set for "homepilot20.0.Actuator.1-14234511.deviceGroup" has to be type "string" but received type "number"
(8043) State value to set for "homepilot20.0.Actuator.2-14234511.did" has to be type "string" but received type "number"

Hi, I get in the log that several data points are of type "boolean" but receive "string" data.

Describe the bug
Debug info in log

Screenshots & Logfiles

`

Versions:

• Adapter version: <v0.0.18>
• JS-Controller version:
  
• Node version: <v12.22.6>
• Operating system:

Seit dem Update auf Admin Version 3.6.10 habe ich andauernd diese Fehlemeldungen.

was kann ich tun?

Node.js: v14.17.4 (Empfohlene Version v12.22.4)
NPM: 6.14.14

Unendliche Fehlermeldungen (auch wenn nur Info), anscheinend wird ein falscher Wertetyp angelegt.
Ist nur ein Auszug ;-).

DuoFerm 9471.1 is missing in the supportet devices

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/homecineplexx/ioBroker.homepilot20

• [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.homepilot20"
• [E300] Not found on travis. Please setup travis
• [E801] No repository about text found. Please go to "https://github.com/homecineplexx/ioBroker.homepilot20", press the first "Edit" button you will find on the page and add the description.
• [E802] No topics found in the repository. Please go to "https://github.com/homecineplexx/ioBroker.homepilot20" and press "Manage topics"

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

• [W400] Cannot find "homepilot20" 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

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/homecineplexx/ioBroker.homepilot20

• [E301] Tests on Travis-ci.org are broken. Please fix.

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

• [W400] Cannot find "homepilot20" 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 Chris,

thank you for the awesome ioBroker adapter, works like a charm. I've found that the Philips Hue Whilte Lamp LWB010 is not recognized by the adapter. The deviceNumber is 99999981. Maybe you like to implement this type, too :-)

Best,
Andreas

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/homecineplexx/ioBroker.homepilot20

• [E118] Versions in package.json and in io-package.json are different
• [E301] Tests on Travis-ci.org are broken. Please fix.
• [E605] No actual year found in copyright. Please add "Copyright (c) 2020 Christian Koller [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2020 Christian Koller [email protected]" at the start of LICENSE

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

• [W400] Cannot find "homepilot20" 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

Background: Bought a "Rademacher Start2Smart Kit" including

• a Bridge and
• RolloTron Basis DuoFern 1200-UW.

Setting everything up and controlling it through the bridge's GUI works fine.

This adapter seems to connect fine to the bridge but continously crashes and restarts.

I've attached an excerp from the log. Let me know if you need further information.

`

Hi, wenn ich ein Gerät in der Bridge hinzufüge wird dies korrekt im ioBroker angelgt. Dabei wird der Name des Gerätes in die Beschreibung des Objektes mit aufgenommen. Ändere ich die Namen des Gerätes in der Bridge wird der Name als Objektname nicht geändert.

Es wäre in meinen Augen sinnvoll den Namen des Gerätes nicht mit in den Objektnamen aufzunehmen. Ein Objekt 'Name' mit dem aktuellen Namen exisitiert ja.

I'm using homepilot20 0.0.31 and have connected different actuators to my homepilot. For the Troll Basis DuoFern 36500172 I don't see the attributes like AUTO_MODE_CFG, DAWN_AUTO_CFG,...
Could you please add? Let me know if you need more details.

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.

Describe the bug
If I tell Siri ("Hey Siri, stop window bling ") to stop a moving window blind it doesn't stop, but closing it.

Versions:

• Adapter version: 0.0.10
• JS-Controller version: 3.1.6
• Node version: 10.21.0
• Operating system: Linux 4.19.118-v7+ #1311 SMP Mon Apr 27 14:21:24 BST 2020 armv7l GNU/Linux on RaspberryPi 3

Is it planned to integrate the new Sun/Win Sensor (9499) into the adapter?
https://www.rademacher.de/shop/rollladen-sonnenschutz/sensoren/duofern-sonnen-windsensor-9499

I received it today and registered in the homepilot and just noticed that it is not yet supported by the adapter.

I would be very happy if this can be realized and of course support if I can provide data.

http://homepilot.local/v4/devices?devtype=Sensor

{"response":"get_meters","meters":[{"description":"Ihre Gerätebeschreibung",
"deviceGroup":3,"did":1010045,"automations":[30,50],"readings":{"sun_detected":false,"wind_detected":false},"timestamp":1652730334,"iconSetInverted":0,"iconSet":{"k":"iconset19"},"name":"DuoFern Sonne-/Windsensor","statusValid":true,"deviceNumber":"32004464","uid":"a901c2_1","visible":true},]}

When trying to intigrate the lamella position by using the signal slatposition it seems to read the right value from homepilot as it matches the actual position. But when i try to change the value e.g. via slider widget nothing happens to the lamella as it stays in his original position.
I hope you can fix this as i would really like to use this adapter
Here is a picture of one of my doufern basic.
Could it be that it has to do with slatposition being a text and not a levelblind?
https://ibb.co/C8twLSX

Hello,
I'm using the last version of the homepilot20 - 0.9.
All my components that are registred on the Hompilot are displayd. That's ok.
But I have the "Umweltsensor (9475)" and three "Tür- und Fensterkontakt" (9431) and they are displayd but they shows no reaction.The attributes do not change.
I have the impression, that the showing attributes are dummy values. Is it so? Or it's a little bug?

Regards Siegmunder

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.

Hi and thanks a lot for writing the adapter. I'm completly new to iobroker and am wondering how to add a device. I have a running homepilot instance and under objects I see the "dummy" devices. But how to i add one of my devices (e.g. an actuator?)

Thanks you!

Describe the bug
I use the Homepilot Bridge version 5.5.10 on my iobroker Node.js v14.19.1. I installed the homepilot 20 v0.0.35.
After the start of the instance I can control my rollershutter. After 1 minute the instance connection failed. And 2 minutes later I get the Host Message frequently crashing adapter instances of homematic 20, when I close It 2 minutes later it comes again.

Expected behavior
I hope that the Homepilot run smooth and I can reliable control my roller shutter.

Screenshots & Logfiles
Node.jsv14.19.1
2022-03-24 14:11:31.360 - error: homepilot20.0 (12624) Cannot read property 'value' of undefined
2022-03-24 14:11:31.365 - info: homepilot20.0 (12624) terminating homepilot20 adapter
2022-03-24 14:11:31.367 - error: homepilot20.0 (12624) Adapter will be stopped
2022-03-24 14:11:31.367 - info: homepilot20.0 (12624) terminating
2022-03-24 14:11:31.368 - warn: homepilot20.0 (12624) Terminated (UNCAUGHT_EXCEPTION): Without reason
2022-03-24 14:11:31.994 - error: host.DESKTOP-ELKKNRQ(teest) instance system.adapter.homepilot20.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2022-03-24 14:11:31.994 - info: host.DESKTOP-ELKKNRQ(teest) Restart adapter system.adapter.homepilot20.0 because enabled
2022-03-24 14:12:02.056 - info: host.DESKTOP-ELKKNRQ(teest) instance system.adapter.homepilot20.0 started with pid 9196
2022-03-24 14:12:05.893 - info: homepilot20.0 (9196) starting. Version 0.0.35 (non-npm: homecineplexx/ioBroker.homepilot20#8bc050486addf2aaa6bffa74358d4b4a5aebfc5b) in C:/Program Files/iobroker/teest/node_modules/iobroker.homepilot20, node: v14.19.1, js-controller: 4.0.21
2022-03-24 14:12:10.967 - warn: homepilot20.0 (9196) Scenes -> Cannot connect to Homepilot: {"statusCode":501,"body":"Not implemented for Bridge!","headers":{"server":"nginx/1.20.1","date":"Thu, 24 Mar 2022 13:12:11 GMT","content-type":"text/html;charset=utf-8","transfer-encoding":"chunked","connection":"close"},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.84","port":80,"hostname":"192.168.178.84","hash":null,"search":null,"query":null,"pathname":"/v4/scenes","path":"/v4/scenes","href":"http://192.168.178.84/v4/scenes"},"method":"GET","headers":{"0":{},"1":{"Content-Type":"application/json"}}}}
2022-03-24 14:12:15.968 - warn: homepilot20.0 (9196) Scenes -> Cannot connect to Homepilot: {"statusCode":501,"body":"Not implemented for Bridge!","headers":{"server":"nginx/1.20.1","date":"Thu, 24 Mar 2022 13:12:16 GMT","content-type":"text/html;charset=utf-8","transfer-encoding":"chunked","connection":"close"},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.84","port":80,"hostname":"192.168.178.84","hash":null,"search":null,"query":null,"pathname":"/v4/scenes","path":"/v4/scenes","href":"http://192.168.178.84/v4/scenes"},"method":"GET","headers":{"0":{},"1":{"Content-Type":"application/json"}}}}
2022-03-24 14:12:18.362 - error: homepilot20.0 (9196) uncaught exception: Cannot read property 'value' of undefined
2022-03-24 14:12:18.364 - error: homepilot20.0 (9196) TypeError: Cannot read property 'value' of undefined

Hi,

is it possible to use the adapter with the bridge?

https://www.rademacher.de/shop/rollladen-sonnenschutz/fernbedienung/bridge

Regards
Mario

sorry close war ein Fehler deshalb neuer Issue

• | starting. Version 0.0.1 in /opt/iobroker/node_modules/iobroker.homepilot20, node: v8.16.1
  -- | --

latest Version 0.0.1
Node.js: v8.16.1
NPM: 6.4.1

Im Log erscheinen seit einiger Zeit folgende Einträge:

Sie erscheinen sehr häufig und unter Actuator kann ich weder Nummer xxx83 noch xxx80 finden.

Hat das evtl mit dem Rademacher Update für HUE zu tun ?

Ich habe in iobroker den homepilot 1.1.6 Adapter installiert und die IP meines Homepilot hinterlegt.
Im Log bekomme ich diese Meldung: Cannot connect to Homepilot: null
Auch beim Versuch ohne IP hatte ich keinen Erfolg.
In den Objekten ist leider auch nichts zu sehen.
Was stimmt da nicht?

Hi Chris,
Was ich letztens mal für IOBroker Integration meine Rollladengeräte gesucht habe: Den Datenpunkt für Auto/Manu Umschaltung. Irgendwie finde ich den nicht. Im HP und der App kann ich den per Switch ändern und das auch schon seit langer Zeit. Übersehe ich in den Datenpunkten des Adapters etwas? Die Geräte ließen sich so dann auch mit anderen Fenster/Türkontakten über IOBroker koppeln. Fenster Auf, Automatik aus. Nix Kritisches aber vielleicht eine sinnvolle Erweiterung, falls ich die nicht übersehen habe! 🙈 LG Sven

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!

Hi,

danke für den Adapter, endlich die letzten Rollläden integriert.

Liefert die REST-API die Möglichkeit abzufragen, ob ein Rollladen gerade fährt?
Ein solcher Datenpunkt wäre sehr praktisch, wenn der Rollladen über eine Taste (bspw. Homematic) hochfahren und stoppen soll: wenn fährt = stop, sonst = hoch.
Wäre soetwas machbar?

Vielen Dank im Voraus,
ke

verwende über Homepilot (5.5.10) 2x Rademacher RolloTron Basis DuoFern 1200-UW (v1.3-2) und 2x Rademacher RolloTron Standard DuoFern 2510-UW (v1.3-2), funktioniert gut

Hallo,
war der Adapter nicht schon mal im Repo enthalten?
Im jetzigen Zustand wird nicht auf Updates hingewiesen ist das so gewollt?

Hello,
wasn't the adapter already included in the repo?
In the current state, updates are not indicated. Is that what you want?

I could not find any of the surface-mounted RolloTron belt winders in the documentation for this adapter.
Are the following models supported?

• RolloTron Schwenkwickler Standard DuoFern Minigurt 2550-UW (Artikelnummer: 14153011)
• RolloTron Schwenkwickler Standard DuoFern 2510-UW (Artikelnummer: 14233011)

These two just as an example.
There are other surface-mounted belt winders that are not listed.

Hi Chris,
weil du es so wolltest, hier das Issue zu meinem "Problemchen" mit den zwei Instanzen.

Zur Beschreibung: Ich betreibe mit rund 600 km Distanz über eine dauerhafte VPN Verbindung zwischen zwei Fritz!Boxen zwei Homepilots. Nennen wir die Instanzen HP20.0 und HPB20.1, um die noch kommenden Screenshots ;) zu nutzen. Für beide Geräte habe ich eine einzelne Instanz in iObroker aufgesetzt, einerseits um die Geräte sauber zu trennen für Visu als auch um hier an meinem HP mal das ein oder andere testen zu können, ohne den anderen in seiner Produktivität zu stören deren dessen User zu verwirren! :)

Soweit funktioniert das, allerdings gibt es ein, vermutlich rein optisches, Problem. In der 2. Instanz tauchen erste die Devices des 2. Gerätes auf, danach dann aber zusätlich nochmal die Devices der ersten Instanz. Hier mal Screens dazu:

Instanz 1: HP20.0

Instanz 2:HP20.1

Spannend in ROT der Wechsel der HPs/Instanzen anhand der Device IDs zu erkennen. Ab dem Rollotron 1800 sind wir auf zurück auf Instanz HP20.0, in BLAU auch die ganzen 1400er Rollotrons, die DEFINITIV am HP20.0 und nicht HP20.1 angebunden sind! Strange finde ich ferner, das die Gewerke und Räume in HP20.0 dargestellt werden, in HP20.1 dann aber nicht....

Ich hab noch etwas getestet:
HP20.0

HP20.1

Die UID ist identisch, damit ist klar, es muss ein und das gleiche Gerät sein. Der aktuelle STATE ist TRUE in Instanz HP20.1 wurde FALSE angezeigt. Das manuelle Ändern des DP in HP20.1 blieb ohne Effekt, da läuft scheinbar was "ins Leere".
Es scheint aber auch sich keine einfach "Investierung" dahinter zu verstecken. Ich hab es im 1800 mal geprüft. Werte in HP20.0 sind (Rollo 80% / inverted 20%) und in HP20.1 steht das Device mit 0%/100%....

Als wenn da eventuell beim Erstellen der Instanz HP20.1 ein Abbild der HP20.0 gemacht und in HP20.1 importiert wurde. Wüßte aber nicht wo das gegangen sein soll und warum ich das aktiviert hätte.

Einzige Erklärung könnte sein, dass ich die HP20.1 Instanz zu Testzwecken zuerst mit der IP meines lokalen OPs gefüttert habe und später dann erst die "entfernte" aus dem angedockten VPN Netz?!?! Also quasi daraus die Frage: Wenn ich die IP eines neuen HPs in der Instanz ändere, bleiben dann in den Objects die Datenpunkte des "alten" HPs erhalten und die des neuen werden nur hinzugefügt? Oder löscht/überschreibt der Adapter beim Ändern der IP die gesamten Datenpunkte mit neuen Datenpunkten.... Kann mich nicht entsinnen es so getestet zu haben, aber es wäre u.U. eine plausible Erklärung?

Ich hoffe du kannst mir halbwegs folgen... Das letzte könnte ich am kommenden WE eventuell mal testen, dann lag es vielleicht daran. Dann geb ich dir dazu nochmals ne Info.

Generell ist es nur ein kosmetischer Bug, Funktion ist gegeben! ;)

Viele Grüße
Sven

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!

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.

Describe the bug
Beim Start und jedem Sync des Adapters wird folgendes ins Log File geschrieben (Auszug):
2021-08-11 23:35:08.624 - info: homepilot20.0 (17653) State value to set for "homepilot20.0.Actuator.1010016-35000662.deviceGroup" has to be type "string" but received type "number"
2021-08-11 23:35:08.625 - info: homepilot20.0 (17653) State value to set for "homepilot20.0.Actuator.1010016-35000662.did" has to be type "string" but received type "number"
2021-08-11 23:35:09.352 - info: homepilot20.0 (17653) State value to set for "homepilot20.0.Scene.5.active" has to be type "boolean" but received type "number"
2021-08-11 23:35:09.352 - info: homepilot20.0 (17653) State value to set for "homepilot20.0.Scene.5.isExecutable" has to be type "boolean" but received type "number"
Diese Information wird für jeden Aktor und jede Szene ausgegeben und überflutet damit das Logfile.

Versions:

• Adapter version: v0.0.25
• JS-Controller version: 3.3.15
• Node version: v12.22.4
• Operating system: Raspbian GNU/Linux 10 (buster)
• IOBroker Admin: 5.1.23
• Homepilot Version: 5.3.24 (Rademacher Homepilot 2)
• DuoFern Version: 0.10

Additional context
An sich funktioniert alles, was ich bisher getestet habe wunderbar. Rollläden lassen sich steuern und der Umweltsensor lässt sich auslesen. Danke dafür, das ist echt eine super Sache. Nur das hier gemeldete Thema mit dem Logfile stört irgendwie.