hart2hart

I used nodelink and moved to envisalink-DSC a couple years ago. It does update status and last user.

I recapped every capacitor and brought two of them back to life. This included the daughter card capacitors. None of the capacitors had ruptured and were not even swollen.

It sure did and I did same with Nodelink. It’s where I became acquainted with optimal humidity levels based on temperature.

I also use Venstar Colortouch thermostat to control humidifier. I have programs that monitor outside temp (also on thermostat if you install remote sensor) and set optimal humidity levels to prevent too much humidity that will fog windows and can cause mold.

As you stated, keISY is a great device and support from UD remains excellent. With the resurrection of Insteon device availability, I plan to be here a long time with Insteon and some zwave devices. Will try out matter if /when it becomes real.

I’ve got a copy of nodelink.dll that you can run on a Windows PC. Docker not required. Let me know if you want it.

EnvisaLink-DSC is a node server that runs on PG3x. It does all same things that original DSCLink did and then NodeLink when it combined several xxLink programs into one program. NodeLink if it can be found will run on Windows. The author io_guy was great but has moved on to other HA endeavors and his automation shack site was shut down. Are you running in ISY994 and if so do you plan to move to eISY?

I moved from it to eISY and PG3x. There is EnvisaLink -DSC node server that replaces nodelink.

Good morning, @bmercier. Got an update notice and upgraded to 1.2.1 from 1.2.0. It says installing but still reports 1.2.0 as version. Also, there are no release notes.

I believe it’s called TimeData. There is also one called Sun. I may have renamed it to include celestial in the name.

My guess is it calculates the sunrise and sunset times at midnight but did not apply new time to the calculations correctly after the change. As others have said, it will probably be right just after midnight. I feel like that this was reported last change and it was confirmed that it’s the displayed sunrise and sunset that are wrong but the actual comparison times used in programs is correct. Did I dream this or does someone else recall the same? I located post where it was discussed. /topic/43242-sunrise-off-1-hour-this-morning/ I use lux value from weatherflow to turn on and off lights based on night and day so wouldn’t notice if it were wrong with eISY.

Here you go: DayLight Saving Time:Check For Change If 'Date Time and Celestial Info / Calendar' DST is not '$Daylight_Saving_Time_Current Boolean' Then Wait 5 minutes Send Notification to 'Me' content 'Daylight Saving Time Change' $Daylight_Saving_Time_Current Init To 'Date Time and Celestial Info / Calendar' DST $Daylight_Saving_Time_Current = 'Date Time and Celestial Info / Calendar' DST System: Restart IoX Else - No Actions - (To add one, press 'Action')

I have a program that uses time nodeserver to detect time change and then forces a reboot. Works great!

The latest version of the node server is for ESPHome based ratgdo firmware. Is 2.59 ratgdo firmware only for the mqtt version? Which would break its connection with the node server.

You can upgrade ISY to 500 board and then make the jump to eISY. It’s what I did.