MrBill

seems to be a Ubiquiti Dream Machine Pro problem then. I didn't think any router would auto-update tho, too easy to break something unattended.

@Pete C Open a ticket. Michel will get you back online faster than alot of back and forth in the forum. support@universal-devices.com

I believe catch up at restart is only referring to the start time of the program. Once the program is running it will run for an hour and finish an hour after it started, not "catch up" the steps by ignoring the 'waits'. So in your example: "Let's say that I have a program that starts at sunrise"-- if it's after sunrise the program will start -- "and this program has several steps after a set number of minutes and ends at sunsrise plus 1 hour." -- the "wait" statements in your program have no way of knowing anything about catching up... they will still wait... the program will still take 1 hour to run.

In my case the bench has many plugs on a strip within arms reach. Like this, but not because mine not plug in and is wiremold branded (a "sample" the factory rep sent me as a christmas present back when I was in the business)

I'm wondering if your SD card failed. and/or you somehow connected with the wrong version of the admin console. Were you working remotely through the portal? Or on the same network as the ISY.

In addition to Factory resetting the ISY you should also factory reset each device. Most devices, Pull out the Air-gap or set button, wait briefly, then press the same all the way in and HOLD it in until the long beep STOPS or ends. Devices that don't have a set button that pulls out, same process basically, hold the set button while the device is powered up and continue holding it in until the long beep stops or ends. This could be done as they are installed, but i tend to wire devices up to a test cord, and plug them in, factory reset them, add them to the ISY, test them, and then install them. (cap the red wire with a wirenut while using the test cord.)

one more thought, you might want to add a nag.... NoExercise.SendMessage - (Enable Run at Startup) If $sExercise.State is 0 Then Wait 170 hours (24*7+2) Repeat every 6 hours Set 'Notification Controller / Service Pushover polyglot' ....... and whatever else to change the message to no exercise in the past 170 hours. Else (none) Now if the 170 hours expires the messages will continue being sent every 6 hours until the generator is exercised.

I'm assuming that excerise state is always 1 or 0, also assuming you want to keep the message that positive message that the exercise started then simply add an ELSE Exercise.SendMessage - [ID 0026][Parent 0025] If $sExercise.State is 1 Then Set 'Notification Controller / Service Pushover polyglot' Send Sys Short With Params To iphone Priority=Normal Format=Monospace Sound=Pushover (default) Retry=30 Expire=60 Else Wait 170 hours (24*7+2) Set 'Notification Controller / Service Pushover polyglot' ....... and whatever else to change the message to no exercise in the past 170 hours. When exercise becomes 1 again the Wait will be interrupted and the notification below will never be sent. Another similar method is a separate program: NoExercise.SendMessage - (Enable Run at Startup) If $sExercise.State is 0 Then Wait 170 hours (24*7+2) Set 'Notification Controller / Service Pushover polyglot' ....... and whatever else to change the message to no exercise in the past 170 hours. Else (none) This program assumes that $sExercise.State will be zero when the ISY starts up, and will immediate start waiting 170 hours. An advantage to this program is that the original program could effectively be disabled, with only No Excercise notifications being sent. Either way should be ok, I would prefer the second if it was mine.

I could write a program (or group of programs) if you'd tell me more than we know here. It would be helpful to see the program that sends the message that the generator is exercising. (right click the program name, choose Copy to Clipboard at the bottom of the choices, then paste into a forum message.) Does the state variable you mention already exist? if so, what are its possible values? What nodes exist? are the simply true or false? or voltages. If the exercise is always at 1PM Sunday, what time does it finish? What time will it be on Sunday when we know it's missed? Its not a big deal to do this, but you've included to little information to be helpful. I too would definitely prefer to be notified if it didn't happen rather than it did.

Michel, @Michel Kohanim Weird things are happaning. ISY Launcher changed to IoX Launcher overnight. I didn't do anything to make this change occur. The icon also moved on the desktop, from the top left corner of the screen to the next available icon position on the desktop. I have no idea what effected this change. My Polisy always shows up in finder as htpps://192.168.1.89:8443/desc After your post above I tried to add the same entry again per your instruction. It doesn't add a second identical entry however. I also tried to delete which also appears to do nothing since Finder found the instance on the network. I then tried to clear the java Cache including installed Applications and Applets. The "IoX Launcher" Icon does NOT deleted. it stays on the screen broken. Further there is no method to remove that icon from the desktop. Windows or Java continues to say "could not find this item". The file at that location in fact does not exist. Downloading a fresh copy of start.jnlp and reinstalling.... reuses that old icon, which I've never seen before. However nothing happens when Finder opens and we attempt to open Admin Colnsole cloud, for a Polisy however opening a Cloud Admin Console for a 994 does work. What exactly is IoX Launcher and why did this "magically" change on my desktop overnight?

I had in my mind that Miami/Ft Lauderdale was farther north. I just zoomed hurricane map enough that it added city names and see you are well South of the path.

Is Nicole done with you? I was thinking about you last night...

I just tested on Polisy, Noting that my ISY Launcher Icon changed magically to IoX Launcher (not sure why). I also see that Admin console will not launch from "cloud" on IoP 5.4.4

It should work. you have an offset added above, so at 20 minutes and 1 second after the calculated sunset time the THEN block of the program should fire. The best troubleshooting step is to open event viewer and set level 3, then look for the transmission at Sunset + 20 minutes 1 second.

I use a VPN. To access PG3, connect to the VPN and use the IPaddr:3000 just like i was sitting on the network at home.

from this wiki: Catch up schedules at Restart - When this box is checked (default) the ISY will attempt to run all programs that are time dependent beginning at midnight until the present time. Missed Schedule Grace Period - If Catch up schedules at restart is not checked or if a program is not run because the ISY is busy this will check for programs that were scheduled to run from the period specified until the present time. Default is 15 minutes. There are enough reports this morning that I suspect Polisy didn't do the time change correctly.

Are you asking if there is a calendar that shows historical (or future) Sunset/Sunrise times? There is not. Latitude and Longitude are used once per day to calculate new values as displayed on the top line of the admin console. Here's a page that explains an algorithm used for such calculations: https://gml.noaa.gov/grad/solcalc/calcdetails.html

Yes, Sunset and Sunrise times are calculated daily based on location. See near the top of the admin console to see: Mines shows custom location because I've entered the Actual longitude latitude of my house. You can configure yours on the Configuration tab > System Subtab Edit to add: if you don't know your exact coordinates use: https://www.latlong.net/convert-address-to-lat-long.html enter both coordinates as positive numbers in the admin console tho.

the first question to ask is what time does the admin console show? Is that correct for your current timezone? I doubt seriously HA has anything to do with this....

Matter will matter differently to people that already have an investment in pre-matter devices. Those that start fresh after-matter may take a different approach entirely. Makers of all types have to figure out how to make interoperability work and bridge the gap. Of course with all this talk we are assuming matter succeeds... what if it doesn't?

You're using sunset, which is all I use. I suspect @oberkc hits the nail on the head tho. Try removing the dusk sensor line and see how the program behaves.

Probably nothing... I don't think they are releasing a matter board for your stargate.

The alternative for "native" support is going to be replacing all switches... which i will never do. ... unless of course I win powerball tomorrow night....

no that should work, no difference in the 30-day portal other than short expiration date. open a ticket with support. it's far safer to use the portal than open ports, and the portal is very inexpensive at under $1/month support@univeral-devices.com

I'd try rebooting the ISY to clear and restart the subscription service....