Integration stopped working yesterday: Received message has unexpected length. (expected: 113 got: 114) (2584)

iamthe1st commented 6 months ago

Logger: custom_components.nano_pk.hargassner Quelle: custom_components/nano_pk/hargassner.py:196 Integration: Hargassner Nano-PK (Dokumentation) Erstmals aufgetreten: 09:31:57 (2586 Vorkommnisse) Zuletzt protokolliert: 10:22:47

Received message has unexpected length. (expected: 113 got: 114) (2584) Received message has unexpected length. (expected: 113 got: 114) (2585) Received message has unexpected length. (expected: 113 got: 114) (2586) Received message has unexpected length. (expected: 113 got: 114) (2587) Received message has unexpected length. (expected: 113 got: 114) (2588)

Does anybody have the same issue?

iamthe1st commented 6 months ago

I had a look in my cellar: The heating unit made an update yesterday... New: V14.0HAR.o4

Here the new DAQ string, which got the integration working again:

msgformat : "<DAQPRJ><ANALOG><CHANNEL id='0' name='ZK' dop='0'/><CHANNEL id='1' name='O2' unit='%'/><CHANNEL id='2' name='O2soll' unit='%'/><CHANNEL id='3' name='TK' unit='°C'/><CHANNEL id='4' name='TKsoll' unit='°C' dop='0'/><CHANNEL id='5' name='TRL' unit='°C'/><CHANNEL id='6' name='TRLsoll' unit='°C' dop='0'/><CHANNEL id='7' name='Spreizung' unit='°C'/><CHANNEL id='8' name='TRG' unit='°C'/><CHANNEL id='9' name='SZist' unit='%' dop='0'/><CHANNEL id='10' name='SZsoll' unit='%'/><CHANNEL id='11' name='TPo' unit='°C'/><CHANNEL id='12' name='TPm' unit='°C'/><CHANNEL id='13' name='TPu' unit='°C'/><CHANNEL id='14' name='Puff Fuellgrad' unit='%' dop='0'/><CHANNEL id='15' name='Puffer_soll oben' unit='°C' dop='0'/><CHANNEL id='16' name='Puffer_soll unten' unit='°C' dop='0'/><CHANNEL id='17' name='PuffZustand' dop='0'/><CHANNEL id='18' name='Max Anf Kessel' dop='0'/><CHANNEL id='19' name='TFW' unit='°C' dop='0'/><CHANNEL id='20' name='Leistung' unit='%' dop='0'/><CHANNEL id='21' name='ESsoll' unit='%'/><CHANNEL id='22' name='min.Leist.TRG' unit='%'/><CHANNEL id='23' name='max.Leist.TRG' unit='%'/><CHANNEL id='24' name='max.Leist.Fuell' unit='%'/><CHANNEL id='25' name='max.Leist.TPO' unit='%'/><CHANNEL id='26' name='ESRegler' unit='%' dop='0'/><CHANNEL id='27' name='Regler K'/><CHANNEL id='28' name='KeBrstScale' unit='%' dop='0'/><CHANNEL id='29' name='Programm' dop='0'/><CHANNEL id='30' name='Störungs Nr' dop='0'/><CHANNEL id='31' name='Max Anf ZenPuf' unit='°C' dop='0'/><CHANNEL id='32' name='I Es' unit='mA' dop='0'/><CHANNEL id='33' name='I Ra' unit='mA' dop='0'/><CHANNEL id='34' name='I Aa' unit='mA' dop='0'/><CHANNEL id='35' name='I Sr' unit='mA' dop='0'/><CHANNEL id='36' name='I Rein' unit='mA' dop='0'/><CHANNEL id='37' name='LZ ES seit Fuell.' unit='Min' dop='0'/><CHANNEL id='38' name='LZ ES seit Ent.' unit='Min' dop='0'/><CHANNEL id='39' name='Anzahl Entasch.' dop='0'/><CHANNEL id='40' name='Anzahl SR Beweg.' dop='0'/><CHANNEL id='41' name='Lagerstand' unit='kg' dop='0'/><CHANNEL id='42' name='Verbrauchszähler' unit='kg' dop='0'/><CHANNEL id='43' name='Heiz P Lambda' unit='W' dop='2'/><CHANNEL id='44' name='Heiz U Lambda' unit='V' dop='2'/><CHANNEL id='45' name='Heiz I Lambda' unit='mA' dop='0'/><CHANNEL id='46' name='U_Lambda' unit='mV'/><CHANNEL id='47' name='U Netzteil' unit='mV' dop='0'/><CHANNEL id='48' name='T Spuelung' unit='°C'/><CHANNEL id='49' name='BRT' unit='°C'/><CHANNEL id='50' name='Tplat' unit='°C' dop='0'/><CHANNEL id='51' name='TVG' unit='°C'/><CHANNEL id='52' name='TVG2' unit='°C'/><CHANNEL id='53' name='AIN17' unit='V'/><CHANNEL id='54' name='Taus' unit='°C'/><CHANNEL id='55' name='TA Gem.' unit='°C'/><CHANNEL id='56' name='Ext.HK Soll' unit='°C' dop='0'/><CHANNEL id='57' name='TVL_A' unit='°C'/><CHANNEL id='58' name='TVLs_A' unit='°C' dop='0'/><CHANNEL id='59' name='TRA_A' unit='°C'/><CHANNEL id='60' name='TRs_A' unit='°C'/><CHANNEL id='61' name='HKZustand_A' dop='0'/><CHANNEL id='62' name='FRA Zustand' dop='0'/><CHANNEL id='63' name='TVL_1' unit='°C'/><CHANNEL id='64' name='TVLs_1' unit='°C' dop='0'/><CHANNEL id='65' name='TRA_1' unit='°C'/><CHANNEL id='66' name='TRs_1' unit='°C'/><CHANNEL id='67' name='HKZustand_1' dop='0'/><CHANNEL id='68' name='FR1 Zustand' dop='0'/><CHANNEL id='69' name='TVL_2' unit='°C'/><CHANNEL id='70' name='TVLs_2' unit='°C' dop='0'/><CHANNEL id='71' name='TRA_2' unit='°C'/><CHANNEL id='72' name='TRs_2' unit='°C'/><CHANNEL id='73' name='HKZustand_2' dop='0'/><CHANNEL id='74' name='FR2 Zustand' dop='0'/><CHANNEL id='75' name='TVL_B' unit='°C'/><CHANNEL id='76' name='TVLs_B' unit='°C' dop='0'/><CHANNEL id='77' name='TRA_B' unit='°C'/><CHANNEL id='78' name='TRs_B' unit='°C'/><CHANNEL id='79' name='HKZustand_B' dop='0'/><CHANNEL id='80' name='FRB Zustand' dop='0'/><CHANNEL id='81' name='TBA' unit='°C'/><CHANNEL id='82' name='TBs_A' unit='°C' dop='0'/><CHANNEL id='83' name='TB1' unit='°C'/><CHANNEL id='84' name='TBs_1' unit='°C' dop='0'/><CHANNEL id='85' name='BoiZustand_1' dop='0'/><CHANNEL id='86' name='TBB' unit='°C'/><CHANNEL id='87' name='TBs_B' unit='°C' dop='0'/><CHANNEL id='88' name='HKR Anf' unit='°C'/><CHANNEL id='89' name='Anf. HKR0' unit='°C' dop='0'/><CHANNEL id='90' name='Anf. HKR1' unit='°C' dop='0'/><CHANNEL id='91' name='Anf. HKR2' unit='°C' dop='0'/><CHANNEL id='92' name='Anf. HKR3' unit='°C' dop='0'/><CHANNEL id='93' name='Anf. HKR4' unit='°C' dop='0'/><CHANNEL id='94' name='Anf. HKR5' unit='°C' dop='0'/><CHANNEL id='95' name='Anf. HKR6' unit='°C' dop='0'/><CHANNEL id='96' name='Anf. HKR7' unit='°C' dop='0'/><CHANNEL id='97' name='Anf. HKR8' unit='°C' dop='0'/><CHANNEL id='98' name='Anf. HKR9' unit='°C' dop='0'/><CHANNEL id='99' name='Anf. HKR10' unit='°C' dop='0'/><CHANNEL id='100' name='Anf. HKR11' unit='°C' dop='0'/><CHANNEL id='101' name='Anf. HKR12' unit='°C' dop='0'/><CHANNEL id='102' name='Anf. HKR13' unit='°C' dop='0'/><CHANNEL id='103' name='Anf. HKR14' unit='°C' dop='0'/><CHANNEL id='104' name='Anf. HKR15' unit='°C' dop='0'/><CHANNEL id='105' name='Wasserdruck' unit='bar' dop='2'/></ANALOG><DIGITAL><CHANNEL id='0' bit='0' name='Störung'/><CHANNEL id='0' bit='1' name='Stb'/><CHANNEL id='0' bit='2' name='Fuellstand'/><CHANNEL id='0' bit='3' name='RLP/PuffP'/><CHANNEL id='0' bit='4' name='RLm_auf'/><CHANNEL id='0' bit='5' name='RLm_zu'/><CHANNEL id='0' bit='10' name='WS freig.'/><CHANNEL id='0' bit='11' name='Akt. Code'/><CHANNEL id='0' bit='14' name='FW Freig.'/><CHANNEL id='0' bit='15' name='gFlP'/><CHANNEL id='0' bit='16' name='gFlM auf'/><CHANNEL id='0' bit='17' name='gFlM zu'/><CHANNEL id='0' bit='18' name='gFl2P'/><CHANNEL id='0' bit='19' name='gFl2M auf'/><CHANNEL id='0' bit='20' name='gFl2M zu'/><CHANNEL id='1' bit='0' name='L Heiz.'/><CHANNEL id='1' bit='1' name='Z Heiz.'/><CHANNEL id='1' bit='2' name='Z Geb.'/><CHANNEL id='1' bit='3' name='AA Run'/><CHANNEL id='1' bit='4' name='AA Dir'/><CHANNEL id='1' bit='5' name='ES Run'/><CHANNEL id='1' bit='6' name='ES Dir'/><CHANNEL id='1' bit='7' name='AS Saug'/><CHANNEL id='1' bit='8' name='AS RA Run'/><CHANNEL id='1' bit='9' name='AS RA Dir'/><CHANNEL id='1' bit='10' name='Rein En'/><CHANNEL id='1' bit='11' name='Rein Run'/><CHANNEL id='1' bit='12' name='Es Rein Endl'/><CHANNEL id='1' bit='13' name='sAS Anf Fuell'/><CHANNEL id='2' bit='0' name='HKPA'/><CHANNEL id='2' bit='1' name='MAA'/><CHANNEL id='2' bit='2' name='MAZ'/><CHANNEL id='2' bit='3' name='HKP1'/><CHANNEL id='2' bit='4' name='M1A'/><CHANNEL id='2' bit='5' name='M1Z'/><CHANNEL id='2' bit='6' name='HKP2'/><CHANNEL id='2' bit='7' name='M2A'/><CHANNEL id='2' bit='8' name='M2Z'/><CHANNEL id='2' bit='9' name='HKP3'/><CHANNEL id='2' bit='10' name='M3A'/><CHANNEL id='2' bit='11' name='M3Z'/><CHANNEL id='2' bit='12' name='HKP4'/><CHANNEL id='2' bit='13' name='M4A'/><CHANNEL id='2' bit='14' name='M4Z'/><CHANNEL id='2' bit='15' name='HKP5'/><CHANNEL id='2' bit='16' name='M5A'/><CHANNEL id='2' bit='17' name='M5Z'/><CHANNEL id='2' bit='18' name='HKP6'/><CHANNEL id='2' bit='19' name='M6A'/><CHANNEL id='2' bit='20' name='M6Z'/><CHANNEL id='2' bit='21' name='HKPB'/><CHANNEL id='2' bit='22' name='MBA'/><CHANNEL id='2' bit='23' name='MBZ'/><CHANNEL id='3' bit='0' name='BPA'/><CHANNEL id='3' bit='1' name='BP1'/><CHANNEL id='3' bit='2' name='BP2'/><CHANNEL id='3' bit='3' name='BP3'/><CHANNEL id='3' bit='4' name='BPB'/><CHANNEL id='3' bit='5' name='BZPA'/><CHANNEL id='3' bit='6' name='BZP1'/><CHANNEL id='3' bit='7' name='BZP2'/><CHANNEL id='3' bit='8' name='BZP3'/><CHANNEL id='3' bit='9' name='BZPB'/><CHANNEL id='4' bit='0' name='Aschebox'/><CHANNEL id='4' bit='1' name='Netztrafo'/><CHANNEL id='4' bit='2' name='Netzrelais'/><CHANNEL id='4' bit='4' name='Lagerraum'/><CHANNEL id='4' bit='6' name='FLP'/><CHANNEL id='4' bit='8' name='ATW'/><CHANNEL id='4' bit='9' name='Entasch gesp.'/><CHANNEL id='4' bit='13' name='HKV'/><CHANNEL id='4' bit='14' name='Spuelung Aktiv'/><CHANNEL id='6' bit='0' name='EHK Anf'/><CHANNEL id='6' bit='2' name='EHK Anf2'/><CHANNEL id='6' bit='3' name='EHK Anf3'/><CHANNEL id='6' bit='4' name='EHKP'/><CHANNEL id='6' bit='6' name='EHKP2'/><CHANNEL id='6' bit='7' name='EHKP3'/><CHANNEL id='6' bit='8' name='KASK1 MinLeist'/><CHANNEL id='6' bit='9' name='KASK2 MinLeist'/><CHANNEL id='6' bit='10' name='KASK3 MinLeist'/><CHANNEL id='6' bit='11' name='KASK4 MinLeist'/><CHANNEL id='6' bit='12' name='KASK1 MaxLeist'/><CHANNEL id='6' bit='13' name='KASK2 MaxLeist'/><CHANNEL id='6' bit='14' name='KASK3 MaxLeist'/><CHANNEL id='6' bit='15' name='KASK4 MaxLeist'/><CHANNEL id='6' bit='16' name='KASK1 Run'/><CHANNEL id='6' bit='17' name='KASK2 Run'/><CHANNEL id='6' bit='18' name='KASK3 Run'/><CHANNEL id='6' bit='19' name='KASK4 Run'/><CHANNEL id='6' bit='20' name='KASK1 OK'/><CHANNEL id='6' bit='21' name='KASK2 OK'/><CHANNEL id='6' bit='22' name='KASK3 OK'/><CHANNEL id='6' bit='23' name='KASK4 OK'/><CHANNEL id='6' bit='24' name='Kask KWK Out'/><CHANNEL id='6' bit='25' name='Kask FW Out'/><CHANNEL id='6' bit='26' name='KASK KWK OK'/><CHANNEL id='6' bit='27' name='KASK FW OK'/><CHANNEL id='7' bit='0' name='DReg P2'/><CHANNEL id='7' bit='1' name='DReg P3'/><CHANNEL id='7' bit='2' name='DReg Mi auf'/><CHANNEL id='7' bit='3' name='DReg Mi zu'/><CHANNEL id='7' bit='5' name='DReg2 P2'/><CHANNEL id='7' bit='6' name='DReg2 Mi auf'/><CHANNEL id='7' bit='7' name='DReg2 Mi zu'/><CHANNEL id='7' bit='9' name='DReg3 P2'/><CHANNEL id='7' bit='10' name='DReg3 P3'/><CHANNEL id='7' bit='11' name='DReg3 Mi auf'/><CHANNEL id='7' bit='12' name='DReg3 Mi zu'/></DIGITAL></DAQPRJ>"

