unclesamswiss / iobroker.luxtronik2 Goto Github PK

View Code? Open in Web Editor NEW

11.0 11.0 12.0 965 KB

ioBroker adapter that connects to Luxtronik heatpump controllers

License: Apache License 2.0

Dockerfile 0.12% JavaScript 19.82% HTML 6.51% CSS 1.05% TypeScript 72.49%

iobroker-adapter luxtronik2

iobroker.luxtronik2's People

Contributors

Stargazers

Watchers

Forkers

tbsjah iobrokertranslator germanbluefox apollon77 derelvis der-obi protree mhuberas24 boellner michiproep iobroker-archive

iobroker.luxtronik2's Issues

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/UncleSamSwiss/ioBroker.luxtronik2

[E605] No actual year found in copyright. Please add "Copyright (c) 2022 UncleSamSwiss [email protected]" at the end of README.md

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

Timer table configurations

Is there a possibility that the time tables are also retrieved and editable?

` // ---- Timer table configurations ----

    // Activated timer table for heating operation.
    // Possible values: 0=week (monday-sunday), 1=5+2 (monday-friday), 2=days (mo, tue, ...)
    'heatingOperationTimerTableSelected': heatpumpParameters[222],
    'heatingOperationTimerTableSelectedString': utils.createTimerTableTypeString(heatpumpParameters[222]), // string representation
    // heating operation table 0: week
    'heatingOperationTimerTableWeek': utils.createTimerTable(heatpumpParameters, 223, 3), // 223..528
    // heating operation table 1: 5+2
    'heatingOperationTimerTable52MonFri': utils.createTimerTable(heatpumpParameters, 229, 3), // 229..234
    'heatingOperationTimerTable52SatSun': utils.createTimerTable(heatpumpParameters, 235, 3), // 235..240
    // heating operation table 2: day
    'heatingOperationTimerTableDaySunday': utils.createTimerTable(heatpumpParameters, 241, 3), // 241..246
    'heatingOperationTimerTableDayMonday': utils.createTimerTable(heatpumpParameters, 247, 3), // 247..252
    'heatingOperationTimerTableDayTuesday': utils.createTimerTable(heatpumpParameters, 253, 3), // 253..258
    'heatingOperationTimerTableDayWednesday': utils.createTimerTable(heatpumpParameters, 259, 3), // 259..264
    'heatingOperationTimerTableDayThursday': utils.createTimerTable(heatpumpParameters, 265, 3), // 265..270
    'heatingOperationTimerTableDayFriday': utils.createTimerTable(heatpumpParameters, 271, 3), // 271..276
    'heatingOperationTimerTableDaySaturday': utils.createTimerTable(heatpumpParameters, 277, 3), // 277..282

    // Activated timer table for hot water operation.
    // Possible values: 0=week (monday-sunday), 1=5+2 (monday-friday), 2=days (mo, tue, ...)
    'hotWaterOperationTimerTableSelected': heatpumpParameters[405],
    'hotWaterOperationTimerTableSelectedString': utils.createTimerTableTypeString(heatpumpParameters[405]), // string representation

    // Important: hot water operation table specifies operation in inverse logic. Therefore swap the on/off times.
    // hot water operation table 0: week.
    'hotWaterOperationTimerTableWeek': utils.createTimerTable(heatpumpParameters, 406, 5, true), // 406..415
    // hot water operation table 1: 5+2
    'hotWaterOperationTimerTable52MonFri': utils.createTimerTable(heatpumpParameters, 416, 5, true), // 416..425
    'hotWaterOperationTimerTable52SatSun': utils.createTimerTable(heatpumpParameters, 426, 5, true), // 426..435
    // hot water operation table 2: day
    'hotWaterOperationTimerTableDaySunday': utils.createTimerTable(heatpumpParameters, 436, 5, true), // 436..445
    'hotWaterOperationTimerTableDayMonday': utils.createTimerTable(heatpumpParameters, 446, 5, true), // 446..455
    'hotWaterOperationTimerTableDayTuesday': utils.createTimerTable(heatpumpParameters, 456, 5, true), // 456..465
    'hotWaterOperationTimerTableDayWednesday': utils.createTimerTable(heatpumpParameters, 466, 5, true), // 466..475
    'hotWaterOperationTimerTableDayThursday': utils.createTimerTable(heatpumpParameters, 476, 5, true), // 476..485
    'hotWaterOperationTimerTableDayFriday': utils.createTimerTable(heatpumpParameters, 486, 5, true), // 486..495
    'hotWaterOperationTimerTableDaySaturday': utils.createTimerTable(heatpumpParameters, 496, 5, true), // 496..505

    // Activated timer table for hot water circulation pump.
    // Possible values: 0=week (monday-sunday), 1=5+2 (monday-friday), 2=days (mo, tue, ...)
    'hotWaterCircPumpTimerTableSelected': heatpumpParameters[506],
    'hotWaterCircPumpTimerTableSelectedString': utils.createTimerTableTypeString(heatpumpParameters[506]), // string representation
    // hot water circulation pump table 0: week
    'hotWaterCircPumpTimerTableWeek': utils.createTimerTable(heatpumpParameters, 507, 5), // 507..516
    // hot water circulation pump table 1: 5+2
    'hotWaterCircPumpTimerTable52MonFri': utils.createTimerTable(heatpumpParameters, 517, 5), // 517..526
    'hotWaterCircPumpTimerTable52SatSun': utils.createTimerTable(heatpumpParameters, 527, 5), // 527..536
    // hot water circulation pump table 2: day
    'hotWaterCircPumpTimerTableDaySunday': utils.createTimerTable(heatpumpParameters, 537, 5), // 537..546
    'hotWaterCircPumpTimerTableDayMonday': utils.createTimerTable(heatpumpParameters, 547, 5), // 547..556
    'hotWaterCircPumpTimerTableDayTuesday': utils.createTimerTable(heatpumpParameters, 557, 5), // 557..566
    'hotWaterCircPumpTimerTableDayWednesday': utils.createTimerTable(heatpumpParameters, 567, 5), // 567..576
    'hotWaterCircPumpTimerTableDayThursday': utils.createTimerTable(heatpumpParameters, 577, 5), // 577..586
    'hotWaterCircPumpTimerTableDayFriday': utils.createTimerTable(heatpumpParameters, 587, 5), // 587..596
    'hotWaterCircPumpTimerTableDaySaturday': utils.createTimerTable(heatpumpParameters, 597, 5), // 597..606

    'hotWaterCircPumpOnTime': heatpumpParameters[697], // Time in minutes the circ pump is turned on within one cycle.
    'hotWaterCircPumpOffTime': heatpumpParameters[698] // Time in minutes the circ pump is turned off within one cycle.`

