Hi

A new release of the Yolink node server (ver 1.8.45). There is a lot of changes below the surface to handle the Yolink API better. Node should be faster and take less resources.

Added quite a few devices (Most of the newly released devices and Thermostat2) and updated a few sensor nodes (The Yolink API was updated - THsensor and LeakSensor ) . Note, the new LeakControllers behave a little different than other devices - they go to sleep. Given this one should use the YoLink specified limits to trigger events. Also, they cannot sleep when added.

YoLink schedules are now in separate child nodes.

As this is a major update, so devices may not work - I have tested the ones I own, but there are derivatives of the devices and a few I do not own, so please help test and let me know if something is not work correctly

Note, there is a minor issue with the Dimmer - there is an API problem YoLink is working to fix - I hope once they release the fix the issue is gone, but I have not received the fix yet (probably low priority as it only related to controlling some attributes) - nothing critical

Edited May 2May 2 by Panda88
missed info

The update installed fine will no errors that I saw. All devices are online in the admin panel. I did have to click update on the temperature sensor to get the current readings. The temperatures would have probably updated on their own if I waited.

A schedules child node was added in the admin panel to both water valves but nothing else.

Thanks for working on this.

not all devices have schedules :-)

All looks good. Thanks for your work.

5 hours ago, Panda88 said:

not all devices have schedules :-)

I didn't know any of them did until last night.

However, I discovered today the update removed the open and close command from any valve manipulator program, so none of the programs functioned. I added an open or close command. Works fine now.

Then, I went through all water programs. The water valve variable-setting programs changed "Manipulator State" to "Manipulator State (legacy)." I changed them all to "Manipulator State." I also had to correct open vs closed in those programs. I didn't test to see if "legacy" worked. I had to fix the open/close anyway, so I changed both lines in the programs. Works fine now, too.

Legacy has been there a while :-) (previous release had it also) - the two are the same - It is to be able to assign the ST parameter to the main function of the node - not just online - This is to show in UDImobile and also an issue with how the system handles variables

I tried to reduce the number of functions (some a doing the same) as they take u a lot of space on AC

Is open/close swapped in the manipulator?

I never noticed the "legacy" before, but I don't usually go poking around old programs that work. Open/close are not swapped.

In this program, Open and Closed were simply removed after the update. So, run then or else did nothing until I added them back.

Water valves - [ID 0037][Parent 0006]

If

- No Conditions - (To add one, press 'Schedule' or 'Condition')

Then

Set 'Water leaks / Cold Water Valve' Open

Wait 5 seconds

Set 'Water leaks / Hot Water Valve' Open

Else

Set 'Water leaks / Cold Water Valve' Closed

Wait 5 seconds

Set 'Water leaks / Hot Water Valve' Closed

I have four of these programs to set the open or close variable for two valves. I can't swear to it, but I think the two open programs changed to Manipulator State is Closed. So, the variable never changed. This is where I changed from legacy manipulator state, also.

Cold valve open variable - [ID 003A][Parent 0006]

If

'Water leaks / Cold Water Valve' Manipulator State is Open

Then

$Cold_water_valve = 1

Else

- No Actions - (To add one, press 'Action')

Like I said, I was poking at four programs, so I can't be sure about that. Regardless, the two variables weren't changing until I fixed them. However, in the first program, I'm sure of the change that broke the program.

Edited May 3May 3 by auger66

I am seeing some unexpected things since updating to the latest release.

• My Local hub now says "Alert" under "Supply Status" in the devices View, and in the Current State when listing devices via the Admin Console. I don't recall seeing that before (but perhaps just missed it) and am not quite sure how to address that if it's a real issue.

• The Current State and multiple other values appearing in the Admin Console device view show as "Unknown" for several devices and device types, including my Flexswitch devices (YS5709-UC) and some but not all of my temp/humidity sensors (YS8006-UC). If I manually update the device status for those devices via the Admin Console, the values seem to get updated but many return to show "Unknown" statuses again shortly after update.

• When updating status manually via Admin Console, I occasionally get "TCP client read response failed" messages (NS-70-YolinkLocal).

