Geddy

Thanks @bpwwer. Was able to upgrade without issue. Just allowed time while I did other work and came back, opened Admin Console and it said it was updated, needing the reboot. Allowed it to reboot and got notification from UD Mobile that eisy went offline and online and a little later tried web access and all was as expected. Well done!

@JSylvia007 if still having issues with such widespread z-wave issues it might be best to open a support ticket with UDI to make sure you're going about the fix correctly. Also, if there are "bugs" or other issues happening that's the only way to report them directly to UDI so maybe they can fix anything that might need fixing moving forward. https://www.universal-devices.com/my-tickets/

This is from the wiki: Hopefully that's what you went back and read again. It's from this section: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#What_to_Expect_During_Migration

@MSpangler moved your post out to a new topic to hopefully get additional attention. You posted to a thread that was over 4 months old and your issue might be different so better to start a new thread. Link to old issue by other user: Have you replaced the batteries lately?

If the program you posted is the only one triggering based on motion then it shouldn't be doing it during the day, but now you've said you've adjusted the motion sensor to only trigger at night. Did that help? What kind of motion sensor are you using? It sounds like there might be another program triggering the light. You can use the "Find/Replace" feature in the program tree. Click on the root folder (probably "My Programs"). Right click to get a menu. Select "Find/Replace". You'll get the window to search for finding "Your Devices". Select the "Parking Pad..." and then only hit "Find" (note, you don't want to replace so be sure you only click "FIND" If you want it to run all night then you should remove the "11:45pm (Same Day)" from the program and make it something like "Sunrise (Next Day)". The example @MrBill gave above was from his own system and it was for a light he wants to turn off before midnight. The example I gave above turns my lights on and off around the sunset/sunrise time. You would want something similar to allow the motion to trigger during the middle of the night. What you posted in a screen shot above could be your issue. Unless you modified THAT program. The way you had it in the screen shot was that anytime there was motion they light would come on. You also ran the "THEN" of the Sunset path meaning whatever that program does happened following the program you posted. When you call on a "THEN" there's no evaluation of that program and it just runs "THEN". So even though the sunset program probably has a time to happen you're avoiding that schedule when you run "THEN" of that program. Since you've been modifying several programs please post all CURRENT programs that trigger the light (Sunset, Sunrise (if still 2 programs), and motion trigger). This way we can accurately review what is currently being used.

@captainc might have not used proper programming, but mine work fine for motions to trigger lights. Check this from @Bumbershoot for possible help:

Are the ones that are still ZW battery devices? I forget where it was documents (can't find it in the wiki), but in a release for ZMatter Z-wave support it was said that all nodes would rename from ZW to ZY. Reason I ask about them being battery is this portion of the wiki might shed some light on why you have some ZW nodes. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Post_Migration @Techman yeah, I am not sure how yours also stayed ZW. Everybody else that runs ZMatter had reported the change. I did not migrate any Zwave and don't run many devices, but they're all showing ZY connected to the ZMatter dongle.

You can always look in this area for all the current releases for UDI products and services: https://forum.universal-devices.com/forum/339-current-release-announcements/

The "else" that @MrBill was suggesting was for your Sunset program. You have a "Sunset" and a "Sunrise" program showing in your screenshot. I think he's assuming that your "Sunrise" program might be turning the outside lights off. You can use his suggestion to only have 1 program. For instance I have this for my front door light: Front Light - Night - [Run At Startup] If From Sunset - 1 hour To Sunrise + 1 hour (next day) Then Set 'Front' On Else Set 'Front' Off This does both the turning on, and turning off. Be sure that it's triggered to run at startup incase you have a power outage that happens before your time and returns after your time it will turn on the outside lights. As you have it now your parking pad light will only trigger from Sunset to 11:45pm. You would set it back to the 35%, but you need to edit the sunset program to turn the lights on to 35%. Right now your program just has them coming "ON" at Sunset. Their on% is either handled by another program or scene or device setting. It's unclear how you're turning those on at 35%. What is "Outdoor Lights On"? Probably a scene? Final comment...wouldn't you want the outside lights to go to 100% if there is motion all night long? It would potentially pause anybody approaching your house with the change in brightness. And if you have outdoor cameras might help with the details of the motion overnight.

@macjeff is Easter the ONLY date you want to figure? Why not just program with specific dates? Dates through 2033... Year Holiday Weekday Date 2023 Easter Sunday Apr 9 2024 Easter Sunday Mar 31 2025 Easter Sunday Apr 20 2026 Easter Sunday Apr 5 2027 Easter Sunday Mar 28 2028 Easter Sunday Apr 16 2029 Easter Sunday Apr 1 2030 Easter Sunday Apr 21 2031 Easter Sunday Apr 13 2032 Easter Sunday Mar 28 2033 Easter Sunday Apr 17 uncheck "daily" and you get the yyyy/mm/dd option. Just plug those into your program(s) for Easter.

@737simguy Do you happen to have any "old" backups from the ISY994 prior to your eisy? Perhaps you migrated from ISY994 to eisy and still have the backup used from the ISY994 for the migration. You should be able to restore that backup. Or if you didn't wipe your previous ISY994 it should be possible to just plug back in and go through the replace PLM process to get things working again. If you added devices or changed programs after going to eisy all those changes would be lost, but using an old backup or if you didn't wipe out the old device you should be at least able to use that and not have to re-link or re-program everything.

This would be up to the developer of each node server to make a post when new releases are available. Several do, but many do not. Additionally, if people follow the root of the node server forum area they would get notifications of new topics created. Many developers seem to be editing or replying to prior posts and that does not trigger any notification to anybody following a topic area. However, following also notifies of other new topics, so not always an easy/clean option. Hopefully @bpwwer and @Michel Kohanim can move the update alert up the importance list soon as it does seem to be a missing link in keeping node servers updated. However, it should be one of the first steps in troubleshooting issues is to simply check if there is a node server update available if/when something isn't working as expected. I think the method @macjeff mentions of sorting by modified column is great. But can't see doing that "daily". Maybe once a week for casual review. If I wasn't as active on the forums I could see going weeks (or maybe months) between the time I log in to my Polyglot dashboard. That's the joy of the reliability of what's running on my system.

@smarthome_newbie If it gives you the options @Javi mentions above, but then there's no other window that pops up you might need to try this: https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored I get that the directions are Windows based, but perhaps macOS also stores *.state files somewhere. Use finder to locate any ud*.state files. delete all ud*.state files clear java cache run start.jnlp again

@Goose66 looks like you’ve hit the quota on messages. Maybe delete some and @drprm1 can msg you. LOL @drprm1 nice try. I’m “just” a user like many others. Only helping out on the forums to keep things neat and tidy at times.

@drprm1 probably best course of action is to submit a support ticket to UDI perhaps submit your ISY error log and node server log package in the ticket when you submit. This way UDI can review the IoX log files and review the node server log with the developer. https://www.universal-devices.com/my-tickets/ For the node server log click on log, change it to debug wait a little bit then restart the node server and wait again. If log has reset to "info" put it back in debug and operate the door a couple of times (by button/remote press, MyQ app, and IoX command). Just so all types of triggers are attempted and perhaps any logging done by the node server will be captured. Then download the log for the node server. The log type should change back to info, but be sure it's set to "info" when you are done. It's not a good idea to leave logs in debug mode. I think they have edited PG3/PG3x to reset it to info to not have huge log files, but best bet is to set it yourself. Of course UDI Support might suggest other logging options as well, but this will at least give them a better starting point when opening the ticket.

Posting on forums is not "reporting issues". If you have an issue you would like to "report" to UDI please submit a support ticket or contact UDI directly through their sales email. https://www.universal-devices.com/contact-us/ Perhaps neither business sees that there is an issue to resolve.

Since on Polisy have you converted that to PG3x? I believe for the Polisy PG3x is on 3.1.26 version. It's a great addition to the system to be able to trigger other events. I'm sure you'll get squared away.

@JBlake01 Are you sure you have an active portal license for the eisy? I'm not familiar enough with the process of install that I don't recall an IP address ever being an issue. I know it's looking for the ISY UUID for the target ISY, but not an IP address. I think support will be the best way to get you fixed up. Please post how you get this fixed so it can help others down the road. (And we can learn what happened too!)

@roblombardo same advice as above for you. Since the log seems to indicate it is installed correctly I would open a support ticket with UDI to see if they can dig deeper. Since this node server is so new there could be a few issues here and there now that more people are using it. If you get this resolved through support please post back what they did to help so that it might help others that run into this issue. https://www.universal-devices.com/my-tickets/

Did you click "authenticate" again in the node server? If I go directly to the link now it gives me the same error. But I clicked on authenticate again (even though mine is working) and it took me to that site. If you are not being forwarded to that when logging in then something else is blocking you. Possibly browser or OS related. I think the best thing, at this point, would be to open a support ticket with UDI and they might be able to review the logs and situation more to see what's happening for your specific issue. https://www.universal-devices.com/my-tickets/

What browser are you using? I seem to think that I had an issue when I installed it for some reason. I think I was in Firefox at the time. I think it was blocking some popup or new tab creation. I'd try from a different browser first. When you click authenticate it should open a tab to the Ring login site to login then prompt to allow UDI to use the Ring information. I just tried it in Chrome and it didn't open a new tab it just went straight to: https://oauth.ring.com/oauth/users/sign_in Maybe if you click authenticate then open that link in another tab you might get to the prompt, but I didn't fully try this time.

You can read the UDI announcement about ending support for the ISY994 on their site: https://www.universal-devices.com/byebye994/

I linked to the pin out in my prior post. You have to alter the adaptor to use the specific wires shown from the UDI site for the adaptor. I'm not sure if they've set it up prior to shipping out or if you have to wire it as such. I'm guessing that you don't still have the old serial wire that came with the PLM? It was tucked away in the box packaging so many people didn't keep it since the ISY994 used a standard cat5 from PLM to ISY994 even though it was using serial communications.

Just to be sure...your "installed, upgrade" means that you got the eisy upgraded? IoX = 5.6 (Firmware & UI) PG3x = 3.1.25 (Current versions as of this post) On the eisy I would press the power button 6 times to force a power down. The blue light will eventually turn read. (prior link to wiki for Multi Function Button) Once eisy shuts down (red light on power button) Pull the power to the eisy Unplug the PLM Wait a minute Plug in the PLM wait for solid green light (or maybe 30-60 seconds) Plug in eisy - wait for it to completely boot (maybe a few minutes) If still not working make sure you followed the pin out for the adaptor. Perhaps something is crossed up there.

Please review the steps in the wiki: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migrating_Node_Servers_to_PG3x I didn’t migrate node servers so can’t say how it works or what to watch for, but seems straight forward.