Luxtronik read error: Error: heatpump busy

Meldung sollte als Warnung ausgegeben werden und nicht als Error

Hysterese writable

Would be very good if the values luxtronik2.0.Einstellungen.Temperaturen.Hysterese-WW / luxtronik2.0.Einstellungen.Temperaturen.Hysterese-HR were also editable.

Both are created as write. However, the changes are not transferred.

parameters without any data

Hi uncleSam,
I just managed to get your adapter running.
Thanks for your work!

I have an AlphaInnotec SWC 82K3 and my firmware is 3.85.0
The adapter connects succesfully but to achieve this, i have to leave the luxtronik-port empty.
I can see all the values, that are viewable in the webinterface.
But ultimately i want to change values. I guess for this, there is the folder "parameters".
But for me, all the datafields in parameters are empty.
The log gives no errors. I tried different luxtronic ports (8888, 8889, 8214) but when i enter a port number, the adapter fails to run.
if i try port 8888 the log just states "connection refused", while if i try port 8889 it gives an many errors:

luxtronik2.0	2021-01-14 09:48:17.484	error	at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
luxtronik2.0	2021-01-14 09:48:17.484	error	at Socket.Readable.push (_stream_readable.js:223:10)
luxtronik2.0	2021-01-14 09:48:17.484	error	at readableAddChunk (_stream_readable.js:284:9)
luxtronik2.0	2021-01-14 09:48:17.484	error	at addChunk (_stream_readable.js:309:12)
luxtronik2.0	2021-01-14 09:48:17.484	error	at Socket.emit (events.js:315:20)
luxtronik2.0	2021-01-14 09:48:17.484	error	at Luxtronik. (/opt/iobroker/node_modules/luxtronik2/luxtronik.js:409:37)
luxtronik2.0	2021-01-14 09:48:17.484	error	at Buffer.readInt32BE (internal/buffer.js:479:5)
luxtronik2.0	2021-01-14 09:48:17.484	error	at boundsError (internal/buffer.js:83:9)
luxtronik2.0	2021-01-14 09:48:17.484	error	(1446) RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 0. Received 4
luxtronik2.0	2021-01-14 09:48:17.483	error	(1446) uncaught exception: The value of "offset" is out of range. It must be >= 0 and <= 0. Received 4

Wassertemperatur Soll automatisch erhöht

Die Soll Temperatur wird um 0,5°C erhöht.
Ursache scheint zu sein wenn die LWP nicht erreichbar ist

Siehe Log

Und Tabelleneintrag

Hängt vielleicht aber auch mit dem luxtronik2.0.parameters.temperature_hot_water_target Parameter zusammen
Beide unterscheiden sich bei mir

More errors after Update to 0.4.1

After updating to version 0.4.1 I get more error messages

Adapter: 0.4.2 - luxtronik2.0 (30738) Cannot read property 'toString' of undefined

Thanks for the adapter I´ve discovered yesterday my first time.

I installed the adapter but the adapter crashed see the log attached.

I´m using the Luxtronik2 from alpha-innotec and the websocket port is 8214 double-checked with wireshark.
using a browser connecting to tthe webserver it shows me
HeatControllertType: LD7REV
Software-Version: V4.81
Bivalenz Step: 2

Is there any other thing to consider to get your adapter up and running?

Thanks for your support!!!

Versions:

Adapter version: 0.4.2
JS-Controller version: 3.3.18
Node version: v12.22.6
Operating system: Linux iobroker-pi 5.10.63-v7+ #1457 SMP Tue Sep 28 11:25:31 BST 2021 armv7l GNU/Linux

Additional context
Add any other context about the problem here.
Luxtronik2.txt

Unknown data

I had a total breakdown of my Raspberry the day before yesterday.
Yesterday I restored the backup. Since then I have been getting the messages shown.

Fail: Unknown data item parameters.solarPumpDeaerate | runDeaerate

Ich habe folgende Fehler im iO-Log:

warn | Unknown data item parameters.solarPumpDeaerate
warn | Unknown data item parameters.runDeaerate

muss ich hier was im Installateur - Modus deaktivieren ?

MODELL: Roth ThermoAura

.Betriebszustand" has to be type "number" but received type "string"

