Log message Warning about missing tag.

[flautze]

Hey,
since I recently looked through my logs I found this:

2024-05-08 12:05:38.158 WARNING (MainThread) [custom_components.waterkotte_heatpump.pywaterkotte_ha] Tag: 'I2610' not found in response!
2024-05-08 12:05:38.173 WARNING (MainThread) [custom_components.waterkotte_heatpump.pywaterkotte_ha] Tag: 'I2609' not found in response!
2024-05-08 12:05:38.173 WARNING (MainThread) [custom_components.waterkotte_heatpump.pywaterkotte_ha] Tag: 'I2614' not found in response!
2024-05-08 12:05:38.189 WARNING (MainThread) [custom_components.waterkotte_heatpump.pywaterkotte_ha] Tag: 'I2611' not found in response!
2024-05-08 12:05:38.204 WARNING (MainThread) [custom_components.waterkotte_heatpump.pywaterkotte_ha] Tag: 'I2612' not found in response!
2024-05-08 12:05:38.234 WARNING (MainThread) [custom_components.waterkotte_heatpump.pywaterkotte_ha] Tag: 'I2613' not found in response!
2024-05-08 12:05:38.250 WARNING (MainThread) [custom_components.waterkotte_heatpump.pywaterkotte_ha] Tag: 'I2608' not found in response!

It does not really affect the integration from working, however I am not sure if this is wanted/Intended. Therefore I decided not to open an issue so far.

Best regards.

Version 2024.5.1
Firmware: 10.10.40.20 BIOS: 6.20
Hardware: 5008.5

[marq24]

I noticed these log messages as well - not 100% sure how to deal with them - in fact there are beside I52 multiple (additional) alarm-bit's - but looks like not all Waterkotte models are supporting these additional bit-fields (I2608-I2614) - I might just reduce the log level in this case but this is only a partly solution - "best" would be, that integration try to guess the possible alarm bit fields - and then use the ones that exist... Let's see what I can implement over time...

In general this warning log mainly exist to indicate the the Integration/sensors configured requesting TAGs that are not supported by the hardware - but in this special ALARM-BITs I decided for a tag combination... -> so the error handling should be different...

[marq24]

I think, this is a some sort of smart fix for the issue...
4017c3d