Geddy

If you just updated to PG3x then make sure your IoX and PG3x is up to date. Follow the process outlined in this post: https://forum.universal-devices.com/topic/42067-update-process-for-eisy-and-polisy-devices/ If after everything is current (compare to what is latest release in the "Current Release" area of the forums) if you are still having restarts please open a support ticket with UD (https://www.universal-devices.com/my-tickets) to get further troubleshooting steps. If you do get help from support please be sure to post back here what happened and hopefully how it was resolved so it might help others if they have similar issues. As for the Portal - you can register a device in the portal and not have a license for it. The license is only necessary if you're planning to use any of the features it adds to the device(s). If the ISY994 is only used for local IR you probably don't have much need for an active portal license.

@aLf question is what computer OS are you running? Windows, macOS, other? Wiki directions: https://wiki.universal-devices.com/Main_Page#Quick_Start_Guides Make sure you're using the basic Java you get when visting: https://www.java.com/en/ (current version 8 Update 421 - Don't download "crazy" java versions thinking a higher number is better...those are typically for only specific use cases. IoX Launcher is developed with "generic" java installed on standard operating systems.) Depending on your computer operating system the process gets tricky if not Windows based.

@smokegrub probably best to raise a ticket with UD. https://www.universal-devices.com/my-tickets I don't think just deleting an app and reinstalling it will do anything to help your situation. It's more likely you would need to remove the skill from the Alexa account and then login again with the skill. I'm not familiar with the process as I haven't had to do that recently, but I'm sure that process is outlined in the UD Wiki somewhere. Maybe also look at this part of the wiki: https://wiki.universal-devices.com/ISY_Portal_Amazon_Echo_Routines_FAQ (while you're not using Routines it might give you other ideas of troubleshooting tips) It's probably a simple fix somehow, but don't know those steps to suggest to be a simple fix. Perhaps through the suppor ticket you can get help to get it sorted out.

I think this might mean it didn't install correctly. Try just installing in the same slot again. What PG3x version are you running?

@Blackbird I use the OpenWeatherMap plugin. You just need to sign up for the API - there's a free option, but be sure you read about the amount of calls you get for free and set your short/long polls accordingly. https://github.com/BME-nodeservers/docs/blob/master/udi-owm-poly.md I believe @bpwwer recently updated this one and it works with the current API supported by OpenWeatherMap. Be sure to read the instructions about how to get an API key and how to setup the plugin. Some on the forums were having issues, but it's just the API does take a little while to "activate". It seems to work fine. I don't use any of the data currently in programs, but when I did there weren't any issues that I knew of for my simple, and limited, use.

If I recall doesn't the Portal integration includes the Networking module. So they aren't as separate as they used to be. But as said above it's no longer add modules to an existing ISY994. I am not sure if that includes signing up a device for the UD Portal though. It might be best to contact UD directly (https://www.universal-devices.com/contact-us/) or open a support ticket to get clarification of what (if anything) can be added. You can open a support ticket here: https://www.universal-devices.com/my-tickets/ Better to get what can or can't be done straight from the source (UD) rather than assumptions reached from these posts. My guess is, since support has ended for ISY994, it might not be possible to setup a new portal account for a "new to you" ISY994.

@Joshhall welcome to the forums! Here is the information for 5.3.4. Install instructions in this post.

@awzulich glad you got it sorted out! Hopefully the new PLM will be easy to swap out and work right away. Quick question about that...did you get a Serial or USB PLM? If USB note that some have said they had connection issues at first, but a few power cycles everything connected normally. Glad to have this one resolved! Thanks for the update.

@arzoo with all the previous help and troubleshooting you've been doing to still have issue it might be time to open a support ticket with UD to see if they can pinpoint the possible issue. https://www.universal-devices.com/my-tickets Keep troubleshooting stuff and let us know what comes from the support ticket. Hopefully it's an easy fix once working directly with them.

I think @paulbates meant SD CARD (not “sim”) on the ISY994. There isn’t an SD card on the eisy, it’s an actual hard drive system. It very well could have been an indicator of a failing SD card on the old system. But doubt it’s impacting the eisy, but I do wonder if it could have corrupted something prior to the migration.

