Geddy

It's found in the wiki in the Polisy User Guide. https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Upgrading_to_PG3x

@Valveman when next in Admin Console please confirm UI and Firmware match. That can be found in the menu option Help -> About In your first post you did not match. Need to confirm you do now that you've fixed your Java issue. Do you have access to any Windows computer to attempt to connect to the ISY with IoX Launcher?

WHAT? So you do have 2 routers? I thought you were just giving additional information in the first post that had no impact on the (real) situation. Your issue is networking if you're plugging a router into a router. Or do you mean that your eero is connected to a MODEM? Please try to clearly explain your network path. i.e.: Modem -> Router #1 -> eero (unusual method, but what you describe in your reply) Expected connection: Modem -> eero -> ISY994 If you're plugging the eero into another router then you have two competing networks (two different devices trying to hand out DHCP to connected devices). You need to set the eero into access point mode (if that's an option - I'm not sure how this is done as the last time I attempted to use an eero it didn't play well with Comcast so I sent it back and haven't ever tried that brand again). @DennisC has a lot of useful information above. If your network is a new setup it seems that you've caused yourself some unexpected network issues that need to get sorted out before you attempt further troubleshooting of the ISY connection. The only other option would be to turn off wifi on the mac and connect with a network cable to the same eero device to access the ISY994. You should be able to find the IP address from the connected device page. You said you see it, "shows "ISY994-EMS" as a wired connection". Somehow in whatever you're looking at it should show you the IP of the connected device. If not that's a shortcoming of the UI for the eero.

@smokegrub does your MAC have any way to use hard wire to connect to the same eero device that the ISY is connected to? It sounds like even though the eero is a mesh system it's not allowing wireless devices to talk to wired devices. Are you able to successfully ping the ip of the ISY? Since you're on macOS also if you can ping the ISY then try downloading admin.jnlp (http://##.##.##.##/admin.jnlp [where ## is replaced with the IP if the ISY]) from the isy directly. Seems that macOS sometimes doesn't like the start.jnlp method of connecting to the ISY. As @landolfi suggest perhaps add the ISY manually by clicking add then using the http://##.##.##.##/desc (again, using the known IP of the ISY994).

Well since op didn’t come back to link it I went searching….here is the post from @MrBill that I assume @philgood is referencing. No mention of scenes, but agreed that if controlling the fan directly then any scenes it might be in could be out of sync, but that’s typical for anytime you change one device directly. It’s also why I mentioned above that I do have programs that will sync the keypad buttons depending on what speed the fan is set to. (Keypads and Fanlinc have always created lengthy discussions. One a while back lead to an updated wiki topic to try to help.) Nothing is showing “running” in your screenshots above. It shows a slight green on the edge of the program to show that it last status was TRUE. You can see if it is “running” in the summary tab. It should just show “last run time” and “status = true”. It was true because you triggered the THEN. It has no if to trigger so anytime you directly call on the THEN it will be true. The off is red because you triggered the ELSE so was false. When a program is actively running the whole icon will be green. I still reason that adding the fanlinc motor as the fan category and being able to control it without programs is much simpler and cleaner. If you do use/need to have it in scenes then that’s a whole different aspect that isn’t being considered in the OP. if Alexa isn’t finding the fan spoken (as you indicate) I would make it a shorter name. Sometimes there is issues with “long” or multi-word spoken names. Keep them short! Another option might be using Groups in the Alexa app. I’ve not tried this and haven’t had great success in the past, but it might allow you to just reference the fan in the room you are in.

@philgood I’m sure I’ve been doing it this way since Fans were added to the Alexa skill in 2020. I just make the spoken simple to keep the command short. ”Alexa, set overhead fan to high”, and boom…it’s on high. Spoken is just “overhead fan”. This way I can control that fanlinc motor from any Echo device/app we have. I’m not sure the @MrBill post you reference (why not link to it)? But there can be more than one way to do things. The skill just seems to make it simple and painless. Perhaps the programs you’re working through solved another issue. Again, you didn’t link to the post for context. Read more about it in first pinned post in the Amazon Echo area of the Portal portion of the forums…

@philgoodwhy make it so difficult just for use with Alexa? In the portal add the Fanlinc motor as a FAN category device. Then Alexa knows how to set speed and turn it off. That’s how mine works, and I don’t have to worry about a program to set the speed. I do have a program to sync the keypad buttons with the proper speed for when the speed changes via other methods than the keypad presses. It’s simple and works. This method allows me to just say, “Alexa set fan to high”. It just goes to high.

@Jimbo.Automates since your post was 2 months old wasn't sure what the new reply to the issue had to do with it. Perhaps both could be related to the sunsetting mentioned here:

Sorry, misread first post. Quick question first, why change to wifi? Are you moving it to somewhere that you cannot connect with a wire? I think it works fine both ways, but just seems more reliable to be wired connection. (IMO) I think you will need to use UD Mobile to set up the wifi, but I’ve never gone from wired to wireless setting so don't know all the steps. Try with UD mobile and review the wiki user guide https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Go_to_WIFI_Setup_or_Leave_WIFI_Setup_mode

Wi-fi should automatically be off if the wired connection is made. I don't think there are any setting adjustments needed.

I believe @Michel Kohanim has said "for the foreseeable future". Nobody really knows/expects a timeline and wouldn't make it public if they did. It just released in December. Typically UDI has supported devices a very long time (the ISY994 just now basically ending support after 14 years) It's also been stated that the Polisy will continue to be supported along side the eisy for the next few years (something like 3 (at a minimum) sticks in my head). But, your request would probably be better handled directly to UDI through their sales email - https://www.universal-devices.com/contact-us/.

@JRC this might be something best fixed with a support ticket. Not sure how Google Home works with UDI so can't give you much help other than what's in the wiki or your the steps you've already tried. Just moved this over to the Google Home area and maybe @bmercier would be able to help on the forums...otherwise try a support ticket for assistance. https://www.universal-devices.com/my-tickets

You need to fix this. FW/UI must match. Clear Java cache the download new start.jnlp (IoX Launcher). Matching should clear up issues 2 & 4 What OS computer are you using? Win, mac, other? You might need to delete ud*.state files. There is a portion of the wiki about deleting those. Might fix issue 1.

I didn't ask to ultimately suggest you update. I just wanted a reference point for others to help troubleshoot. Probably 99% of the active users will be on a more current release for the ISY994 or at least used it more recently and didn't want to send you down a path of troubleshooting or fixing based on a firmware you don't run. If you do make sure which current version your device supports (i.e. do you have/use z-wave?). Also, there is a large change in how scenes are created in 5.x so make sure you read old posts about that. I'm not 100% sure if all of the changes were documented in the wiki and know the ISY Cookbook was written based on 4.x firmware so some of its instructions on scenes is outdated. Upgrading to 5.x requires a fair amount of prep and cleanup work. Please prepare accordingly. I would troubleshoot as @Techman stated above with a different device to see if the outlet even works as expected generally. It's probably best to fix the issue NOW, on the firmware you have and know, rather than blindly trying to upgrade THEN fixing a problem that you already had.

Yes, I've used gmail since day 1 and other than making minor adjustments when Google changed how to log in it's worked very well for me. You can follow the setup instructions mentioned in the wiki - https://wiki.universal-devices.com/index.php?title=ISY994:Configure_Mail_Server_Settings There was a post a while back (maybe a year or more) about something happening with outlook.com for sending emails. I haven't tried setting it up recently, but know when that post was made used some outlook.com settings and it also worked well. I just have better success with gmail.

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.