Geddy

dang...that's a bummer. Glad you got some help and hopefully the replacement one will be there before you know it. You certainly know a lot of troubleshooting steps at this point!

@Jay M because you've posted this in the ISY994 area it would also be good to know what Firmware you're running. Please check admin console help -> about and post what Firmware and UI you're running. Make sure those match!

@dpierre do you have anything automating the shades currently? I've got a few Somfy controlled roller shades and have always hade their MyLink. It's painfully low tech, but does the bare minimum that works for us (timed raising and lowering of the shades). Sadly, there was never a node server for the MiLink option. There was a Home Assistant option at one point, but it too was discontinued. Somfy also has their Tahoma option, but it's perhaps as unreliable as the MiLink product. I haven't ever tried the Tahoma. I have looked into the Bond pro option in the past, but couldn't bring myself to buying another $300+ "hub" just to control a few window coverings. If/when the MyLink ever fully dies I might have no other choice but to buy an expensive hub or just use the remote daily.

@GTench and @mjrush at this point I thin you've got to wait for the developer to update the files again. Sounds like they weren't released to the server correctly or maybe a spot showing the version number was missed somehow. Being that it's a holiday more than likely it might be something that will get handled later in the week. I tagged both the node server developer and PG3x developer (above) and neither have chimed in so I'd say allow them the holiday and see what happens. If "urgent" and you want to try contacting the developer another way you could raise an issue on the github - https://github.com/Panda88CO/udi-yolink/issues

I prefer to suggest people start a ticket so all of UDI can be aware of any issues going on. Certainly @bpwwer has offered to review logs for others for specific issue. However, since this covers node servers, UD Mobile, and ISY Portal it's best to start a ticket so the issue can be reviewed by everybody and see how their part plays into this. Something like this impacts the entire process so best to have everything worked out eventually.

@GTench what happens if you go to the YoLink node server information in the store? Do you have an "Update" button where the "Install" button was originally? @Panda88 or @bpwwer might be able to provide insight as to what is or isn't happening.

@mbking Which device is this happening on? Are you running both devices and having the issues at the same time? Or are you only running one device and this has been an ongoing issue that you're asking about? Not sure if it would be an indication in your case, but see two replies from @bpwwer in another thread talking about this happening to others. Reply 1 - https://forum.universal-devices.com/topic/41247-support-thread-for-pg3x-v3127-may-22-2023/?do=findComment&comment=366754 Reply 2 - https://forum.universal-devices.com/topic/41247-support-thread-for-pg3x-v3127-may-22-2023/?do=findComment&comment=366867 Probably the best thing to do is the next time this happens would be to pull a log package and open a support ticket and include the log package. It might be valuable to look at two different logs: 1 being just the standard log when you see this happen (you'll need to catch it on the same day that you get the notifications) 2 change the log type to "debug" then restart the node server(s) you are having issues with. Then restart Polyglot and allow things to settle in the log (maybe 2-5 minutes) then download that log package (maybe add the word DEBUG in the file name to indicate it as different and possibly more information). I think Bob made a change that the log will revert back to info after a period of time, but to be safe make sure you change the log type back to "Info" so it doesn't keep flooding all the debug info into the log file.

@mfbrin there's also an entire forum section for the UD Mobile app: https://forum.universal-devices.com/forum/24-ud-mobile/ Can get help and read more about what others have been doing there.

Bummer! But that's not the first one this week that said they can't find the eisy. At least you can SSH into it so you know it's connected to the network. Is this the first time that you have powered up the eisy? Are you attempting to use wireless or wired connection? You said you tried to add it manually. Make sure you use the options in the wiki section for help. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Can't_Find_eisy I recall there being one update that didn't allow me to add the eisy.local:8443 address and only allowed the IP:8443 address. I'm sure Michel will get you some information to try. Don't go crazy pressing the power button trying to update or reset the networking on it until directed to do so from UDI. I think many will try a bunch of different attempts to fix it and not really know what state the device is in. Sorry you ran into issues.

@JRC at this point best to wait for support to reply to your ticket before attempting anything else. You've done so much who knows what status it is in? Just wait for support to assist. Please report back how this is resolved though. Would be interested to learn what happens.

1 - email sales@universal-devices.com to ask them directly - nobody here would know as we're mostly user-to-user support. 2 - If they're accepting orders then the hope/thought would be that they would ship out in the order they received orders. When items are out of stock though no orders seem to be available. Again, something to ask when you email to see when devices will be "in stock". 3 - This is for developers only. Kind of unclear as to why it hasn't been amended to suggest that it's directed to developers and not "general" consumers. From time to time UDI has offered discounts shown in their blog posts. Those can be found on the main UDI website.

