Token? (OAuth flow support) #7
Comments
|
Ah, seems they have changed authentication. So previously you would just generate an API key and use it. Now there is a full oAuth flow. I'll look into this and get it implemented. |
|
Thanks for getting back and taking a look at this!
|
|
Turned into a little bit of a project :D. New version posted soon 🤞🏻 |
Due to breaking changes introduced by v2 for oAuth support, some hacking things done with depreciation warnings supporting backwards compatibility. When using secrets version will default to V2 which is not yet tested / implemented for all endpoints. Will be supported in the coming PRs in non-breaking way as possible. This will resolve dogmatic69/nordigen-homeassistant#7 once the HA integration is updated
Various endpoints changed so adding support for new endpoints and redirecting old requests where possible to avoid breaks. Could still be issues with the actual data, will look into that in a later PR. Upgrade required to support OAuth flow in dogmatic69/nordigen-homeassistant#7
|
@magnushasselquist Mostly implemented now, I'll do a bit of testing with this new version and push a new integration release soon. 👌🏻 |
|
Fantastic news! I will try it out as soon as you feel it is ready from your
end. :)
/Magnus
Den sön 9 jan. 2022 kl 22:09 skrev Carl Sutton ***@***.***>:
… @magnushasselquist <https://github.com/magnushasselquist> Mostly
implemented now, I'll do a bit of testing with this new version and push a
new integration soon. 👌🏻
—
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJBV5T6XUDDFRJ7PIUGJTTUVH2PLANCNFSM5J5W5JPA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Magnus Hasselquist
***@***.***
|
|
Hey ! Just to tell you that i'm really interested to ;p |
|
It's mostly working but i've side tracked into config flow. I need to finalise as I want it too :D (maybe a bit of HACS is needed for installation). The biggest side track though, was the 11000 SEK electricity bill in December, had to do some emergency heating automations which took a while to sort out as I had hardware issues :/ |
|
Hi! Just to check on status :) Anything I could help out with? |
|
Yo, taken some time off this but was actually just looking at it over the weekend. Can't do too much till next week, will push something up then. Last I recall just needing a bit more unit testing on the config flow and finalising the steps. The whole dev toolchain I was using was lame but I now found the integration blueprint so hopefully will be more fun to work on... Let me migrate it all to that setup and then we can see what more is needed |
|
Also very interested - hope you get it up and running! :-) |
|
Good news, I've got the code migrated and setup using the integration blueprint so there will be a better workflow for development and HACS support for easy install. Most tests working, need to finish off the config flow. |
|
NICE !! looking forward to test it ! |
|
Is this being implemented or is the add-on decommissioned? |
Hi,
So happy I have found this integration.
From Nordigen I get "secret id", "secret key", and by using them I can retrieve the "access token" as well as a "refresh token".
What is in more detail, the "token" needed in the configuration, is it the id, key or access-token, as per above, or a combination?
/Magnus
The text was updated successfully, but these errors were encountered: