YoLink - device never sees a payload

[logbuilder]

In setting up the YoLink plugin in mcsMQTT, I have entered 4 different YoLink 32 character device QR codes. I can't see any payloads from 1 of those devices. The 32 char code is correct. I can see the device changing in the YoLink app just fine. Also, how do you delete on of these 32 character entries. When I try, it comes back.

[Michael McSharry]

There is some debug in \Data\mcsMQTT\mcsMQTT Debug.txt if Debug has been enabled from the top of the General tab of the MQTT page.
What type of YoLink device(s) are you using? I have Window/Door, Water Leak and Outlet during my testing.
Are you using the mcsMQTT credentials to access the YoLink server or are you using your personal credentials?

QR code entry requires codes to be 32 characters or a change from something to a blank box. The second of these two will remove the QR code. If any other edit of the QR text box is made then the entry is ignored. If an invalid entry is made the invalid entry will remain until the screen is refreshed.

When a valid QR entry is made then mcsMQTT will add that QR code to the YoLink server and the server will respond with a YoLink/+/response message. This message should then be visible on the Association tab. Subsequently any change of state of this YoLink device will have a YoLink/+/result message which will also show up in the Association tab. If this is the first time that you are "initializing" this YoLink device then use the Rebuild button on the Topic filter of the Association tab so it will be visible as a filtered selection in the Association table. Alternately assure no filter has been selected so all messages will show up in the Association table and then page through the table.

[logbuilder]

Thanks Michael. I’ll look for the debug file. I’m using your credentials. The device is a temp sensor. I have two. One works fine. I’ll work with it tomorrow and will get back.


Sent from my iPhone using Tapatalk

[Michael McSharry]

I looked at you debug file and can see one Temp sensor with deviceId d88b4c020003f8cc. I used the QR posted above and it responded with deviceId d88b4c020003f9da. This means that the QR code is valid and should work for you as well. My test setup is



After the sensor reported in the /report subtopic I see the following in the Association tab. There were other subtopics that it reported before this.



mcsMQTT refreshes pages based upon dynamic received data. To conserve CPU cycles logic exists for the page to disconnect if there has not been any use actions on the page for something like 10 minutes. If you had the TCP page open and made no edits to it for awhile then go back to it to make an edit the entry will be ignored. If you are going to make edits on a stale page you should first refresh the page. I was able to edit this QR code so it is likely the issue you had is the page became stale due to lack of use so the edit was ignored.

At this point I am assuming the debug file did not have this second temperature sensor because of the lack of success in editing the QR code.

[logbuilder]

Try as I might, I can't get rid of the erroneous entry via the TCP page. I looked at the mcsMQTT.ini and found the erroneous entry. I removed it and saved. Still no payload from the 2nd temp sensor.

BUT..... all the other devices do work so I'm quite appreciative for the YoLink support!!

Thanks very much for your contributions to the HS community.

[Michael McSharry]

Can you PM or email to mcsSolutions at CenturyTel dot net the set of QR codes that you are using (such as providing mcsMQTT.ini) so I can try to replicate what you are observing? I am traveling, but will be back on Wednesday.

[Michael McSharry]

I worked with your data and found the issue with edit of the QR code. I also modified the management of the YoLink server response to correlate a request with a response and this allowed a message to be be shown in the HS Log when a QR code has an issue. In your case the QR code starting with 7AB provides an error response from YoLink server "Device not existed". This means to me that the QR code does not exist in the YoLink server database so it does not know if it is a Temp sensor, door sensor, etc. Unzip one of the zip files into \bin\mcsMQTT. A very careful look at the QR code starting with 7AB is needed since what now exists is not recognized.

HS3: http://mcsSprinklers.com/MCSMQTT_51803.zip
HS4: http://mcsSprinklers.com/MCSMQTTHS4_51803.zip

[logbuilder]

Thanks Michael. I'll delete and rebind that device and see if it works. Interestingly, it is reporting fine in the YoLink app (IOS). Either way, you have identified the problem as with the device. I'm glad you were able to find the editing problem.

Thanks again and enjoy the cooler day. We are headed off to the zoo with a 4yo. Should be fun.

Robert

[Michael McSharry]

One does not need to use the YoLink App to add devices. The YoLink server knows the device based upon encoding in the QR code and not based upon it being registered via the App. It really seems like the 32 character code has some typo in it which makes it something that fails the YoLink encoding scheme.

[Michael McSharry]

You will notice that in the middle of the QR code A73E. Your INI has A7E3

[logbuilder]

Well don't I feel dumb!

Hanging my head in shame. Works great now.

Thanks Michael.