hart2hart

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.

I had about that length over shielded cat 5 or 6 for a time. Seemed fine. I don’t recall which 2 of the 3 wires were in a twisted pair but I’m sure google will tell you. Also a balun could be used which moves signal from unbalanced to balanced for the trip over wire.

FYI PaulWieland commented 4 days ago I finally have an example of this problem in front of me so I can trouble shoot and fix it, and plan to do so in the next few days PaulWieland added a commit that referenced this issue 31 minutes ago Fix command values … 7521d1e PaulWieland commented 20 minutes ago Version 2.59 changes the data values sent to the GDO for control, and should hopefully fix this issue. PaulWieland closed this as completed 20 minutes ago

Touch and hold app icon and it pops up as one of a few options.

You can add faceid to app in ios18.

I did the same when I installed it. LOL

Did you enter latitude and longitude?

Gotcha and you are likely right. If you want to test…. Put thermostat in Auto mode. Set a cool and heat setpoint 3 degrees apart. Set thermostat to Cool mode. Move the cool set point 1 degree from the last heat point while stat was in auto mode. Now set stat in auto mode from AC and see what you get. I believe on my Venstar colortouch it originally would not make the switch to Auto mode and in a later version of its firmware started showing what you described or could have been the opposite.

Thermostats usually have a dead band between heat and cool set points. Don’t have nest but I’m guessing they have to them. If so… Your current heat cool on thermostat at button press are conflicting with the program set points. In essence the thermostat is ignoring the conflicting points. You can test it by setting thermostat to values that will not cause a conflict. As I recall, usually caused when switching Modes from heat/cool and auto. I wrote programs to deal with the issue on Venstar Colortouch if you’re interested after confirming it’s the issue.

Sounds like it may not have done the replace. What do you mean by power supply cable for new PLM? 2413s only has a serial data cable and plugs into a AC outlet. For serial data cable, did you pull new one from box or use one that was with old PLM? Also, a few people have accidentally purchased 2413u instead of 2413s as it comes first on Insteon.com. Also you say ISY didn’t recognize old PLM and symptoms you describe indicates ISY doesn’t recognize new one so could be the ISY.

Install purchased version in same slot as trial version.

The buttons should be in respective scenes as controllers.

In addition, you need to add the new keypad too. Then you can select the old keypad now out of a folder and replace it with the new keypad.

Hi. Just saw this and installed the beta. I’m just using switches but I’ll test that portion a bit.

I believe you need to set a variable (including init value for persistence) when enabling or disabling a program then check that variable. Alternatively you could set that variable and have it in the if of program you would be enabling and disabling.

@Jimbo.Automates , thanks!

Can you turn on the device “Irrigation / Irrigration-1 - Z1 Front Lawn” from device tree in the AC and confirm it actually turns on in the yard?

As I recall, You’ll need to create another variable and keep its value and init to value in sync your variables init to value.