My local hub is suddenly working perfectly. Not sure if support pushed a minor update to it, or if rebooting it has fixed the issue. But it’s working! Both HTTP API and MQTT are working as expected.
Just updated to 0606 and all seems to be working well. I really only use it for the matter integration however. I will report if I notice any issues.
Has it opened up new devices? Right now my Flex Fob and Siren are in HA over Matter. But I can’t do anything with them. So I’m wondering if you have a device that works now but didn’t work before?
Would someone mind sharing how you accessed the MQTT information? Any hints or general approach to this would be much appreciated!
Unfortunately my lock v2 and vibration sensor still don’t work with the updated software.
Leak detect, motion, contact sensors all still function perfect.
I finally updated, nothing changed on my end. My Flex Fob and Siren still doesn’t do anything over Matter despite being bridged over.
I’m not surprised your tilt sensor isn’t working but the lock not working is surprising. I figure that’d be a no brainer like a motion or contact sensor.
Would someone mind sharing how you accessed the MQTT information?
There’s instructions on the yolink website, but I believe it’s currently geared towards developers. But basically the process is, obtain clientId and clientSecret from the YoLink app by going to the Local Hub → Integrations. Make an HTTP request to Local Hub get an access token. Use an MQTT client to connect to Local Hub using Client ID and access token from previous step. Subscribe to topic using Subnet obtained from YoLink app in Local Hub details. Make sure the ports for HTTP and MQTT match what’s in the Local Hub documentation as they’re different than the cloud API. And pay special attention to the naming of the MQTT topic which is also different than the cloud API.
And more verbose details about MQTT here:
2 Likes
Brilliant! That was what I needed to connect the dots. Thank you!
Next question: I had an existing (non-local) hub, and then added the new local hub. The new local hub now shows up as a device in my YoLink app, similar to other devices such as leak and vibration sensors. I can click on the “YoLink Local Hub” device and everything seems to be as expected, with the “Local Network” link at the bottom, etc. Everything works (Matter and MQTT), but it seems strange to have the Local Hub “subordinate” to the non-local one. So is this the right way to have things set up, or would I be better off killing the old non-local hub and all its device connections first, then fresh installing the local hub?
1 Like
I don’t think the Local Hub is subordinate to the cloud hubs. The cloud hubs should also show up in your device list. Maybe you just need to change your tab to All Devices.
But I’m also a bit confused on the role of the cloud hub once you have a local hub. The local hub is not like a fail-over device where if the cloud hub loses internet, you can still fallback on local hub automations.
I think instead Local Hub is independent of the cloud hub. Once devices are added to the Local Hub, I believe they’re no longer using the cloud hub at all. So if you add all devices to Local Hub, then it seems there’s no purpose to having cloud hub. Someone can please correct me if I’m wrong. I have two speaker hubs and one OG hub and I’m not sure what to do with them once this is all setup and working reliably. Right now I only have a few spare sensors on the local hub for testing purposes.
Virtualarm Service with Yolink for 24/7 monitoring?
I recently bought a YoLink Local Hub - I have been able to manually (via the HA command line) subscribe to MQTT messages from YoLink. Using the Mosquitto Add-On broker, I am trying to get MQTT via bridge mode - which so far have not had any luck. Does anyone have a working MQTT setup with Home Assistant and the YoLink Local Hub?
Here is what I have configured currently for bridge mode (yolink.conf):
connection yolink
address 192.168.0.198:18080
remote_username my_username
remote_password my_password
cleansession true
clientid yolink-bridge
topic ylsubnet/C000fe/+/report both 0
It connects successfully, then disconnects right afterards - over and over. I never see any MQTT topics in the Mosquitto broker add-on. Only manually subscribing via the HA console do I see messages.
1 Like
Well the Local Hub has let me down in this specific case. So for years I had a motion sensor in the mailbox and it worked perfectly fine without issue. After getting the local hub I wanted everything to be local so I moved the motion sensor to the Local Hub. But it would keep going offline, even after resetting it.
Then I replaced it with a different motion sensor, same problem. Then I tried a contact sensor that I wasn’t using, same problem. Then I finally decided to stop using the Local Hub for the mailbox and went back to my original cloud only hub that I bought almost 5 years ago. And everything has been working perfectly fine since then.
It’s not a range issue because I have tested the Local Hubs range and things still worked at further distances. I also have a outdoor motion sensor tied to the Local Hub sitting by the Mailbox and it has no issue whatsoever. But when you factor in the sensor being inside a mailbox with the distance, the $200 Local Hub somehow can’t handle it while the old hub can?
Not a big deal in the end since this sensor is barely used, but still pretty disappointing.
Maybe you need to RMA the local hub. I just started using the local hub here about a week ago and have not had any major issues. I have some gate sensors that are a good 50 feet away and through concrete walls and everything is working fine - via MQTT.
I ended up using Node-Red, set an MQTT-in to connect to the local hub, and then an MQTT-out to relay and send everything to my HA MQTT Mostquitto broker.
I have all the YoLink devices in Home Assistant using MQTT - gate sensors and water temperature sensor. It would be easier if they allowed MQTT direct to a broker from the hub (which I suggested to them), but you can get around that using Node-Red.
Not all the information for the device is populated yet in MQTT - like signal strength, but I have the main things - temp, battery, open/closed working.
Other than the mailbox problem, I haven’t had a single issue since they mostly fixed Matter on their end. And considering this is just 1 sensor and a non vital issue, I don’t care to raise a ruckus about it.
Nice that you have MQTT running. I’ll just stick with Matter since I don’t know how that stuff works. Maybe someone can make a local integration someday. That’s the only way I could see myself switching from Matter.
Amen to that
Can you share your node red flow json please?
[{"id":"8437dcc0492c58d0","type":"tab","label":"Flow 1","disabled":false,"info":"","env":[]},{"id":"ca6bcb3d0876e193","type":"mqtt in","z":"8437dcc0492c58d0","name":"","topic":"ylsubnet/C000fe/#","qos":"2","datatype":"auto-detect","broker":"44a914c3ee3ebdca","nl":false,"rap":true,"rh":0,"inputs":0,"x":250,"y":320,"wires":[["379f6ae2335cbc2d","d7d28d553ed2cd0a"]]},{"id":"379f6ae2335cbc2d","type":"debug","z":"8437dcc0492c58d0","name":"debug 1","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload","targetType":"msg","statusVal":"","statusType":"auto","x":330,"y":140,"wires":[]},{"id":"d7d28d553ed2cd0a","type":"mqtt out","z":"8437dcc0492c58d0","name":"","topic":"","qos":"","retain":"true","respTopic":"","contentType":"","userProps":"","correl":"","expiry":"","broker":"0523e3ed15bfaeb1","x":510,"y":140,"wires":[]},{"id":"44a914c3ee3ebdca","type":"mqtt-broker","name":"YoLink-Hub","broker":"192.168.0.198","port":"18080","clientid":"","autoConnect":true,"usetls":false,"protocolVersion":4,"keepalive":60,"cleansession":true,"autoUnsubscribe":true,"birthTopic":"","birthQos":"0","birthRetain":"false","birthPayload":"","birthMsg":{},"closeTopic":"","closeQos":"0","closeRetain":"false","closePayload":"","closeMsg":{},"willTopic":"","willQos":"0","willRetain":"false","willPayload":"","willMsg":{},"userProps":"","sessionExpiry":""},{"id":"0523e3ed15bfaeb1","type":"mqtt-broker","name":"HomeAssistant-Mosquitto","broker":"192.168.0.14","port":1883,"clientid":"","autoConnect":true,"usetls":false,"protocolVersion":4,"keepalive":"300","cleansession":true,"autoUnsubscribe":true,"birthTopic":"","birthQos":"0","birthRetain":"false","birthPayload":"","birthMsg":{},"closeTopic":"","closeQos":"0","closeRetain":"false","closePayload":"","closeMsg":{},"willTopic":"","willQos":"0","willRetain":"false","willPayload":"","willMsg":{},"userProps":"","sessionExpiry":""}]
For Node-Red in HA, it is basically an MQTT-In to subscribe to the topics from the Yolink-Hub, and then an MQTT-Out to re-send all the data to the Home Assistant Mosquito MQTT broker.
From there, I made entities from the data of each device in HA from the MQTT data.
Have you noticed any speed/latency difference between the three integrations? Yolink cloud vs matter local vs mqtt local?
For me they all trigger at the exact same second, which is a bit disappointing.