Just came back from my vacation, that’s why I didn’t respond for a while
I don’t have a timeline yet, basically all features aside from the current ones rely on my being able to obtain more information about Remeha’s API. There is no official API, so I’m talking against the one that the Remeha Home mobile app uses. This API is not documented apart from what some other people out there have been able to reverse engineer (for example for the Remeha Home Assistant integration). I have sent an email to Remeha but so far they have been unresponsive. I guess they don’t really care about 3rd party integration with their systems. If anyone wants to send some emails to Remeha support to further press this issue that would be greatly appreciated!
I will! Perhaps you have the email so we all can send it to the same address?
I hope it helps because Remeha isn’t that consumer friendly. They always refer you back the install company if you have questions….
I’ll look into it. Probably some value is no longer coming back from the Remeha Home API and I’m trying to access that value with a startsWith function.
The heat pump probably has this value somewhere internally and show it on the built-in LCD display, and probably the installer or Remeha technicians can access it. However the eTwist Smart Thermostat does not report the value to the Remeha Home cloud platform, meaning I cannot grab it from there in the Homey integration. Whether the eTwist doesn’t receive the value from the heat pump at all, or the eTwist simply doesn’t expose it I don’t know. You might be able to check this by connecting another OpenTherm-compatible smart thermostat to the heat pump.
I know the wired eTwist does report it and it’s visible in Insights. See picture.
Strangely enough in the beginning it also reported the CV water temperature but that unfortunately doesn’t work anymore so it seems Remeha does change these things on their end in some updates.
Yeah Remeha doesn’t have an official API so we’re all just reverse-engineering whatever their mobile app talks to. None of it is officially supported by Remeha and they probably change stuff when they want to for their own app. I’m quite surprised the whole authentication method still works actually
It was a far stretch of course, but either way the data doesn’t come from the wireless eTwist, and likely never will as Remeha doesn’t seem to be actively adding functionality to their systems after shipping.
