Hi,
/usr/share/openhab/addons/ did the trick!
thanks!
Kim
1 Like
I use this binding with a chest device.
There is the “underfloor heating” function for the vertical air flow direction.
Can this be included in the binding?
Otherwise the binding works perfectly, thanks to the developer!
Thank You!
Hi @violine
For now it is not the intention to add new functionality. At this point I want to deliver a stable version so that it is approved and included as an official binding.
Maybe when the version is more stable I can add it.
Greetings Alexander
1 Like
Understandably!
I don’t know if it’s just a display problem?
The corresponding item returns NOTAVAILABLE; you can choose from Stopped, Swing and Windnice.
I couldn’t find the Windnice function on the chest device.
Best regards
"Great, when do you think it will be available in the official binding?
I don’t know. I need an approval from the openhab development team. To get that, i have some work to do. This i have to do in my spare time. And i also need to keep my wife happy 
3 Likes
I can confirm similar issues.
RPI 4 / 8 GB, after upgrading OpenHABian from 4.1.2 to 4.1.3, the Onecta binding was gone without a trace, but I had the failure mentioned before when trying to install it with the Plugin Manager.
Manually copying the Jar file to the plugins folder made it come back to life, but of course now it’s no longer listed in the GUI for installed plugins, but well, as long as it’s working that’s a luxury problem 
More interesting was that only the most recent 4.1.x jars are working. The newer 4.2 complains about missing dependencies in the logs.
Is the 4.2 version of the binding intended explicitly for OpenHAB 4.2.x and the error is somewhat expectable, or should it be working anyway and may point to an issue?
Yep, I also received this message a couple of minutes ago.
Iam trying to find out what to do. If an developer has an idea please let me know.
Here I could use some help from a specialist. In order to connect, a redirect must be done from the binding where the user must give the binding permission on the daikin site. Then a key is sent to a return url with which the binding should be able to log in.
i.e. need help
Here is link for the case someone wants to contribute and got no mail.
Specification
Documentation
1 Like
I just got this too. Unfortunately I have no idea what to do with it.
Hi @Alexander_Drent,
as I know the Miele@Home binding uses a similar process. Maybe have a look there.
Cheers,
Daniel
Oh,… Thanks. I wil take a look at it
Hi @Alexander_Drent,
have a look at the HA integration of OneCTA. There is a pretty neat readme how to get the new API working. You need to create a developer account and an “app”.
I would do a entrypoint like /mielecloud in the Miele binding, which retrieves the token.
Cheers,
Daniel
1 Like
Hi @Alexander_Drent,
how about doing it in two steps / getting the initial auth flow working via postman is relatively simple. That gives us an ‘access’/‘id’ as well as ‘refresh token’. The refresh token is valid for 1 year and we always get a new one whenever exchanging it for a new access token.
So maybe the “easiest/fastest” for now is to provide a refresh token as part of the configuration and then we’ll live of those refresh tokens for a while until the entire flow is integrated into openHAB.
I’d love to support on the code side (I’m very fluent in the Microsoft ecosystem but Java is giving me some challenges) - I can provide a postman collection with the authentication flow setup, if that helps?
Nils
1 Like
Hi Nils,
Thanks for you response.
I have also managed to generate a token and after some code adjustments I have managed to connect the binding to Onecta.
But!
- The new refresh token cannot be used in binding, this token is not valid on the old Diakin domains.
- The Refresh token is bound to an account and can therefore not be shared with others.
- The Refresh token is valid for one year but can only be used once.
- There is a rate limit of 200 call /24h
Greetings alexander
Hey Alexander,
I can try to help mapping the curent requests to the new ones - regarding rate limiting, I’m sure we’ll find a way - and regarding the refresh tokens - of course they are bound to an individual account - but I could write a howto on how everyone can generate “their individual refresh token” that we’ll then accept in the configuration?
Nils
1 Like
Did not dive deeper, but couldn’t the refresh token be received and refreshed via a simple http call with credentials? Normally this is is how auth works.
Hi @dandjo,
that’s exactly how it works - it’s a simple post - that’s why I was suggesting to go for an external solution for the first refresh token (as a quick solution - as that’s complicated with the redirects) and then work only with refresh token for now.
Getting an access token with a refresh token is a simple as this call (POST)
https://idp.onecta.daikineurope.com/v1/oidc/token?grant_type=refresh_token&client_id={{clientId}}&client_secret={{clientSecret}}&refresh_token={{refreshToken}}
Nils
1 Like
Hey Nils,
Thanks for the help.
it seems that the mapping of the commands are the same. only the domain is different. i am trying to adjust the binding a bit so that it can work with a new refresh token and not executes the current login procedure.
The binding can also start with the return code of the redirect page.
Now i use as return adres https://home.myopenhab.org/test
this will give
gr. Alexander