@Kentinada The names should update if they have names associated with them in the web plugin list. I recall mine updating after bringing into admin console. Did you name them in the YoLink app? Mine follow the naming from the app, but I do think you can name them from admin console and be just fine. Some underlying PG3x setting might keep them in sync though. I recall others having an issue in other plugins when renaming in admin console it pushed back to the plugin and app and made issues. That was while back though and might have been fixed. Glad it seems to be working out. It’s okay to delete the plugin, but so much can be fixed without doing that it’s usually a last resort for me, but for many it’s their first thought. I don’t recall if they can group, but certainly putting in a folder helps. I have them nested in the Plugin folder for YoLink. Seems they just needed a push to get synched to the plugin then to admin console.

I might revoke that key and generate a new one. Something might have not copied correctly. Make sure admin console is closed while updating the plugin. Verify you get nodes added in the plugin web interface first before opening admin console again. Don’t delete or uninstall the plugin! Just try a new key and then restart the plugin. Watch the log for issues when the plugin restarts.

@Kentinada Make sure you’ve restarted the admin console. You probably have since you see a yolink setup in there. In PG3 dashboard does it show any nodes? If not then something isn’t right with the setup. Maybe put the log in debug and restart the plugin and see if it’s giving you any login errors. Looks like the plugin information also says it might take a full reboot for nodes to sync. Make sure you see all devices in the YoLink app. Make sure you copied the UUID and Secret Key correctly then perform a reboot of the eisy/Polisy. It should sync quickly, but notes do seem to make it appear it might be random time/process to get a good sync.

