I did that and they finally got back to me, here is what they said
Thank you for your inquiry regarding the hub firmware update from version 0606 to 0608. We greatly appreciate your interest in the improvements we have made to our products. Version 0608 mainly focuses on enhancing the overall performance of the device and optimizing the interaction experience between the hub and its connected devices . In addition, when the local hub is connected to the internet, the settings for local subnet devices in the app will now take effect as well. The hub supports both public network remote access and local subnet connections simultaneously, without any conflict or impact on your existing app configurations. We hope the above information clarifies your questions. Please feel free to contact us if you have any further inquiries about this update or our products. Best regards,
So it was just optimization. Disappointing that they didnāt at least support more device types.
TL;DR: what is the correct and working way to add the YoLink integration to HA for a cloud-based hub?
I have a YS1603-UC hub which had been working fine for over a year, until recently everything went Unavailable. I am trying to start over with reinstalling the integration, and am not able to get it to complete the authentication in the config flow. My problem is really similar to one posted a while back by @007DJ but I could not find if a solution was ever posted.
When I just add the integration, the config flow fails fast with a logged error Cannot provide OAuth2 implementation for cloud services. Failed to fetch from account link server. and never prompts for anything. After that failure, the config flow is left in an in-progress state but never recovers.
The documentation page āCommunity Notesā for the integration says āpleaseā not to use UAC, but I tried creating UAC credentials in the yolink app. Then when I attempt to add the integration from a mobile device that is running the app already, it sometimes gives me the āneeds to open an external websiteā prompt, opens the app, which pops up an authorization dialog, which I Allow - but then the config flow never completes and the integration is not added. There are different scenarios depending on whether HA is running in the mobile app or in a browser, but neither way works.
OK so the question is, what is supposed to work nowadays? Knowing this will at least let me focus on where the right way is going wrong. I suspect there is a vestige of my old credentials somewhere, but I canāt find it. E.g. there is a revoked set of oauth creds in my yolink account - could that matter?
I am running HA in docker. Not using Nabu cloud (although it is āenabledā and I know it can be used for account linking).
Full Disclosure: this is related to a prior post in another topic that has gotten no notice. If I get a solution I will update there.
I setup HA a few weeks ago and added my existing yolink hub which was also being accessed by a different home automation controller. I followed the directions, used my account email and password, and it logged in, took a few minutes to discover everything and itās worked as expected since then.
Awesome, thanks for responding. I guess I need to focus on why I get the Cannot provide OAuth2 implementation for cloud services error when the config flow tries to start up, instead of getting prompted for login credentials.
So I finally noticed something new. The battery levels are consistent now in HA over Matter. But they still donāt match the Yolink integration.
As we all know, the Yolink app shows us a battery with 4 levels. The Yolink integration shows it as 100, 75, 50, and 25 where as the Matter integration shows it as 80, 60, 40, and 20(no 100%).
Itās a nice QoL change. At least we can depend on those battery percentages now to give us an idea of how much time our devices have.
Iāve been following this thread with interest. Iāve had a YoLink hub 2 for about 3 years with devices I very much depend on for monitoring various things in my house, and also involved in automations that YoLink sensors provide the data to say its time to turn a certain fan on via a not YoLink switch
I get the value of the local hub. My monitoring and reporting, as well as important house automations break when the internet goes outā¦ rare, but it happened just this week.
Iām trying to resolve between these 2:
a local hub that removes the internet / cloud from automations that are strictly local
the point/value of matter in this?
It has to be how the hub connects to HA, but why is that needed? LoRa specs destroy matter specs by any measure for sensor applications. Itās a simple connection to HA for serial line speed transactions, WiFi is fine for that.
The same sensor battery output can be formatted to whatever
The Local Hub gives you the option of using either Matter or MQTT for the ālocal networkā component. I played with Matter a bit then turned that off and switched to MQTT. That has been solid (and fully local) for me since.
After several more days of trying random things, I was finally able to re-add the YoLink integration (cloud), using just my account login, from my desktop (not the mobile device with the YoLink app). The last thing I changed before it finally worked, was changing my routerās DNS resolver from the ISP default to 8.8.8.8, which I did for unrelated reasons. Next time I tried right after that change, it worked, after 2 weeks of failing. I donāt know what really made the differenceā¦ just posting this in case someone else runs into this situation.
