Ignorance is the mother of all disagreements!
Anyone who does some research about Yolink and the technology behind it will agree to the following facts:
Yolink as a company has been around since 2008, operating under different names, which
designed developed and sold software infrastructure products. They were/are also involved into
internet browser-based application and database management systems.
The LoRa devices does not contain Yolink technology, but rather Yolink integrated Semtech’s LoRa
modules in their devices for good reasons.
In order to understand why Yolink would not offer MQTT service for their devices, one needs to
learn the LoRaWAN specification and the way the LoRaWAN network is designed.
The Semtech’s LoRa modules allows devices to communicate with each other.
According to the LoRaWAN specifications the Yolink/LoRaWAN network consists of the Yolink LoRa
devices connected to the Yolink hub which then connects to the Yolink network server, to which
all the devices are reporting messages and information of their status to keep them authenticated.
From there, as per the specifications, the server communicates back to the client’s app.
The hub is the gateway (node) which relay messages between the end devices and the network
server. All customer hubs connect to the same network server which now becomes the Yolink
Under no circumstances do I believe that a Yolink employee would get you as a customer “API
access to the YoLink ecosystem”.
Further, I can only suspect that the information is being collected into the Yolink database.
In order for local control to be achieved, a local network server need to reside into the hub’s ESP32 or the HA integration. The latter will make things a lot simpler.
There was mention of some devices communicating with each other. That is due to the Semtech’s technology design. However, the LoRaWAN specification states that the device must report to the network sever in s specific time, otherwise it will get kicked out. One could deduct that a server may already exists in the hub to maintain communication with the devices during the internet service interruption.
Andrew, my interest in a HA integration is just as high as any HA user owning a device and who want that device to work offline. We all want privacy and security for our personal network. Having integrated
cloud based hubs on a private network is just an invitation for privacy violation, hacking, spying etc. Of course, all of this happens if one is completely ignorant. The hub could have integrated in the firmware monitoring software, a proxy server and who knows what else.
Looking at their history, does anyone think that Yolink will give that up, in favor of local control due to a handful of Yolink users requesting local control. Look no further to what happened to Wink products. Everyone knows Wink just got dumped by HA. What makes you think that HA will support Yolink?
Andrew, just because you apparently get some help from Eric, it does not mean there is going to be an HA integration. As a developer, and after some research you could have come to the same conclusion as me, and not ask if MQTT is possible. With the current hardware, MQTT is easily possible to achieve. The question is if Yolink is willing to share the information with us. You have access to their API and being a developer, it should not be hard to achieve that.
You state that you are a developer and access the “Yolink ecosystem” first hand. Do you mind sharing the API and all the gathered information with all of us. After all, we all are Yolink customers. We should be treated the same as you.
I have no idea what you and Eric are up to, but these forums are for supporting HA users in a constructive and productive way. Definitively not for promoting and selling manufacturer’s products.
I understand your opinions and disagreement, but telling me what to do or not to do is inappropriate.