Jump to content

Recommended Posts

Posted
There was no way in the old programs.  I could add this as a relay command to the next version.

My current use case is it to program a reboot of ISY on time change nights to get it back in sync. If it’s easy to do, would be great. Now I have a email sent to make me manually reboot. May all be moot if US legislature puts us on DST permanently.

I can’t help but think that other use cases exist. Also, think I recalled it was a command from ISY to reboot computer that xxxLink was running on that I remember.

Is move to net 5 next big change?
Posted

Not really, it's just a re-run of the install script, same as had to be done when it moved to Net Core 3.  

The part that's more breaking is the node def files.  I've changed a number of them to allow for dynamic unit changes (no separate C and F devices).  That may require the device to be reinstalled in the ISY.  Going to talk to UDI before it happens to see if there's a clean way to avoid this.  

Posted

I spoke with Chris, looks like there will be a way to avoid re-doing anything in the ISY, just need to send a rest command from your browser which I'll identify once I roll out the new version.

  • Like 1
Posted
I spoke with Chris, looks like there will be a way to avoid re-doing anything in the ISY, just need to send a rest command from your browser which I'll identify once I roll out the new version.

Thanks for everything over the years. NodeLink and it’s xxxlinks before it are a huge part of my home automation.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...