different values for same uri
greentux opened this issue · comments
Hi,
I want to switch the Heizkreis every evening to "Auto" mode back.
This is the uri:
<value uri="/user/var//112/10101/0/0/12092" strValue="Tag" unit="" decPlaces="0" scaleFactor="1" advTextOffset="2301">2301</value>
</eta>
You can use this readonly for the number and the string. But its also writable with number to set the Mode to "auto"
(5 = auto).
How can we do this?
regards
Hi,
advTextOffset is 2301, so "Auto" should be 2305, not 5, right?
There are 2 possible ways (as always ;-) ):
- I can add the unitless entities to the list of writable entities, and you can then write any value you want
- You can then use some Jinja2 templating magic to map the values to text (e.g. 2301 is "Tag", ...)
- I can implement a dropdown sensor with all valid values
- I'd need a list of all possible values for that
Can you send me all valid values for that url?
2301 should be "Tag"
2305 is "Auto" (?)
Unfortunately I don't have that url on my ETA unit, so I can't get all valid values myself.
I prefer first one, because I have no idea to get all the valid values...
Only with trial and see. So You mean this?
I prefer first one, because I have no idea to get all the valid values...
Only with trial and see. So You mean this?
Hello,
you can get the values if you enter the Uri in a internet browser maybe later I can post an example
It is the local ip address followed by the uri address
Best regards
ND
Hi,
@greentux Yes, you would have to set a value on the ETA unit, call the url, write down the strValue and value iself, change the setting on the ETA unit, and repeat all steps for every possible setting.
I dug a bit deeper to see if I can extract the look-up-table from the system software update files, but I couldn't find that specific value in any of the versions i tested (2.35.18 - 3.59.3). I did find the value 2301, but it means Heizen on those versions, so it looks like that url doesn't exist on those firmware versions any more?
I think the easiest option for now is to just add a checkbox to the integration settings, which the user can check to be able to add every possible sensor as a writable one.
If someone has a look-up-table of the possible values and posts it here, I can still add the dropdown sensor option in the future.
I use 1.35.15 :) My heater is from 2010 and no upgrade is possible without changing a lot of hardware..
Perhaps You can use the Version 1 Files?
Otherwise I can evaluate the values manual.
I found some ids on 1.35.18:
2301 = Tag
2302 = Nacht
2303 = Tag
2304 = Nacht
2305 = Aus
2306 = Urlaub
2307 = Estrich
I don't know why Tag and Nacht are defined twice. Also, Auto is missing. Are you sure the text on your terminal says Auto and not Aus?
Could you check if these are the values you can select on your terminal?
After some more digging, I also found the ids in the later software versions, but they were renamed:
2301 = Heizen
2302 = Absenken
2303 = Heizen
2304 = Absenken
2305 = Aus
2306 = Urlaub
2307 = Estrich
I added a script thats writes the values while changing with names. I will check some modes in the evening...
Ok, I read my logic again :)
"Write 1 to hk-auto-key if hk-status is not 5" aka "set auto key if not in holiday mode".
I noticed, that I can do the same now.
I can use the HK-auto-button and can check the holiday state separately.
So no essentiell need for me in the moment... Sorry, but that was a missinterpretation from my old python logic. We can close the issue.
But for information some values:
on Nov 27 2023 13:47:28 Ein Nacht
Mon Nov 27 2023 13:47:28 2.0
Mon Nov 27 2023 14:39:30 Aus Sommer
Mon Nov 27 2023 14:39:30 15.0
Mon Nov 27 2023 14:42:02 Ein Restwärme
Mon Nov 27 2023 14:42:02 19.0
Mon Nov 27 2023 14:46:38 Ein Tag
Mon Nov 27 2023 14:46:38 1.0
Mon Nov 27 2023 14:47:39 Ein Nacht
Mon Nov 27 2023 14:47:39 2.0
Mon Nov 27 2023 14:48:10 Aus Warmwasser
Mon Nov 27 2023 14:48:10 16.0
No problem.
I will implement the dropdown sensor option in the future, but first I have to find a way to automatically parse the system software files so I don't have to generate the look-up-tables by hand.
I'm closing this issue for now.