ta2k/iobroker.weishaupt-wem

ioBroker Adapter for weishaupt WEM Portal

ioBroker.weishaupt-wem

Tests::

weishaupt-wem adapter for ioBroker

Adapter for weishaupt WEM Portal

Custom Befehl

Für ein Custom Befehl benötigst du die URL und den gewünschten Wert. Für die URL einfach die Option im WEM Portal mit Chrome aufrufen und dann rechte Maustate Untersuchen dann unter Elements/Elemente mit STRG+F nach iframe suchen mit dem name="RDWWriteParameter" die URL nach src mit rechts Klick Link kopieren raus kopieren. Für den Werte nach <option suchen und den gewünschten Wert unter value kopieren und als state Wert eintragen. z.B.: https://www.wemportal.com/Web/UControls..., 208557

App Support

Der Adapter liest auch die Daten aus der App aus.

weishaupt-wem.0.20999 "Name via App"

weishaupt-wem.0.20999.1-3.parameters Hier findest du den aktuellen Status und kann via NumericValue oder StringValue geändert werden. Du findest dort auch die Min Max Werte und unter EnumValues findet man die Beschreibung für NumericValue

Changelog

0.0.16

• (ta2k) Improve error and login handling

0.0.15

• (ta2k) add app support

0.0.14

• (ta2k) fix command sends

0.0.13

• (ta2k) update dependencies

0.0.9

• (ta2k) fix for Status label

0.0.5

• (ta2k) fix remote for WWP

0.0.4

• (ta2k) remove spaces in ids

0.0.3

• (ta2k) Fix remote control

0.0.2

• (ta2k) Möglichkeit Parameter zu ändern
• Nummerische Werte als Zahlen in ioBroker geschrieben

0.0.1

• (ta2k) initial release

License

MIT License

