5.26.5.4 Release

[Michael McSharry]

Version 5.24.5.4 has been released via the HS Updater. It is an incremental release that captures changes since the last update. New feature added and issues addressed per mcsMQTT Change Log (HS4 & HS3) - HomeSeer Message Board and the release notes.

Backward compatibility has been an objective so an update should be transparent to users. This post is make users aware of a change in the UI for selecting a JSON key to be a unique identifier. i.e. elevate. In prior release the elevate function was done by associating the JSON key that is to be elevated and then using the Edit tab to mark this key as being elevate either singularly or as a wildcard.

With the 5.24.5.x the UI has changed so that elevate capability is performed on the main topic by entering on the Edit tab text box of the parent topic the elevate key (e.g., Id or for wildcard as *: Id.) vs. the prior approach of selecting a radio button of the JSON key that is to be elevated. There is no longer a need to associate the elevated key to create a HS device.

The more significant impact is that mcsMQTT.db that contains the elevate information in the field ElevateKeys has changed so that the elevate key is now just the key as one would enter in a textbox rather than the full path of parent JSON objects that include the key. mcsMQTT, at startup, tries to recognize the change and formats the ElevateKeys field to the new convention. This means the change should be transparent to the user if all goes as intended. For the user of the wildcard radio option for elevate there should be no impact since the ElevateKeys field in the database did not change in this case.

Bottom line is:
1. The user interface has changed on how JSON keys are elevated so their value becomes part of the unique identification. It is now a textbox on the parent topic rather than a radio on the JSON key.
2. A backup should be done before updating to 5.26.5.4 via Updater so that it is possible to go back it all does not go as intended.

[jim@beersman.com]

Michael, I installed the update on my HS3 box and te Yolink part of MCSMQTT does not appear to be working in the new version. I looked in the DEBUG file and I see "Thread Client Created for YoLink Server". But after that no communication with YOLINK at all.

[Michael McSharry]

I just tried the HS3 plugin on my system. Powered the hub then installed an outlet a little later. Received the following in the debug file. First to send the QR codes setup by user then data and then the YoLinkReceive as data pushed from the YoLink server.

In my case I have two hubs. The one that is plugged in eventually goes offline with flashing red led on house icon. I swap the other in its place and then back online again until it happens again. Just cycling power on the hub that goes offline does not work. I need to swap.

