I have to use Version 1.1.0 to get any data. Then its working for the BM-1, but there is no data for CGB-2, but a lot of errors in der ioBroker log like the following. Other people mentioned the issue already.

Version 1.2.1 does not work at all. 1.2

Hi Zusammen,

vielen Dank für die Updates des Adapters! Ich finde es klasse, dass er nochmal aktualisiert wurde!
Allerdings bekomme ich trotz Update auf die neuste Version 1.32 die Fehlermeldung, dass die Variablen nicht den richtigen
Typ zugeordnet haben. Muss ich dafür etwas ändern oder ist das im Adapter fix vorgesehen?

`

Danke und Gruß,

Claus

changelog of 1.2.0:

• (schweigel) Added for all variables "write" as Bool value

it should be:

• (LHBL2003) Added for all variables "write" as Bool value

For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268

Moin Moin,

ich nutze den Wolf Adapter 1.2.1 von GitHub mit meiner Wolf24.

Mein Fußbodenkreis ist etwas exotisch verbaut und hängt nicht mit dem Radiatorenheizkreis zusammen, sondern am MM1. Damit kann ich den DPT_HVACMode für Radiatoren und Fußboden getrennt zwischen Standby und Automatikbetrieb wechseln.

Leider fehlen die Datenpunkte 67-79 im Wolf Adapter, d.h. ich kann zwar die Radiatoren von IOBroker aus schalten, nicht jedoch die Fußbodenheizung.

[https://www.wolf.eu/fileadmin/Wolf_Profi/Downloads/Montage-Bedienungsanleitungen/Regelungen/Zubehoer/3064356_201611_ISM8i_Montage-u.Bedienungsanleitung.pdf] Seite 23.

Wie kann ich die fehlenden Datenpunkte nachtragen/erweitern?

Danke, -MN

Hi all,

I manually added datapoint wolf.0.bm1.194 (1xWarmwasserladung | 1x warm water) in order to automate a logic for saving energy.
Could you please add this datapoint into the adapter by default? Manually added works perfect but would be great if included by default.
I use it to store photovoltaic energy with raising the warm water temperature when the sun is shining for more than 15 min from 45 to 58 degrees. Therefore I use the datapoint to start the warming up process.

Thx and brgds,

Claus

Hallo,

ist es möglich mit diesem Modul die Betriebsstunden des Verdichters der Wärmepumpe auszulesen? Über die Weboberfläche kann ich diesen Wert ablesen, im IoBroker (Anbindung per ISM8) kann ich den Wert leider nicht finden.

Um Belastung/Verschleiß der Pumpe zu dokumentieren, wäre dieser Wert sehr hilfreich.

Vielen Dank!

Dear,

I installed a firewall between my LAN (192.168.1.0/24) which includes the ISM8i module and my IOBroker (192.168.3.0/24).

ISM8i Network configuration has changed accordingly to the IOBroker address and a rule for port 12004 as shown on the ISM8i webinterface has been added.

However, there is no communication possible between both devices. What do I need to pass in the firewall to allow messages being exchanged?

Thanks, -JM

Hi Steffen,
hast sicher viel um die Ohren....
Machst du eigentlich aktuell was mit ScriptGUI für ioBroker?
VG Martin

Hej,

my ISM8i-Modul is configured to use DHCP and uses IP-address 192.168.1.158/24 ("LAN" Network).

My IOBroker is configured at 192.168.3.30/24 and uses Port 12004 for WOLF ("SERVERLAN" network).

Between LAN- and SERVERLAN network an Opnsense firewall routes traffic. To allow traffic from ISM8i to IOBroker a very open rule is configured:

Allow IPv4/Any Protocol, Any Port. to Host_IOBroker, Any Port

Connect from LAN any client to Wolf adapter on Port 12004 is working fine (tested with telnet):

And IOBroker shows active connections from ISM8i on the Linux operating system level:

Wolf Adapter is configured but is not creating any objects:

I have restarted the Adapter and the Host. No changes.

What else can I test to get the Wolf adapter working again?

Thanks, -JM

Wäre es möglich die aktuelle Leistung der Umwälzpumpe abzufragen? Der Zustand wird ja bereits abgefragt.

Object wolf.0.bm0.194 is invalid: obj.common.name has an invalid type! Expected "string" or "object", received "number"

Hi,
I have been using my own modified wolf adapter (installed via admin interface) for a while. Modifications done following this post:
https://forum.iobroker.net/topic/20222/gel%C3%B6st-adapter-wolf-heizung-cwl-ansteuern-mit-iobroker

After noticing there is a new version available I tried to use this one. Unfortunately I get the same error as in the old version deployed with iobroker admin interface.

Any hints? Should I try to include my changes to the Repro?

Sorry, I'm new at GitHub ;)

New ISM8i with FW 1.6 installed in BWL
adapter version 1.2.1 installed,
module indicates successful connection,
adapter also shows all green
but no objects are created.

After stepping back to 1.2.0 objects appear and CWL and BWL can be controlled.

Hallo,

bei der CWL erscheint leider der oben genannte Fehler gefolgt von einr weiteren Serie an Fehlermeldungen
uncaught exception: The "list[1]" argument must be one of type Array, Buffer, or Uint8Array. Received type string. Unter anderem werden

Versucht mit Node 8.X und 10.X mit einem Raspi und mit einem Windows Rechner

Gruss
Klaus

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

According to documentation the type of DP 149 should be DPT_HVACMode but is:

Hallo,

nachdem ich am 01.09. die neuste Version 1.32 installiert habe habe ich alle Objekte gelöscht und neu anlegen lassen.
Das hat super geklappt, allerdings habe ich gerade festgestellt, dass er seit dieser Zeit die Werte nicht mehr
aktualisiert hat. Die Werte sind alle samt noch vom 01.09..

Woran kann das liegen und was kann ich tun um das zu ändern?
Meldungen (Fehler/Warnung) werden im Protokoll keine angezeigt.

@GermanBluefox ich habe nun wieder v 1.20 installiert das funktioniert einwandfrei. Kannst Du ggf. Die Änderungen an dieser Version vornehmen? Dann hätten wir eine funktionierende Basis auf dem aktuellen Stand.

Danke und Gruß,

Claus

Hallo Zusammen,

vielen Dank für den Adapter!
Mittlerweile funktioniert er einwandfrei (Heizung mit Wärmepumpe BWL-1S und Bedienmodul, mit Version 1.2).
Die Soll-Temperatur kann ich problemlos umstellen, nun würde ich gerne das Programm "1xWarmwasser" starten.
Hat jemand eine Idee was ich dafür antriggern muss damit das startet?

Danke und Gruß,

Claus

Kann in den Parametern 154 bis 157 und 159 bis 162 keine vernünftige Daten eintragen.
Habe den Wert 155 und 160 direkt an der BM geändert. Der Versuch es über IoBroker zu machen scheiterte kläglich.
error | Caught by controller[0]: TypeError [ERR_INVALID_ARG_TYPE]: The "list[1]" argument must be an instance of Buffer or Uint8Array. Received type string ('e')
Habe diverse Formate versucht aber kein Erfolg gehabt
Sorry, dass ich alles auf deutsch schreibe, aber mein englisch ist für so etwas nicht wirklich geeignet.
Gruß
Klaus

Does anyone have it running with a BWL-1-I model (not the split one)?
Is ISM8i itself incompatible or is it an issue of the adapter. If it's the latter one I will buy one and create the necessary modifications/pull-requests to make the adapter compatible.

Sorry, but I don't quite understand how the adapter should work? Does it only work with the ISM8i device? Can I connect via Link Pro?

Hello for some reason my "Modulationsgrad Brennerleistung" stopped updating after patching... I tried uninstalling the Wolf module and reinstalling it, after that I had no more wolf objects in the tree. After downgrading to 1.2.0 then the data points came back, after that I upgraded to 1.2.1, next I noticed in the Logs:

warn: admin.0 (711) Object ... is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.

Is this linked to the issue of the objects not showing up in the tree?

Log Dump:
2020-09-27 14:21:57.729 - info: host.raspberrypi instance system.adapter.wolf.0 started with pid 26270
2020-09-27 14:21:59.133 - debug: wolf.0 (26270) Redis Objects: Use Redis connection: 127.0.0.1:9001
2020-09-27 14:21:59.179 - debug: wolf.0 (26270) Objects client ready ... initialize now
2020-09-27 14:21:59.186 - debug: wolf.0 (26270) Objects create System PubSub Client
2020-09-27 14:21:59.188 - debug: wolf.0 (26270) Objects create User PubSub Client
2020-09-27 14:21:59.190 - debug: wolf.0 (26270) Objects client initialize lua scripts
2020-09-27 14:21:59.207 - debug: wolf.0 (26270) Objects connected to redis: 127.0.0.1:9001
2020-09-27 14:21:59.218 - debug: wolf.0 (26270) objectDB connected
2020-09-27 14:21:59.223 - debug: wolf.0 (26270) Redis States: Use Redis connection: 127.0.0.1:9000
2020-09-27 14:21:59.239 - debug: wolf.0 (26270) States create User PubSub Client
2020-09-27 14:21:59.244 - debug: wolf.0 (26270) States create System PubSub Client
2020-09-27 14:21:59.257 - debug: wolf.0 (26270) States connected to redis: 127.0.0.1:9000
2020-09-27 14:21:59.259 - debug: wolf.0 (26270) statesDB connected
2020-09-27 14:21:59.611 - info: wolf.0 (26270) starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.wolf, node: v12.18.4, js-controller: 3.1.6
2020-09-27 14:22:06.206 - info: host.raspberrypi stopInstance system.adapter.wolf.0 (force=false, process=true)
2020-09-27 14:22:06.208 - info: host.raspberrypi stopInstance system.adapter.wolf.0 send kill signal
2020-09-27 14:22:06.214 - info: wolf.0 (26270) Got terminate signal TERMINATE_YOURSELF
2020-09-27 14:22:06.252 - debug: wolf.0 (26270) system.adapter.admin.0: logging true
2020-09-27 14:22:06.718 - info: wolf.0 (26270) terminating
2020-09-27 14:22:06.720 - info: wolf.0 (26270) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-09-27 14:22:07.211 - info: host.raspberrypi stopInstance system.adapter.wolf.0 killing pid 26270
2020-09-27 14:22:07.252 - info: host.raspberrypi instance system.adapter.wolf.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-09-27 14:22:09.242 - info: host.raspberrypi instance system.adapter.wolf.0 started with pid 26437
2020-09-27 14:22:10.714 - debug: wolf.0 (26437) Redis Objects: Use Redis connection: 127.0.0.1:9001
2020-09-27 14:22:10.761 - debug: wolf.0 (26437) Objects client ready ... initialize now
2020-09-27 14:22:10.766 - debug: wolf.0 (26437) Objects create System PubSub Client
2020-09-27 14:22:10.768 - debug: wolf.0 (26437) Objects create User PubSub Client
2020-09-27 14:22:10.770 - debug: wolf.0 (26437) Objects client initialize lua scripts
2020-09-27 14:22:10.788 - debug: wolf.0 (26437) Objects connected to redis: 127.0.0.1:9001
2020-09-27 14:22:10.799 - debug: wolf.0 (26437) objectDB connected
2020-09-27 14:22:10.803 - debug: wolf.0 (26437) Redis States: Use Redis connection: 127.0.0.1:9000
2020-09-27 14:22:10.818 - debug: wolf.0 (26437) States create User PubSub Client
2020-09-27 14:22:10.823 - debug: wolf.0 (26437) States create System PubSub Client
2020-09-27 14:22:10.835 - debug: wolf.0 (26437) States connected to redis: 127.0.0.1:9000
2020-09-27 14:22:10.837 - debug: wolf.0 (26437) statesDB connected
2020-09-27 14:22:11.111 - info: wolf.0 (26437) starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.wolf, node: v12.18.4, js-controller: 3.1.6
2020-09-27 14:22:43.092 - warn: admin.0 (711) Object wolf.0.hg1.1 is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-09-27 14:22:43.099 - warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.
2020-09-27 14:22:43.108 - info: sql.0 (799) enabled logging of wolf.0.hg1.1, Alias=false
2020-09-27 14:23:06.641 - warn: admin.0 (711) Object wolf.0.hg1.12 is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-09-27 14:23:06.642 - warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.
2020-09-27 14:23:06.649 - info: sql.0 (799) enabled logging of wolf.0.hg1.12, Alias=false
2020-09-27 14:23:34.202 - warn: admin.0 (711) Object wolf.0.hg1.13 is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-09-27 14:23:34.203 - warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.
2020-09-27 14:23:34.212 - info: sql.0 (799) enabled logging of wolf.0.hg1.13, Alias=false
2020-09-27 14:23:52.913 - warn: admin.0 (711) Object wolf.0.hg1.197 is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-09-27 14:23:52.915 - warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.
2020-09-27 14:23:52.926 - info: sql.0 (799) enabled logging of wolf.0.hg1.197, Alias=false
2020-09-27 14:24:01.897 - warn: admin.0 (711) Object wolf.0.hg1.198 is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-09-27 14:24:01.898 - warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.
2020-09-27 14:24:01.905 - info: sql.0 (799) enabled logging of wolf.0.hg1.198, Alias=false
2020-09-27 14:24:09.741 - warn: admin.0 (711) Object wolf.0.hg1.199 is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-09-27 14:24:09.742 - warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.
2020-09-27 14:24:09.752 - info: sql.0 (799) enabled logging of wolf.0.hg1.199, Alias=false
2020-09-27 14:24:18.070 - warn: admin.0 (711) Object wolf.0.hg1.2 is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-09-27 14:24:18.071 - warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.
2020-09-27 14:24:18.081 - info: sql.0 (799) enabled logging of wolf.0.hg1.2, Alias=false
2020-09-27 14:24:26.357 - warn: admin.0 (711) Object wolf.0.hg1.3 is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-09-27 14:24:26.358 - warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.
2020-09-27 14:24:26.367 - info: sql.0 (799) enabled logging of wolf.0.hg1.3, Alias=false
2020-09-27 14:24:34.100 - warn: admin.0 (711) Object wolf.0.hg1.4 is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-09-27 14:24:34.101 - warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.
2020-09-27 14:24:34.110 - info: sql.0 (799) enabled logging of wolf.0.hg1.4, Alias=false
2020-09-27 14:24:42.039 - warn: admin.0 (711) Object wolf.0.hg1.5 is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-09-27 14:24:42.040 - warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.
2020-09-27 14:24:42.056 - info: sql.0 (799) enabled logging of wolf.0.hg1.5, Alias=false
2020-09-27 14:24:49.944 - warn: admin.0 (711) Object wolf.0.hg1.6 is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-09-27 14:24:49.945 - warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.
2020-09-27 14:24:49.953 - info: sql.0 (799) enabled logging of wolf.0.hg1.6, Alias=false
2020-09-27 14:24:57.321 - warn: admin.0 (711) Object wolf.0.hg1.7 is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-09-27 14:24:57.322 - warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.
2020-09-27 14:24:57.329 - info: sql.0 (799) enabled logging of wolf.0.hg1.7, Alias=false
2020-09-27 14:25:05.798 - warn: admin.0 (711) Object wolf.0.hg1.8 is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-09-27 14:25:05.799 - warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.
2020-09-27 14:25:05.806 - info: sql.0 (799) enabled logging of wolf.0.hg1.8, Alias=false
2020-09-27 14:25:13.898 - warn: admin.0 (711) Object wolf.0.hg1.9 is invalid: obj.common.type has an invalid value (state) but has to be one of number, string, boolean, array, object, mixed, file, json
2020-09-27 14:25:13.900 - warn: admin.0 (711) This object will not be created in future versions. Please report this to the developer.
2020-09-27 14:25:13.912 - info: sql.0 (799) enabled logging of wolf.0.hg1.9, Alias=false

Gruß Rusty

Is it possible to change the request frequency so that the datapoints are read at least every 10mins ?
Maybe trigger a readout of all values in an interval ?

This are my current readouts... as you can see "kesseltemp" has an current value. The rest lags behind at least 20min

Thanks

Edit: I know some of them already changed but are not requested / send to the iobroker yet.

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.

In boolean mode the DPT_Switch can be read correct, but if the value is changed inside iobroker the value switched to "On" or "Off" instead of "true" or "false".
I have fixed it in my fork (https://github.com/schweigel/ioBroker.wolf) but I'm not sure how to merge only this change.

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/ioBroker/ioBroker.wolf

• [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) 2015-2022 smiling_Jack [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2015-2022 smiling_Jack [email protected]" at the start of LICENSE

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

• [W801] .npmignore not found

Thanks,
your automatic adapter checker.

For instance DP 177 "Betriebsart" is not changing it's value on 1.2.1. If I'm going back to v. 0.9.2 its working proper. Are there any dependencies on node.js or something else?

The DP ID 175 has currently the unit "Heizgerät(1)". It should have no unit.
I have corrected it in my fork (https://github.com/schweigel/ioBroker.wolf) but I'm not sure how to merge only this change.

Since two days i`m getting this error and adapter is terminated within one minute. Also I get not find the dp offset.

