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/unltdnetworx/ioBroker.stiebel-isg

• [E503] "iob_npm.done" found in repo! Please add it to .gitignore
• [E818] file iob_npm.done found in repository, but not found in .npmignore
• [E914] file iob_npm.done found in repository, but not found in .gitignore

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

If I write the value of "LÜFTUNGSSTUFE (Tag)", sometimes the old values overwrite my value after some seconds. Could it be, that the pull request overwrite all set Data before the new Values send to ISG?

Im Log habe ich regelmäßig Warnungen vom Adapter aufgrund von Werten außerhalb des gültigen Bereichs.
Ich besitze eine LWZ504. Die Werte sollten eigentlich alle korrekt eingestellt und gültig sein. Die Werte wurden nicht über den Adapter gesetzt, sondern direkt an der Heizung oder per ISG Weboberfläche.

Hallo,

ich nutze den ISG-Adapter schon eine Weile. Zusätzlich verwende ich noch die MODBUS-Schnittstelle.

Beide Adapter funktioniere einwandfrei und über die MODBUS-Schnittstelle kann ich noch zusätzlich über die Input-Register Einstellungen der Anlage verändern.

Bei beiden Adaptern gibt es allerdings einen kleinen Wermutstropfen und zwar, dass ein paar wichtige und interessante Werte nicht von diesen geliefert werden.

Bei dem ISG-Adapter Handel es sich um folgende Daten aus der Seite: http://[IP-Adresse]/#page

• ISG-Software-Version

• Systemstatus

• Portalstatus

• Letzter Kontakt

• Portalschlüssen vorhanden/nicht vorhanden

• Betriebszustand

• Betriebszustand seit dd.mm.yyyy hh:mm

• SG Ready

Wenn diese Werte noch geliefert werden könnten, wäre der Adapter perfekt.

Gruß Stefan

Hallo Michael
Ich habe zwei Themen:

1. Haben die Objekte im Zweig "Einstellungen" bewusst keine sprechenden Namen, d.H. stiebel-isg.0.Einstellungen.HEIZEN.ELEKTRISCHE NACHERWAERMUNG.val41 anstelle ... NACHERWAERMUNG.BIVALENZTEMPERATUR_HZG
   oder ist das Folgefehler aus Problem 2?

