New Release 1.5.13

[Panda88]

Hi

I just released a new version of the YoLink server 1.5.13.  

Added support for HUB (battery powered hubs can now be used to test if powered by AC or internal battery) - Need to poll this as it does not seem like message is generated on change

Updated IRremoter to have subnodes for each code - supports learning codes now.  

NOTE - 

By request I changed behavior of ST and added a GV30 variable to all nodes - GV30 is the existing ST (mostly if node is online) - Changed ST to show the most relevant parameter of the node - this is to support udiMobile status icons (they trigger of ST parameter)  - I hope that it is not too big a problem as some code may need to be updated if programs tests for online status 

Few other bug fixes 

I hope this covers the requests I have had over the last few months 

Next is support for new LeakStop devices as well as a more robust retry handling when devices are off-line

Will also work on bringing the YoLinkLocal Beta (support for local hub) into a production form 

 

[sjenkins]

9 hours ago, Panda88 said:

 

Will also work on bringing the YoLinkLocal Beta (support for local hub) into a production form 

 

Thanks for all the work ; putting my plug in for the last one on the list  

(I know you know)

[BobM99]

Hi, I'd also like to thank you for all your work with this. Regarding--

"By request I changed behavior of ST and added a GV30 variable to all nodes - GV30 is the existing ST (mostly if node is online) - Changed ST to show the most relevant parameter of the node - this is to support udiMobile status icons (they trigger of ST parameter)  - I hope that it is not too big a problem as some code may need to be updated if programs tests for online status"

--when I sync with UD Mobile I do get errors:

0. Notify Node Server Dev!!! Status name is missing for : ST. Node Server Instance: 11

1. Notify Node Server Dev!!!  Status name is missing for: nlshub. Node Server Instance: 11

I have no idea what this means or if it's related. 

[Panda88]

seems there is a bug in the config file for normal hub (i did not test that as I use a different hub)

i'll release a fix shortly  - hopefully that is the only one