iamthe1st commented 6 months ago

Does anybody know how to disable the automatic updates? I don't need them and they only cause additional work when they break the integration again...

skrue commented 6 months ago

I had the exact same issue, the firmware was updated and the integration stopped working without any previous (or subsequent) notification from Hargassner. I also had to manually update the DAQ string in the config file to get it working again. Maybe it helps to disable the "Maintenance by Hargassner" option in their web portal? Might be worth a try.

EpicLPer commented 4 months ago

Added my own NANO_V141O3 now and the one @iamthe1st mentioned :)

EpicLPer commented 4 months ago

I'm not sure what the technician did today, but I somehow have a different format after his visit today even tho I'm on the same exact firmware version as before... This has been added afterwards now.

I'll add this as NANO_V141O3_2 in a pull request but I'm a bit confused now... The format from Hargassner in general to throw this out on Telnet with different possible message lenghts is a bit clumsy at best :( I e-mailed them to ask if they can improve this, either by adding the ability to add our own MQTT server as a second one or by having their own official Home Assistant integration, but it kind of sucks having to manually get these logging files and adjusting things by hand each time.

anderl78 commented 4 months ago

Does anybody know how to disable the automatic updates? I don't need them and they only cause additional work when they break the integration again...

Yes. To disable the automatic update:

Register your heater inside the App / Web
Log into the app (or direktly to the website and login there)
burger-menu --> click "Web-Version" (if asked, login there)
click top right -->"info"-button
click "Settings"
disable automatic update (read the warning and choose like you want)
done

btw: Its not possibe (at least at the moment), to disable automatic updates inside the app

mkaufmann0983 commented 2 months ago

Hi,

The problem persists again after the heating system has been updated. Reading out the msgformat again did not resolve the error.

Hargassner:

2024-08-30_15:12:17 KD=Hargassner 2024-08-30_15:12:17 KT=Nano.2(.3) 15 2024-08-30_15:12:17 SW=V14.0HAR.p1 2024-08-30_15:12:17 HW=V1.2.4 2024-08-30_15:12:17 UPDATEDATE=29.08.2024 13:32 2024-08-30_15:12:17 UPDATE=V14.0n3

HA-Version:

Core 2024.8.3 Supervisor 2024.08.0 Operating System 13.1

I also thought that the msg format had changed again but after reading and saving again the error persists:

HargassnerBridge._update(): Received message has unexpected length.

Has anyone already found a solution to the problem?

anderl78 commented 2 months ago

For me too. The "...p1" update seems to make something different. I have no time to look deeper into this at the moment. As a workaround I disabled the length check in hargassner.py. really ugly, I know, but the system keeps running at least for the most values, till a real fix is available

iamthe1st commented 2 months ago

Sad to hear that the update breaks the integration :-/ - I was too dumb and lazy to deactivate the Hargassner update, while It was possible...

Now it is also stopped working for me. But I need the values for my PV-surplus warm water heater to work properly...

I hope somebody is able to fix it :-)