Copyright (c) 2019 ta2k [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

iobroker.weishaupt-wem's Issues

Neue Version 0.0.15 bringt Fehlermeldungen im log

Ich habe seit ein paar Tagen die neue Version 0.0.15 installiert und bin begeistert, dass ich nun auch über die App-Parameter Werte in meiner Brennwerttherme verändern kann (z.b. Umschalten des Zeitprogrammes).
Leider treten aber auch regelmäßig Fehler auf, wie im beigefügten screenshot zu sehen ist.
Ich denke, der Fehler 504 müsste auf der Weishaupt-Serverseite gelöst werden, aber der "Cannot read property "textContent" Fehler sieht für mich eher wie ein code fix aus.
Der Fehler tritt unregelmäßig auf. Ich habe das Update intervall auf 5 min eingestellt und oft geht das für eine längere Zeit gut , doch dann tritt der Fehler wieder auf. Hängt vielleicht auch mit dem "504" Fehler zusammen, könnte aber vielleicht abgefangen werden???

Dann noch eine Frage:
Kann ich nach Änderung eines Wertes einen Refresh forcen oder muss ich das ganze Update-intervall abwarten, bis ich den geänderten Wert im ioBroker sehe?

Vielen Dank...

Versions:

• Adapter version: 0.0.15
• JS-Controller version: 4.0.23
• Node version: 14.21.3
• Operating system: Ubuntu 20.04.5
  

Fehler in 0.0.14

Hallo zusammen,
ich habe gerade das Update von 0.0.13 auf 0.0.14 installiert.
Leider wirft es mir jetzt laufend Fehlermeldung und es werden auch nicht mehr alle Datenpunkte ausgelesen.

AxiosError: Request failed with status code 400

{"Status":3000,"Message":"Mindestens ein erforderlicher Parameter fehlt","DetailMessages":[]}

Compatibility check to js-controller 4.0

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!

Compatibility check to js-controller 3.3 and Admin5 React UI

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!

Think about to fix the issues found by adapter checker

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/TA2k/ioBroker.weishaupt-wem

• [E150] No common.connectionType found in io-package.json
• [E152] No common.dataSource found in io-package.json
• [E154] common.dependencies must contain {"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}
• [E605] No actual year found in copyright. Please add "Copyright (c) 2022 ta2k [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2022 ta2k [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

Adapter does not start properly

The Adapter stays red, no Objects are updated, see error log below.
System running on a Pine Rock64 (Armbian stretch)
npm 6.14.4
nodejs v14.18.2
Any hints, or is it just outdated?

host.ioBroker-Rock64 2021-12-06 08:41:50.198 error instance system.adapter.weishaupt-wem.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.ioBroker-Rock64 2021-12-06 08:41:50.197 error Caught by controller[0]: }
host.ioBroker-Rock64 2021-12-06 08:41:50.196 error Caught by controller[0]: code: 'ERR_DLOPEN_FAILED'
host.ioBroker-Rock64 2021-12-06 08:41:50.195 error Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:790:12) {
host.ioBroker-Rock64 2021-12-06 08:41:50.195 error Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:950:32)
host.ioBroker-Rock64 2021-12-06 08:41:50.194 error Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
host.ioBroker-Rock64 2021-12-06 08:41:50.193 error Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:1085:14)
host.ioBroker-Rock64 2021-12-06 08:41:50.193 error Caught by controller[0]: at Object. (/opt/iobroker/node_modules/canvas/lib/bindings.js:3:18)
host.ioBroker-Rock64 2021-12-06 08:41:50.192 error Caught by controller[0]: at require (internal/modules/cjs/helpers.js:93:18)
host.ioBroker-Rock64 2021-12-06 08:41:50.191 error Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:974:19)
host.ioBroker-Rock64 2021-12-06 08:41:50.190 error Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:790:12)
host.ioBroker-Rock64 2021-12-06 08:41:50.189 error Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:950:32)
host.ioBroker-Rock64 2021-12-06 08:41:50.189 error Caught by controller[0]: at Object.Module._extensions..node (internal/modules/cjs/loader.js:1144:18)
host.ioBroker-Rock64 2021-12-06 08:41:50.188 error Caught by controller[0]: the module (for instance, using npm rebuild or npm install).
host.ioBroker-Rock64 2021-12-06 08:41:50.187 error Caught by controller[0]: NODE_MODULE_VERSION 83. Please try re-compiling or re-installing
host.ioBroker-Rock64 2021-12-06 08:41:50.186 error Caught by controller[0]: NODE_MODULE_VERSION 72. This version of Node.js requires
host.ioBroker-Rock64 2021-12-06 08:41:50.185 error Caught by controller[0]: was compiled against a different Node.js version using
host.ioBroker-Rock64 2021-12-06 08:41:50.183 error Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/canvas/build/Release/canvas.node'
host.ioBroker-Rock64 2021-12-06 08:41:50.182 error Caught by controller[0]: ^
host.ioBroker-Rock64 2021-12-06 08:41:50.180 error Caught by controller[0]: return process.dlopen(module, path.toNamespacedPath(filename));
host.ioBroker-Rock64 2021-12-06 08:41:50.179 error Caught by controller[0]: internal/modules/cjs/loader.js:1144

Adapter bleibt nicht Grün (Gelöst)

Hallo Zusammen,
wenn ich den Adapter Starte ruft er kurz die Werte ab und springt dann auf rot.
Installiert im Docker auf einer Synology NAS.

Node.js v14.18.3
NPM 8.3.1

Im Report steht folgende Fehlermeldung.

weishaupt-wem.0 | 2022-01-15 11:58:48.202 | warn | Terminated (UNCAUGHT_EXCEPTION): Without reason -- | -- | -- | --
weishaupt-wem.0 | 2022-01-15 11:58:48.199 | info | terminating
weishaupt-wem.0 | 2022-01-15 11:58:48.192 | info | cleaned everything up...
weishaupt-wem.0 | 2022-01-15 11:58:48.137 | error | The id "Keller XXXXXX." is invalid. Ids are not allowed to end in "."
weishaupt-wem.0 | 2022-01-15 11:58:48.136 | error | Error: The id "Keller XXXXX." is invalid. Ids are not allowed to end in "." at validateId (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:537:23) at WeishauptWem.setObjectNotExists (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3387:17) at Request._callback (/opt/iobroker/node_modules/iobroker.weishaupt-wem/main.js:330:30) at Request.self.callback (/opt/iobroker/node_modules/iobroker.weishaupt-wem/node_modules/request/request.js:185:22) at Request.emit (events.js:400:28) at Request. (/opt/iobroker/node_modules/iobroker.weishaupt-wem/node_modules/request/request.js:1154:10) at Request.emit (events.js:400:28) at Gunzip. (/opt/iobroker/node_modules/iobroker.weishaupt-wem/node_modules/request/request.js:1076:12) at Object.onceWrapper (events.js:519:28) at Gunzip.emit (events.js:400:28)
weishaupt-wem.0 | 2022-01-15 11:58:48.133 | error | unhandled promise rejection: The id "Keller XXXXX." is invalid. Ids are not allowed to end in "."
weishaupt-wem.0 | 2022-01-15 11:58:48.132 | error | Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