2. Das eigentliche Problem:
   Nach dem der Adapter klaglos seinen Dienst verrichtete, gibt es nach dem Update auf 1.5.2 nur Fehler im Log.
   Kann ich etwas Unternehmen um das Problem einzugrenzen?
   Auszug ioBroker Log:
   stiebel-isg.0 | 2020-08-10 10:36:00.844 | info | (19357) Terminated (NO_ERROR): Without reason -- | -- | -- | -- stiebel-isg.0 | 2020-08-10 10:36:00.843 | info | (19357) terminating stiebel-isg.0 | 2020-08-10 10:36:00.815 | error | at main (/opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:718:18) stiebel-isg.0 | 2020-08-10 10:36:00.815 | error | at Array.forEach (<anonymous>) stiebel-isg.0 | 2020-08-10 10:36:00.815 | error | at /opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:719:9 stiebel-isg.0 | 2020-08-10 10:36:00.815 | error | at getIsgCommands (/opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:379:21) stiebel-isg.0 | 2020-08-10 10:36:00.815 | error | at getHTML (/opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:185:12) stiebel-isg.0 | 2020-08-10 10:36:00.815 | error | at new Promise (<anonymous>) stiebel-isg.0 | 2020-08-10 10:36:00.815 | error | at /opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:186:9 stiebel-isg.0 | 2020-08-10 10:36:00.815 | error | at request (/opt/iobroker/node_modules/request/index.js:53:10) stiebel-isg.0 | 2020-08-10 10:36:00.815 | error | at new Request (/opt/iobroker/node_modules/request/request.js:127:8) stiebel-isg.0 | 2020-08-10 10:36:00.815 | error | at Request.init (/opt/iobroker/node_modules/request/request.js:273:31) stiebel-isg.0 | 2020-08-10 10:36:00.815 | error | (19357) Error: Invalid URI "http:///?s=4,3,4" stiebel-isg.0 | 2020-08-10 10:36:00.814 | error | (19357) unhandled promise rejection: Invalid URI "http:///?s=4,3,4" Unhandled | 2020-08-10 10:36:00.814 | error | 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(). stiebel-isg.0 | 2020-08-10 10:36:00.813 | error | at main (/opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:718:18) stiebel-isg.0 | 2020-08-10 10:36:00.813 | error | at Array.forEach (<anonymous>) stiebel-isg.0 | 2020-08-10 10:36:00.813 | error | at /opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:719:9 stiebel-isg.0 | 2020-08-10 10:36:00.813 | error | at getIsgCommands (/opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:379:21) stiebel-isg.0 | 2020-08-10 10:36:00.813 | error | at getHTML (/opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:185:12) stiebel-isg.0 | 2020-08-10 10:36:00.813 | error | at new Promise (<anonymous>) stiebel-isg.0 | 2020-08-10 10:36:00.813 | error | at /opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:186:9 stiebel-isg.0 | 2020-08-10 10:36:00.813 | error | at request (/opt/iobroker/node_modules/request/index.js:53:10) stiebel-isg.0 | 2020-08-10 10:36:00.813 | error | at new Request (/opt/iobroker/node_modules/request/request.js:127:8) stiebel-isg.0 | 2020-08-10 10:36:00.813 | error | at Request.init (/opt/iobroker/node_modules/request/request.js:273:31) stiebel-isg.0 | 2020-08-10 10:36:00.813 | error | (19357) Error: Invalid URI "http:///?s=4,3,3" stiebel-isg.0 | 2020-08-10 10:36:00.813 | error | (19357) unhandled promise rejection: Invalid URI "http:///?s=4,3,3" Unhandled | 2020-08-10 10:36:00.813 | error | 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(). stiebel-isg.0 | 2020-08-10 10:36:00.812 | error | at main (/opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:718:18) stiebel-isg.0 | 2020-08-10 10:36:00.812 | error | at Array.forEach (<anonymous>) stiebel-isg.0 | 2020-08-10 10:36:00.812 | error | at /opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:719:9 stiebel-isg.0 | 2020-08-10 10:36:00.812 | error | at getIsgCommands (/opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:379:21) stiebel-isg.0 | 2020-08-10 10:36:00.812 | error | at getHTML (/opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:185:12) stiebel-isg.0 | 2020-08-10 10:36:00.812 | error | at new Promise (<anonymous>) stiebel-isg.0 | 2020-08-10 10:36:00.812 | error | at /opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:186:9 stiebel-isg.0 | 2020-08-10 10:36:00.812 | error | at request (/opt/iobroker/node_modules/request/index.js:53:10) stiebel-isg.0 | 2020-08-10 10:36:00.812 | error | at new Request (/opt/iobroker/node_modules/request/request.js:127:8) stiebel-isg.0 | 2020-08-10 10:36:00.812 | error | at Request.init (/opt/iobroker/node_modules/request/request.js:273:31) stiebel-isg.0 | 2020-08-10 10:36:00.812 | error | (19357) Error: Invalid URI "http:///?s=4,3,2" stiebel-isg.0 | 2020-08-10 10:36:00.812 | error | (19357) unhandled promise rejection: Invalid URI "http:///?s=4,3,2"

Umgebung: Aktuelles Raspberry 4 mit aktuellem ioBroker und ISG Version vom 2019 (meines Wissens auch aktuell)

Besten Dank für den tollen Adapter und Danke für Dein Engagement.
Beste Grüsse
Aare

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!

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!

Describe the bug
toe log-file shows several warnings and info
2021-07-27 14:12:44.191 - info: stiebel-isg.0 (4612) State value to set for "stiebel-isg.0.Info.ANLAGE.STATISTIK.WARMWASSERENERGIE.SO.WARMWASSERENERGIE_LINE" has to be type "number" but received type "string"

2021-07-27 14:12:44.192 - info: stiebel-isg.0 (4612) State value to set for "stiebel-isg.0.Info.ANLAGE.STATISTIK.WARMWASSERENERGIE.LATEST_VALUE.WARMWASSERENERGIE_LINE" has to be type "number" but received type "string"
2021-07-27 14:12:44.192 - info: stiebel-isg.0 (4612) State value to set for "stiebel-isg.0.Info.ANLAGE.STATISTIK.WARMWASSERENERGIE.MO.WARMWASSERENERGIE_LINE" has to be type "number" but received type "string"
2021-07-27 14:12:44.193 - warn: stiebel-isg.0 (4612) State value to set for "stiebel-isg.0.Start.val1" has value "5" greater than max ""
2021-07-27 14:12:48.177 - warn: stiebel-isg.0 (4612) State value to set for "stiebel-isg.0.Einstellungen.HEIZEN.GRUNDEINSTELLUNG.val107" has value "1" greater than max ""
2021-07-27 14:12:48.180 - warn: stiebel-isg.0 (4612) State value to set for "stiebel-isg.0.Einstellungen.HEIZEN.GRUNDEINSTELLUNG.val35" has value "3686.4" greater than max "50"

