I’ve been playing with the API, but honestly with MQTT it’s a dead end b/c it is so slow to poll via UAC.
The developer said two things 1) matter is new, they are working on stability, etc and 2) MQTT is coming.
Once we have MQTT, I think we will have a plug-in replacement for the HAAS pluging basically.
I really hope that’s the case with your last sentence. Would be convenient if it could just do both cloud and local.
@Khouse85 Nothing has changed in my end. I did message them a bunch over the weekend but have stopped since then. I figured they’re working on it so I’m just going to leave them alone for a week or two before asking again.
Many thanks to you and Rice_Eater for your updates about developments involving the new cloud-free hub.
It will be amazing if the new hub can support MQTT, as both a publisher and subscriber (for relay control), for all YoLink remote device types. A reliable local-only LoRa integration for HA is my holy grail!
Known Issues:
The “Local API/Matter” section in the app persistently displays “Failed to load data.”
• Cause: Incorrect initialization configuration of the Hub.
• Fix: Use the “Restart Local Network” button in the latest app (v1.40.37+) or contact our technical team for troubleshooting.
• Resolution: Will be fixed in the next firmware update.
LAN devices show as offline in the app.
• Fix: Follow the troubleshooting steps in Issue 1. If unresolved, contact our technical team.
Local API does not support MQTT.
• Resolution: Support will be added in the next firmware update.
Cellular-related information is not displayed in the app.
• Fix: Update the app to v1.40.37 or later.
“Network Credentials” error when adding devices to LAN.
• Cause: Missing network credentials for the device.
• Fix: Contact our technical team for assistance.
Limited Matter integration compatibility & new LAN devices not recognized by the Matter platform.
• Status: Matter integration is in its early stage; optimizations are ongoing.
Matter integration occasionally stops running unexpectedly.
• Status: Technical team is investigating the root cause.
Incorrect device status on the Matter platform after Matter integration restarts.
• Resolution: Will be fixed in the next firmware update.
LAN schedules do not execute.
• Cause: App does not support modifying the Local Hub’s timezone.
• Resolution: Will be fixed in the next app update.
Factory Reset button on the Local Hub is non-functional.
◦ Status: Currently, Factory Reset is only supported via the app. Hardware reset will be enabled in future firmware.
Technical Support Contact:
Email: [email protected]
Note: Include “P1606-related issue” in your message and request escalation to the R&D team.
Thanks for giving us an update on the current status of things and the solutions for each problem as they become available. It seems most of the problems will be solved in the next update. Which is good to know.
So the only one that I’m having that won’t be is the Network Credentials issue. So I’ll make sure to contact support about that and hopefully it gets resolved.
@HA.YoSmart Good to see you here YoSmart! Any time and investment to put into the HA community will pay off as not only is HA is huge, but it’s growing faster than ever and will dominate the home automation space!
This is great info. Unfortunately because of #7 my hub is essentially unusable right now. Look forward to all this getting resolved and I’m happy to provide any info I can to assist with investigating #7. Thanks.
Is there an estimate for the new Firmware - trying to decide if I should start integration as is or wait for MQTT
Been tearing into this new hub since I received it. Due to the hub being in active development, I am disinclined to disclose too much information.
I have managed to achieve a firmware dump of the device, gained root shell on the device, have located their code (written in JS but obfuscated by webpack).
Still a lot to investigate, like the openvpn daemon I found on the device.
If you would like to collaborate on the reverse engineering efforts of this ecosystem, feel free to reach out to me.
Pretty concerned about the OpenVPN daemon. Thinking I may need to isolate the device with some firewall rules just in case. I don’t like the fact that it’s possible for it to tunnel onto my LAN.
Technically that’s true for every device, but I’m not extremely worried about Lutron for example.
That said poking holes for Matter, API, MQTT, etc makes sense I think.
Or maybe I’ll just shove this on my IoT VAN and rely on MQTT and API instead. Matter isn’t really a great solution for me with HA, anyway.
Same, extremely concerned about any closed source device on my network. Obviously there’s nothing you can do about some products, notably Apple products, but if possible any device either goes into an IoT or NoT firewalled subnet and this local hub will be no different. Unfortunately I haven’t been able to get the local hub to communicate with HA via matter when on a separate subnet, even when all communication to and from the hub and HA is allowed. So I’ll be waiting either for MQTT or an integration that utilizes the hubs local API. I’d prefer its own local integration instead of MQTT so it keeps the device separate from MQTT and doesn’t depend upon a broker. Hopefully this is on the roadmap.
Are you using mDNS reflection for the matter discovery across vlans?
Yes, but I just realized I don’t have IPv6 enabled on the subnets. Most likely this is the issue.
If Yosmart is monitoring this thread, please allow the reporting time and temperature/humidity delta reporting interval to be configurable for matter, MQTT or local API when the thermometer is bound to the local LoRa subnet. It’s understandable that Yolink doesn’t want to store that much time series data on their cloud servers but those using the local hub and their own home automation system to store the data should not be bound to these same reporting restrictions.
The current five minute sampling interval is not optimal for many situations even at the cost of lower battery life. For instance when used with a HVAC or humidifier as a “follow me” remote thermometer/hygrometer for sensing room environment the thermostat/hygrometer needs to receive near real time data and 5 minutes is not granular enough.
Yosmart has the opportunity to sell many local hubs and thermometers as the current range of range of available battery operated thermometers is very limited. I for instance would like to replace my current fleet of Oregon scientific 433 sensors as they are aging and Oregon appears to be not offering models with large readable displays. This would be sought-after for anyone who has a greenhouse or wants to monitor their individual room temperatures closely.
Glad to see work going on this new hub! Eagerly watching to see if anyone manages to get the device encryption keys for Lora… I’ve got a gateway sitting here waiting for new devices to try. I ended up ditching all my YoLink gear a year ago back when local control was still a distant dream. Le sigh 
Don’t have anything to add to that but I do have an update. It appears they fixed the Network Credential issue. Two of my sensors that had that problem and they work now.
I was hoping that meant more but when I readded the hub back to Matter I’m still not getting my motion sensors. Baby steps I guess.
I’m away at the moment but I’m curious if they fixed the thing where Matter goes offline after a couple hours.
I can handle the current limitations as far as device types, but as long as the Matter connection won’t stay online, the hub is useless.
That’s what I’m currently testing. It was constantly going offline for me as well. So when they fixed the Network Credential thing I decided to pair it to HA via Matter again to see if anything has changed.
As of this post it has been 2 hours and 24 minutes so far. Normally I was getting 2-6 hours before so I’ll edit this post later tonight to let you know how long it lasted or if it’s still working.
EDIT: And it’s dead. It lasted 3 hours 29 minutes and 5 seconds this time lol. I’m not going to bother again until we get that update that’s supposed to fix most of these issues.
At the price it’s no longer worth it. I can buy a lot of Zigbee devices for the cost. I bought into yolink with their promise of adding local support. I have been moving slowly over to zigbee replacements for their devices. It’s really sad they did this as its a great technology and the battery life is incredible on these. Hope they consider changing the price.
Has anyone elses device gone totally dead/offline? I swapped hubs a few weeks ago and it was working fine, then one day it decided to go offline and even though it has lights on it continues to show offline. I brought up my old hub in the mean time