Geddy

@Jack D Yep...your folder is messing you up... The My Programs folder has a "next scheduled" run time. I assume that's also sunset. So for that moment the folder is true thus allowing the sunset program to run. After such time the folder would be False and not allow anything else to run. That's why no other programs have a "Next Scheduled Run" showing. Even the Sunset program itself doesn't have a next runtime because it's in a false folder. (Notice that your "ON" "Query All" also don't have any last run times and no scheduled run times.) Click on the "My Programs" folder. On the right side there should be a line in the "IF" area. Click on that. Click "Remove Line" (see arrow below) Then "Save Changes" on the bottom left column of the admin console Once you do that the "My Programs" folder shouldn't appear in the summary screen. As noted above when there aren't conditions in the folder it won't show up on the summary tab because it has no reason to run. Your other programs should then populate "Next Scheduled Run". Final comment - notice in my program above that you can achieve both the On and Off setting with one program. You don't need to have two programs for the different times. If you really aren't turnning off both devices that you're turning on at sunset then just put the ones you want to turn off in the ELSE of a single program to run from Sunset to Sunrise (next day) and the light will turn off (if you follow the program I posted earlier. Good luck!

@Jack D For your Sunrise program is there a "Next Scheduled Run" time shown? I just created a test program like your Sunset program. The status matches what you're seeing. The above "Light-test1" is for Sunset, and "light-test2" is for Sunrise. Make sure that you've saved the programs. They shouldn't have a green arrow on the name like this one does: If I run the "IF" of the Sunrise program my light turns off. It also updates the summary for "Last Run Time" so you know something in that program ran when you triggered it manually. The program is: light-test2 - If Time is Sunrise Then Set 'Front Door' Off Else - No Actions - (To add one, press 'Action') OH!!!! I've got it (I think)! While I was typing the above I looked at your screen shot again. You've got a folder condition in the "My Programs" folder that is making the folder false. Anything in that folder won't run. (which makes it odd that your sunset program ran - maybe it ran yesterday, but didn't run tonight if you changed something today). Make sure your "My Programs" folder looks like this: NO conditions! Mine doesn't have any conditions and doesn't show up in the summary tab. I added a condition that would make that folder false and it showed up in the summary tab. Because the "My Programs" is typically the root folder none of the programs in the root would show that as the path. Only programs in subfolders would show something in the "Path". I still don't know how your Sunset program shows "True".

@Jack D yes, check the version to make sure they match. Especially since you said you just updated. Looking at your programs again and the summary something isn’t right…the “Sunset” program should only be “True” at the moment of sunset. All other times it should be false. Something is causing it to always be true. Perhaps UI/FW don’t match. A way to test is: Then turn on the light strip. Right click on the sunrise program and select “Run Then”. Do they turn off? Doing this is a simple way to test that the program actually controls what you expect it to do. Do you have any other programs that might be conflicting with the time and keeping those lights on? Lastly, since you said you transitioned from the Insteon Hub to the ISY did you reset any/all devices before adding them to the ISY? I don’t think that would block a program from even running and it clearly doesn’t have a “last run” time shown. I assume you made the program before today so it should have run at sunrise today. Also since you did just update make sure you save the programs again. Select one, then hit save again. Just as a troubleshooting step following the update.

@Jack D Welcome to the ISY way of life! We're here to get you sorted out. The forums are great for user-to-user support and assitance. First off, the best way to get program help is to post the actual program. If you're on the details tab and click on the program you want to work on. Right click that program and at the bottom of the menu that comes up will be the option "Copy to Clipboard". Then come to the forum post and paste it as text. For your first request, here is a simple program that turns on a light in the evening and off in the morning. Front Light - Night - [ID 0002][Parent 0001][Run At Startup] If From Sunset - 1 hour and 30 minutes To Sunrise + 1 hour and 20 minutes (next day) Then Set 'Front Door' On Else Set 'Front Door' Off The way the ISY programs work is they are ALWAYS running. So you seeing them "enabled" is fine. The "True" and "False" status is what you want to look at. A program that is "TRUE" means everything in the "IF" portion of the program happened. My program above currently shows: The program would be "FALSE" when it doesn't meet the criteria of the "IF" portion. The best thing I would suggest to you is to review the UDI Wiki and download the ISY Cookbook and search for topics you want to learn more about. The cookbook was written a few years ago and hasn't been "updated", but it still reflects the basics of how to program and definitions of each part of a program mean. Post your program to get help with the specific issue. The summary tab doesn't help us be able to help you very much. It's also key for us to know what your ultimate goal is. So just turning some lights on at sunset and off at sunrise can be done with a very simple program. More complicated things will require a lot more information from you for what you actually want to accomplish.

@larryllix overall I agree, but I don't like getting lost in the weeds by nitpicking what is typed out. I'd say even the most casual user could understand the instructions as written. Sure, they could be cleaned up a little and matched EXACTLY, and certainly someone could suggest this directly to UDI (there's a great "contact us" link on their website). How do you jump to the conclusion that the instructions might cause people to "factory reset" their devices? That's quite a huge leap from where the discussion was heading. Are you alright? Either your keyboard/device is having issues or you might need medical attention. What is "5 .inured"? I can figure out "co fusion" is just a space instead of "n", but...? I can recall all the 4.x and 5.x updates for ISY994 that seemed to just copy/paste the method for updating and big differences that were sometimes in those instructions or results. Besides, if the instructions were exactly right what would we then be able to discuss on the forums? I mean it's not like there's NOTHING else that needs the attention to detail. So I'm willing to look past a few minor discrepancies in the instructions because I know what to expect.

Since you're on Polisy is your PG3 version now 3.1.18? That's the latest release. Should be what was updated in the process. Glad it seems working again. Might still be of value to submit a ticket to UDI for record of what happened (Save your error log now if you randomly clear it from time to time!). Since they're so focused on fixing things that are being reported via support tickets they might miss some of the details in these threads and not realize something went wrong.

I think the option to update/upgrade PG3 inside of the PG3 dashboard was removed in a past PG3 (Polisy) update. Currently the only way to update PG3 is through admin console "Upgrade Packages" button. What @asbril was implying was just the restart PG3 option (what he supplied in the screenshot above). In the past the PG3 update needed a reboot of PG3 for things to come back online and load correctly. It would alert you in the footer of the dashboard that PG3 needed to be restarted. Rebooting/restarting is still the case, but think UDI has adjusted the code in IoX Admin Console to give you the steps needed to complete the update.

A technical brain! I know Michel has commented in the past that they're coders...not manual writers. The instructions also say "(Admin Console | File | Backup IoX )". I've never seen "Backup IoX" as an option. But I understand that "Backup ISY" means the same thing. But, agree...instructions don't directly match the options being discussed. I think somebody else pointed out the "Update Packages" is actually "Upgrade Packages" button. As long as the code is right I can deal with little details issues in the instructions...as long as the general instructions are easy to follow and most can figure out what buttons/options are really meant. It seems some just enjoy playing in the weeds!

Thankfully, UDI has top notch support. That's what it is for is to help when things go south. It's a whole lot better than randomly running commands and trying to fix it yourself that can sometimes just do more harm than good. It's great that you remember some commands that Michel used previously and that you might be well versed in the system language (more than myself or other casual users), but at the end of the day the point of developing the hardware and the software/firmware running on it is to try to keep issues like you are experiencing from happening. When may others are posting that the upgrade process went off without a hitch when there is an issue it's key to let UDI know so they can troubleshoot and learn from it themselves. They're too busy right now to monitor the forums for the details (like your case). So if there's a bug/flaw the best way to communicate this to UDI is through the support ticket process. It also allows UDI to better finetune the product for the rest of us so others don't have the issues that you're experiencing. And no, I don't think Polisy is anywhere near "obsolete". UDI has stated they plan to support it for a few more years. It's just that the hardware was unavailable last year so they sourced the eisy devices. They're developing for both Polisy and eisy at the same time. Trying to keep them similar and bring the PG3 side in line for both is a tall ask. So don't think that there's any problem with the hardware you have. If I had to guess it's as though the IoX process on the Polisy isn't starting correctly. If you've rebooted the Polisy and it still isn't starting then something might have become corrupt in the update. That's where UDI support needs to step in to identify the parts that aren't updated and get you fixed.

👍 I'm with you! That's why I was so glad to see the line about them working with Insteon to get full support. It's fantastic news. I know from watching the "Lunch with Insteon" (or whatever they call it) that Insteon does want to work with 3rd parties and it's great that UDI is open to working with Insteon. I think UDI was always open to working with Insteon, but the old Insteon wasn't willing to work with UDI. It has to be cooperation so the consumers win.

This is a new update notification system that @bpwwer has commented on before. I think PG3x sees the update is "out there", but it's being tested (internally) and not available for wide (public) update yet. It's been this way for a few weeks now. No need to update until a release announcement is made (at this point).

If you’re going to quote the release maybe post the WHOLE release…or at least the important part after what you seem to take issue with… I’d say that UDI even adding/acknowledging that some of the i3 support is available is a big step, and saying they are actively WORKING with Insteon is an even bigger step. Considering the focus of recent updates was squashing bugs the process to introduce the initial support for a brand new (to the wide public) product is HUGE! So don’t throw shade without acknowledging the line following your quote. Would you have rather waited for UDI to comment on i3 support until it was fully implemented? We already have posts here asking if i3 will work with eisy/Polisy, heck even some hoping it will show up on the “ancient” <grin> ISY994. I think this release addresses those questions perfectly. It’s in the works, they’re working with Insteon to have full support. And for those 994 users that want to add i3 now know they will need to upgrade to have support. No more questions and wishful thinking. Well done UDI! Thank you for addressing the i3 support question!

@Javi on .24 (and probably earlier, but didn’t notice it). If you edit the name of the Geofence area then edit the location bubble or radius the name is not saved and needs to be edited again. Not sure if fixable, but I didn’t catch it until I saved the new zone and had to go up back and edit the name again. No big issue, but if able to add a check/save option when editing the name before going to a different setting to save the entry. No longer have duplicate zones added. Thanks!

@f11 at this point you are probably better off with a support ticket to get direct help. I think it wouldn’t be wise for anybody to speculate what to do next other than UD Support directly. The current IoX release (5.5.9) has started adding groundwork to have PG3x on the Polisy. So what you’re seeing is probably fine. I would not randomly run SSH update/upgrade commands since UDI has suggested the best upgrade path is through Admin Console because they developed the scripts for what gets updated and works for their need on their hardware. Blindly upgrading things through SSH could cause issue. Please start a new ticket: https://www.universal-devices.com/my-tickets/

Don't know. I don't run the node server. But there was discussion about it in another post that worked out for them. It's all it what works for your needs/comfort.

Yes, I think @apostolakisl found the long poll was keeping the vehicle awake and set it to either 24 hours or near 24 hours. Anything that's checking the status of the EV will keep the vehicle awake and use battery. It's just as though you're opening the Tesla app. It's waking the car up to get status.

I've been told it does accomplish the same thing. Now, I can't verify this for this update since there is some groundwork for future changes to PG3x for the Polisy. But I think if you've successfully updated and things are back as expected then you should be okay. If you notice admin console, PG3, or node servers not loading then perhaps a full power cycle might be needed.

@Techman the OP (@teverk) posted that needed cables have been purchased. @JP If they're currently unavailable from UD you can buy this cable from Amazon. Do you have the original RJ45 to DB9 cable that came with the serial PLM? If not you can then buy the adaptor too. Be sure you follow the pin out information on the UD site and in several posts found around the forums.

@ABietsma Welcome to the forums. First, make sure the ISY has internet connection. Do you see it active connected to your router? (Log into your router and see if you have anything for "Connected devices".) If it's connected to your router then make sure that you can access the admin console while local. While in Admin Console check the status of the portal on the Configuration -> Portals tab. Make sure that your ISY Portal license hasn't expired. Logging into my.isy.io, click "Select tool..." -> Information -> ISY Portal Access License. If you confirm all the above let us know. It's probable that you might need to open a support ticket (https://www.universal-devices.com/my-tickets) to see what happened. My hunch is either license expired or something happened in the network to knock the ISY off your local network.

@JP glad you got it figured out. This is the only reCAPTCHA that I see when submitting a new ticket. You weren't able to see/or click on that? Very strange.

WOW! People use some close/small zones. I found about 1000-1500 meters to be ideal for my situation. But I just used geofence for lights. I guess some use it to open garages and unlock doors (too unsecure for my liking!). It also doesn't seem to be a battery drain by having larger areas (<1% in last 24 hours in background use).

@JP the email method might not get you in the ticket system. If you get an automatic reply that a ticket has been generated then okay, but recently the email was removed as a method to generate a ticket due to site/system issues. Surprised the web is giving you issues. Do you run firewall or other web blockers that might be blocking something? Maybe try a incognito or private browser session.

@ctviggen1 make sure you’ve added the eisy to your portal account and setup the trial portal subscription for the eisy. Wiki instructions to migrate the portal: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Migrate_configurations_to_a_new_ISY If you have the eisy on the portal it needs to be approved in admin console on configuration tab then portals tab.

You’re at 5.5.7 so no need to upgrade packages again (currently). You can follow the “current release” area to get notifications when new releases are posted. That’s when you would want/need to update. I usually suggest people don’t randomly hit update. Many have learned it has crashed their systems randomly hitting the upgrade packages process. It’s hard do hold off thinking you’ll get some random update, but best to wait until official releases are posted if you’re at the current level already. All your issues seem to be known issues and hopefully corrected in next release.

Interesting. Can’t help on that then. My eisy is not in an area I can connect a monitor to so just use admin console.