Values shown in objects:

val1 | Betriebsart | state | level |   |   | WARMWASSERBETRIEB(5)
stiebel-isg.0.Einstellungen.HEIZEN.GRUNDEINSTELLUNG.val107 AUS(1)
stiebel-isg.0.Einstellungen.HEIZEN.GRUNDEINSTELLUNG.val35 3686.4

To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
no warnings in log

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

Versions:

• Adapter version: 1.6.0
• JS-Controller version:
• Node version: v12.22.3
• Operating system: Windows10

Additional context
Add any other context about the problem here.

Hello,

since some days the adapter crashes permanently.
Error in the log:

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().
statusText: undefined
statusCode: 500
(19695) unhandled promise rejection: null

I have tryed to downgrade from 1.5.3 -> 1.5.1 but same result.
Maybe it base on a other adapter ?

What can I do ?

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/unltdnetworx/ioBroker.stiebel-isg

• [E605] No actual year found in copyright. Please add "Copyright (c) 2019 [object Object]" or "Copyright (c) 20xx-2019 [object Object]" at the end of Readme
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2019 [object Object]" or "Copyright (c) 20xx-2019 [object Object]" at 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

Think about update stable version to 1.5.1

Version: stable=1.4.11 (172 days old) => latest=1.5.1 (15 days old)
Installs: stable=89 (65.44%), latest=14 (10.29%), total=136
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/unltdnetworx/ioBroker.stiebel-isg

• [E104] No common.title found in io-package.json
• [E813] file src/ found in repository, but not found in .npmignore

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

Bitte ändern dass boolean Werte kein Null bekommen.
Speziell geht es mir um den Betriebsstatus (stiebel-isg.0.Info.STATUSANLAGE.BETRIEBSSTATUS)
Hier werden die aktiven States mit dem Stati True versehen. Anstatt für die inaktiven Stati False zu verwenden, werden diese Null gesetzt. Das ist nicht schön, denn wenn ich diese Werte per Javascript trigger auswerte, wird immer eine Fehlermeldung generiert wenn der Wert Null ist, als wenn der State überhaupt nicht vorhanden ist.
Für diese States sollte statt Null, einfach False verwendet werden. Das wäre super.

I'm looking for information, how to setup my lwz to produce warm water.
Background is, if my batterie is full from solar i will push my lwz to take the free energy and start warm water.

I have tryed to set the status to warmwater, but I think it is only in combination with the scheduled hours possible.

What can I do ?

Describe the bug
A wrong value for val35 (Grundeinstellung / Festwertbetrieb) = 3686.4°C.

To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
the setting on the device: it's switched off

Screenshots & Logfiles
stiebel-isg.0 | 2021-08-09 08:56:39.160 | warn | State value to set for "stiebel-isg.0.Einstellungen.HEIZEN.GRUNDEINSTELLUNG.val35" has value "3686.4" greater than max "50"

Versions:

• Adapter version: 1.7.3
• JS-Controller version: 3.3.15
• Node version: v12.22.4
• Operating system: Windows X64

Additional context
Add any other context about the problem here.

Nach dem Update von 1.7.1 auf 1.7.2

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/unltdnetworx/ioBroker.stiebel-isg

• [E104] No common.title found in io-package.json
• [E813] file src/ found in repository, but not found in .npmignore

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

The iot-Adapter cannot insert a state as smartdevice which uses the unit " °C". Please remove the unnecessary space character.

Think about update stable version to 1.7.4

Version: stable=1.7.3 (159 days old) => latest=1.7.4 (15 days old)
Installs: stable=222 (75.77%), latest=25 (8.53%), total=293
Click to edit

`

`

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

1. thanks for the plugin!!!
   When I try to update i will get this error:

$ ./iobroker upgrade stiebel-isg
Update stiebel-isg from @1.2.4 to @1.3.2
NPM version: 6.4.1
npm install [email protected] --production --save --prefix "/opt/iobroker" (System call)
npm
ERR! code ETARGET
npm ERR! notarget No matching version found for [email protected]
npm ERR! notarget In most cases you or one of your dependencies are requestingnpm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in:

npm ERR! /home/iobroker/.npm/_logs/2019-01-30T06_02_37_361Z-debug.log
npm install --production (System call) in "/opt/iobroker/node_modules/iobroker.stiebel-isg"
got /opt/iobroker/node_modules/iobroker.stiebel-isg/admin
upload [4] stiebel-isg.admin /opt/iobroker/node_modules/iobroker.stiebel-isg/admin/words.js words.js application/javascript
upload [3] stiebel-isg.admin /opt/iobroker/node_modules/iobroker.stiebel-isg/admin/stiebel-isg.png stiebel-isg.png image/png
upload [2] stiebel-isg.admin /opt/iobroker/node_modules/iobroker.stiebel-isg/admin/index_m.html index_m.html text/html
upload [1] stiebel-isg.admin /opt/iobroker/node_modules/iobroker.stiebel-isg/admin/i18n/en/translations.json i18n/en/translations.json application/json
upload [0] stiebel-isg.admin /opt/iobroker/node_modules/iobroker.stiebel-isg/admin/i18n/de/translations.json i18n/de/translations.json application/json
Adapter "stiebel-isg" updated
process exited with code 0

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/unltdnetworx/ioBroker.stiebel-isg

• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.stiebel-isg"

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. First of all thank you for the adapter!

My question: Why are the values of all boolean states (for example stiebel-isg.0.Info.ANLAGE.BETRIEBSSTATUS.HEIZEN or stiebel-isg.0.Info.ANLAGE.BETRIEBSSTATUS.WARMWASSERBETRIEB) "null" when they should be "false"? When accessing them via "getState", a warning is thrown: getState "stiebel-isg.0.Info.ANLAGE.ENERGIEMANAGEMENT.Betriebszustand_3" not found (3) and the value is null. How can I workaround this problem?

Thanks and regards,

Dirk

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!

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,

alle Felder in den kein True steht haben keinen Inhalt, wie z.B. False. Damit sind die Felder nicht bzw. nur sehr schwer auswertbar.

Gibt es eine Lösung dafür?

Hello,

all fields that do not contain True have no content, such as False. This means that the fields cannot be evaluated or can only be evaluated with great difficulty.

Is there a solution for this?

Hello,

since 2 days the Siebel ISG adapter crashes periodically. Log:

2021-03-03 20:19:50.457 - 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().
2021-03-03 20:19:50.459 - error: stiebel-isg.0 (23999) unhandled promise rejection: Cannot read property 'replace' of undefined
2021-03-03 20:19:50.461 - error: stiebel-isg.0 (23999) TypeError: Cannot read property 'replace' of undefined
at createISGCommands (/opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:346:14)
at Node. (/opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:514:21)
at initialize.exports.each (/opt/iobroker/node_modules/cheerio/lib/api/traversing.js:562:24)
at Node. (/opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:492:52)
at initialize.exports.each (/opt/iobroker/node_modules/cheerio/lib/api/traversing.js:562:24)
at getIsgCommands (/opt/iobroker/node_modules/iobroker.stiebel-isg/main.js:460:35)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
2021-03-03 20:19:50.464 - info: stiebel-isg.0 (23999) cleaned everything up...
2021-03-03 20:19:50.487 - info: stiebel-isg.0 (23999) terminating
2021-03-03 20:19:50.490 - info: stiebel-isg.0 (23999) Terminated (NO_ERROR): Without reason
2021-03-03 20:19:51.019 - info: host.raspberrypi instance system.adapter.stiebel-isg.0 terminated with code 0 (NO_ERROR)
2021-03-03 20:19:51.021 - info: host.raspberrypi Restart adapter system.adapter.stiebel-isg.0 because enabled

During the time its running (usually approx. 1 min), I can retrieve data from the ISG.

Raspberry Pi 3
Linux raspberrypi 5.10.11-v7+
Node.js: v14.13.0
NPM: 6.14.8

Any ideas?

regards
thomas

$ ./iobroker upgrade stiebel-isg
Update stiebel-isg from @1.4.0 to @1.4.1
NPM version: 6.4.1
npm install [email protected] --production --save --prefix "/opt/iobroker" (System call)
npm
WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.stiebel-isg
npm WARN
[email protected] requires a peer of pg@>5.0 but none is installed. You must install peer dependencies yourself.

