This is fixed in the current version, please update your files from github.
1 Like
Thank you for the quick answer.
As far as I know, I used the latest files.
But I got it working fine by comment the line 7 out (#from apscheduler.schedulers.background import BackgroundScheduler).
Just for my understanding: Where and why apscheduler ist needed? For me, it works also without apscheduler.
Me once more.
Just figured out, that in my manifest.json apscheduler was missing in requirements. So I did not used last version. Sorry for that. Now it´s working. Thanks for your help and your work on the integration.
But the question why it works without apscheduler is still open.
Sorry if this has been covered and I missed it. Is it possible to use this integration âthroughâ the Hargassner internet bridge? Or do you need the heating plugged in directly on the LAN and you can only have one or the other?
Thanks in advance.
Hi t2njgttn,
the integration uses telnet to get the data. So you need to connect the heating to your lan. But to push the data to the internet, the heating should have an internet-connection. In my case via my internet-router.
Still no change after update the integration and Home Assistant.
Getting these errors:
Logger: custom_components.nano_pk.sensor
Quelle: custom_components/nano_pk/sensor.py:220
Integration: Hargassner Nano-PK (Dokumentation)
Erstmals aufgetreten: 09:34:22 (106 Vorkommnisse)
Zuletzt protokolliert: 09:43:07
HargassnerStateSensor.update(): Invalid state.
and:
Logger: custom_components.nano_pk.sensor
Quelle: custom_components/nano_pk/sensor.py:143
Integration: Hargassner Nano-PK (Dokumentation)
Erstmals aufgetreten: 09:34:22 (106 Vorkommnisse)
Zuletzt protokolliert: 09:43:07
HargassnerEnergySensor.update(): Invalid value.
Any ideas? 
I have had also this problem. After investigation I recognized, that the heating made an update to version V14.1HAR.pr_FT. After update the hargassner.py with the parameters of the new version (as discribed in the github-readme â How to use with other Hargassner models or different firmware versions), itâs working as before.
Confirmed - Integration stopped for me several days ago as well - I just re-did the logging-part, entered my new DAQPRJ string and now itâs working again.
Fine to hear that your integration is working again.
Hello,
i tried to make this integration work today.
Could anyone please tell me where exactly i can find the firmware version of my Hargassner nano-PK heating?
I had a look at the options, but didnât see it.
Thanks.
Following Error since HA Update. Any quick fixes?
Logger: homeassistant.helpers.frame
Quelle: helpers/frame.py:190
Erstmals aufgetreten: 18. Mai 2024 um 05:45:58 (3 Vorkommnisse)
Zuletzt protokolliert: 18. Mai 2024 um 05:46:19
Detected that custom integration 'nano_pk' accesses hass.helpers.discovery. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from discovery directly at custom_components/nano_pk/__init__.py, line 42: hass.helpers.discovery.load_platform('sensor', DOMAIN, {}, config), please report it to the author of the 'nano_pk' custom integration
Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 642: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues
Ah⌠that Issue is already reported:
My NanoPK did an update to V14.0HAR.p
Since that HomeAssistant cannot read the values anymore. Has anybody else observed this ?
see my post from may 6. Just update the hargassner.py with the new value-map.
Works !
Thanks a lot !
Hello,
since the update of Home Assistant this week, the integration stopped working.
Details:
Home Assistant Core: 2024.8.3
Log:
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: custom_components.nano_pk.sensor
Quelle: custom_components/nano_pk/sensor.py:196
Integration: Hargassner Nano-PK (Dokumentation)
Erstmals aufgetreten: 27. August 2024 um 10:12:10 (15325 Vorkommnisse)
Zuletzt protokolliert: 07:29:26
HargassnerBridge.getValue(): Parameter key Verbrauchszähler not known. HargassnerBridge._update(): Received message has unexpected length.
HargassnerBridge.getValue(): Parameter key Verbrauchszähler not known.
HargassnerBridge.getValue(): Parameter key Verbrauchszähler not known. HargassnerBridge.async_update(): Error opening connection
HargassnerBridge.getValue(): Parameter key Verbrauchszähler not known. HargassnerBridge.async_update(): Telnet connection error (TimeoutError())
HargassnerBridge.getValue(): Parameter key Verbrauchszähler not known. HargassnerBridge.async_update(): Telnet connection error (ConnectionResetError(104, 'Connection reset by peer'))
Has someone else this problems?
Hi,
The problem does not seem to be with HA in general. I have read out my heater and realised that an update has taken place:
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?
Hi,
it seems that others still have the same problem:
Solution has not yet been found.
Did you update your hargassner.py with the actual value-may? How to-> see my post from may 6th.