Questions regarding Estia

[martinnj]

This isn't a feature request so much as a question, I hope it's okay to post it in the "issues". :)

Estia devices are controlled from the same app, but use slightly different API endpoints, primarily:

• /api/Estia/GetConsumerEstiaMapping
• /api/Estia/GetCurrentEstiaStateByUniqueDeviceId

They take different argument name, DeviceUniqueId, instead of ACId as the GET argument.
The responses also differ quite a bit, especially the state-string which seems to be around twice as long (more sensor data I'm guessing).

I've been trying to decipher the data myself, both the JSON fields and the state-string, but I'm having a hard go at it.
When you figured out how to read the state string, how did you go around that?

I've tried unpacking the apk with JADX, Android Studio and whatever else I could find, but haven't been able to find any reasonably readable code snippets or tips. Did you disassemble the .so files to figure out how to read them, or am I missing something somewhere? :)

[KaSroka]

I have unpacked the android app and then disassembled the libraries. Good for me they were .net so a lot of info was left in the libraries and they were quite readable after disassembly.

[KaSroka]

Part of the process is described here: h4de5/home-assistant-toshiba_ac#72 (comment)

[martinnj]

I have unpacked the android app and then disassembled the libraries. Good for me they were .net so a lot of info was left in the libraries and they were quite readable after disassembly.

Thank you for getting back to me, I might take a shake at getting a look at the CIL then. :)

[Zyxl72]

Hi , i want to reactivate this little Topic and ask if you would help with coding a "Toshib-Estia-control" API?
i have an Estia and use the app and got the app running on an avd and could intercept all the traffic,
so i could provide you a lot of informations and did already identify a lot of the state-string.

To integrate the Estia to Home-Assistent h4de5 would need this API.

would be great if you could help us.

[Zyxl72]

Pusher ..
I would really appreciate your help.
My use Case is that i can use HA for turning the Estia with Water or Heating on/off as with the 4 time Slot of the app there is no really control possible.

BR

[KaSroka]

Currently I don't have enough time for this. Also I don't have such a device so testing would be hard. I will be more than happy to accept a PR with required changes, but on the other hand this library is very AC centric, so it may be hard to integrate changes without breaking API.

What is included in the state string? It would help me identify work needed to do it.

[h4de5]

i cannot give you detailed instructions as I never tried this out myself, bit I just read that it is compatible with google assistant. maybe that way is already providing enough functionality.

[Zyxl72]

I could give you my developer account with access to my Estia, it is controlled with the same App from Toshiba.

IMHO i would create a new API for Estia by cloning the AC API. This would most likely lead to a seperate Toshiba Estia Integration in HA.
Here i would need your opinions.

All the Informations i have result from intercepting the traffic.
I documented the results from the http REST API calls in https://github.com/Zyxl72/home-assistant-toshiba_estia

in the amqp Calls i saw that the Commands used, differ from the AC
I had a look in your Code and think that of course the classes of the devices with the properties have to be adopted and
most likely the interpreter of the results, what i'm most unsure is how to adopt the amqp results to the classes.
Where i hoped that you find out more easy with the unpacked APK informations, as the same apk is used for Estia.

[KaSroka]

AMQP should provide the same format as ACStateData. Looking at your findings it indeed looks very similar. A few adjustments will be needed mainly in the values parsers. It may be more beneficial to try to merge both ac and heatpump functionality in this lib.

[Stuckcesium]

I'm interested for this feature also... can we expect to get an enhancement of the current version ? or it's not planned ?

in parralell
I had a look to the documentation written by @Zyxl72 https://github.com/Zyxl72/home-assistant-toshiba_estia and I didn't see updates request, I saw only GET..

[KaSroka]

I'm currently out of time for this project. But I'm open to any contributions.

[Zyxl72]

Hi
Update are done by AMQP requests, which i did not manage to simulate.

We hope KaSroka will find time soon as he is owner of the API used in the AC App, which we want to reuse.

I for myself found a workaround with an actor for my raspmatic and the Estia has connectors with which you can turn on/off the heatpump for water or heating.
BR

[Stuckcesium]

I for myself found a workaround with an actor for my raspmatic and the Estia has connectors with which you can turn on/off the heatpump for water or heating. BR

hum interesting @Zyxl72
can you say more on that please ? when you say connector is it physical connector directly on heatpump? managed by a relay ? do you have schema /doc/photo ?

thx in advance

[Zyxl72]

Here you see two Pages from the Installation manual, i used I/P 5 and 6 with the actor.
On the first you see whete to find CN21 in your Estia Unit.

But as mentioned, you can't use the commands with the APP anymore, as this overrides any command

BR

[Stuckcesium]

wooh thanks a lot @Zyxl72

It seems to fit perfectly to what I want to do (eg. switch of and on hot water production based on solar production...)
and it's a good news also for me because I never bought the wifi module (with the related phone app), I was waiting for a better HA integration.