search

marq24 / ha-waterkotte-the-fork

HACS integration for Waterkotte Heatpumps [build since 2018] - # This version is deprecated - and no further updates will be provided! Please migrate to the new version of the Integration that have been published - TIA - see the 'Migration Guide' for details
MIT License
7 stars 1 forks source link

Password/Username wrong #1

Closed flautze closed 1 year ago

flautze commented 1 year ago

Hi Marq, currently I am trying to transition from the original waterkotte integration to your integration, as it has more working values for me (heating Curve, setpoints).

However I cannot get it to run. I always get the password/username not correct prompt. Password / user waterkotte/waterkotte works fine for me on the other integration... I tried

The original integration I could easily add again, after I failed with your integration.

The only way I got it to run was:

der-berni commented 1 year ago

Hi, You can fix the error by changing the following line in config_flow.py Line 145 https://github.com/marq24/ha-waterkotte/blob/master/custom_components/waterkotte_heatpump/config_flow.py#L145

-host, username, password, session, None, systemType=systemType +host, username, password, session, None, systemType=systemType, tagsPerRequest=tagsPerRequest

Greetings Berni

marq24 commented 1 year ago

First of all "Asche auf mein Haupt" - it took me way to long to realize, that there have been an issue reported... excepect a fixed version "today" (@der-berni THANKS!)

flautze commented 1 year ago

Thanks for closing this. However I have the problem that my Heatpump shows all sensors as „unavailable“.

device info seems to recognise my model: Firmware: 192.xx.xx.xx BIOS: 6.20 Hardware: 5008.5

also I read on the Github that this only works for 2018+ models, until recently it used to work also for m model (which I got 2013).

is there any way I can assist in finding the problem?

i already tried reinstalling/disabling/deleting…

marq24 commented 1 year ago

So the "initial" bug has been solved - right? The Login Dialog works (now) - and you can add the integration - is that correct?

First thing you should check, if the HASS Log will give you any information - sometimes the waterkotte just reply with "TOO MANY USERS" - I have seen this once here @ home on Friday when I was testing/debugging with the new version.

In general support for "older" Waterkotte Heatpumps can be quite tricky for me from remote. Do you know how to to the DEBUG Tools of the Browser? [In order to inspect requests and responses?] - If yes please use the original Waterkotte Webfrontend (that will be served directly from the IP)... There you can check how many parameters the build in webfrontent is requesting from the HP in a single requests. Older systems might only support 10 parameters per request - while the one I just got in November 2022 can handle 75 parameters in a single call.

flautze commented 1 year ago

The initial bug has been solved, since I can login and also the version is recognised. since I see the version of the heatpump, that is working at least. I will try to log errors when I am back home (next week)and have more time. Currently I only have access via mobile since we are on vacation. I think I used the 10 parameters setting.

flautze commented 1 year ago

I am reopneing, to keep better track. With devtools, after accessing the webservice I can see as follows: There is 13 lines like this: readTags?n=28..... containing (1 file as example) `#I136 S_OK 192 0

I137 S_OK

192 0

I138 S_OK

192 0

I139 S_OK

192 0

A1 S_OK

192 100

A2 S_OK

192 120

A3 S_OK

192 135

A4 S_OK

192 204

A5 S_OK

192 164

A6 S_OK

192 154

A7 S_OK

192 243

A8 S_OK

192 117

A9 S_OK

192 0

A10 S_OK

192 430

A11 S_OK

192 233

A12 S_OK

192 233

A13 S_OK

192 147

A14 S_OK

192 147

A15 S_OK

192 116

A16 S_OK

192 -400

A17 S_OK

192 -400

A18 S_OK

192 -400

A19 S_OK

192 456

A20 S_OK

192 0

A21 S_OK

192 0

A22 S_OK

192 0

A23 S_OK

192 0

A24 S_OK

192 89`

When I look into the current setting of the integration in HA I have the following settings (working with my workaround since I needed to go to a backup to get it back to work) Polling interval 60s Number of tags to fetch: 10 SystemType: EcoTouch mode (what exactly has to be set here? Does it depend on the heatpump? And what is the effect?) When I go to my heatpump display it states on top "Waterkotte EasyCon Touch". So do I need to switch this to EasyCon maybe?

for logging HASS my entries should be the following, right?

logger: logs: custom_components.waterkotte_heatpump: debug

flautze commented 1 year ago

