Geddy

@naeblis strange that everything was working then suddenly it doesn't seem to connect. It's possible that during the reboot something didn't load correctly. I'm sure you've probably tried to power cycle several times and it still isn't coming back up. It's possible it could have been in an update status depending on what you had been updating during your setup. It is possible to setup wireless connection, but you need to use UD Mobile with that (I believe), and I it's been a while since I tried it that I can't help with the direct steps to try. Read through the eisy User Guide in the wiki (https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide) and it should help you with the wi-fi setup. Ultimately, it might be best to start a support ticket just to be sure something else hasn't happened to the device: https://www.universal-devices.com/my-tickets What brand/model router are you using? The only other steps I would suggest is to power cycle the router. Unplug the eisy (both power and network cable), then power cycle the router. Allow the router to fully boot up. Log into the router, if you have an IP reservation for the old ISY994 or the new eisy remove them (both). Then connect the network cable to the eisy and router then power up the eisy. If it reconnects to the router then you can setup IP reservation again from the router. Also, are you using any Insteon devices? You mentioned getting all your z-wave devices back online. Just wanted to make sure if you have Insteon devices that the PLM is connected via USB to the eisy. The network jack on the eisy is just that...a network connection, not the PLM/serial connector like it was with the ISY994.

@naeblis welcome to the forums. I'll assume that "no longer showing online" means from the Portal when logged in. Are you able to access the device locally with admin console from a computer? Make sure that you can connect to the device locally. It's possible during the moving around or power cycling that it activated the wireless setup and didn't reconnect via the wired connection. Unlikely since I think when a network cable is connected the wireless is disabled, but could still have been bumped inadvertently to initiate the wireless setup. Check from your router if you see the mac address for the eisy as a connected device. Lastly, double check that the portal registration isn't pending in the admin console. Configuration tab -> Portals That should show "Online" and "Registered"

@TheA2Z @Athlon not sure how much Michel might actually be watching the forums currently so best way to report this as possible bug is through a support ticket. https://www.universal-devices.com/my-tickets/ Certainly the advised method to report bugs so they can be tracked and fixed internally is through support tickets. Be sure you attach screen shots of UI/FW information to your ticket.

@KHouse I've had good success with using this website to make sure Alexa is learning devices correctly: https://alexa.amazon.com/spa/index.html You can login there and then click on "Smart Home" -> "Devices" and see what it's seeing or has listed. You will need the UD Skill "ISY Optimized for Smart Home V3" installed on your Alexa account. Wiki might have further help for you to troubleshoot if you don't get it sorted out quickly. https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3#Instructions_for_New_Users

There should have been a sheet if instructions included in the envelope. I know there was back when it was first being shipped out. But, you're right...if not in there it's difficult to find. There was a link available to them when the product was released and first shipped for the ZMatter board that referenced the colors. It's still in the wiki, but I think only under the Polisy entry and more for the internal board for the Polisy. https://www.universal-devices.com/docs/ZMatter-Assembly- Instructions.pdf

@JTsao Haven't seen many others report this. It might be that you need to get a IoX and PG3x log and open a support ticket and have it reviewed in detail. https://www.universal-devices.com/my-tickets

Do you have the eisy registered with ISY Portal? You don't have to have a "subscription", but the device should be registered with the portal. Have you just been rebooting via the Admin console? If you can access the device try pressing the button 5 times to reboot. Otherwise, press it 6 times to shutdown (power light will go red) then pull the power for 10-20 seconds then plug it back in and allow several minutes (as many as 5) for the system to be fully functional.

@dougos2 Looks like might be a "known" issue with this brand/manufacturer. Here are a couple of old posts to review: PS: Since these posts are archived the only way to find them is with Google Site Search. These don't show up when searching via the forums search tool.

@dougos2 Could you add some additional system details to try to help? What's your ISY994 Firmware? What is your UI for Admin Console (Help -> About) What series Z-Wave do you have? (Use this post to help determine your series controller) Do you have any other Z-Wave devices that report status correctly? I'm not familiar with the smart plug, but it's possible it is a newer 500 or 700 series device that isn't correctly sending information to the ISY994 z-wave module you have. Perhaps others with more z-wave experience can chime in, but additional information on your setup could be helpful.

Probably nothing to fit your need mentioned in the forums (as you said link shared by @lilyoyo1 didn't fit your need). So the best bet would be to open a support ticket directly with UDI and get information directly from them (if it's available). https://www.universal-devices.com/my-tickets Honestly, I don't get the worry/concern. It's all internal so no traffic is leaving your network. Hope you get the answers to your questions.

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.