I will Weheat ask again to fix this (and I may put out a review about this problem). Hope every Weheat/homey-owner will do so (and that we are many).
I chose a Weheat Blackbird heatpump because a few years ago they advertised loud and clear that they were very smart-home friendly. I feel let down and i am very VERY disapointed by the way they quietly pull back from this.
AT LEAST I need some basic functions to be controlled by Homey, like heating/cooling/off (which is a hassle now)
It hás to work with external EMS like (the soon to come) Homey-ems (energy management), for the energy balance in my home working well.
And: thanks Edwin, for the update.
It is currently possible to update certain settings, which are in the device settings in Homey.
These include cooling mode, sanitary hot water temperature and sound mode. Not really fancy, but at least it is possible to update the device.
@evdpol: I now see that I can change some settings in the device button and in the device settings. I was trying to set up automations and could not find any ‘then-cards’. Why are there no ‘then-cards’ to use in flows did I do something wrong? Or should I try this with logic-cards? A thing I would like to automatie is setting thermostate and heatpump to ‘cooling’ or ‘heating’ simultaniously.
New Weheat Blackbird owner here. Just a question on two different solutions (this app en OTGW MQTT). Based on @JohanP his solution, i bought the OTGW which connects fine and by sending the CS command every 50 seconds the OTGW is in control. But i don’t know how to get the temperature of the room being shown in the weheat app. So maybe not the right topic, but it definitely relates to the Weheat heatpump. And i expect a lot of experienced Weheat users over here.
I think your OTWG isn’s actualy sending the Roomtemp to MQTT, try executing this 
Edit: DA resulted in NF, but after sending AA=24 the OTGW app showed the right room temperature and also the weheat-monitor is showing the room temperature.
My response and the flow i am using to send the calculated CS value to the OTGW.
Little background: My thermostat is a Tado V3, which is connected to the OTGW and of course the OTGW is then connected to the HP. My OTGW is running version 6.8.
Sending Da or AA is only needed one, you just activate a ID to be sent.
No issues here, online and getting data…
To enthousiat: No more data, can’t even login to teh Weheat cloud/Webinterface..
Needed to login again on the App too.
On Tweakers more ppl who are offline..
Same issue here. No data and when trying to repair it shows an error. Is the API broken?
No problems here : Homey is getting Weheat data. Blackbird on the roof.
Still dead here…
Yes Weheat made the API more strict:
- RedirectURL is now tied to the ClientID. So I’m not sure if this integration still uses the ClientID of HomeAssistant, but that is now tied to Link to OAuth2 Authorize Callback – My Home Assistant
- The integration now require PKCE for the OAuth integration.
I cannot help you with Homey, but I’m the maintainer of the HomeAssistant version. See the PR here: Use PKCE for Weheat OAuth2 authorization by barryvdh · Pull Request #181881 · home-assistant/core · GitHub
And yes, it’s annoying that they keep changing the API without notifying.
I think the redirect URL should allow Homey already, and PKCE is temporarily disabled. Does it work now?
From work I’m not able to login to auth.weheat.nl so I’m kind of stuck now… On mobile it works but I can’t repair, the loginscreen disapears before I can confirm username/password..
Keep in mind that the app isn’t updated yet, so it uses a different base API URL. I need to phase out the old 3rd party API and use the new one.