EN: I uninstalled the Wolf adapter. When uninstalling the adapter the variables were deleted properly. But when installing version 1.2.0 no variables are created.
All devices have the Auto check mark set.

DE: Ich habe den Wolf Adapter deinstalliert. Beim deinstallieren wurden die Variablen ordnungsgemäß gelöscht. Aber beim installieren der Version 1.2.0 werden keine Variablen erstellt.
Alle Geräte haben den Haken Auto gesetzt.

Hallo zusammen,
ich habe eine CHA-Wärmepumpe mit ISM8i. Leider habe ich keine Ahnung vom Programmieren. Nach meiner Meinung müste diese Anlage relativ einfach in den Adapter zu integrieren sein da die Datenpunkte auch in der gleichen Anleitung offengelegt wurden wie die bisherigen integrierten Wolf-Anlagen. Ich habe den Adapter in iOBroker installiert und hatte einmal einen Abruf mit Daten hinbekommen, aber aktualisiert wird er nicht. Die CHA ist wohl letztes Jahr ganz neu auf den Markt gekommen. Ich denke da sind in der Zukunft bestimmt noch mehr die darauf zugreifen würden. Für Erprobungen würde ich mich auch gerne bereitstellen.
Uwe

All values with format DPT_Date have a wrong interpreted month.
Alle Werte mit dem Format DPT_Date haben einen falsch interpretierten Monat.

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.

