My concern with the Websocket interface is that it seems to allow only very few write operations and the binary one seems to allow more (maybe you know that better?).
The suggestion for the chat was that there might be some technical discussions which might be irrelevant for HASS users on this forum. Like when we try to figure out how to get a sensor with multiple values or by searching for such patterns in similar addons. Just my opinion, but I’m also fine staying here.
There are only a few write options I need I just don’t want that we miss possibilities by just supporting the websocket interface. But in anyway, If absolutely needed we might be able to switch to the binary interface without too much of a hassle. The only quesion is if we will ignore those that do not have the websocket interface or if we still want to stay with the websocket? The current known ratio is that 33% would not be able to use the component
Regarding the sensor: I think a sensor can only have one value but multiple attributes. So either we create sensors for each value we want to expose or one/a few sensors with multiple attributes. Maybe we should first create a list of values we want to show and/or edit? What do you think? I am thinking about a google doc here to collect that information so we can collaborate easier.
Another question: Do you know about internationality? In the xml we have usually an id, a name and a value. The id is dynamic as far as I know and not always the same for the same element. So we would need to go for the name. Is the name always in German or is it English if you have setup your heatpump/Luxtronik to English?
Edit: If we would need to support multilanguage, the binary interface suddenly gets more appealing as there we only have numbers.
I think you’re right, maybe we should go for the binary protocol as we could support all users and we’re not dependent on the language!
I’ll collect samples of the binary protocol and post 'em in a minute.
If I understand it correct, the 3004 values are calculations, read only values.
The 3003 values are parameters, read and write parameters, right?
The command 3002 is then used to write those parameters.
What do you think, should we kind of restrict the writable values to those we know for sure!?
Just to beware users of accidentally change values that normally are not changeable through the webinterface.
I’ve created a pypi installable package for getting data from the Luxtronik and parsing it into a huge dict.
Writing is parameters is further back on my list, I’ve decided to get the sensor/binary_sensor parts up and running first.