Think about to fix the issues found by adapter checker

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/TA2k/ioBroker.weishaupt-wem

• [E145] No news found for actual version 0.0.9
• [E150] No common.connectionType found in io-package.json
• [E152] No common.dataSource found in io-package.json
• [E605] No actual year found in copyright. Please add "Copyright (c) 2021 ta2k [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2021 ta2k [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

Compatibility check and testing for Node.js 14 and 16

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!

Update stable version in repo from 0.0.9 to 0.0.10

Think about update stable version to 0.0.10

Version: stable=0.0.9 (307 days old) => latest=0.0.10 (15 days old)
Installs: stable=139 (67.48%), latest=23 (11.17%), total=206
Click to edit

Update stable version in repo from 0.0.15 to 0.0.16

Think about update stable version to 0.0.16

Version: stable=0.0.15 (71 days old) => latest=0.0.16 (62 days old)
Installs: stable=150 (49.18%), latest=22 (7.21%), total=305
Click to edit

Please add your adapter to ioBroker.discovery

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

Status der Eingänge anzeigen

Hi @TA2k,

vielen Dank für den Adapter.
Es funktioniert alles super.
Was für mich noch hilfreich wäre, ist die Anzeige der Eingänge.
Damit könnte man herausfinden, ob zum Beispiel die EVU Sperre aktiv ist.
Das wäre interessant für meine Auswertungen.
Die Anzeige befindet sich in der Fachmann Ebene unter "Eingänge" (siehe Screenshot)

Besten Dank & viele Grüße
Daniel

l

Keine Steuerung möglich

Hallo

ich habe eine Weishaupt Gastherme, den Adapter habe ich zum laufen bekommen Version 0.0.11 . DIe richtigen Datenpunkte von der Anlage bekomme ich auch unter Objekten rein. Das funktioniert super. Leider kann ich aber die anlage nicht steurn, alles was ich bei remote probiere funktioniert nicht. Auch eine eingabe über den custom befehl bewirkt keine veränderung an der anlage.
Gruss Julian

Additional Info and Error Messages

Is there a possibility that the other tiles can also be queried in the expert view?
A display of the current error messages would also be a great thing.
If your time allows, I would be extremely grateful.

Add Alerts

Is it possible to add alerts?
I want to get warnings and errors to display in iobroker. For example. Last error and when it was.

So i can trigger node red flow to get a message when something happens.

Or is this possible at the moment?

Keep up the great work and thanks!

Request failed with status code 500

Ich habe 2 Anlagen im WEM-Portal und bekomme bei der Abfrage der Daten folgenden Fehler: "AxiosError: Request failed with status code 500" (siehe Bild) und es werden entsprechend keine Objekte erzeugt.

Wenn ich zusätzlich die Datenabfrage aus der App aktiviere, bekomme ich zwar noch die gleiche Fehlermeldung, aber es werden die Objekte für die App-Abfrage erstellt und die werte sollten so auch stimmen glaub ich.

Die 2. Anlage ist erst kürzlich hinzugekommen und ich hatte den Adapter in einer älteren Version die ganze Zeit problemlos am laufen. Nach der Umstellung auf das neueste Docker-Image von iobroker und die neueste Adapter Version bekomme ich den Fehler.

Versions:
Adapter version: 0.0.16 (aktuell von github)
Node version: v18.16.0
Plattform: docker

Anbindung Android API

Hi @TA2k,

es gibt wohl auch die Möglichkeit die Android API zu nutzen.
Das würde den Adapter umfangreicher und flexibler und gleichzeitig einfacher in der Anwendung machen.
Die Beschreibung dazu habe ich hier gefunden. Lässt sich so recht gut in Postman testen.
erikkastelec/hass-WEM-Portal#9

Hättest du Interesse den Adapter umzustellen? Alternativ überlege ich, ob ich den Adapter neu schreiben soll auf Basis der Android API.

Ein kurzer Austausch dazu wäre cool.

Viele Grüße
Daniel