iamthe1st commented 2 months ago

In my last daq string, I replaced the Umlaute with ae or ue and ß with ss. - maybe this would help?

Without that, it did not work for me.

anderl78 commented 2 months ago

Umlauts were never a problem for me... weird...

But what I noticed when quickly comparing my two data sets "...p" vs. "...p1" is that the "...p" had three more channels (CHANNEL 119, 120 and 121) than the "...p1". The p1 data set seems to be complete, the differences are in the middle of the data. Nevertheless, the integration does not work, neither with the new nor with the old data set. Apparently the data set description from the SD card and the TELNET data from the heater do not match, this would have to be compared. Unfortunately, I have no idea what the Telnet data used to look like formerly, so it is more difficult for me than I want to

ZEkE-999 commented 2 months ago

Please fix @TheRealKillaruna

anderl78 commented 2 months ago

I added a possible fix yesterday. Also we should debug here more, see my issue from yesterdayand the corresponding pull request...

mkaufmann0983 commented 2 months ago

I added a possible fix yesterday. Also we should debug here more, see my issue from yesterdayand the corresponding pull request...

Thanks for the customisation. If I change this accordingly, the error changes to this error message:

Nano-PK 15

HargassnerBridge.async_update(): Unexpected message length. Expected: 114, Actual: 116 HargassnerBridge.async_update(): Unexpected message length. Expected: 114, Actual: 116 HargassnerBridge.async_update(): Unexpected message length. Expected: 114, Actual: 116 HargassnerBridge.async_update(): Unexpected message length. Expected: 114, Actual: 116 HargassnerBridge.async_update(): Unexpected message length. Expected: 114, Actual: 116 HargassnerBridge.async_update(): Unexpected message length. Expected: 114, Actual: 116 HargassnerBridge.async_update(): Unexpected message length. Expected: 114, Actual: 116 HargassnerBridge.async_update(): Unexpected message length. Expected: 114, Actual: 116

