@xcesmess It works now. Thanks
Wow! This is a tough crowd! I have not been on here since my last post, Iām sorry. The last time I asked my guys about it was 5 days ago, they said it was being reviewed by HA. I see we submitted a bug fix 2 days ago.
Regarding our missing the end-of-March deadline we set for ourselves, I canāt fall on my sword over that. I know two things: we went into it with the expectation weād hit the deadline, and this is our first integration and itās apparent we didnāt know how involved it would be. We are still at it, and weāll get there!
Thanks for the update.
Donāt worry about it ā take your time and get it right, itāll be worth it!
We are just ready to start using the Yo-Link integration! Thanks for your work. Hope its coming soon. Iāll probably celebrate by buying some yo-link devices
Thanks for the feedback.
Most know the effort that has been put in.
Really appreciated!
What is promising is that you are not giving up! That alone it testament for your commitment.
It will eventually be approved.
Thank you!
Kind Regards
Jason
Have you considered posting it in HACS ahead of time? That would allow some of us to start using (at our own risk, obviously) until the official integration is put into place.
yes, letting others use through HACS would have had us all testing much faster!! Now when there is an issue we will have to wait for the next HA release instead of releasing on demand and us updating via HACS.
Hey, Thanks for this. I canāt seem to get it 2 connect though. When I try using MQTT Explorer I just get connection refused: Not authorized. I have generated UAID in the app. Used MD5 Hash Generator with the Secret Key. I verified 8003 is getting out. It will not connect in node-red either with same parameters. What am I missing?
Thanx, Michael
The instructions above only work if you have one of the precious API keys that were given out in the early days. I have yet to make the app-generated API keys work with MQTT. Their documentation indicates that it will but Iāve yet to make it successfully grant a token (which is required for the MQTT connection).
@Eric-YoLink would you have any ideas? Are there any tricks to making the app-based API stuff work? I suppose one could jump on the discord chat as well and see if there is some example code for it. I just havenāt found much.
While I know that it is no replacement for a Home Assistant integration, I just needed a way to trigger some real-time local action based on some events from a YoLink sensor, which was actually not overly complicated to write in Python using the YoLink HTTP and MQTT APIs.
Granted, I am a Python dev, but still, it wasnāt that difficult.
For the brave of you (and the ones with Python knowledge), I have shared the code on GitHub: GitHub - zoltan-fedor/yolink-integration: Yolink integration to trigger some custom action in your home using Python
I am late to the party here but just had a water event that caused $$$ damage. I stumbled upon YoLink and investigated if it would integrate with HA.
It is SOOO awesome seeing YoLink look into this them selves. Really refreshing to see a brand have active development like this.
While waiting for the release, got a question about the YoLink Motion Sensor. Right now I am just using IFTT to flip a cloud-based wifi light switch and it takes about 1-2 seconds for the lights to go on (after I see the red led on the motion sensor). Came across āYoLink Controlā (device to device integration) and wondering if that will speed up the things for me if I get a switch from YoLink. I suppose doing the automation in HA will also speed up the process compared to IFTT. Has anyone had a similar case?
The light switch btw, when operated from HA, works instantly, with milliseconds of delay.
I donāt know if we ever cleared it up for people other than those that asked, but recently it was decided the API was for commercial/business customers only. Frankly, weāve been challenged by the demands for API access and this is out of necessity as our sales have been growing rapidly but our manpower has struggled to keep up. Our engineers are always very busy with something. I work 80 hours a week on a light week but I think they sleep there, some days. This means, not a lot of engineers idle, ready to answer developer questions in a timely basis. The Discord group allows sort of a crowd-supported option for figuring things out. Generally, someone in there has an answer, and if they donāt I can get it.
If you would email me a detailed explanation of your issues or questions along with your code, give me 2-3 business days and I will get you an answer. But I do encourage posting the question in our API/developer discord. eric at yosmart.com is my email
Killing a couple proverbial birds with one figurative stone: HA integration appears to be in their court. I refuse to throw anyone under the bus, but last I heard, we had been waiting for a question about āwhatās the next step?ā - I see now there has been some activity today, possibly because I mentioned it being in their court to someone yesterday. I donāt relish any of this, if they have been a delay. I did see something somewhere in here they are hella busy and are asking for help reviewing integrations. Iām sure the answer to all this is more patience. BTW, for those that are threatening in here or on our social media to return, or go all Office Space on your YoLink devices if we donāt get the HA integration working soon, I hope this helps.
One more thing, the local access/offline mode hub project is moving along, not as fast as any of us would hope, but I did hear they like my idea of running it on a Raspberry Pi with a YoLink/LoRa shield. What you may not like is it appears to be getting merged with our keypad project, becoming a super tablet dashboard of sorts. This will drive the cost up accordingly and you may have some hardware you have no need for, but weāll have local control YoLink devices available to you.
And, we plan to incorporate our Control-D2D feature into this unit, so that you can get some functionality out of your YoLink devices, even if your network and power is out/down/kaput. The primary benefit is as a home security system - sirens are going to activate on intrusion, regardless of power or internet being available, and your HA server being out of commission. And, yeah, I know, burg alarms from the 70s could do that, but itās not as common for smart systems.
Thatās all for now!
Eric
Control-D2D is lightning-fast. Youāll like it.
I PMād you!
@Eric-YoLink ask your dev team to make the integration compatible with HACS and then you can release it today for people to start using and fix bugs on your own cadence instead of waiting for HA to approve releases.
Thanks for the feedback Eric! Love the idea of a LoRa shield.
Big big fan of Yolink devices. I educate people on the features, nearly every day. Love everything. Routinely visit their site for new products.
I donāt have any of the skills to help with integration. I am just now trying HA. I am thankful those of you that can, do.
Eric is a GREAT ambassador of Yolink products. Have reached out to him several times. Always positive interaction and helpful. Thank you sir.