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

Additional Tags I have found , just an idea for when you work on it again #4

Closed flautze closed 8 months ago

flautze commented 1 year ago

Hey there, when using the website for the waterpump I tried out and testet a lot of tags related to time schedules. I will list them here so they do not get lost and you may implement them at a later time - if at all.

Time Schedule Heating Monday: On/Off-Switch D42 (On=1, Off=0) // Time from: I151 : I179 ( HR : MIN ) // Time to: I207 : I235 (for example From 09:30 would be I151 = 09 and I207 = 30) Monday-Adjustment1: On/Off = D46 // Offset value: A63 -1.0 K = -10 // Time from: I152:I180 (always 1 higher than the normal time) // Time to: I208 : I236 Monday-Adjustment2: On/Off = D47 // Offset: A64 // From: I153:I181 // To I209:I237

Tuesday: Just add 4 to each register, for example: on/off = D46 / From I155:I183 / to: I211:I239 and so on

Wednesday: add 4 to Tuesday (or 8 to monday), and so on.

Time Schedule Water (follows the same rules as heating, just add 4 for each day) Monday: on/off = D125 // From = I393:I421 // To = I449:I477 Mo-Adj1: D126 // A141 // From I394:I422 // To = I450:I478 Mo-Adj2: D127 // A142 // From I395:I423 // To = I450:I479

Cooling Schedule (also same rules, just add 4 to each for Tuesday and so on) Monday: on/off = D86 // From: I276:I304 // to: I332:I360 Mo-Adj1: D87 / A112 / From: I277:I305 // to: I333:I361 Mo-Adj2: D88 // A113 // From: I278:I306 // to: I334:I362

marq24 commented 1 year ago

... just a little update in this issue - I am currently thinking about a complete RE-WRITE of the complete integration since the experience I gained in the past month (working in ha-senec-v3 and some other things) have made me thinking...

The current architecture is IMHO not very clean and also IMHO full of evil hacks - yes it still works - but the time I had invested just to figure out how to translate options was really bad experience... sorry - now I stop wining ;-)

flautze commented 1 year ago

That’s fine. If you need a hand or test subject, let me know.

devfaz commented 1 year ago

Same here - looking forward to test :)

marq24 commented 8 months ago

Finally I am looking into this... I have to admit, that I have difficulties to verify your provided information via the waterkotte webinterface (not your fault!)...

I have one thing, that I am wondering - you wrote:

Monday: On/Off-Switch D42 (On=1, Off=0) // Time from: I151 : I179 ( HR : MIN ) // Time to: I207 : I235 (for example From 09:30 would be I151 = 09 and I207 = 30)

My expectation would be, that I207 is the hour part of the end (Time to), it would sounds much more logical to me, if the example FROM time (09:30) would be encoded in I151 = 09 and I179 = 30

flautze commented 8 months ago

Hm, It was a long time ago when I found this in the webinterface. And yes you are right I put the wrong number in my example. Instead of I207 it should be I179=30 what I meant is the following: I151 hour from time I179 minute from time I207 hour to time I235 minute to time

marq24 commented 8 months ago

I have implemented a first (draft) version...

Monday-Adjustment1: On/Off = D46 // Offset value: A63 -1.0 K = -10 // Time from: I152:I180 (always 1 higher than the normal time) // Time to: I208 : I236 Monday-Adjustment2: On/Off = D47 // Offset: A64 // From: I153:I181 // To I209:I237

and just have another "correction" remark (just as reference) - I assume Monday-Adjustment1 will be D43 and Monday-Adjustment2: On/Off will be D44 - in any other case these numbers would collide with the:

Tuesday: Just add 4 to each register, for example: on/off = D46 / From I155:I183 / to: I211:I239 and so on

... since D42 + 4 would be D46 (which seams to be the right transition from MO to TU)...

I have written here code to generate all the TAGs and corresponding Sensors - I am honestly not really sure IF somebody would like to use this... [I will release a BETA shortly (when I found a good approach to the translation)...

In the meantime it would be cool, to get the numbers for the POOL and MIX1-MIX3

flautze commented 8 months ago

I will fire up my test instance here today or tomorrow, the. I will check/test. My webinterface is buggy/not working, so I am not sure if I can find the values for the mixer/pool ( also I don’t have these in operation), but I will try.

also I agree, that for Monday registers would be 42,43,44 Seems like I wrote it and may have skipped lines between Mo and Tue.

marq24 commented 8 months ago

actually I think you can save your time - I have found a way to get the tag info for the other SCHEDULES (I know)

marq24 commented 8 months ago

@flautze -> let's continue here: https://github.com/marq24/ha-waterkotte/issues/4#issuecomment-1964894039