Object has wrong type
should be string

seit Firmware 3.89.1 >> Couldn't handle 'Informationen.Energiemonitor'

Seit Upgrade zu Firmware 3.89.1 (SWC 142 K3) erhalte ich folgende Error:
luxtronik2.0 | 2023-09-11 22:42:22.477 | warn | Unknown data item parameters.runDeaerate
luxtronik2.0 | 2023-09-11 22:42:22.476 | warn | Unknown data item parameters.solarPumpDeaerate
luxtronik2.0 | 2023-09-11 22:42:19.067 | error | Couldn't handle 'Informationen.Energiemonitor' -> 'Eingesetzte Energie': Error: setStateAsync() not supported on section.
luxtronik2.0 | 2023-09-11 22:42:19.065 | error | Couldn't handle 'Informationen.Energiemonitor' -> 'Wärmemenge': Error: setStateAsync() not supported on section.

See Debug File
iobroker.current.log.zip

Datenpunkt luxtronik2.0.Informationen.Anlagenstatus.Betriebszustand wird nicht aktualisiert

luxtronik2.0.Informationen.Anlagenstatus.Betriebszustand Zeigt Wert an
Wird aber nicht gespeichert in der Tabelle
Änderungen werden nicht erkannt

heating_curve_parallel_offset RL nicht editierbar

Eingabe nicht möglich für luxtronik2.0.parameters.heating_curve_parallel_offset

Fehlerreport Couldn't handle 'Informationen.Energiemonitor'

Describe the bug
Habe eine neue Alpha Innotec mit Luxtronic 2.1 in der Software Version V3.88.0 , Rev. 9015 seit einigen Tagen installiert. Habe immer wieder Fehlermeldungen im Log und das der Adapter neu startet. Daten kommen jedoch regelmässig rein.

To Reproduce
Adapter verbunden über Websocket Port 8214, Luxtronic Port ist leer

Screenshots & Logfiles

uxtronik2.0	2023-05-18 09:09:41.048	error	Couldn't handle 'Informationen.Energiemonitor' -> 'Eingesetzte Energie': Error: setStateAsync() not supported on section.
luxtronik2.0	2023-05-18 09:09:41.048	error	Couldn't handle 'Informationen.Energiemonitor' -> 'Wärmemenge': Error: setStateAsync() not supported on section.
luxtronik2.0	2023-05-18 09:09:37.445	debug	{"Content":{"item":[{"$":{"id":"0x8a83b4"},"name":["Temperaturen","Temperaturen"],"item":[{"$":{"id":"0x8a8c8c"},"name":["Vorlauf"],"value":["22.9°C"]},{"$":{"id":"0x8a8d64"},"name":["Rücklauf"],"value":["22.6°C"]},{"$":{"id":"0x8a914c"},"name":["Rückl.-Soll"],"value":["24.2°C"]},{"$":{"id":"0x8a9184"},"name":["Rückl.-Extern"],"value":["22.9°C"]},{"$":{"id":"0x8a67ec"},"name":["Heissgas"],"value":["24.9°C"]},{"$":{"id":"0x8a91cc"},"name":["Außentemperatur"],"value":["10.6°C"]},{"$":{"id":"0x8a9214"},"name":["Mitteltemperatur"],"value":["11.0°C"]},{"$":{"id":"0x89eb94"},"name":["Warmwasser-Ist"],"value":["61.3°C"]},{"$":{"id":"0x89012c"},"name":["Warmwasser-Soll"],"value":["52.0°C"]},{"$":{"id":"0x8a67a4"},"name":["Wärmequelle-Ein"],"value":["12.7°C"]},{"$":{"id":"0x89ec24"},"name":["Wärmequelle-Aus"],"value":["13.4°C"]},{"$":{"id":"0x8a94ec"},"name":["Mischkreis2-Vorlauf"],"value":["22.9°C"]},{"$":{"id":"0x8a9534"},"name":["Mischkreis2 VL-Soll"],"value":["18.0°C"]},{"$":{"id":"0x8aa5b4"},"name":["Solarkollektor"],"value":["5.0°C"]},{"$":{"id":"0x8aa5fc"},"name":["Solarspeicher"],"value":["150.0°C"]},{"$":{"id":"0x8aa644"},"name":["Externe Energ.Quelle"],"value":["5.0°C"]},{"$":{"id":"0x8a8cd4"},"name":["Vorlauf max."],"value":["66.0°C"]},{"$":{"id":"0x8a5c94"},"name":["Ansaug VD"],"value":["20.6°C"]},{"$":{"id":"0x8a5694"},"name":["VD-Heizung"],"value":["27.2°C"]},{"$":{"id":"0x8a56dc"},"name":["Überhitzung"],"value":["-1.6 K"]}]},{"$":{"id":"0x8a64e4"},"name":["Eingänge","Eingänge"],"item":[{"$":{"id":"0x8aa94c"},"name":["ASD"],"value":["Ein"]},{"$":{"id":"0x8aaa9c"},"name":["EVU"],"value":["Ein"]},{"$":{"id":"0x8a59bc"},"name":["HD"],"value":["Aus"]},{"$":{"id":"0x8aaae4"},"name":["MOT"],"value":["Ein"]},{"$":{"id":"0x8aac04"},"name":["AIn 21"],"value":["0.01 V"]},{"$":{"id":"0x8a997c"},"name":["AIn 22"],"value":["0.01 V"]},{"$":{"id":"0x8aa8bc"},"name":["HD"],"value":["8.03 bar"]},{"$":{"id":"0x8aa904"},"name":["ND"],"value":["8.39 bar"]},{"$":{"id":"0x8add54"},"name":["Durchfluss"],"value":["--- l/h"]}]},{"$":{"id":"0x8a7804"},"name":["Ausgänge","Ausgänge"],"item":[{"$":{"id":"0x8ae33c"},"name":["BUP"],"value":["Aus"]},{"$":{"id":"0x8ae384"},"name":["FUP 1"],"value":["Ein"]},{"$":{"id":"0x8ae3cc"},"name":["HUP"],"value":["Ein"]},{"$":{"id":"0x8ae2f4"},"name":["Ventil.-BOSUP"],"value":["Aus"]},{"$":{"id":"0x8af62c"},"name":["Verdichter"],"value":["Aus"]},{"$":{"id":"0x8ae534"},"name":["ZIP"],"value":["Aus"]},{"$":{"id":"0x8ae654"},"name":["ZUP"],"value":["Aus"]},{"$":{"id":"0x8af5a4"},"name":["ZWE 1"],"value":["Aus"]},{"$":{"id":"0x8ae21c"},"name":["ZWE 2 - SST"],"value":["Aus"]},{"$":{"id":"0x8ae69c"},"name":["ZWE 3"],"value":["Aus"]},{"$":{"id":"0x8ae6e4"},"name":["SLP"],"value":["Aus"]},{"$":{"id":"0x8ae774"},"name":["Mischer 2 Auf"],"value":["Aus"]},{"$":{"id":"0x8ae7bc"},"name":["Mischer 2 Zu"],"value":["Ein"]},{"$":{"id":"0x89f22c"},"name":["FUP 2"],"value":["Aus"]},{"$":{"id":"0x89f2f4"},"name":["FUP 3"],"value":["Aus"]},{"$":{"id":"0x89f33c"},"name":["AO 1"],"value":["10.00 V"]},{"$":{"id":"0x89f384"},"name":["AO 2"],"value":["0.00 V"]},{"$":{"id":"0x89f45c"},"name":["AO 21"],"value":["0.00 V"]},{"$":{"id":"0x89f4a4"},"name":["AO 22"],"value":["0.00 V"]},{"$":{"id":"0x8ae2ac"},"name":["VD-Heizung"],"value":["Aus"]},{"$":{"id":"0x8a4324"},"name":["Freq. Sollwert"],"value":["0 Hz"]},{"$":{"id":"0x8a43bc"},"name":["Freq. aktuell"],"value":["0 Hz"]},{"$":{"id":"0x8a4524"},"name":["Ventil.-BOSUP"],"value":["0 %"]},{"$":{"id":"0x8a469c"},"name":["ZUP"],"value":["0 %"]}]},{"$":{"id":"0x8a8eac"},"name":["Ablaufzeiten","Ablaufzeiten"],"item":[{"$":{"id":"0x89f724"},"name":["WP Seit"],"value":["00:00:01"]},{"$":{"id":"0x8ad40c"},"name":["ZWE1 seit"],"value":["00:00:00"]},{"$":{"id":"0x8ad454"},"name":["ZWE2 seit"],"value":["00:00:00"]},{"$":{"id":"0x8ad4e4"},"name":["Netzeinschaltv."],"value":["00:00:00"]},{"$":{"id":"0x899644"},"name":["SSP-Zeit"],"value":["00:00:00"]},{"$":{"id":"0x88ded4"},"name":["VD-Stand"],"value":["01:48:08"]},{"$":{"id":"0x8ad52c"},"name":["HRM-Zeit"],"value":["00:00:00"]},{"$":{"id":"0x8ad574"},"name":["HRW-Zeit"],"value":["00:01:18"]},{"$":{"id":"0x8ad5bc"},"name":["TDI seit"],"value":["00:00:00"]},{"$":{"id":"0x8a6b5c"},"name":["Sperre WW"],"value":["00:00:00"]},{"$":{"id":"0x88a1e4"},"name":["Freig. ZWE"],"value":["01:00:00"]},{"$":{"id":"0x8ad724"},"name":["Freigabe Kühlung"],"value":["01:00:00"]}]},{"$":{"id":"0x8a63dc"},"name":["Betriebsstunden","Betriebsstunden"],"item":[{"$":{"id":"0x8aad04"},"name":["Betriebstund. VD1"],"value":["28h"]},{"$":{"id":"0x8ad7ac"},"name":["Impulse Verdichter 1"],"value":["6"]},{"$":{"id":"0x8aaf44"},"name":["Laufzeit Ø VD1"],"value":["04:36"]},{"$":{"id":"0x8ab064"},"name":["Betriebstunden ZWE1"],"value":["0h"]},{"$":{"id":"0x8ab0ac"},"name":["Betriebstunden ZWE2"],"value":["0h"]},{"$":{"id":"0x8ab13c"},"name":["Betriebstunden WP"],"value":["28h"]},{"$":{"id":"0x8ab184"},"name":["Betriebstunden Heiz."],"value":["28h"]},{"$":{"id":"0x8ab1cc"},"name":["Betriebstunden WW"],"value":["0h"]},{"$":{"id":"0x8ab214"},"name":["Betriebstunden Kuehl"],"value":["0h"]}]},{"$":{"id":"0x8a57d4"},"name":["Fehlerspeicher","Fehlerspeicher"],"item":[{"$":{"id":"0x8a4a4c"},"name":["16.03.23 09:59:27"],"value":["Hochdruckstörung (716)"]},{"$":{"id":"0x8a4adc"},"name":["16.03.23 09:59:26"],"value":["Hochdruckstörung (716)"]},{"$":{"id":"0x8a4b6c"},"name":["16.03.23 08:12:38"],"value":["Fühler Aussentemp. (711)"]},{"$":{"id":"0x8a4bfc"},"name":["----"],"value":["----"]},{"$":{"id":"0x8a4c8c"},"name":["----"],"value":["----"]}]},{"$":{"id":"0x8a93d4"},"name":["Abschaltungen","Abschaltungen"],"item":[{"$":{"id":"0x8a50ac"},"name":["18.05.23 07:21:01"],"value":["keine Anf."]},{"$":{"id":"0x8a502c"},"name":["18.05.23 02:56:43"],"value":["keine Anf."]},{"$":{"id":"0x8a4fac"},"name":["18.05.23 00:09:56"],"value":["keine Anf."]},{"$":{"id":"0x8a4f2c"},"name":["17.05.23 21:05:21"],"value":["keine Anf."]},{"$":{"id":"0x8a4eac"},"name":["17.05.23 12:25:06"],"value":["keine Anf."]}]},{"$":{"id":"0x8a9cf4"},"name":["Anlagenstatus","Anlagenstatus"],"item":[{"$":{"id":"0x89fd0c"},"name":["Wärmepumpen Typ"],"value":["MSW2-9S"]},{"$":{"id":"0x898044"},"name":["Softwarestand"],"value":["V3.88.0"]},{"$":{"id":"0x899eac"},"name":["Revision"],"value":["9015"]},{"$":{"id":"0x8ae894"},"name":["Max/IO"],"value":[" Revision:8889 CPU:3 "]},{"$":{"id":"0x8ae8dc"},"name":["Bedienteil"],"value":[" Revision:2003 "]},{"$":{"id":"0x8a5294"},"name":["Inverter SW Version"],"value":["47"]},{"$":{"id":"0x8aeb14"},"name":["Bivalenz Stufe"],"value":["1"]},{"$":{"id":"0x8a3eac"},"name":["Betriebszustand"],"value":[""]},{"$":{"id":"0x8aeb5c"},"name":["Leistung Ist"],"value":["0.00 kW"]}]},{"$":{"id":"0x8a9654"},"name":["Energiemonitor","Energiemonitor"],"item":[{"$":{"id":"0x8aeabc"},"name":["Wärmemenge","Wärmemenge"],"item":[{"$":{"id":"0x8b05d4"},"name":["Heizung"],"value":["80.4 kWh"]},{"$":{"id":"0x8b0d14"},"name":["Warmwasser"],"value":["0.0 kWh"]},{"$":{"id":"0x8b0d9c"},"name":["Kühlung"],"value":["0.0 kWh"]},{"$":{"id":"0x8b0b54"},"name":["Gesamt"],"value":["80.4 kWh"]}]},{"$":{"id":"0x8aeec4"},"name":["Eingesetzte Energie","Eingesetzte Energie"],"item":[{"$":{"id":"0x8b0c14"},"name":["Heizung"],"value":["7.1 kWh"]},{"$":{"id":"0x8b12cc"},"name":["Warmwasser"],"value":["0.0 kWh"]},{"$":{"id":"0x8b1a0c"},"name":["Kühlung"],"value":["0.0 kWh"]},{"$":{"id":"0x8b1a54"},"name":["Gesamt"],"value":["7.1 kWh"]}]}]},{"$":{"id":"0x8a969c"},"name":["GLT","GLT"],"item":[{"$":{"id":"0x8b198c"},"name":["Art"],"value":["Aus"]}]}],"name":["Informationen"]}}
luxtronik2.0	2023-05-18 09:09:37.399	debug	Getting 0x818730

