I definitely hope it happens! But I also like the idea of maybe getting something like esphome running on this thing for total local control.
I hope the local hub will not require different sensors 
1 Like
I have the speaker Hub and 2 leak sensors
Android app works fine
Tried the HA integration (which said Done! Your account is now linked)
Devices show correctly but No states are shown or updated
@Eric-YoLink Any idea when the HA integration will support multiple homes? The YoLink app supports it, but no dice on the HA side 
I have the same issue. All set uo and working with app (8 door sensors, 2 motion sensors) via the speaker hub which is also yolink.
I also had the integration done / accounts linked.
I did this with Alexa directly to and have that account linked.
Neither Alexa direct or HA can see the state of any device. They see the device but do not get triggered. I have tried to force the app to alert āAlwaysā but no luck there either.
So I have a lora system that works with the app only and although itās integrated with HA and Alexa the integrations fail to recognise states.
How goes the progress?
I recently got the Ethernet hub and a few X3 T&H devices along with an outside temp sensor. I was able to easily add them to the hub. After that adding them to HA was very straightforward. The T&H sensors are in some large commercial fridges inside my metal barn where we keep things like eggs and milk . The hub is approximately 100ft inside my home with metal siding. They have been working great where previous wifi T&H sensors would never work.
Hoping for local integration but plan on getting some more types of sensors due to their range for our small homestead.
1 Like
Hello, you replied to me that the local control will be available by end of 2022, it is July 2023 already and the local is not available yet! When do you think it will happened? I invested a lot of your product already and referring your products to my customers too.
Thanks
This might help:
I, too, would very much like to have a local control YoLink hub. If or when that happens, Iāll definitely be buying it. In the mean time, their stuff works pretty well and is reasonably priced.
As for @Eric-YoLink, he gave us the best info he had at the time. Companies plans change and some things are harder than initially thought. Iāve been hung out to dry on roadmaps that never panned out. Doesnāt matter how many disclaimers you give, people are always sore.
Enjoy the product they did deliver. Give them feedback on things youād like to see. But give Eric a rest. I donāt even think heās in that same job anymore.
6 Likes
Like the above commenter, I also would like to see support for local control of YoLink sensors. However, unlike the above commenter, for me it was a dealbreaker and is the only reason I chose not to enter the YoLink sensor ecosystem at all.
In my system, disallowing any raw sensor data from leaving the premises is a hard requirement. This is both for security (to eliminate any risks associated with data breaches in the public cloud) and for control (to eliminate any ongoing hold a profit-seeking company might have over my private system). To achieve this end, any brand-specific hubs or WiFi enabled devices that are in my setup must be blocked from accessing the internet by the router.
After doing all the product research, I am saddened because the YoLink sensors really do seem to be among the best on the market (great battery life, long range, affordable, several different sensor options) but for me security and control take precedence.
It feels important not to encourage empty corporate promises by not buying any products whose suitability is contingent upon them so, while I absolutely would have purchased YoLink sensors if a local control hub was available, instead I will list the competing sensors that I actually did purchase to document the business YoLink could have had and offer alternatives for others who may be building under the same design constraints. Hopefully, folks find this relevant to the thread as it helps illustrate why the current YoLink integration is insufficient and draws attention to the specific business consequences YoLink is suffering because of this shortcoming.
At the present time, I have been focused on water leak sensors and have purchased the following:
- Govee 433MHz sensors (without hub) + RTL-SDR Dongle
I also considered the Treatlife zigbee sensors + SONOFF zigbee 3.0 USB gateway as this combination also satisfies the local control requirement.
3 Likes
Iām having a similar issue to so other recent posters on here.
i.e. Iāve added the YoLink integration, signed in and it has discovered all the devices correctly named (4 x flood) along with the entities but the status for everything is unknown.
Is there something Iām missing in setup as clearly others are working fine?
Thanks
I have been working on a reverse engineering effort of the yolink hub to allow for local communication and I am still very optimistic about getting the current hardware version of the hub in a state where local communication is possible. Below are some notes about the effort:
I have managed to connect to the hub via the debug header present on the board, have dumped the firmware, and have analyzed a fair bit of it. In pursuit of this, I identified that the popular reverse engineering tool, ghidra, does not support the processor present in this device. As such, part of this effort has been spent building out the support within ghidra for further analysis of the firmware binary. The merge request for xtensa support is here: Add Tensilica Xtensa processor support by austinc3030 Ā· Pull Request #5442 Ā· NationalSecurityAgency/ghidra (github.com)
I have been partially pulled away from this project as we are expecting our first child in about a month so my time has been more spent on baby prepping.
That said, I do plan to continue to work on this project as I would love local access and really like the yolink HW.
Some ideas I have for local access involve changing the server that is hard coded into the firmware to point to a local server. Another option would be to redirect the network traffic from the device to local broker. It does appear the hub uses normal MQTT to communicate with yolinkās servers.
At this point, it is looking like any local access will require some hardware interfacing with the hub, i.e. very similar to sonoff devices where youād need to connect to the debug pins.
My ideal solution would be to drop something like esphome or tasmotta or something onto the hub but this would require REāing the communication protocol between the esp32 board and the proprietary yolink chip that is present in the hub.
I will work on open sourcing some of my research as time permits. If anyone has RE skills and wants to join me in this effort, please contact me and I can likely get you things sooner than it will take for me to open source what Iāve found.
1 Like
For what itās worth, I did just come across this: Feedback for The IoT Bridge: A no-code LoRaWAN Gateway with built-in support for hundreds of sensors : r/homeassistant (reddit.com)
And also for what itās worth, once theres local control, Iām ready to drop almost $1K in one order for various sensors and devices. So needless to say, Iām still very interested in local control.
They are supposedly coming up with a hub that is local. Vaporware/Check is in the mail (lol). If you switch to all local control, then you lose the one thing that Yolink offers that as far as I know, no other integrations offer. 24/7 monitoring and alerting the police/authorities if you do not respond - for only ~$9/Mo for an unlimited number of devices (per hub I would think, not sure).
I have all of my smoke detectors and leak detectors set to be armed 24/7 for same, and what I call my access point detectors (door and window, motion) set to be armed while I am away. They have a keyfob for an alsrm (four buttons) Home/Away/Armed Home/Panic - actually a variety of fobs with differing numbers of buttons. I told Eric I need a panel to put by some doors with an LED to show armed or not etc. (Green and Red etc.). He said they are working on LCD panels they will come out with soon that can be used for that purpose.
So - then being stuck not just local with them - is no so bad. The monitoring company they work with is called Virtualarm
I have asked several times across many forums - but never received an answer. Is there a monitoring service that would work with home assistant admins that is vendor agnostic - and if not, what other hardware sensor vendor that has an HA integration - offers monitoring to call the owner and then the fire/police?
2 Likes
Thanks for the update. Iām watching your progress with great interest.
Small update as I continue my pursuit of this project.
It appears that the chip the hub is using for Lora communication is a SemTech LLCC68. There is also an ESP32 chip on the hubās board. It would appear that the ESP is communicating to the SemTech chip via SPI and is beginning to look very similar to some projects I have come across on github.
I have a hunch that the first link could support the hub to turn it into a nicely packaged lorawan gateway to mqtt, either out of the box or with minimal effort as the architecture of the hub looks very similar to this project.
A caveat is what type of encryption is being done between the hub and the sensors. I have taken apart some sensors and they are based on what appears to be a custom chip designed by yolink as the chip is stamped with their name. I havenāt documented my findings of the sensors yet to pull any part numbers.
So at best, I am confident the hub can be repurposed into a general purpose lorawan to mqtt gateway. To my knowledge, there doesnāt appear to be any friendly devices/board already built that allow lorawan to mqtt without DIYāing a solution. So if we can convert the yolink hub into a generic gateway, I would say that is progress.
However, I, and Iām sure many others, would really like to get yolink sensors to work in this architecture and I plan to continue working on this despite the rumored news of a new hub with local access.
7 Likes
Eric has been promising local control for at least a year. Donāt waste your money. Itās not happening.
2 Likes
If you are doing all of thisn just for fun - all the more power to you - but it does sound like a road of diminishing returns you are traveling along - this may be impossible but if you do hack it to make it operate locally - that might ābreakā the virtualarm functionalityā¦ and it could be an huge hassle for you to get it to work - right around the time a newer version of the hub comes out - and the old āhackableā model is no longer available to buy to modifyā¦ but keep going for it! Ideally we could create our ownand then connect just the sensors to it that do not need the cirtualarm functionality? Good luck!
If the local control was even on their radar, Eric would be on here promoting it
1 Like
Dont foget that the LORA frequencies for the US and EU/UK are different. You canāt mix them and, technically, it is illegal to use the US models in the EU/UK, The correct models for the EU/UK have the xxxxxx-EC format and use 868 Mhz band.