@marq24 here my logs: seems like something is off with the tags or a tag. `2023-04-24 18:06:03.362 ERROR (MainThread) [custom_components.waterkotte_heatpump] Unexpected error fetching waterkotte_heatpump data: A1669 tag not found in response Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 250, in _async_refresh self.data = await self._async_update_data() File "/config/custom_components/waterkotte_heatpump/init.py", line 229, in _async_update_data tagdatas = await self.api.async_get_data() File "/config/custom_components/waterkotte_heatpump/api.py", line 80, in async_get_data ret = await self._client.read_values(self.tags) File "/config/custom_components/waterkotte_heatpump/pywaterkotte_ha/ecotouch.py", line 1334, in read_values e_values, e_status = await self._read_tags(e_tags) File "/config/custom_components/waterkotte_heatpump/pywaterkotte_ha/ecotouch.py", line 1394, in _read_tags results, results_status = await self._read_tags( File "/config/custom_components/waterkotte_heatpump/pywaterkotte_ha/ecotouch.py", line 1432, in _read_tags raise Exception(tag + " tag not found in response") Exception: A1669 tag not found in response 2023-04-24 18:06:03.364 DEBUG (MainThread) [custom_components.waterkotte_heatpump] Finished fetching waterkotte_heatpump data in 0.083 seconds (success: False)

2023-04-24 18:07:03.327 ERROR (MainThread) [custom_components.waterkotte_heatpump] Unexpected error fetching waterkotte_heatpump data: A1669 tag not found in response Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 250, in _async_refresh self.data = await self._async_update_data() File "/config/custom_components/waterkotte_heatpump/init.py", line 229, in _async_update_data tagdatas = await self.api.async_get_data() File "/config/custom_components/waterkotte_heatpump/api.py", line 80, in async_get_data ret = await self._client.read_values(self.tags) File "/config/custom_components/waterkotte_heatpump/pywaterkotte_ha/ecotouch.py", line 1334, in read_values e_values, e_status = await self._read_tags(e_tags) File "/config/custom_components/waterkotte_heatpump/pywaterkotte_ha/ecotouch.py", line 1394, in _read_tags results, results_status = await self._read_tags( File "/config/custom_components/waterkotte_heatpump/pywaterkotte_ha/ecotouch.py", line 1432, in _read_tags raise Exception(tag + " tag not found in response") Exception: A1669 tag not found in response 2023-04-24 18:07:03.328 DEBUG (MainThread) [custom_components.waterkotte_heatpump] Finished fetching waterkotte_heatpump data in 0.048 seconds (success: False) 0258467 2023-04-24 18:08:03.332 ERROR (MainThread) [custom_components.waterkotte_heatpump] Unexpected error fetching waterkotte_heatpump data: A1669 tag not found in response Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 250, in _async_refresh self.data = await self._async_update_data() File "/config/custom_components/waterkotte_heatpump/init.py", line 229, in _async_update_data tagdatas = await self.api.async_get_data() File "/config/custom_components/waterkotte_heatpump/api.py", line 80, in async_get_data ret = await self._client.read_values(self.tags) File "/config/custom_components/waterkotte_heatpump/pywaterkotte_ha/ecotouch.py", line 1334, in read_values e_values, e_status = await self._read_tags(e_tags) File "/config/custom_components/waterkotte_heatpump/pywaterkotte_ha/ecotouch.py", line 1394, in _read_tags results, results_status = await self._read_tags( File "/config/custom_components/waterkotte_heatpump/pywaterkotte_ha/ecotouch.py", line 1432, in _read_tags raise Exception(tag + " tag not found in response") Exception: A1669 tag not found in response 2023-04-24 18:08:03.334 DEBUG (MainThread) [custom_components.waterkotte_heatpump] Finished fetching waterkotte_heatpump data in 0.054 seconds (success: False)

2023-04-24 18:08:14.262 INFO (MainThread) [homeassistant.components.websocket_api.http.connection] [140244434954720] Connection closed by client `

flautze commented 1 year ago

seems to be related to the added tag which you handled under issue#3 https://github.com/marq24/ha-waterkotte/issues/3

I will try to remove that tag in my local installation and see if this solves the issue as probably not all models support this value.

der-berni commented 1 year ago

Check the latest release 1.0.4 (https://github.com/marq24/ha-waterkotte/releases/tag/1.0.4) in HACS, which handle the tag not found exception.

marq24 commented 1 year ago

@flautze... please be so kind and option new issues for "new issues" - in any other case this issue#1 becomes your "personal support" issue...

nevertheless the provided log output was pretty clear, that the implementation of issue#3 is the root cause - when in looked into the output I found it quite irritating, that a "none present" Tag can cause a "Exception" in den 'common watterkotte python lib' - so this has been changed this behaviour in the 1.04 impl (as @der-berni pointed out)