The upgrade installed without issue but some of my T\H Sensors are showing humidity is not supported, and the value always shows as 98. It appears the UOM is being set to 25 on the ones that don't work and is 51 on the ones reporting humidity.

I have leak sensors, door open\close, and motion sensors and so far these seem to be working.

TS_Garage is not working below but TS_CrawSpace is working like before the upgrade. All my sensors worked properly on the old plug-in.

Edited May 3May 3 by JRissmiller
Added screenshots

11 hours ago, auger66 said:

I never noticed the "legacy" before, but I don't usually go poking around old programs that work. Open/close are not swapped.

In this program, Open and Closed were simply removed after the update. So, run then or else did nothing until I added them back.

Water valves - [ID 0037][Parent 0006]

If

- No Conditions - (To add one, press 'Schedule' or 'Condition')

Then

Set 'Water leaks / Cold Water Valve' Open

Wait 5 seconds

Set 'Water leaks / Hot Water Valve' Open

Else

Set 'Water leaks / Cold Water Valve' Closed

Wait 5 seconds

Set 'Water leaks / Hot Water Valve' Closed

I have four of these programs to set the open or close variable for two valves. I can't swear to it, but I think the two open programs changed to Manipulator State is Closed. So, the variable never changed. This is where I changed from legacy manipulator state, also.

Cold valve open variable - [ID 003A][Parent 0006]

If

'Water leaks / Cold Water Valve' Manipulator State is Open

Then

$Cold_water_valve = 1

Else

- No Actions - (To add one, press 'Action')

Like I said, I was poking at four programs, so I can't be sure about that. Regardless, the two variables weren't changing until I fixed them. However, in the first program, I'm sure of the change that broke the program.

Do you need anything changed? I do not 100% follow - if yes, can you send a log with debug enabled (just PM me)

1 hour ago, JRissmiller said:

The upgrade installed without issue but some of my T\H Sensors are showing humidity is not supported, and the value always shows as 98. It appears the UOM is being set to 25 on the ones that don't work and is 51 on the ones reporting humidity.

I have leak sensors, door open\close, and motion sensors and so far these seem to be working.

TS_Garage is not working below but TS_CrawSpace is working like before the upgrade. All my sensors worked properly on the old plug-in.

Can you send me a log with debug enabled - There were changes to THsensor and LeakSensor as new functionality we enabled in the API (and I wanted to include those) - There is likely a return from the API I do not know of that may cause the unknow state to appear (if the device is not reporting its value in this return _ I just need to ignore it missing)

Can you validate the device types you have - the node sees the garage sensor as T only - look at the name - They must have different types YSXXXX-UC in the app ... area

Edited May 3May 3 by Panda88
Need more info on the device types

2 hours ago, dwengrovitz said:

I am seeing some unexpected things since updating to the latest release.

• My Local hub now says "Alert" under "Supply Status" in the devices View, and in the Current State when listing devices via the Admin Console. I don't recall seeing that before (but perhaps just missed it) and am not quite sure how to address that if it's a real issue.

• The Current State and multiple other values appearing in the Admin Console device view show as "Unknown" for several devices and device types, including my Flexswitch devices (YS5709-UC) and some but not all of my temp/humidity sensors (YS8006-UC). If I manually update the device status for those devices via the Admin Console, the values seem to get updated but many return to show "Unknown" statuses again shortly after update.

• When updating status manually via Admin Console, I occasionally get "TCP client read response failed" messages (NS-70-YolinkLocal).

Can you send me a log with debug enabled. It may be I mapped alert wrong - it is likely charging. I did add new functionality in the localHub to allow it to detect if it is operating of its own battery or by power from outlet, but it seems Alert is not the correct message.

I do not own a flex switch - I should be able to identify the issue from the log

I think the last NS-70 message is beyond the node server layer but I'll check

Edited May 3May 3 by Panda88

34 minutes ago, Panda88 said:

Do you need anything changed? I do not 100% follow - if yes, can you send a log with debug enabled (just PM me)

No, everything is fine. I just wanted to give feedback let and others know the update altered my programs. After I "unaltered" them, it's all good.

My temperature sensor doesn't update the temperature, among other values, unless I hit update on the admin console, so that's a bit of problem.