Unfortunately, I can't make heads or tails of the false report either.

ZEkE-999 commented 2 months ago

NanoPK 20:

HargassnerBridge.async_update(): Unexpected message length. Expected: 140, Actual: 142 HargassnerBridge.async_update(): Unexpected message length. Expected: 140, Actual: 142 HargassnerBridge.async_update(): Unexpected message length. Expected: 140, Actual: 142 HargassnerBridge.async_update(): Unexpected message length. Expected: 140, Actual: 142 HargassnerBridge._update(): Received message has unexpected length. HargassnerBridge.async_update(): Unexpected message length. Expected: 140, Actual: 142 HargassnerBridge.async_update(): Unexpected message length. Expected: 140, Actual: 142 HargassnerBridge.async_update(): Unexpected message length. Expected: 140, Actual: 142 HargassnerBridge.async_update(): Unexpected message length. Expected: 140, Actual: 142 HargassnerBridge.async_update(): Unexpected message length. Expected: 140, Actual: 142 HargassnerBridge._update(): Received message has unexpected length.

anderl78 commented 2 months ago

Absolutely nuts.... you both have different message-lengths - or even better, we three have this! Hargassner doesn't like us... i guess they want to sell there gateway and App. The telnet is no documented interface, as far as I know.

You both could do this: Add two dummy-entries in your msg-format, I suggest you to place them in front of the digital channels. In my example position 119 and 120. But then check your values carefully, especially if you use automations with them. Incorrect values in an automation could cause damage in some individual cases - I can't give you any guarantee...