Not really a limit. According to the hub faq: While YoLink has a main FAQ some of your questions are answered in the specific product FAQ. Also, doesn’t look like they have a support forum, but they do mention a Discord channel for help, but think you need to request the link to it (from what I saw in their FAQs. Which hub did you get? It’s a slippery slope….I started with maybe 4 or 5 temp sensors to test and now up to about 10 sensors of various kinds. Mostly I’d say I’m very happy with the product. Hope the water sensors do what you want them to.

According to YoLink’s FAQ you can have more than one hub, but not sure if they’d connect at the same time. Source link Didn’t specifically see if you had speaker and non-speaker if they’d announce if not connected to it at the time. But like @paulbates suggests the range is amazing. So ideal would be get the hub that fits your need/want.

Just give a link to it and they can review if it helps. But sounds like will end up being PLM issue. Keep us posted.

That has nothing to do with IoX (if that's how your wiring works). It's just acting like a normal switch then. If you can't control from the Admin Console then it's a PLM/communciation issue. If the backup wasn't from the moment you made the conversion then it's highly possible you've made changes that weren't in that migration backup and is what's causing your problem for missing devices and corrupt programs. I would: Remove a switch you can get to easily from the Admin Console that has an exclamation mark on it meaning it cannot communicate with the PLM/Admin Console Factory Reset the switch Search online for the switch type and the reset method and be sure to follow it exactly! Pressing in the set button for a while (usually until the beeping stops) is most often the hardest part, but be sure you look up for your type of device because it can be different from other items Add the switch back to Admin Console - I usually auto link - be sure you select to clear out prior links upon adding Test if device can be controlled from IoX. When you mentioned that your backup was old made me think that you might have made changes and didn't follow the migration steps of making a current backup before moving away from the ISY994.

@JerryR This is mentioned in the "fixes" for 5.8.4.

@awzulich glad Support got you back into admin console at least! Did you happen to include anything about this issue on your support ticket or just trying to get you back into admin console? 15+ year old PLM - that's amazing! I know many have had some fail in just a few years. Mine (knocking on wood) is about 7 or 8 years old (if memory serves). With a WHITE light on it? I'm not sure they ever had one with white led on the side of the PLM. Others (that had older PLMs) might be able to answer if old devices had a white light rather than green. Are you able to control any devices from the admin console or are all your devices with a red exclamation point suggesting they cannot communicate with IoX? That would usually indicate PLM failure or on a bad circuit. Is the PLM plugged into the same outlet you used for the ISY994? Have you performed a full power cycle? Shutdown the eisy (press and hold the power button until it turns red - or press it 6 times and it should turn red after 30-60 seconds - multi-function button info on wiki) Unplug the PLM from the wall Wait a while (sometimes 2-3 minutes) Plugin PLM - allow light to settle (become solid) - should be green (at least "recent" PLMs) (maybe 60 seconds?) Power up eisy wait ~2-3 minutes for it to boot completely Open admin console Do you get any errors about communicating to devices? Take a screenshot of any errors you get on logging in if you can. Try controlling a device (just by turning it on/off). If it work then your PLM is communicating with that device. If your programs still have the statements from your first post it might be a corrupt migration. At this point I might open another support ticket to see if there is something they see in the progress of the migration that could have corrupted your IoX system. https://www.universal-devices.com/my-tickets By chance - before you left the ISY994 did you make a copy of the programs? I usually suggest people make a digital copy of all their programs in case something like this happens. This way at least you have a representation of the programs and you can rewrite them fairly easily. Right click on the root program folder and select "copy folder to clipboard" then paste in a text document. It's probably too late now because if you power up your ISY994 without the PLM it will have a lot of errors and the programs might wipe out and not be of much use. At the very least I would copy from the eisy now to at least have times and schedules even if the programs aren't fully loaded. They'll show the missing nodes (or just say something about the node missing), but times and if's, then's, else text should be available to somewhat help if you have to start completely over. Good luck! Maybe @Techman might have some other tips to try. Either way, if you get support to help you please post back if/when this is resolved to know what was done so it might help others down the road.

How "ancient"? (roughly) How is it connected to the eisy? (depends on your answers to @Techman's questions above.) It's quite possible it is just old enough to have gone bad in the transfer, but not very likely to be the case. Perhaps the cable is not seated properly. I know when the eisy first came out UD had a 2 part cable for the Serial USB. Now it appears to be just one cable. Hopefully that limits connection issues. But be sure that the PLM is connected to a USB port and not the network port of the eisy. Since the "old" serial PLM used what appeared to be a network cable to connect to the ISY994 when you changed to the eisy you have to connect using only USB.

I did use with Alexa for a vibration alert device (attached to our dryer that the end of cycle buzzer has gone out on). The process uses automations within the YoLink app. They are fairly simple based and are easy to setup, but leave a lot of customization out of the process that many take for granted with IoX/Polyglot. While the alerts usually worked, it did seem to have similar issues that many have reported here with links to the Echo system. I experienced a few days where the alerts didn't work. I since started using the YoLink plugin, programs, variables, and notifications to get alerts more reliably. The good thing is you can use both Alexa/Echo connection and the YoLink Plugin to keep the IoX/PG3x system to deliver alerts just as well. You don't have to only pick/rely on one. Note if you get the Speaker hub it doesn't have an ethernet connection so only uses wifi (2.4GHz band only) to connect to the network. When I got my system I got the 1st hub so I could hardwire it into my network. I know 2.4GHz has "long" range, but it also has the most trouble in some mesh/long-range wifi systems where 2.4GHz and 5.0GHz SSID cannot be split (or aren't split). Making troubleshooting connection issues for a system like this more trouble than I want(ed) to deal with. I think the 3rd gen hub has an ethernet port, but doesn't appear to have a speaker. My points for this is that you could get the speaker hub and not have to rely on Alexa for voice alerts, but it's drawback (for me) was wifi only. The other hubs don't offer the speaker so you then rely on the links from hub to other (3rd party) systems for voice alerts (which may not always be reliable and difficult to troubleshoot).

Might be time to open a support ticket to see if other settings need to be adjusted in admin console or underlying system setup. https://www.universal-devices.com/my-tickets Please post back what ends up resolving this in case others have this issue down the road. Glad the PG3x part fixed the UUID issue though!

@mdecou do you have any idea what version PG3x you're running? Not sure if the Zooz stick has anything to do with it, but sometime recently an issue was commented on that no UUID could be resolved by being sure you migrated to PG3x (the Polisy did not come with that version so you must run the process outlined in the Wiki - https://wiki.universal-devices.com/Polisy:User_Guide#Upgrading_to_PG3x). Make sure you pay attention to the note that the user/pass will change for PG3x to match the IoX Admin Console login.

@awzulich as @Techman asks about the Firmware and UI versions this appears an issue when they don't match. Also, make sure that the PLM is connected and that Insteon Support is checked on the Admin Console "Configuration" tab. Reference in wiki: https://wiki.universal-devices.com/Eisy:User_Guide#INSTEON_Support (Note: Screenshot is outdated, but the box is still there.) Once you confirm you Firmware and UI match and the PLM is connected and Insteon support checked you might need to restore the backup again to fix the program issues.

Yes. Exactly. If you want/need to have the ISY at the same IP the current recommended/suggested method is via DHCP Address Reservation at the router level. Since you seem to be running multiple network devices/systems you need to figure out which device to set that reservation on. As you experienced the additional network devices were blocking the ability for the ISY994 to connect externally.