npm ERR! path /opt/iobroker/node_modules/iobroker.stiebel-isgnpm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/opt/iobroker/node_modules/iobroker.stiebel-isg'
npm ERR! { Error: EACCES: permission denied, access '/opt/iobroker/node_modules/iobroker.stiebel-isg'
npm
ERR! stack: 'Error: EACCES: permission denied, access '/opt/iobroker/node_modules/iobroker.stiebel-isg'',npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'access',
npm ERR! path: '/opt/iobroker/node_modules/iobroker.stiebel-isg' }

npm ERR! npm ERR!
The operation was rejected by your operating system.npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm
ERR! permissions of the file and its containing directories, or try runningnpm ERR! the command again as root/Administrator (though this is not recommended).

npm
ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2019-03-15T13_23_11_249Z-debug.log

ERROR: host.stariobroker Cannot install [email protected]: 243
ERROR: process exited with code 25

It seems to me that unter "HEIZEN" all numerical values are of type string. Whereas unter "Info" it is correct.
This makes it difficult to store it in an influxDB which is very sensitive to it.
Can this be configured somewhere?
Please see screenshots below:
Log entry with errors

Values in "HEIZEN" have a decimal comma

values in "Info" have a decimal point

Adapter lässt sich nicht mehr starten

`

`

Hi,

nach dem Update auf 1.7.1 bekomme ich folgendes:

`

`

Think about update stable version to 1.6.1

Version: stable=1.6.0 (99 days old) => latest=1.6.1 (15 days old)
Installs: stable=113 (62.78%), latest=23 (12.78%), total=180
Click to edit

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.

Hi,
since the js-controller update the log gets filled up with:

2021-08-12 00:32:24.840 - warn: stiebel-isg.0 (24359) State value to set for "stiebel-
isg.0.Start.val39" has value "5" greater than max ""
2021-08-12 00:32:34.621 - warn: stiebel-isg.0 (24359) State value to set for "stiebel-isg.0.Einstellungen.ENERGIEMANAGEMENT.val60305" has value "1" greater than max ""
2021-08-12 00:32:34.623 - warn: stiebel-isg.0 (24359) State value to set for "stiebel-isg.0.Einstellungen.ENERGIEMANAGEMENT.val60028" has value "1" greater than max ""
2021-08-12 00:32:36.444 - warn: stiebel-isg.0 (24359) State value to set for "stiebel-isg.0.Einstellungen.ENERGIEMANAGEMENT.val60305" has value "1" greater than max ""
2021-08-12 00:32:36.446 - warn: stiebel-isg.0 (24359) State value to set for "stiebel-isg.0.Einstellungen.ENERGIEMANAGEMENT.val60028" has value "1" greater than max ""
2021-08-12 00:32:40.596 - warn: stiebel-isg.0 (24359) State value to set for "stiebel-isg.0.Einstellungen.LUEFTEN.PASSIVKUEHLUNG.val413" has value "1" greater than max ""
2021-08-12 00:32:43.488 - warn: stiebel-isg.0 (24359) State value to set for "stiebel-isg.0.Einstellungen.LUEFTEN.FEUCHTESCHUTZ.val364" has value "1" greater than max ""
2021-08-12 00:32:49.404 - warn: stiebel-isg.0 (24359) State value to set for "stiebel-isg.0.Einstellungen.WARMWASSER.GRUNDEINSTELLUNG.val116" has value "1" greater than max ""

at the object tree at
stiebel-isg.0 - INFO - STATUS - BETRIEBSSTATUS
you can find the stati of the ISG. Is it possible to set the status to false if it is not set?
Actually you only set it to true if you find it in the page.
Maybe you could implement a routine that check all states and if you could not find the state
set it to false.

Describe the bug
If I change the values ​​val82 and val83, this has no effect on the machine. The values ​​are read correctly, but changes are not written.

To Reproduce
Steps to reproduce the behavior:

1. Change value val82 (fan level day) in the ioBroker from 2 to 0
2. Check changes in the web front end of the ISG - no change
3. After the pull interval, the value val82 is overwritten with the old value 2 again

Expected behavior
I expect that value is written to the ISG

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

Versions:

• Adapter version: 1.6.1
• JS-Controller version: 3.2.16
• Node version: 12.22.1
• Operating system: Container on unraid

Additional context
For questions contact me at [email protected]

