I forgot to mention that my heat pump has a Waterkotte remote box, a small Raspberry Pi connected to the same network (with a different IP) so that the Waterkotte service can connect remotely.
I’ll attempt to close all my sessions in the app and the browser, and I’ll update you shortly.
Thank you!
ah, that might use up all the connections… the old systems only support 2 sessions.
Can you disconnect the remote box to test if it is working then?
Nothing… User/password wrong 
Now, I can´t connect with the mobile app, but I can with the browser
Can you see anything in the logs of HA?
Are you able to capture the traffic to the heatpump from the integration to see what exactly is happening?
The only thing i noticed in your har file that i found odd was that the reply from the heat pump was status code 500 even though it returned the session token.
Because it was not a complete session you recorded I assumed that is the reason, but maybe your heatpump is sending the wrong http status code… I haven’t seen this in others.
Can you try to let the integration talk to your connect box? the Mobile app is using the same protocol, maybe that will work better.
I installed version 0.1.00 via HACS without any problems. I also can see the mixing circuits as hidden sensors. unfortunately the status stays “unknown” for all sensors… Do you have any idea what could be wrong? Thanks so much for your work so far!!!
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: custom_components.waterkotte_heatpump
Source: helpers/update_coordinator.py:300
Integration: Waterkotte Heatpump (documentation, issues)
First occurred: 22:24:56 (19 occurrences)
Last logged: 22:33:56
Unexpected error fetching waterkotte_heatpump data: undefined entity: line 1, column 144
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 300, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/config/custom_components/waterkotte_heatpump/init.py”, line 223, in _async_update_data
tagdatas = await self.api.async_get_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/config/custom_components/waterkotte_heatpump/api.py”, line 82, in async_get_data
ret = await self._client.read_values(self.tags)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/pywaterkotte/ecotouch.py”, line 1370, in read_values
e_values, e_status = await self._read_tags(e_tags)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/pywaterkotte/easycon.py”, line 86, in _read_tags
tree = ET.fromstring(r)
^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/xml/etree/ElementTree.py”, line 1338, in XML
parser.feed(text)
xml.etree.ElementTree.ParseError: undefined entity: line 1, column 144
I pushed a new version that adds a little more logging.
Unfortunately I don’t have a EasyCon system to test against so I’m not sure what happens there…
hello, i have the same problem with the version 0.1.00 all sensors stay unkown.
how can i install the version with more logging?
Version 0.1.01 should be available already for 2 days.
Anybody how is affected and knows a bit of python can contact me directly to help.
I actually forgot to create the release and only created the tag on github 
Should be available any minute now.
Hi Michael,
I have installed 0.1.01, Debug Mode on and this is in the log.
I have deleted lines from other addons from the log.
KeyError: ‘sensor’
2023-12-10 19:21:45.927 DEBUG (MainThread) [custom_components.waterkotte_heatpump.binary_sensor] Sensor async_setup_entry
2023-12-10 19:21:47.154 DEBUG (MainThread) [custom_components.waterkotte_heatpump.select] Sensor async_setup_entry
2023-12-10 19:21:47.232 DEBUG (MainThread) [custom_components.waterkotte_heatpump.sensor] Sensor async_setup_entry
2023-12-10 19:21:47.263 DEBUG (MainThread) [custom_components.waterkotte_heatpump.switch] Sensor async_setup_entry
2023-12-10 19:21:47.269 DEBUG (MainThread) [custom_components.waterkotte_heatpump.number] Sensor async_setup_entry
2023-12-10 19:22:16.189 DEBUG (MainThread) [custom_components.waterkotte_heatpump] Finished fetching waterkotte_heatpump data in 0.110 seconds (success: True)
2023-12-10 19:22:46.148 DEBUG (MainThread) [custom_components.waterkotte_heatpump] Finished fetching waterkotte_heatpump data in 0.071 seconds (success: True)
I think I found the issue… I fixed something in the lib and it had side effects 
v0.1.02 should work again now.
Hi Michael,
great work!
The Fix is working, all Sensors are working now.
Thanks.
Torte
Hello again,
Nothing appears in the logs, and I’m unable to capture the traffic. Trying to connect to the IP of the remote box also proves unsuccessful.
Thank You!!
Can you try this in a command line against your heatpump ip and the connect box ip?
curl -vv 'http://x.x.x.x/config/query.cgi?var%7CI%7C30%7C0%7C'
Thank you so much for your work! Most of the things work perfectly! WONDERFUL! I was ill for a few days, so I had to delay testing… Here are some minor bugs I found so far:
sensor.waterkotte_heatpump_temperature_mixing1
sensor.waterkotte_heatpump_temperature_mixing2
sensor.waterkotte_heatpump_temperature_mixing3
(I think, these are the actual temperatures in the mixing circuits) status stays “unknown”
number.waterkotte_heatpump_temperature_adjustment_2
number.waterkotte_heatpump_temperature_adjustment_3
number.waterkotte_heatpump_temperature_adjustment_4
(Temperature adjustment in the mixing circuits) the K value is 4 in HA (should be 0.0 in EasyCon), when e.g. changing in EasyCon to 0.5 it changes to 5 in HA or when changing to -0.5 it changes to 3 in HA. Therefore changing the position of the slider in HA produces an error message (slider is - 2 to +2)
Would that be fixable?
I’ll try to have a look at the weekend, should be easy.
I’m struggling to find the sensor with the name you post above…
Did you rename them?
Could you try to completely remove the device and add it again?
If there was a weird numbering due to the update it should be gone… there should not be anything with a “4” at the end.
I just pushed a new release for v0.1.13 that adds more debug logging when you enable the debug log in HA.
Hopefully that will allow a better understanding what happens when something goes wrong!
Anybody who has an issue please update to this version and run it with debugging enabled for a while and then send the log along with the problem description.
