YoLink integration

I see the Local Hub is back in stock and wanted to see if anyone is having any issues with mqtt on it. I emailed support and they said mqtt is now in the official firmware and not just beta. I really want to get a local option going for my yolink devices and not have to rely on the cloud.

1 Like

My bricked on a firmware update :frowning_face:

Are they sending you a new one? After I told them what happened they said they would send me one when they’re in stock again. And that finally happened because they just shipped me a new one this past Wednesday.

Only difference is that it doesn’t come with a sim card. Which doesn’t bother me since I was never going to sub to their service.

1 Like

I need to reach out, just read your post about a similar experience!

YoLink customer service was very responsive and they are sending me another hub. Appreciate the advice!

1 Like

I finally received the Hub yesterday. Connected it to HA via Matter with all the device I still use. All my sensors show up and work fine. No disconnects after a day so Matter is finally functional for me like it has been for others.

Some other devices still don’t work over Matter but I can live with that. Hopefully that can be fixed later but at least all my sensors work locally now.

What firmware is currently on the new hub?

Still 0605, so nothing since the one from a few months ago.

Appreciate it! Going from 0604 to 0605 bricked my first local hub.

Would you mind outlining the steps to get a Yolink device connected to HA via Matter on a new local hub?

I can start Matter in the Local Network section of the Yolink app, but then how do I connect this up with HA?

Any help would be much appreciated!

2 Likes

I got my local hub today but can’t connect it. I started matter on the device but HA Matter server addon can’t commission it because device does not respond on UDP request from HA to device port 5540. Also Local API HTTP port 1080 does not respond too. I see that server sends SYN request to device on port 1080 but no any packets back.

I didn’t mention this but I couldn’t get it connected either. I contacted Yolink and they said they did something on their end and for me to try again. After I restarted the hub by flipping the power off and on it finally worked.

So contact Yolink and you may need to provide them with some information about your hub in order for them to help you.

Yes I contacted with support by phone. They took my account name, email and told me that I have to wait email.

That’s a little ironic for something that is supposed to be local… !

1 Like

I have updated Local Hub firmware to 0606 and now Matter does not work at all and even Integrations page can’t load data :frowning:

Thanks for the heads up. I suggest you contact Yolink and hopefully they can help.

I do see the new update. But here’s the thing, I got the local hub around March. Then waited a month for an update to fix the issues it has. Then that update bricked it and I waited another 2 months to receive a new one which finally works.

So I’ve waited nearly 4 months since I ordered it to receive a working product. I’m not taking any risk lol. I’ll update when I see some people say it’s fine on their end.

I read his post and said the same thing to myself. My replacement arrives this week.

I suggest you contact Yolink and hopefully they can help.

Yolink support almost useless because only response that I got in last 4 days is ā€œWe’ve forwarded your message to the appropriate engineerā€. They have no time to contact me 4 days but published firmware that made even worse. Looks like that have no any software professionals but just 1 student that patch live system without any tests.

Hi all, I just registered to give my experience. I don’t use Home Assistant (yet), but plan on using YoLink’s LocalHub with the raw HTTP and MQTT API. I received one of the latest batches of local hubs. I had no issues adding it to the YoLink app or setting it up, but my experience mirrored Dmitry’s. Calling the HTTP endpoint would timeout so I could not get an access token. This was on firmware 0605. But I have had very positive experience with their support. They pushed 0606 to my device on July 4th holiday which I was not expecting, and that fixed the HTTP issue. I can make calls via HTTP and see devices that are added to the Local Hub in the JSON response.

The issue I’m having now is I’m not receiving any MQTT events. I believe there’s some sort of syncing issue where the MQTT broker is not in sync with the HTTP API. With the 0605 firmware, a little LAN icon would show up on the device info card in the YoLink app next to the Wifi icon to indicate it’s joined to the Local Hub. With 0606 firmware this doesn’t seem to be working anymore, even though the devices are showing up on the Local Hub device tab. So that’s where I’m at now, but I feel confident it will be resolved with another firmware update or me tinkering with the app again (removing everything and setting it up again).

Other people that are on 0605 seem to be working fine on the Discord channel, so I’m not sure if they have the older batch of hubs which might be slightly different HW or just that there’s something unique with my local network.

Well I guess you can’t say they arent trying! I use the VirtuAlarm 24/7 monitoring so I am reticent about moving to the local hub lest I lose that functionality… I heard on this forum that they are no longer actively marketing this service - but I need to ask them if the local hub would continue to support that.