Versions:

Adapter version: 0.4.2
JS-Controller version: 18.16.0
NPM: 9.5.1

Restart loop

Hi,
Ich bekomme immer wieder im Log den folgenden Ablauf:

luxtronik2.0	2022-02-12 08:22:51.801	info	terminating with timeout
luxtronik2.0	2022-02-12 08:22:51.498	info	terminating
luxtronik2.0	2022-02-12 08:22:51.495	info	Terminated (NO_ERROR): Without reason
luxtronik2.0	2022-02-12 08:22:51.493	info	terminating
luxtronik2.0	2022-02-12 08:22:50.297	warn	Restart initiated
luxtronik2.0	2022-02-12 08:22:50.221	error	Didn't receive data from Lux port after 3 retries, restarting adapter
luxtronik2.0	2022-02-12 08:17:55.169	info	Connecting to 192.168.178.16:8889
luxtronik2.0	2022-02-12 08:17:46.790	info	Connected to ws://192.168.178.16:8214
luxtronik2.0	2022-02-12 08:17:46.771	info	Connecting to ws://192.168.178.16:8214
luxtronik2.0	2022-02-12 08:17:44.325	info	starting. Version 0.4.2 in /opt/iobroker/node_modules/iobroker.luxtronik2, node: v14.19.0, js-controller: 3.3.22
`

Habe ich etwas falsch eingestellt?
Danke!

Erstellung eines falschen Datenpunkts

Ich habe eine Alpha Innotec Wärmepumpe mit Luxtronik2.

Soweit funktioniert alles. Nun ist mir aber folgendes aufgefallen:

Wird die Heizgrenze der Heizung an der Wärmepumpe verstellt (bei mir von 10 -> 11) kommt es zu einer Warnmeldung und es wird ein neuer Datenpunkt angelegt.

Der Wert des richtigen Datenpunkts luxtronik2.0.parameters.thresholdHeatingLimit stimmt auch überein.

Problem ist die Anlegung des Datenpunkts luxtronik2.0.Informationen.Wärmemenge.11-0_C

Adapter crashing: Cannot read properties of null (reading 'end')

Describe the bug
Adapter terminating with error "Cannot read properties of null (reading 'end')"

Screenshots & Logfiles

host.homebridge	2022-06-16 22:04:49.559	warn	Do not restart adapter system.adapter.luxtronik2.0 because restart loop detected
host.homebridge	2022-06-16 22:04:49.559	info	Restart adapter system.adapter.luxtronik2.0 because enabled
host.homebridge	2022-06-16 22:04:49.557	error	instance system.adapter.luxtronik2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
luxtronik2.0	2022-06-16 22:04:48.965	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
luxtronik2.0	2022-06-16 22:04:48.963	info	terminating
luxtronik2.0	2022-06-16 22:04:48.955	error	Cannot read properties of null (reading 'end')
luxtronik2.0	2022-06-16 22:04:48.953	error	TypeError: Cannot read properties of null (reading 'end') at Luxtronik._nextJob (/opt/iobroker/node_modules/luxtronik2/luxtronik.js:444:21) at processTicksAndRejections (node:internal/process/task_queues:78:11)
luxtronik2.0	2022-06-16 22:04:48.951	error	uncaught exception: Cannot read properties of null (reading 'end')
luxtronik2.0	2022-06-16 22:04:48.945	error	Cannot read properties of null (reading 'end')
luxtronik2.0	2022-06-16 22:04:48.943	error	TypeError: Cannot read properties of null (reading 'end') at Luxtronik._nextJob (/opt/iobroker/node_modules/luxtronik2/luxtronik.js:444:21) at processTicksAndRejections (node:internal/process/task_queues:78:11)
luxtronik2.0	2022-06-16 22:04:48.941	error	uncaught exception: Cannot read properties of null (reading 'end')
luxtronik2.0	2022-06-16 22:04:48.932	error	Luxtronik read error, will retry later: Error: Missing element at luxtronik response to 3005

Versions:

Adapter version: 0.4.2
JS-Controller version: 5.7.0
Novelan/Luxtronik Firmware: 3.87

Eingabe Temperaturen (Wasser, RL, VL...)

Zur besseren Übersichtlichkeit sollten Werte wie

VL Temp (luxtronik2.0.parameters.heating_curve_end_point)
RL Temp.(luxtronik2.0.parameters.heating_curve_parallel_offset)
Wasser Soll (luxtronik2.0.parameters.warmwater_temperature / luxtronik2.0.parameters.temperature_hot_water_target)
Parallelverschiebung (luxtronik2.0.parameters.heating_temperature / returnTemperatureSetBack)
Modus Wasser (luxtronik2.0.parameters.warmwater_operation_mode)
Modus Heizung (luxtronik2.0.parameters.heating_operation_mode)

In ein eigenes "Verzeichnis" (Bsp. Benutzereingabe) abgelegt werden

Sentry: No name for handler: Informationen.Fehlerspeicher.

https://sentry.iobroker.net/share/issue/71da0e8f9add40dca45c233fa4dc56c8/

temperature_hot_water_target wird nicht nach Änderung aktualisert

Nach Eingabe bei
luxtronik2.0.parameters.warmwater_temperature wird der Wert bei luxtronik2.0.parameters.temperature_hot_water_target nicht aktualisiert

Werte werden jedoch korrekt von Regler übernommen

Unknown data item

My heatpump Alpha Innotec HMD_9_LWD LD9V V3.87.1

Adapter crashes continuously.

First of all thank you for starting the work on the adapter.

I installed the Adapter changes the port and entered the password. On the first sight everything was fine, but after a while a lot of failures dropped in until restart of the adapter.

System:
Iobroker on Raspi4 (3.3.18)
Node.js. v12.22.7
NPM. 6.14.15

see extract:

luxtronik2.0	2021-10-30 09:14:32.104	warn	Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
luxtronik2.0	2021-10-30 09:14:32.048	error	adapter disabled
luxtronik2.0	2021-10-30 09:13:57.507	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
luxtronik2.0	2021-10-30 09:13:57.506	info	terminating
luxtronik2.0	2021-10-30 09:13:57.489	error	Exception-Code: ERR_OUT_OF_RANGE: The value of "offset" is out of range. It must be >= 0 and <= 4. Received 8
luxtronik2.0	2021-10-30 09:13:57.488	error	RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 4. Received 8 at boundsError (internal/buffer.js:82:9) at Buffer.readInt32BE (internal/buffer.js:478:5) at Luxtronik. (/opt/iobroker/node_modules/luxtronik2/luxtronik.js:480:41) at Socket.emit (events.js:314:20) at Socket.EventEmitter.emit (domain.js:483:12) at addChunk (_stream_readable.js:297:12) at readableAddChunk (_stream_readable.js:272:9) at Socket.Readable.push (_stream_readable.js:213:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
luxtronik2.0	2021-10-30 09:13:57.487	error	uncaught exception: The value of "offset" is out of range. It must be >= 0 and <= 4. Received 8

Any idea?
Stephan

heating_operation_mode wird falsch angezeigt

Getestet mit: v0.1.1

Habe den heating_operation_mode mit dem Wert 3 geschrieben. Hat auch funktioniert. Allerdings wurde nach dem nächsten Lesen "Aus(3)" angezeigt, müsste aber "Ferien(3)" lauten. Beim heating_operation_mode_string war aber richtigerweise "Ferien" zu lesen.

MK warnings

i do not have a "Mischkreis"
Think this will be the reason that i got a lot of wanings (every pull)

Couldn't handle 'Informationen.Energiemonitor'

Since the update to the firmware version wp2reg-V3.88.0-9015 the values for the "Wärmemenge" und "Eingesetzte Energie" are no longer read:

luxtronik2.0 2023-01-21 10:48:53.092 error Couldn't handle 'Informationen.Energiemonitor' -> 'Wärmemenge': Error: setStateAsync() not supported on section.
luxtronik2.0 2023-01-21 10:48:32.709 error Couldn't handle 'Informationen.Energiemonitor' -> 'Eingesetzte Energie': Error: setStateAsync() not supported on section.

IOBroker:
Version: v6.3.5
Plattform: linux
RAM: 971.6 MB
Node.js: v14.21.1
NPM: 6.14.17
Adapter: luxtronik2 v0.4.2

Heatpump:
Manufacturer: Alpha-Innotec
Product: SWC122H3
Steering: Luxtronik 2.0
Firmware new: wp2reg-V3.88.0-9015
Firmware old: wp2reg-V3.87.1-8454

Please add ventilation properties

Hi,

Luxtronik2 is also used to control Ventilation. This is not yet reflected in the parameter object catalogue. It would be great to add the parameters to actively control the operation modes

Automatic
Holiday
Party
Off

I have the Model "alpha innotec KHZ LW80" in use.

Thank you, bye.

heating_curve_end_point VL nicht editierbar

Eingabe nicht möglich für luxtronik2.0.parameters.heating_curve_end_point

Keine Verbindung nach Firmwareupdate

Empty Values heatSourceDefrostAirEnd / heatSourceDefrostAirEnd

Got WebSocket error / ERR_OUT_OF_RANGE

Describe the bug
Etwa einmal täglich wird der Adapter jeweils mit den beiden Fehlermeldungen beendet.

Screenshots & Logfiles

luxtronik2.0 | 31095 | 2021-10-11 03:34:42.121 | error | Got WebSocket error Error: connect EHOSTUNREACH 192.168.178.33:8214
-- | -- | -- | -- | --
luxtronik2.0 | 31095 | 2021-10-11 03:34:42.078 | error | Luxtronik read error, will retry later: Error: connect EHOSTUNREACH 192.168.178.33:8889
luxtronik2.0 | 29101 | 2021-10-11 03:34:02.828 | error | Didn't receive data from WebSocket after 3 retries, restarting adapter
luxtronik2.0 | 24324 | 2021-10-11 03:22:50.598 | error | Didn't receive data from Lux port after 3 retries, restarting adapter
host.raspberrypi |   | 2021-10-11 02:57:05.987 | error | instance system.adapter.luxtronik2.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.raspberrypi |   | 2021-10-11 02:57:05.986 | error | Caught by controller[0]: at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
host.raspberrypi |   | 2021-10-11 02:57:05.986 | error | Caught by controller[0]: at Socket.Readable.push (internal/streams/readable.js:204:10)
host.raspberrypi |   | 2021-10-11 02:57:05.986 | error | Caught by controller[0]: at readableAddChunk (internal/streams/readable.js:265:9)
host.raspberrypi |   | 2021-10-11 02:57:05.985 | error | Caught by controller[0]: at addChunk (internal/streams/readable.js:290:12)
host.raspberrypi |   | 2021-10-11 02:57:05.985 | error | Caught by controller[0]: at Socket.emit (domain.js:470:12)
host.raspberrypi |   | 2021-10-11 02:57:05.984 | error | Caught by controller[0]: at Socket.emit (events.js:400:28)
host.raspberrypi |   | 2021-10-11 02:57:05.984 | error | Caught by controller[0]: at Luxtronik.<anonymous> (/opt/iobroker/node_modules/iobroker.luxtronik2/node_modules/luxtronik2/luxtronik.js:480:41)
host.raspberrypi |   | 2021-10-11 02:57:05.983 | error | Caught by controller[0]: at Buffer.readInt32BE (internal/buffer.js:479:5)
host.raspberrypi |   | 2021-10-11 02:57:05.982 | error | Caught by controller[0]: at boundsError (internal/buffer.js:83:9)
host.raspberrypi |   | 2021-10-11 02:57:05.975 | error | Caught by controller[0]: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 4. Received 8
luxtronik2.0 | 16321 | 2021-10-11 02:57:05.833 | error | Exception-Code: ERR_OUT_OF_RANGE: The value of "offset" is out of range. It must be >= 0 and <= 4. Received 8
luxtronik2.0 | 16321 | 2021-10-11 02:57:05.832 | error | RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 4. Received 8 at boundsError (internal/buffer.js:83:9) at Buffer.readInt32BE (internal/buffer.js:479:5) at Luxtronik.<anonymous> (/opt/iobroker/node_modules/iobroker.luxtronik2/node_modules/luxtronik2/luxtronik.js:480:41) at Socket.emit (events.js:400:28) at Socket.emit (domain.js:470:12) at addChunk (internal/streams/readable.js:290:12) at readableAddChunk (internal/streams/readable.js:265:9) at Socket.Readable.push (internal/streams/readable.js:204:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
luxtronik2.0 | 16321 | 2021-10-11 02:57:05.827 | error | uncaught exception: The value of "offset" is out of range. It must be >= 0 and <= 4. Received 8

Versions:

Adapter version: 0.3.2
Node version: 14.17.5
Operating system: Linux (RPi)

Abschaltungen

Bestehende DP werden nicht mit den neuen Werten aktualisiert
Es werden neue DP angelegt

Bug oder Feature?
Evtl in Optionen Auswahl wie viele Einträge behalten werden sollen
Der Rest wird gelöscht

Warmwasser_extra

Hi,

would be interessted to start my heatpump if weahter is nice outside and my PV system generates enough energy. From my understanting the only possibility to request the heatpump to start heating the water is by setting the Warmwasser_extra parameter.
There is a python luxtronik script availabe which specify the following parameter

1052: Unknown("ID_Einst_Warmwasser_extra")

Would it be possible to integrate this parameter in the iobroker adapter?

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!

Fehler: uncaught exception: The value of "offset" is out of range. It must be >= 0 and <= 0. Received 4

Ich bekomme bei jeder Aktualisierung folgenden Fehler:

> 2020-12-26 00:08:58.455  - error: luxtronik2.0 (1791) uncaught exception: The value of "offset" is out of range. It must be >= 0 and <= 0. Received 4
> --
> 2020-12-26 00:08:58.456  - error:  luxtronik2.0 (1791) RangeError [ERR_OUT_OF_RANGE]: The value of  "offset" is out of range. It must be >= 0 and <= 0. Received 4
> at boundsError (internal/buffer.js:82:9)
> at Buffer.readInt32BE (internal/buffer.js:478:5)
> at Luxtronik. (/opt/iobroker/node_modules/luxtronik2/luxtronik.js:406:37)
> at Socket.emit (events.js:314:20)
> at addChunk (_stream_readable.js:297:12)
> at readableAddChunk (_stream_readable.js:272:9)
> at Socket.Readable.push (_stream_readable.js:213:10)
> at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
> 2020-12-26 00:08:58.464  - info: luxtronik2.0 (1791) terminating
> 2020-12-26 00:08:58.465  - info: luxtronik2.0 (1791) Terminated (NO_ERROR): Without reason
> 2020-12-26 00:08:58.496  - error: luxtronik2.0 (1791) uncaught exception: The value of "offset" is out of range. It must be >= 0 and <= 0. Received 4
> 2020-12-26 00:08:58.496  - error:  luxtronik2.0 (1791) RangeError [ERR_OUT_OF_RANGE]: The value of  "offset" is out of range. It must be >= 0 and <= 0. Received 4
> at boundsError (internal/buffer.js:82:9)
> at Buffer.readInt32BE (internal/buffer.js:478:5)
> at Luxtronik. (/opt/iobroker/node_modules/luxtronik2/luxtronik.js:390:37)
> at Socket.emit (events.js:314:20)
> at addChunk (_stream_readable.js:297:12)
> at readableAddChunk (_stream_readable.js:272:9)
> at Socket.Readable.push (_stream_readable.js:213:10)
> at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
> 2020-12-26 00:08:58.535  - error: luxtronik2.0 (1791) uncaught exception: The value of "offset" is out of range. It must be >= 0 and <= 0. Received 4
> 2020-12-26 00:08:58.536  - error:  luxtronik2.0 (1791) RangeError [ERR_OUT_OF_RANGE]: The value of  "offset" is out of range. It must be >= 0 and <= 0. Received 4
> at boundsError (internal/buffer.js:82:9)
> at Buffer.readInt32BE (internal/buffer.js:478:5)
> at Luxtronik. (/opt/iobroker/node_modules/luxtronik2/luxtronik.js:406:37)
> at Socket.emit (events.js:314:20)
> at addChunk (_stream_readable.js:297:12)
> at readableAddChunk (_stream_readable.js:272:9)
> at Socket.Readable.push (_stream_readable.js:213:10)
> at TCP.onStreamRead (internal/stream_base_commons.js:188:23)

Wärmepumpe: Alha-Innotec
Softwarestand: V3.85.1 (r5783)

Edit: Log Output formatiert

"Mischkreis1" (MK1) Heizkurve fehlt

Ich habe die Heizkurve für den MK1 nicht gefunden. Die Heizkurve für den Heizkreis ist vorhanden und kann man auch erfolgreich setzen (heating_curve_end_point und heating_curve_parallel_offset). Wäre es viel Aufwand, die zwei Werte für den Mischkreis MK1 auch hinzuzunehmen?
Danke und Grüße

"Fehlerspeicher" will be updated ever few seconds

More than 80,000 entries have already been created. Happens since the controller on the heater was replaced

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!

Update stable version in repo from 0.0.0 to 0.4.2

Think about adding version 0.4.2 to stable repository.

Version: stable=0.0.0 (0 days old) => latest=0.4.2 (517 days old)
Installs: stable=0 (0%), latest=230 (82.44%), total=279
Click to edit

unclesamswiss / iobroker.luxtronik2 Goto Github PK

iobroker.luxtronik2's People

Contributors

Stargazers

Watchers

Forkers

iobroker.luxtronik2's Issues

Think about adding version 0.4.2 to stable repository.

Recommend Projects

Recommend Topics

Recommend Org