I just followed your steps and I can confirm it is working great also with Ochsner AirHawk 208C! Amazing work! 
1 Like
Update - converted it to a HACS custom repo to allow for easier install / updates
1 Like
Hi, this is great! That is what I was looking for all the time! When reading,it was to much for me to understand at once and I will not have time to follow this up until end of the month. Once I do, I will report my experience.here
Thank you very much for this excellent work and time you spent into this topic.
A shame, that Ochsner doesn’t support an api officially, In a mail - discusssion with ochsner erarly last year they said " We are discussing smart home issues internalyl"
Pretty sure the support won’t be any better for this one than for the modbus 
in fact better not tell them at all lest they break it.
It should theoretically be possible to convert this into a dynamic integration that only requires you to input your ochsner credentials once for onboarding and your local controller ip for the api, and have the integration automatically parse all the values in the config file with the same logic as the app, and add them to HA with their names and types already configured. But for now, I think its simpler to go with the manual route. Most of the values you really don’t need to view / control in HA anyway, mainly a few key ones are of interest I guess. But maybe once the AI tools get a bit better that can also be done in a prompt or two…
Alright. Apparently the AI made me a liar. After 5h of back and forth this afternoon I finished the thing I said I wouldn’t do:
OTS-HomeAssistant - v1.0.0 Release!
It’s now a full-blown UI Integration where all you have to do is add the Repo to HACS, and then add the Ochsner Integration, enter your user and pw once, then enter your heat pump IP, and it automatically imports all readable values and even auto-translates them to readable names! No more manually searching for values with the python script!
It even groups all the values all by heating circuit when adding them.
AI is really getting crazy.
I’d recommend going through and disabling any entities you don’t need / want to control once, to reduce the polling load, and so that your HA entities are less cluttered.
Also, the cloud credentials are not saved, they are only needed to initially download the config during setup, after which the integration runs entirely offline.
I updated the repo on github, let me know if it works for you. If you still have the old climatix_generic: config section, either remove that and do it entirely via the UI, or you can also rename the section to ochsner_local_ots: and continue using your manually configured version (at least in theory). I’d recommend just using the UI version since that’s what the latest release has been tested for.
Note: I also just realized that Ochsner released a new app last year (Ochsner Smart app as opposed to the OTS app), and that app wants me to update the heat pump in order to use it. Would be curious if anyone managed to get this script to work after they already updated their system to work with the new app still, or if that will brick it.
1 Like
Thanks a lot to @permissionBRICK for the great effort in integrating the Ochsner heat pumps.
Also thanks to @Alfred99, I’m using the Modbus integration as well.
I personally have an Air Falcon 212 C11 AT200. Since I’m using the Ochsner Smart App, I had to update the heat pump firmware about two months ago.
I’ve just installed version 1.0.3, and so far everything is working perfectly!
1 Like
WOOOHO Thanks a thousand times @permissionBRICK
Confirming that your integration is working fine on AirHawk 726
Finally I am able to see more details and automatically set the option of warm water to “reduced” in summer where PV makes warm water.
And finally I am able to use the BOOST option in HomeAssistant
1 Like