Kann im Code der main.js die Schrittweite die in der Bedienungsanleitung steht angepasst werden?
Hier wird die Math.round Funktion mit *2 ) /2 gemacht, für die Schrittweite von 0,5 wäre aber *10)/10 angebrachter.

Auszug Bedienungsanleitung ISM8:
IDs Datenpunkt Einheit Wertebereich Schrittweite
65 / 78 / 91 / 104 Sollwertkorrektur K -4K - +4K 0,5K
66 / 79 / 92 / 105 Sparfaktor K 0K - 10K 0,5K

Codeauszug:
} else if (type === 'DPT_Tempd' && name === 'Sollwertkorrektur') {
val = Math.round(data * 2) / 2;
if (val > 4) {
val = 4
}
if (val < -4) {
val = 4
}
return [enc.encodeDPT9(data), val];
} else if (type === 'DPT_Tempd' && name === 'Sparfaktor') {
val = Math.round(data * 2) / 2;
if (val > 10) {
val = 10
}
if (val < 0) {
val = 0
}
return [enc.encodeDPT9(data), val];

Danke und MfG Silvio

Ich würde gerne von den statischen IP-Adressvergaben weg kommen, damit das System nach einem Anbieterwechsel (Telekom, Vodafone) sofort wieder lauffähig ist. Ja ich könnte einfach das IP-Adresssegment im Router anpassen, so das der Router wieder 192.168.0.xxx verwendet. Sterbe ich aber, so muss dies jemand anderes dies aber wissen. (z.B. meine liebste)
Daher würde ich es bevorzugen, dass ich einfach das System via DNS Namen erreichen kann.

Vielen Dank

Fresh installation with 1.2.1 but no DataPoints get created.
A hint from iobroker Forum was to use 1.2.0 but also with this Version no Data Points get created

can you please help, thanks

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!

Erstmal Danke für die tolle Arbeit. Habe die neueste Version runtergeladen und ein bisschen damit rum probiert.
Habe zwei Dinge die mir aufgefallen sind. Die erste betrifft die CWL und einen Fehler in der Main.js und der zweite ist das es zu Warnmeldungen kommt wenn man Werte ändert. Dieses betrifft Switch Werte (und auch HVACMode undDHWMode).
`
javascript.0 | 2020-06-24 20:50:00.009 | warn | (7340) You are assigning a number to the state "wolf.1.cwl.149" which expects a state. Please fix your code to use a state or change the state type to number. This warning might become an error in fut

Dieses habe ich wegbekommen indem ich aus Logikwert Zahl gemacht habe (bei Objekt bearbeiten).

Gruß Klaus

Hi Zusammen,

ich erhalte seit Einbindung meiner Lüftungsanlage (was übrigens einwandfrei funktioniert hat) folgende Fehlermeldung:

`

Leider kann ich die Anzahl Zeichen nicht manuell ändern. Gibt es einen Workaround um den Fehler abzustellen bzw. im Programm zu beheben?

Danke und Gruß,

Claus

DE: Über den FHEM Adapter kann man direkt die Wolf Adapter Variablen beschreiben.
Hierzu muss aber für die RW Variablen in den RAW Daten unter "common": { mindestens folgender Inhalt enthalten sein: "write": true
Dieser Eintrag definiert im ioBroker ob eine Anwendung auf die Variable schreiben darf.
Gleichzeitig sollte man auch für alle Variablen das "read": true nachpflegen.

Der aktuelle Eintrag "native": { "rw": "rw" ist nur Info Material und hat daher keine Funktion.

EN: With the FHEM adapter you can directly describe the Wolf adapter variables.
For this purpose, however, the RW variables in the RAW data under "common": { must contain at least the following content: "write": true. This entry defines in the ioBroker if an application is allowed to write to the variable. At the same time you should also maintain the "read": true" for all variables.

The current entry "native": { "rw": "rw" is only info material and therefore has no function.

Think about update stable version to 1.3.4

Version: stable=1.2.1 (665 days old) => latest=1.3.4 (153 days old)
Installs: stable=188 (67.14%), latest=45 (16.07%), total=280
Click to edit

Hallo Zusammen,
da die aktuelle Version nicht funktioniert würde ich gerne die alte noch funktionierende Version
installieren. Über GIT gibt es diese leider nicht mehr. Hat jemand eine Idee, woher ich die noch bekommen kann?
Danke und Gruß,
Claus

Dear Adapter develop,

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!

Wenn ich die Version 1.2.1 installiere werden keine Objekte angelegt.
Wenn ich die Version 1.2.0 installiere werden zwar Objekte angelegt aber nicht alle. z.B. mein Solarmodul erscheint überhaupt nicht !

I get errors for all DPT_TimeOfDay values in log:
Ich bekomme Fehler für alle DPT_TimeOfDay Werte im Log:

wolf.0 2019-11-20 18:01:44.200 error (638) Can't parse DP : 162 - data: 0620f080001704000000f00600a2000100a20303150400 - length: 23
wolf.0 2019-11-20 18:01:44.051 error (638) Can't parse DP : 161 - data: 0620f080001704000000f00600a1000100a10303120400 - length: 23
wolf.0 2019-11-20 18:01:43.418 error (638) Can't parse DP : 157 - data: 0620f080001704000000f006009d0001009d0303150400 - length: 23
wolf.0 2019-11-20 18:01:43.258 error (638) Can't parse DP : 156 - data: 0620f080001704000000f006009c0001009c0303120400 - length: 23

In object browser no values are set for these datapoints.
Unter Objekte enthalten die Datenpunkte keine Werte.

Tested with ioBroker.wolf 1.1.0
Getestet mit ioBroker.wolf 1.1.0

Wenn ich die 149 ansteuer kommt es zum Error

wolf.1 | 2020-06-24 20:46:26.630 | error | (4296) uncaught exception: The "list[1]" argument must be an instance of Buffer or Uint8Array. Received type string ('e')

Habe in der Main.js gesehen das dort etwas fehlt.
So sieht der Bereich ab Zeile 354 aus
` } else if (name === 'Programmwahl Warmwasser') {
if (data == 0 || data === 'Standby') {
return [new Buffer('04', 'hex'), 'Standby'];
}
else if (data == 2 || data === 'Dauerbetrieb') {
return [new Buffer('02', 'hex'), 'Dauerbetrieb'];
} else {
return [new Buffer('00', 'hex'), 'Automatikbetrieb'];
}
} else if (name === 'Programmwahl Mischer' || name === 'Programmwahl Heizkreis') {
if (data == 0 || data === 'Standby') {
return [new Buffer('02', 'hex'), 'Standby'];
}

dort fehlt die Anwahl für die CWL (zwischen Warmwasser und Mischer||Heizkreis)

` } else if (name === 'Programmwahl Warmwasser') {
if (data == 0 || data === 'Standby') {
return [new Buffer('04', 'hex'), 'Standby'];
}
else if (data == 2 || data === 'Dauerbetrieb') {
return [new Buffer('02', 'hex'), 'Dauerbetrieb'];
} else {
return [new Buffer('00', 'hex'), 'Automatikbetrieb'];
}
} else if (name === 'Programmwahl CWL') {
if (data == 3 || data === 'Reduzierte Lüftung') {
return [new Buffer('03', 'hex'), 'Reduzierte Lüftung'];
}
else if (data == 2 || data === 'Feuchteschutz') {
return [new Buffer('02', 'hex'), 'Feuchteschutz'];
} else if (data == 1 || data === 'Nennlüftung') {
return [new Buffer('01', 'hex'), 'Nennlüftung'];
}
else {
return [new Buffer('00', 'hex'), 'Intensivlüftung'];
}
} else if (name === 'Programmwahl Mischer' || name === 'Programmwahl Heizkreis') {
if (data == 0 || data === 'Standby') {
return [new Buffer('02', 'hex'), 'Standby'];

Wenn man die Zeilen ab 226 ebenfalls anpasst kann man die CWL super ansteuern`

aktuell............
` } else if (datapoints[dp].name === 'Programmwahl CWL') {
if (_data === 0) {
return 'Automatikbetrieb';
} else if (_data === 1) {
return 'Nennlüftung';
} else if (_data === 3) {
return 'Reduzierte Lüftung';
} else {
throw '';
}
} else {
throw '';
}

}
else if (type === 'DPT_HVACMode') {`

meine geänderte Version
} else if (datapoints[dp].name === 'Programmwahl CWL') { if (_data === 0) { return 'Intensivlüftung'; } else if (_data === 1) { return 'Nennlüftung'; } else if (_data === 3) { return 'Reduzierte Lüftung'; } else if (_data == 2) { return 'Feuchteschutz'; } else { throw ''; } } } else if (type === 'DPT_HVACMode') {

Man kann dann mit der 149 in Verbindung mit 153 und 158 4 Geschwindigkeiten der Lüftung steuern

Grüße Klaus

Think about update stable version to 1.2.0

Version: stable=0.9.2 (1203 days old) => latest=1.2.0 (15 days old)
Installs: stable=129 (82.69%), latest=18 (11.54%), total=156
Click to edit

Hi Guys,

since a few days I get the following Error on a daily basis:

error | Socket error: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed

Does someone know what this is or how I can deactivate it?

Thx,

Claus

Hi, habe den Wolf ISM7 Adapter,

wie baue ich den zu diesem Kontakt auf? Ich kann ja nirgendwo die IP eingeben...
Allgemein wie funktioniert der Adapter und wie nutze ich Ihn ?