Correct. The Polisy replaced the ISY994 a few years ago and added the ability to run node servers and ISY as a service all on one device. In Dec 2022 UDI released the eisy (yes, all lowercase) to replace the Polisy (and the ISY994) as the hardware for the Polisy was no longer available. The Polisy and eisy are able to run ISY as a service as well as Polycglot V3/V3x to run node servers for many different services. Currently there are over 100 node servers in the node server store (https://polyglot.universal-devices.com/). You'll see that there are many options to incorporate other systems into the world of ISY (now simply referred to as IoX - you'll see why in the wiki) UDI sells all their equipment on their site: https://www.universal-devices.com/ You can find users selling their old Polisy in the Coffee Shop area of these forums if you're inclined to get that hardware. UDI has stated that both the Polisy and eisy will be supported for the time being. No certain "EOL" information has been given for the Polisy. UDI does not "require" a cloud service, but it sure does help. The UDI Portal offers so much additional options for remote access, network resources, and smart assistant connectivity (Amazon and Google). You will need a UDI Portal account to buy node servers. Accounts are free, it's the portal access/service that costs (very minimal amount for the advanced services provided). The best places to do research is reading the UDI Wiki (https://wiki.universal-devices.com/index.php?title=Main_Page) and reading posts on the forums.

@pjjameso 3.1.27 is for PG3x running on eisy or Polisy. If you're not yet running PG3x on the Polisy then you have the current version of 3.1.21 (at least as of the time of these posts). To learn how to update to PG3x on the Polisy please review the wiki: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Upgrading_to_PG3x

PLM must connect to the eisy via USB. I'm not sure what color wiring has to do with that. It can be any color of USB cable you have. As @elvisimprsntr shows the path of cable and converter if you got the converter from UDI be sure you follow the pin out for the serial PLM kit. There is only one network jack on the eisy. That is ONLY for wired network connection. That is NOT where the PLM should connect. That's a change from the ISY994 that used a network cable to connect to the ISY994. But the PLM 2413S is a serial connection. There was another cable in the PLM box originally that had a network cable at one end and serial DB9 connector at the other end. Many did not keep that (or didn't realize it was tucked away in the packaging) and so need to go through the adaptor process and then DB9 to USB convertor cable to concect to the eisy.

@JRC welcome to the forums! Have you watched this video from UDI for setting up in wired format? https://youtu.be/GdKfAVfz2Fk Also, just good to make sure you read and check the eisy User Guide in the wiki as you get things running. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide What do you mean by this statement? It's fine to keep both ISY and eisy running at the same time. Just for setting up it's fine. Once you move the PLM and/or any ZWave devices to the new eisy please turn off the ISY994. (Especially if you have zwave devices!) I can't help with the android device as I'm an iOS user. Also, macOS users seem to have success or heartache with IoX Launcher. If you've used the IoX Launcher successfully on the mac in the past to work on the ISY994 then you should be okay once you have the eisy connected to your network. I would do as @tazman suggests of pressing the button 4 times to reset networking then I would do as @Techman says of pulling the power and trying a different network cable. Oddly enough it could be THAT simple. I know I didn't attempt to use an old cable and just use brand new cables when new devices are being added to the network. Just like to keep things "new" that way.

This is very possible with DHCP reservations. Depending on the router you might have to connect everything first then assign IP reservations. Some routers will allow you to reserve IP with the MAC address before connecting, but depends on the brand and firmware.

Yes. It's normal "now". Seems to be changed from a previous update. I noticed same thing in recent PG3x update process. What are you trying to update? Looks like you are current for IoX and PG3. You can always check what the current versions are in the Current Release Announcements area of the forums: https://forum.universal-devices.com/forum/339-current-release-announcements/ As of today: 3.6.0 IoX (released April 20, 2023) 3.1.21 PG3 (Polisy) (released May 22, 2023)

Does this mean you've resolved your issue or are you still having problems? When you click install it should pop up a window to Purchase. After you purchase you might have to click "install" again. At this point it should pop up another window. At the bottom it has an option for what slot to install it into: Select the slot number you want to install it to and click "install". It should then process correctly. Purchasing and installing node servers is documented here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#NodeServer_Store_Menu

@mapeter This is something UDI would need to answer directly. Best to open a support ticket to ask the question directly to UDI. https://www.universal-devices.com/my-tickets/ Doubtful any user-to-user support would give a valid answer since only UDI knows the dependencies of the systems they've developed.

@TriLife first thing you will need to do is update the ISY994 to 5.3.4. That's the only path to migrate to IoX. Before you migrate get the eisy connected and updated to the current version. Links to all current version firmware and how to update can be found in the "Current Release Announcements" area of the forums. My suggested path would be to migrate directly from ISY994 to eisy. I don't know what "whole bunch of Tasmota/MQTT devices" implies, but Insteon and Zwave migration should be straight forward at this point. You are on your own for the other devices. Make sure you read through the eisy user guide and pay special attention to the migration instructions: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide There are some specific posts for Z-Wave migration pinned in the IoX Support part of the forum. Be sure to review those for your situation. (Note: unsure where it's mentioned, but all Zwave nodes will change their node nomenclature from ZW to ZY) You CANNOT migrate PG2 node servers to PG3/PG3x. You will need to start fresh with node servers if you are not running any PG3 node servers on the Polisy. There is no migration path from PG2 to PG3/PG3x. You can only migrate PG3 to PG3x. If you've never entered the PG3 side of you Polisy you can see the current list of PG3/PG3x node servers here - https://polyglot.universal-devices.com/ (There is a production store and non-production [beta/test] store. You will probably want to stick with the production store.) Simple suggestion is to stay focused and target the update/upgrade and migration steps in order. Read the whole process so you know what to expect and steps to do. If/when you run into issue fix only THAT issue. Don't move on to something else thinking that you can fix more later. It's usually easier to fix a system when only ONE thing is not functioning properly. If you go off and have multiple things trying to fix all at once it gets confusing for you and those helping you. Note that this is a holiday weekend in the US so not sure how much support there would be through UDI support tickets or activity on the forums. But you know the community is here to help if needed! Good luck and keep us posted on your progress.

@hart2hart Sorry you're having the issues. Hopefully @Michel Kohanimor @bmercier can get to the bottom of this. I checked again after my last reply and thought I had an issue, but it looks like I had a false alarm that it didn't trigger. If you've got the new node server and authenticated it again I'm surprised it isn't working. I went through it and restarted the node server, hit authenticate and motions and rings trigger fine. For my testing I set the log into debug, restarted the node server, hit authenticate allowed a few minutes for things to settle. Went and made motion. I saw the motion result in the log for the node server. Then opened admin console and the program had "last run time" of my motion and the light I trigger had come on (I could see that while I was outside). What I saw in the node server log is: 🤞 they get you squared away. Keep us posted in case others have this issue.

Actually it's better than perfect (for 99% of the users). There has been multiple threads about this since IoP (now IoX) was released. Very few people might have a true use case for something like that, but 99%+ of the users are better served by using the solution @lilyoyo1 posts. Many moons ago it became the suggested method of using a DHCP reservation on the router to keep the ISY994/Polisy/eisy at a known IP address. The reason has been repeated many times that so many support tickets were created due to users replacing the router. The issue always centered around somebody setting a static IP on the (old) ISY994 then changing their router and ultimately the underlying DHCP IP table. The ISY994 couldn't connect to the new DHCP table if it was a static point with a different LAN IP table. Typically most involved and (I dare say) responsible users will make note of settings and remember that things are set statically at the device level rather than at the router. Sadly, many that don't remember those things, or didn't set it up originally panicked when they replaced the router and the ISY994 didn't magically reconnect to their network. Thus resulting in a support ticket. When UDI introduced IoX they removed the ability to set IP at the device level. Meaning the only way to keep the device at a "static" IP is to use the DHCP Reservation from the router level. 👍

@hart2hart what happens if you select "run then" of the programs above? Do you see it triggering the program you're calling? I'm using the Ring node server with a Pro doorbell and a wired Floodlight Camera. What's strange is since the devices are linked in the Ring app it seems if there's motion at my doorbell the floodlight doesn't trigger motion (at least from my limited use/testing). However if the motion of the floodlight triggers first if fires my motion program all the time. On the motion program why do you have the "And $Front_Porch_Motion_Running is 0"? Even if you're saying it's set correctly you've got 3 and statements that all must be true. I'd test it with just the motion first then add one and clause then another if it's needed. Seems too complicated just for a motion trigger. My test program was: ~Flood-Motion-test - If '~NodeServers / ~Ring / Driveway (Motion)' is switched Motion Then Set 'Lamp' On 100% Wait 2 minutes Set 'Lamp' Off Else - No Actions - (To add one, press 'Action') Do you have devices linked in the Ring app? Perhaps motion is being triggered by another device and the porch camera is linked and therefore not the one triggering the motion. Last effort is...have you created the programs as NEW? Using the new nodes? You mentioned they're what you ran when using the PGC version of this from ages ago. I'd try a new program rather than trying to modify an existing one. Doubtful it would have any difference, but something might be goofy.

What resulted from your ticket? Were the old ZW nodes able to be removed somehow? I'm confused as to why/how some remain ZW. Perhaps it's an issue that hasn't been encountered (i.e. reported to UDI) enough for them to consider it being an issue worth making a note/comment in the migration process. If you got resolution through the support ticket share what happened with that so it would help others that might suffer the problem. Additionally in the support ticket suggest that it be documented somewhere that this might happen and possible way to resolve it.

If Honeywell's site doesn't see their own products then that's probably where I would start. Once it shows up on their servers the node server should probably find it by connecting somehow. To me I'd say this is probably an "unsupported" node server. You could open an issue on the github, but appears that @bpwwer is the one updating a few files there now. https://github.com/UniversalDevicesInc-PG3/udi-honeywellhome-poly/issues