Edited May 3May 3 by auger66

Here are a couple of screen shots of before and after I press the update button on the admin console. Something weird is going on with the last status update time.

After pressing the update status button, the time moves a few hours into the future. The status update time before pressing update status is correct.

Edited May 3May 3 by auger66

can you send me a log with debug enabled. there must be a bug somewhere but i need to know what the device reported you can pm it to me. enable debug under logging. update sensor —set log back to info and download log - just the pg3 log

i did find a bug but nit related to this

@Panda88 - I tried sending you a debug log with some screenshots, but the UD message system just said "Panda88 cannot receive messages."

@Panda88 I tried to send my logs but I'm not sure they went. I'll try one more time. UD system might be having issues.

I found a few of the bugs - I still need to figure out the time jump issue - I'll try to release a patch release once I have the last bug ironed out

I think I can receive messages again - hit a limit

On 5/3/2026 at 9:05 AM, dwengrovitz said:

I am seeing some unexpected things since updating to the latest release.

• My Local hub now says "Alert" under "Supply Status" in the devices View, and in the Current State when listing devices via the Admin Console. I don't recall seeing that before (but perhaps just missed it) and am not quite sure how to address that if it's a real issue.

• The Current State and multiple other values appearing in the Admin Console device view show as "Unknown" for several devices and device types, including my Flexswitch devices (YS5709-UC) and some but not all of my temp/humidity sensors (YS8006-UC). If I manually update the device status for those devices via the Admin Console, the values seem to get updated but many return to show "Unknown" statuses again shortly after update.

• When updating status manually via Admin Console, I occasionally get "TCP client read response failed" messages (NS-70-YolinkLocal).

Can you send me a log with debug enabled - and let me know when you pressed the update (roughly in time)

Also if you can turn the switch on and off in the log

Found a bug for Alert

Prior to the new update I had 39 nodes listed under PG3 Yolink. Post update I have only 18 nodes recognized but all are on line in the Yolink app. I have two hubs, missing are several temp sensors while some are present, also door lock, wall plug, and one motion sensor with one motion sensor listed. So a mixed bag of some present and some missing.

Any insight and advise would be appreciated. Attached is the PG3 error log if that will be of value.

Thanks

Stan

pg3_5-7-2026_33140_PM.zip

3 hours ago, Stan said:

Prior to the new update I had 39 nodes listed under PG3 Yolink. Post update I have only 18 nodes recognized but all are on line in the Yolink app. I have two hubs, missing are several temp sensors while some are present, also door lock, wall plug, and one motion sensor with one motion sensor listed. So a mixed bag of some present and some missing.

Any insight and advise would be appreciated. Attached is the PG3 error log if that will be of value.

Thanks

Stan

pg3_5-7-2026_33140_PM.zip

Can you enable debug and send me the node log (not the PG3 log) - that will help me understand the issue

Hopefully this is what you requested.

Thank you.

SS

DebugLog.txt

Sorry - no - click download log - make sure debug is enabled

Best if you can restart after enabling debug, wait a little, and then click Download Log

Sorry for my lacking skill set, little out my element here.

I hope this is the info you need. Again thank you.

SS

YoLink_5-8-2026_32713_PM.zip

thanks - that works - I had a bug in the old Lock code (I no longer have that device) - I'll fix, and release a new updated version - hopefully you can help test

released version 1.8.50 - minor bug fixes

I believe I have addressed reported issues - Only known issues is Dimmers and Switches report an ERROR in Log - Yolink is working to fix this - it is an docmented but non-functional API to control attributes - should not matter (should allow controlling the LEDs on the devices)

Online reporting has been updated - there was a bug it would report offline if a state did not change for 4 hours (It should only be if reporting did not update for 4 hours)

I now ignore historyReports from some newer sensors (it was the root cause for reporting offline/Unknown) - Data is not used anyway

I have updated the Fob behavior a little to make sure it identifies remotes with one press type and remotes with 2 press types (LONG and SHORT press)

I do not have the old lock anymore so I cannot test it - let me know if ok

I do not have a flex switch so I cannot test it - let me know if ok

Edited Saturday at 06:51 PM3 days by Panda88