it wil lbe usefull when you can send an message when this state is changing. After the xmas holidays i come back to my cold house, because of an "Niederdruck Fehler" :-(

Think about update stable version to 1.5.3

Version: stable=1.5.1 (59 days old) => latest=1.5.3 (15 days old)
Installs: stable=53 (40.46%), latest=10 (7.63%), total=131
Click to edit

Describe the bug
Value check for value Warmwasser.grundeinstellung.val113 is wrong. All values between 0 and 3 are fine. Value ckeck must check if a value is negativ or greater 3. 0 is a allowed value in the Stiebel-ISG and in the machine it self.

To Reproduce
Steps to reproduce the behavior:

1. Set Warmwasser.Grundeinstellung.val113 in Stiebel-ISG or on the machine to 0
2. see error: State value to set for "stiebel-isg.0.Einstellungen.WARMWASSER.GRUNDEINSTELLUNG.val113" has value "0" less than min "1"

Expected behavior
No warning in the logs.

Screenshots & Logfiles
stiebel-isg.0 | 2022-11-19 13:55:40.716 | warn | State value to set for "stiebel-isg.0.Einstellungen.WARMWASSER.GRUNDEINSTELLUNG.val113" has value "0" less than min "1"

Versions:

• Adapter version: 1.7.5
• Node version: 14.18.1
• Operating system: linux

Übernahme der ISG Fehlerliste in die Objekte.

Think about update stable version to 1.5.1

Version: stable=1.4.11 (174 days old) => latest=1.5.1 (17 days old)
Installs: stable=88 (65.67%), latest=14 (10.45%), total=134
Click to edit

Hi since update to 1.6. i have an issue, so I goes back to 1.5.3 and all is working fine

Is this Adapter still maintained?
Adapter frequently crashes due to unhandled exception and stucks in restart loop.

I have a small problem with the ISG adapter. In the logs I regularly find warnings shown below. I use the adapter in version 1.7.3. The data for my system are:

Node.js: 12.22.7
NPM: 6.14.15
Controller: 3.3.18

I think the problem is not serious but unsightly.

---log---
stiebel-isg.0 | 1331 | 2021-11-25 13:29:36.667 | warn | State value to set for "stiebel-isg.0.Start.val39" has value "11" greater than max ""
stiebel-isg.0 | 1331 | 2021-11-25 13:24:41.499 | warn | State value to set for "stiebel-isg.0.Start.val39" has value "11" greater than max ""
stiebel-isg.0 | 1331 | 2021-11-25 13:19:36.522 | warn | State value to set for "stiebel-isg.0.Start.val39" has value "11" greater than max ""

Since round about 1 or 2 weeks the adapter can`t read and write all values under "Info" and then "WAERMEPUMPE". So I don't get the values for used energy. All other values are available.
I guess the ISG made an automatic Update. My ISG-Version is 10.2.
When I use the display of the heating pump I get the informations.

Zuerst eine Beobachtung. Seit ISG auf Version 12.0 (automatisch 1 Jahr Gratisvertrag) reagiert diese nicht mehr so träge bei Abfragen.

Bereits früher und auch jetzt Adapter V 1.5.3 mit ISG Version 12.00 (Build 123 oder so) habe ich eine fehlerhafte Einheit 00KWh bei der Wärmemenge Tag

stiebel-isg.0.Info.WAERMEPUMPE.WAERMEMENGE.VD_HEIZEN_TAG 5.45 00KWh

Denke da sind Wert / Einheit irgendwie durcheinander gekommen

2. Noch eine Frage zum Adapter.
   In diesen Werten habe ich keine Daten:
   stiebel-isg.0.Info.STATUSANLAGE.BETRIEBSSTATUS.HEIZEN
   stiebel-isg.0.Info.STATUSANLAGE.BETRIEBSSTATUS.WARMWASSERBEREITUNG
   stiebel-isg.0.Info.STATUSANLAGE.BETRIEBSSTATUS.HEIZKREIS_1_PUMPE

Werden diese nicht erhoben / geliefert nur je nach WP Typ oder braucht es da ein Update?
Eigentliches Ziel wäre herauszufinden warum die Pumpe läuft. Für Heizung oder Warmwasser.
Die Wärmemenge Heizen und Warmwasser werden leider erst geschrieben wenn die WP bereits wieder gestoppt hat
stiebel-isg.0.Info.WAERMEPUMPE.WAERMEMENGE.VD_HEIZEN_TAG und stiebel-isg.0.Info.WAERMEPUMPE.WAERMEMENGE.VD_WARMWASSER_TAG

Danke !