9/7/2022 10:28:16 AM 59059 | YoLink Not Connected Yet
9/7/2022 10:28:16 AM 59061 | Thread Client Created for YoLink Server
9/7/2022 10:28:16 AM 59324 | YoLink Server Connect Response=0
9/7/2022 10:28:16 AM 59324 | YoLink Server Connection Accepted, Connected=True
9/7/2022 10:28:16 AM 59326 | YoLink SendQR mcsSolutions/mcsMQTT/request={"method": "Manage.addYoLinkDevice","params":{"sn":"yyy"}, "time": 1662571697}
9/7/2022 10:28:16 AM 59520 | YoLink Receive Topic: mcsSolutions/mcsMQTT/response Payload: {"code":"000000","time":1662571696488,"msgid":1662571697,"me thod":"Manage.addYoLinkDevice","data":{"deviceId":"d88b4c010 002fcdc","deviceUDID":"4350d039432141c5ad0430b351e5787c","na me":"YoLink Plug","token":"xxx","type":"Outlet"}}
9/7/2022 10:28:16 AM 59661 | ActOnMessageForTrigger Topic YoLink/d88b4c010002fcdc/response,Payload={"code":"000000","time":1662571696488,"msgi d":1662571697,"method":"Manage.addYoLinkDevice","data":{"dev iceId":"d88b4c010002fcdc","deviceUDID":"4350d039432141c5ad04 30b351e5787c","name":"YoLink Plug","token":"xxx","type":"Outlet"}}, Triggers=15
9/7/2022 10:28:18 AM 61332 | YoLink Send Topic: mcsSolutions/mcsMQTT/request Payload: {"method": "Outlet.getState","targetDevice":"d88b4c010002fcdc","token": "xxx", "time": 1662571699}
9/7/2022 10:28:19 AM 62072 | Update Accepted 48 to 0 StatusType=1 Payload= 0 RegExValue=0
9/7/2022 10:28:19 AM 62074 | Updating Device from -1 PayloadNumeric=True nValue=0
9/7/2022 10:28:19 AM 62075 | Button Value 0, prior value = -1, for VSP of 0
:
9/7/2022 10:28:22 AM 65390 | YoLink Receive Topic: mcsSolutions/mcsMQTT/response Payload: {"code":"000201","time":1662571702435,"msgid":1662571699,"me thod":"Outlet.getState","data":{},"targetDevice":"d88b4c0100 02fcdc","desc":"Can't connect to Device"}
9/7/2022 10:28:22 AM 65392 | YoLink Server error response {"code":"000201","time":1662571702435,"msgid":1662571699,"me thod":"Outlet.getState","data":{},"targetDevice":"d88b4c0100 02fcdc","desc":"Can't connect to Device"}
9/7/2022 10:28:22 AM 65443 | ActOnMessageForTrigger Topic YoLink/d88b4c010002fcdc/response,Payload={"code":"000201","time":1662571702435,"msgi d":1662571699,"method":"Outlet.getState","data":{},"targetDe vice":"d88b4c010002fcdc","desc":"Can't connect to Device"}, Triggers=15
9/7/2022 10:28:36 AM 79398 | YoLink SendQR mcsSolutions/mcsMQTT/request={"method": "Manage.addYoLinkDevice","params":{"sn":"yyy"}, "time": 1662571717}
9/7/2022 10:28:36 AM 79575 | YoLink Receive Topic: mcsSolutions/mcsMQTT/response Payload: {"code":"000000","time":1662571716522,"msgid":1662571717,"me thod":"Manage.addYoLinkDevice","data":{"deviceId":"d88b4c010 002fcdc","deviceUDID":"4350d039432141c5ad0430b351e5787c","na me":"YoLink Plug","token":"xxx","type":"Outlet"}}
9/7/2022 10:28:36 AM 79602 | ActOnMessageForTrigger Topic YoLink/d88b4c010002fcdc/response,Payload={"code":"000000","time":1662571716522,"msgi d":1662571717,"method":"Manage.addYoLinkDevice","data":{"dev iceId":"d88b4c010002fcdc","deviceUDID":"4350d039432141c5ad04 30b351e5787c","name":"YoLink Plug","token":"xxx","type":"Outlet"}}, Triggers=15
9/7/2022 10:28:38 AM 81404 | YoLink SendQR mcsSolutions/mcsMQTT/request={"method": "Manage.addYoLinkDevice","params":{"sn":"yyy"}, "time": 1662571719}
9/7/2022 10:28:38 AM 81581 | YoLink Receive Topic: mcsSolutions/mcsMQTT/response Payload: {"code":"020101","time":1662571718524,"msgid":1662571719,"me thod":"Manage.addYoLinkDevice","data":{},"desc":"Device not existed"}
9/7/2022 10:28:47 AM 90466 | YoLink SendQR mcsSolutions/mcsMQTT/request={"method": "Manage.addYoLinkDevice","params":{"sn":"yyy"}, "time": 1662571728}
9/7/2022 10:28:47 AM 90660 | YoLink Receive Topic: mcsSolutions/mcsMQTT/response Payload: {"code":"000000","time":1662571727595,"msgid":1662571728,"me thod":"Manage.addYoLinkDevice","data":{"deviceId":"d88b4c010 002fcdc","deviceUDID":"4350d039432141c5ad0430b351e5787c","na me":"YoLink Plug","token":"xxx","type":"Outlet"}}
9/7/2022 10:28:47 AM 90686 | ActOnMessageForTrigger Topic YoLink/d88b4c010002fcdc/response,Payload={"code":"000000","time":1662571727595,"msgi d":1662571728,"method":"Manage.addYoLinkDevice","data":{"dev iceId":"d88b4c010002fcdc","deviceUDID":"4350d039432141c5ad04 30b351e5787c","name":"YoLink Plug","token":"xxx","type":"Outlet"}}, Triggers=15
9/7/2022 10:28:49 AM 92475 | YoLink SendQR mcsSolutions/mcsMQTT/request={"method": "Manage.addYoLinkDevice","params":{"sn":"yyy"}, "time": 1662571730}
9/7/2022 10:28:49 AM 92666 | YoLink Receive Topic: mcsSolutions/mcsMQTT/response Payload: {"code":"020101","time":1662571729605,"msgid":1662571730,"me thod":"Manage.addYoLinkDevice","data":{},"desc":"Device not existed"}
9/7/2022 10:28:51 AM 94488 | YoLink SendQR mcsSolutions/mcsMQTT/request={"method": "Manage.addYoLinkDevice","params":{"sn":"yyy"}, "time": 1662571732}
9/7/2022 10:28:51 AM 94670 | YoLink Receive Topic: mcsSolutions/mcsMQTT/response Payload: {"code":"000000","time":1662571731613,"msgid":1662571732,"me thod":"Manage.addYoLinkDevice","data":{"deviceId":"d88b4c020 000f7d7","deviceUDID":"b42c16ed1fe14817a6eab42b2476953e","na me":"Leak Sensor","token":"xxx","type":"LeakSensor"}}
9/7/2022 10:28:52 AM 94876 | ActOnMessageForTrigger Topic YoLink/d88b4c020000f7d7/response,Payload={"code":"000000","time":1662571731613,"msgi d":1662571732,"method":"Manage.addYoLinkDevice","data":{"dev iceId":"d88b4c020000f7d7","deviceUDID":"b42c16ed1fe14817a6ea b42b2476953e","name":"Leak Sensor","token":"xxx","type":"LeakSensor"}}, Triggers=15

[jim@beersman.com]

This is all I'm seeing when I enable the Yolink Interface. It's been running for over an hour and no messages of "YoLink Receive"

9/7/2022 12:05:33 PM 12251 | YoLink Not Connected Yet
9/7/2022 12:05:33 PM 12251 | Update Accepted 2080 to offline StatusType=1 Payload= offline RegExValue=offline
9/7/2022 12:05:33 PM 12253 | Thread Client Created for YoLink Server

The App on my Phone is showing the correct status of my devices.

[Michael McSharry]

At startup is when the connection to the Yolink server/broker is done and messages occur in the log for the connect status and sendQR. Do you have these near the start of the debug, assuming you have debug enabled when starting?

It is acting as if the YoLink broker connection has been lost. Recovery is the same as used for other MQTT brokers with retry every 10 seconds.

[jim@beersman.com]

Michael, had the Plugin running since yesterday and the only 2 entries in the Debug file for Yolink where these

9/7/2022 12:05:33 PM 12251 | YoLink Not Connected Yet
9/7/2022 12:05:33 PM 12253 | Thread Client Created for YoLink Server

Nothing after that

[jim@beersman.com]

Okay, I'm not sure what was going on but it all started working again. I see the message below and then statuses from other devices. Just glad it's back to working

9/8/2022 10:11:49 AM 2902446 | YoLink Server Connection Accepted, Connected=True