ZEkE-999 commented 2 months ago

Hey @anderl78 - can you describe this in some more detail or give an example? I don't get it fully. I just read out the data, so there should be no damage. Thanks

anderl78 commented 2 months ago

ok, i will try....

The data set or better the data from the SD card (msgformat) consists of two parts. It begins with an "ANALOG" part, followed by a "DIGITAL" part. In both parts, each block is marked by a numbered CHANNEL. The digital part is, at least as far as I have seen so far, made up of 8 channels (CHANNEL 0 to 7, but the digital values are special because several BIT values are defined for each channel, each encodes a different value. So each digital channel contains several values, depending on CHANNEL-number and BIT).

So what you can do: start at the end of your msgformat and loock backwards in the data set until you reach the first digital "CHANNEL id=0". Before this value you will see the DIGITAL marking and before the DIGITAL-marking you will see that, ANALOG ends with "/ANALOG". In concrete terms, it looks something like this: the last analog value is defined (btw, for analog channels each channel has only one value, no BIT):

...<CHANNEL id='105' name='Wasserdruck' unit='bar' dop='2'/></ANALOG><DIGITAL><CHANNEL id='0' bit='0' name='Störung'/>CHANNEL...

To stay within this example, you would have to insert two additional analog channels (here 106 and 107). That would look like this:

...<CHANNEL id='106' name='Dummy' unit='°C' dop='0'/><CHANNEL id='107' name='Dummy2' unit='°C' dop='0'/></ANALOG><DIGITAL><CHANNEL id='0' bit='0' name='Störung'/><CHANNEL....

you don't have to change the digital part, let it unchanged. insert your new msgformat in homeassistant, restart and it should work (perhaps with a few false values...)

anderl78 commented 2 months ago

...at least as far as I could figure out here... my biggest problem is, that I don't known the TELNET output from earlier firmware nor from other heaters. Would be greate,if everybody would give us firmware, name of heater and msgformat-info (number of channels in msgformat and corresponding values from telnet - as done now with new debugging-line in the code)

mkaufmann0983 commented 2 months ago

@anderl78- Thank you very much for this explanation and now I understand more how the whole thing is structured. Values are now displayed again after the two dummy entries.

I have connected to my heating system via Telnet:

Nano-PK 15

KT=Nano.2(.3) 15 SW=V14.0HAR.p1 HW=V1.2.4

`pm 1 1.1 7.5 33.1 0 34.6 32 13 36.8 0 0 53.9 120 51.8 75 5 0 0 0 54 0 0 30 100 100 100 0 86.4 82 3 0 0 10 3 0 2 0 38 0 0 3109 5246 4866 0.00 0.00 -3 50.4 24145 140.0 113.5 34 -20.0 -20.0 0.0 28.2 26.2 1 0 -20.0 0 20.0 20.0 0 1 27.7 0 20.0 22.0 5 1 140.0 0 20.0 20.0 0 1 -20.0 0 20.0 20.0 0 1 -20.0 0 53.8 0 0 1 -20.0 0 0.0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.00 6 0 0 0 1 0 0 0

pm 1 1.1 7.5 33.1 0 34.6 32 13 36.9 0 0 53.9 120 51.8 75 5 0 0 0 54 0 0 30 100 100 100 0 86.4 82 3 0 0 11 1 0 3 0 38 0 0 3109 5246 4866 0.00 0.00 -3 50.4 24145 140.0 111.6 34 -20.0 -20.0 0.0 28.2 26.2 1 0 -20.0 0 20.0 20.0 0 1 27.8 0 20.0 22.0 5 1 140.0 0 20.0 20.0 0 1 -20.0 0 20.0 20.0 0 1 -20.0 0 53.8 0 0 1 -20.0 0 0.0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.00 6 0 0 0 1 0 0 0 ` Here is the msgformat from the heater (without dummy):

I hope this is the edition you wanted.

naklar25 commented 2 months ago

@mkaufmann0983 : can you send me your "new" msgformat please?

mkaufmann0983 commented 2 months ago

@mkaufmann0983 : can you send me your "new" msgformat please?

This is now with the dummy line that @anderl78- mentioned:

After restart HA values are displayed again.

anderl78 commented 2 months ago

Sounds good :-)

But the circumstances are not pleasant. I ask everyone to publish their data here, perhaps we can see somithing there... interesting that such different data sets exist. Especially since Hargassner seems to keep a list of the registers for the modbus. Here from the ioBroker community is an (older) PDF about an operating manual for the ModBus interface: https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://forum.iobroker.net/assets/uploads/files/1615657901472-bedienungsanleitung_modbus_de_v06_11058240-002.pdf&ved=2ahUKEwiW0P6DoqeIAxWQBNsEHYAhGrgQFnoECAYQAQ&usg=AOvVaw2U3GXqfWjTqICegsfsqrNJ

Really, Hargassner should give a little bit more support to the open source community!

ZEkE-999 commented 2 months ago

I added to dummies, some sensors are missing, just checking now. Output from my side:

2024-09-03_20:56:56 KD=Hargassner 2024-09-03_20:56:56 KT=Nano.2 32 2024-09-03_20:56:56 SW=V14.0HAR.p1 2024-09-03_20:56:56 HW=V1.2.0`

Telnet-Output:

pm 1 1.2 0 22.9 0 23.4 30 16 29.6 0 0 58.9 58.2 52.7 81 5 0 0 0 59 0 0 0 0 39.3 39.3 0 0 0 3 0 0 0 2 7 2 0 0 0 0 0 1 4892 9759 14638 0.00 0.00 -4 50.4 24227 140.0 113.5 31 -20.0 -20.0 0.0 20.1 20.9 1 3 0 0 -20.0 0 20.0 20.0 0 1 23.9 0 20.0 20.0 0 4 24.1 0 20.0 21.0 5 1 24.6 0 20.0 20.0 5 1 24.0 0 20.0 20.0 0 4 -20.0 0 20.0 20.0 0 1 -20.0 0 59.9 0 0 0 120.0 0 0 -20.0 0 0.0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 197.5 197.5 0.0 120.0 120.0 120.0 0.00 2 1000 0 0 1 0 0 0

naklar25 commented 2 months ago

Hello, I am not able to adjust my msg format. I have entered two dummies, but no values are displayed.

Here the original msg format

Can you help me please?

mkaufmann0983 commented 2 months ago

@naklar25

In this line

<CHANNEL`` id=‘103’ name=‘Anf. HKR14’ unit=‘°C’ dop=‘0’/><CHANNEL id=‘104’ name='Anf. HKR15‘ unit=’°C‘ dop=’0‘/><CHANNEL id=’105‘ name=’Water pressure‘ unit=’bar‘ dop=’2‘/><CHANNEL id=’106‘ name=’Dummy‘ unit=’°C‘ dop=’0‘/><CHANNEL id=’107‘ name=’Dummy2‘ unit=’°C‘ ``dop=’0'/></ANALOG>

must be entered here before the </ANALOG:

<CHANNEL`` id=‘106’ name=‘Dummy’ unit=‘°C’ dop=‘0’/><CHANNEL id=‘107’ name=‘Dummy2’ unit=‘°C’ ``dop=‘0’/>

The complete line then looks like this:

<CHANNEL`` id=‘103’ name=‘Anf. HKR14’ unit=‘°C’ dop=‘0’/><CHANNEL id=‘104’ name='Anf. HKR15‘ unit=’°C‘ dop=’0‘/><CHANNEL id=’105‘ name=’Water pressure‘ unit=’bar‘ dop=’2‘/><CHANNEL id=’106‘ name=’Dummy‘ unit=’°C‘ dop=’0‘/><CHANNEL id=’107‘ name=’Dummy2‘ unit=’°C‘ ``dop=’0'/></ANALOG>

naklar25 commented 2 months ago

Thank you for the quick respons and for your time. I have adjusted the line, but it doesn't work.

I will try it without the Internet gateway over the course of the week, maybe it will work that way.

mkaufmann0983 commented 2 months ago

@naklar25 What happens with errors in the log? Can you name them?

anderl78 commented 2 months ago

@naklar25 It should make no difference, if there is a gateway or not. The telnet data comes from the heater. Look into your config, if there is the IP from the heater or from gateway. It should not work, if you configured the gateway there, because the gateway doesn't send telnet from port 23 (my gateway has no open port, I scanned for all ports on my gateway with no success for nothing)

iamthe1st commented 2 months ago

Hallo zusammen, vielen Dank für eure tolle Unterstützung bei der Problembehebung! Dank eurer Hilfe habe ich die Integration bei mir wieder zum laufen bekommen.

Ich musste auch zu den "Analog-Channels" am Ende zwei Dummy channels hinzufügen.

Aufgefallen ist mir, dass sich dieser Sensor Wert verschoben hat: sensor.nano_pk_hot_water_1_temperature wurde zu sensor.nano_pk_hot_water_1_temperature_target

Hier das Original MSG Format für meine Nano PK 12 KD=Hargassner KT=Nano.2(.3) 12 SW=V14.0HAR.p1 HW=V1.2.4 UPDATEDATE=28.08.2024 09:56 UPDATE=V14.0n

naklar25 commented 2 months ago

@naklar25 What happens with errors in the log? Can you name them?

Hi, you can find my logs in the txt.

home-assistant_nano_pk2024-09-05T19-14-11.365Z.txt

wumpsven commented 2 months ago

ich musste 3 Dummys hinten ansetzen.

TYP Nano.2(.3) 15 SW: V14.0HAR.p1

Markus226 commented 2 weeks ago

ich musste 3 Dummys hinten ansetzen.

TYP Nano.2(.3) 15 SW: V14.0HAR.p1

Wie sieht das in etwa aus? Bzw. was muss ergänzt werden?

wumpsven commented 2 weeks ago

ich musste 3 Dummys hinten ansetzen. TYP Nano.2(.3) 15 SW: V14.0HAR.p1

Wie sieht das in etwa aus? Bzw. was muss ergänzt werden?

https://github.com/TheRealKillaruna/nano_pk/issues/24#issuecomment-2328012215

Bei einigen reichten wohl 2 Dummys ich brauchte 3

Spacey-Rat commented 2 weeks ago

ich musste 3 Dummys hinten ansetzen. TYP Nano.2(.3) 15 SW: V14.0HAR.p1

Wie sieht das in etwa aus? Bzw. was muss ergänzt werden?

https://github.com/TheRealKillaruna/nano_pk/issues/24#issuecomment-2326133951

TheRealKillaruna / nano_pk

Integration stopped working yesterday: Received message has unexpected length. (expected: 113 got: 114) (2584) #24