Geddy

@jkraus There have been limited debates in the past with which is better. It comes down to personal preference and personal ability to support which route you take. z-wave = talk to each other for local relay kaza = wifi connections Basically, any wifi connected devices can ultimately overpower your home router. Many consumer grade routers aren't designed to handle ip routing for a large number of devices. Sure, they can operate well at 10-20 devices, but some people are pushing 50+ or 100+ devices and if all that went to an underpowered router it will ultimately cause more issues. It also puts you back into a "cloud based" system. z-wave (as I understand it...I don't personally use any) is independent and communicates directly with the controller and then each powered device acts as a signal relay. So as long as you build out your network your coverage should be acceptable. If you don't have many devices and you have only limited devices at far ends of your house then you will need repeaters to build a stronger z-wave mesh communication network. Z-wave is local based and, thus, would operate without internet dependency. no, don't have any experience with that.

I case you're not aware there was a huge change in the IoT market recently when Insteon turned off their cloud servers. Many users scrambled to look for other options. Some rushed to buy the Polisy that were available. I'm sure it's just a run on stock and as soon as UD can get some more devices assembled they will be made available through the UD store. You could contact them directly via email at: sales@universal-devices.com What kind of system have you been running? The ISY994 and Polisy both require a PLM (an Insteon device). Those are very difficult to get at the moment, so if you don't already have one you will want to subscribe to the UD Product News & Announcements email list by making an account and selecting that email newsletter.

@jkraus It will certainly be a learning curve, but that's where the forums are here to help. Also consider UD Wiki, specifically the Polisy User Guide to help with some questions you might have along the way... https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide And would be a good idea to review some of the information found in this thread (by @dbwarner5) for migrating efforts...

@kyderr I'd say that you're trying to get notified about an issue rather than fixing the issue. If the ISY is going "offline" then it is probably a network issue that you're having. Otherwise, ISY isn't known to just go into an "offline" state. I would suggest opening a support ticket to see if there is something in the logs as if there are indeed errors with the ISY causing problems. Otherwise, it's a network related issue and should be troubleshot with the router manufacturer or your ISP. What model device are you using, and what is your Firmware and User Interface (in Admin Console menu Help -> About). Create a ticket with support one of these ways: Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

If it's in a folder with conditions like that even running then "THEN" won't do anything. The whole folder is being limited by the folder conditions. Typically the root (My Programs) folder should NOT have any "Folder Conditions". Click on the time and you should have a option/button to remove and then "save changes" Note - none of the programs in "My Programs" probably work correctly because of the folder conditions. Will you confirm if they are working? (What happens if you right click and "Run Then" on those programs while the folder conditions are on the root folder?) Do you have folder conditions set for your irrigation folder? If you do you shouldn't have any conditions on the root folder so all programs will run when triggered. Also as info - you can copy/paste programs from admin console to the forums easily by right clicking on the program and selecting "Copy to Clipboard" (last option on pop up menu). Then pate the text into the forum message. That way you don't have to take screen shots or pictures of the monitor and try to paste into your posts. Same can be done for the event viewer...click the clipboard button and it will copy the text and can then be pasted into the message (and thus be searchable in the future).

@kyderr If/when you get support from UD and they get you sorted out please post back what resolved this issue to possibly help others that might have this problem down the road.

@Wes Westhaver make sure if they get you sorted out that you post back here what helped in case this issue comes up again. I too am not familiar with those errors.

@macjeff just checked...seems to be PG3 option now indeed - https://github.com/UniversalDevicesInc-PG3/holidays-google-poly/blob/master/README.md

@macjeff Not sure of holiday ones on PG3 (not currently able to access that store), but know there's one that worked on PG2 - https://github.com/firstone/holidays-google-poly I know @asbril uses it quite a bit.

@oper8 since we couldn't help you here you should open a support ticket with Universal Devices and ask them directly if this is an ISY issue, a Z-wave issue, or product developer issue. They would know best. I think the replies here have all pointed to the product and manufacturer of such product not sending the full information to the ISY. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com Either way...report back with what you find out! Would be good to get a real resolution to the question to possibly help others that might have the similar issue.

@asbril glad the reboot worked. But sounds like it might be a network related issue rather than just a power cycle issue. Does your son know if his router (auto) upgraded firmware in the recent days? Even though the ISY was sending out notifications it might have had good outbound traffic, but not inbound traffic somehow and the reboot put it back on the network right. Like @lilyoyo1 I've not had to reboot the ISY just because the portal subscription renewed (as you seemed to imply being the only difference). My guess it was more a network related issue that might pop up again. I've seen this kind of issue with Netgear routers and firmware upgrades over the last 12 months. It's really played havoc with wireless printers and desktops/laptops not seeing the local printer as being online. But glad it's working as expected again, and was a simple fix.

Step 1 - Make sure your Firmware and User Interface are the same version. In Admin Console menu "Help" -> About If on 5.3.4 should be similar to this: Step 2 - This could be a java memory issue. Try setting the java memory this way: (512 or 1024 can be used depending on your computer's available memory. If you have lots of ram perhaps use 1024.) Info: Use -Xmx to specify the maximum heap size. Use -Xms to specify the initial Java heap size. Let us know if you have success after any UI or Java adjustment.

Can this model set the desired temp to a #.5° C? All the display examples I see online show this as whole degrees only. Perhaps those are only °F temps. I suspect this is a z-wave limit from GoControl that isn't passing the .5°C information back to the node to be read by the ISY. Sorry...I don't use z-wave or other thermostat, but this appears to be that most don't set to partial degree temp, but rather whole degree. Indeed, probably a (outside of the) US problem since 0.5° C can be about 1°F difference that could be an issue. But I think it's a thermostat manufacturer issue not feeding the 10th of degree to the node that the ISY would pickup. Maybe @Chris Jahn would have more insight as he seems to be the z-wave guru for UD.

@KHouse - by chance what version of Alexa skill are you running? On your Alexa app (on your phone/tablet) go to Skills -> My Skills and look for the Universal Devices skill. It should be the v3 looking like this: It's possible you haven't updated to the v3 even though it's been out quite a while. Perhaps you still had v2 and it might not work well with ongoing updates for Alexa. Just wanted to check. It's not happening often, but there are times where Alexa services are flaky or down. This is just a function of cloud dependency. Usually lengthy outtages will make the "news" or be talked about in lots of places on social media. Other times they're just local blips depending on the server your Alexa us using. The next step is to make sure that your "spoken" are unique and easy to speak and understand. Sometimes Alexa doesn't correctly hear long commands, and sometimes short spokens can sound too much like other devices. However, you mentioned something in the first post that concerns me... This might be signs of sudden communication issues with either failing PLM or line noise from other electrical changes in the house. Often times people will simply say "I haven't added anything new", but there have been a lot of recent reports of OLD power supplies suddenly adding noise in the electrical service. In the Admin Console under the programs tab make sure you look at summary and check when the program(s) last ran and when they're supposed to run again. To test them perhaps run the "then" portion of the program and make sure the status of last run time changed. And see if the program did what you expected it to do. Would you log into the ISY admin console and open the event viewer and set it to level 3. Now, control lights/devices within the admin console and make sure they act as expected and no extra errors are showing up in the event viewer. Then try controlling the SAME devices with Alexa. The results should be identical. If you're getting errors or different hops this could indicate noise. @MrBill has posted how to check/find noise in a recent post that should be checked out. Ultimately the steps I would take are: 1 - Making sure you have the ISY v3 skill enabled with Alexa. Do as @MrBill suggests - remove existing devices from alexa.amazon.com (https://alexa.amazon.com/spa/index.html#appliances) and go through the "Alexa, discover devices" process again. 2 - On ISY Portal make sure spoken and/or device names are unique and easy to speak and understand 3 - Check event viewer on Admin Console for differences in hops to/from devices when controlled in admin console and with Alexa 4 - Check for noise if there are differences in the event viewer A "simple" power cycle of the ISY doesn't always mean it's going to be better. If you have ongoing issues then it's usually going to be more serious and requires more troubleshooting steps. Let us know after you've done this to see if some here can help. Otherwise, it might be best to get a support ticket going and see if Universal Devices can get you back on track. Good luck!

@bigdog Glad you're up and running on 5.3.4! Great tip to use Windows if possible. I know it's been hit and miss on MAC systems using the ISY Launcher process. You're lucky to be able to use a Win install to get things going for you. Good luck going forward! If you run into any new issues be sure to post (hopefully new threads to get specific support for any issues you run into).

@webminster Will you confirm UI/FW match? (UI = User Interface, FW = Firmware) Since you say you recently upgraded please check the Firmware and User Interface versions match. If they don't this can sometimes cause similar errors. In Admin Console menu -> Help -> About It should match and look similar to this: (if you're using a PLM) If these versions don't match make sure you clear your Java cache (checking all 3 boxes in the process) and then download a new file of the ISY Launcher found at https://isy.universal-devices.com/start.jnlp. (Make sure you're downloading a NEW file and not using an old version of admin.jnlp or even start.jnlp that you might have downloaded in the past. Steps for installing admin console on the desktop can be found in the wiki - https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop The "new" (since 2018) launcher method is the best use method to make sure that UI/FW always match.

@StangManD there was another thread about VLAN settings recently. Sadly that user never posted the resolution so I am not sure how they got it resolved. The best bet is to open a support ticket with Universal Devices and they should be able to help directly and get you running. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com If you're able to get this resolved with UD Support please post back here to possibly help others that might have this issue down the road. Welcome to the forums.

@DClausen Also, there are directions on the Wiki - https://wiki.universal-devices.com/index.php?title=ISY_Portal_Installation_Instructions

@FloridaGary Technically I'd say it's not super critical to factory reset, but it is suggested as common practice. Especially when migrating from an existing system with a different controller. There have been debates about this process, but typically the cleanest method is to try to factory reset if you can. This is simply to clear out any old device specific dependency that might have been "written" to the device memory (i.e. local scene or local 3-way function). There is a step when adding devices to the ISY platform to remove existing links. That might be enough for the hard/impossible to reach devices, but for "easy" to access devices the factory reset is a simple and fool-proof way to be sure you clear out any previous programming specifically applied to the device. Thanks for posting that link above for factory reset references. I've printed to PDF to have for the future (if needed) in case the Insteon site goes boom soon. PS: To tag users you did it right to start with the @, but then as you type the name a list will appear. You have to select the name you want to tag for it to take and the person should get a notification about the mention. When you get the list you can down arrow and enter on the name or click with mouse/curser. You know it's tagged when the blue bubble surrounds the user name. Good luck with the "great migration"! Welcome to the UD Forums.

After you've double checked you have the correct file for your system make sure three things: 1) Do not unzip the file - the upgrade process uses the .zip file 2) Perhaps set the Java memory to a higher level (512 or 1024) 3) It could be a corrupt MicroSD card. Before replacing the SD card though I might suggest opening a ticket with UD Support (https://www.universal-devices.com/my-tickets/) just to try before going the whole card replacement or card formatting route.

UD Mobile is for ISY 5.0.16 and above. (Currently for ISY994 devices without z-wave I would suggest 5.3.4) Learn more about UD Mobile in the UD Wiki. I have about as many devices as you do, but they're all 2015 and newer (roughly). Thankfully I haven't had the same fail rate that you're experiencing so perhaps your units are much older or you have power supply issues. Either way, you might want to see if you've got a home electrical problem rather than an Insteon problem just to be sure something isn't frying those devices. You wouldn't want to switch to a different type of device and still have the same fail rate. Since you're only Insteon (and few x10) then I'd say your upgrade to 5.3.4 should be mostly smooth. The only major issue going from 4.9 to 5.3.4 is if you have programs that use adjust scene. This is because of the change of how scenes are handled in 5.x. The key (tip/trick) is to copy all programs to a text editor so you can refer back them after the upgrade and adjust accordingly. Never expect to adjust (or recreate) programs from memory. In the program tab of the admin console right click the root "My Programs" folder (of if you changed the name whatever the root folder is). Then select Copy Folder to Clipboard (note...last option in screenshot below). Now, paste that to a text editor (in Windows I suggest Notepad - just something that will NOT auto format any text). Make sure you do not stop at the option to "export to clipboard". That will give you an xml file and be more difficult to read. The text pasted from the "Copy Folder to Clipboard" option is clean and clear to follow for reference. What you will get in Notepad will start like this: (very easy to read programs this way) =================================================================================== My Programs - [ID 0001][Parent 0000] Folder Conditions for 'My Programs' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Allow the programs in this folder to run. Another note to keep up with...make note of any disabled programs you might have. When I upgrade from 4.9 to 5.3.x all my disabled programs became enabled and I had to turn them off again. Some around here will mark disabled programs by name or put them in a folder called disabled. Disabled programs will show up in your text file with [Not Enabled] clearly shown. Now is also a good time to go through and possibly rename programs so that ones that run processes in the same room or rely on other programs might be close together in the name list for ease of reference. It's been almost a year since I upgraded, but still remember that it took me less than an hour to make the upgrade and confirm/adjust programs. Then, over the following weekend if I noticed programs not doing what I expected just spent a little time fixing those up. There weren't many, but there were a few minor tweaks to make. Once up and running with 5.3.4 then you can begin using UD Mobile. It's really becoming a great addition to the ISY world and becoming quite powerful with options. Final tip - BACKUP! BACKUP! BACKUP! Make sure you backup your current setup before you attempt the upgrade. Since it's a manual upgrade that's a step in the process, but it's good to run one before attempting the manual upgrade too. Then, when you get to step 7 in the process just do the first part: This will download/add the ISY Launcher process for accessing Admin Console. (If you're on Windows this is a simple process...on Mac it's a mixed bag) Run the "start.jnlp" once and it will install the ISY Launcher icon to your desktop. Now, always use this to access the admin console. This will usually open the "ISY Finder" window and should automatically list the local ISY (as long as it is found on the local network). If after you go through the upgrade process and have issues jump back here and let us know what issues you're having and somebody might be able to help. Otherwise, open a support ticket with Universal Devices (https://www.universal-devices.com/my-tickets/) for individual support for your issue. Good luck!

@Prana electric welcome to the forums and the world of Polisy! Some "light reading" and to get you started would be to review the Universal Devices Wiki about the ISY and Polisy abilities. Then, I would suggest downloading and having handy the ISY Cookbook. Finally, bookmark UD Support ticket location. If you've come here and gotten some help from the forums, but still stuck then UD Support is top notch and can help specific problems. But the general user-to-user support found on these forums is always a great starting spot. Wiki - https://wiki.universal-devices.com/ Cookbook - https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Cookbook UD Support (tickets) - https://www.universal-devices.com/my-tickets/ There are some videos (some a little aged, but still somewhat relevant in process with minor changes) found in the Wiki. Just know that some processes have changed slightly, but you'll get the idea of what you will want to look for. One thing I remember when starting out was that it's difficult to read/watch if you're not doing. So it might sound like a lot if you just read/watch now. Once you've got the Polisy up and running it should be simple to learn and maintain. Just note that a few things of the Polisy are still very much in development so there could be a few wrinkles along the way. Key points to note: Factory reset devices before adding to ISY - Many will suggest, since you're going to be moving from the hub to the Polisy, the best way to setup the system within the Polisy and ISY on Polisy (IoP) will be to factory reset all Insteon devices before adding them to the Polisy. This will be sure to clear any current links or scenes currently written to the devices don't live in the device memory when the IoP is trying to control them. The factory reset processes can be found in the device manual. Firmware and User Interface must match versions - Once you are up and running with IoP is using the admin console check out the Menu -> Help -> about and make sure that firmware and user interface always match. That is step # 1 on any troubleshooting issue you might have once using ISY (IoP) and if devices aren't behaving the way you expect them to. FW/UI matching is always very important. Next will be to ask if all previous links/scenes were removed from the device when added to the ISY. Again, welcome and feel free to ask for help if you get stuck along the way in setting things up!

@Ed Bean First off...what Firmware are you trying to upgrade to? Do you have a Z-Wave controller in the ISY? It doesn't appear that you do based on the about screen you gave. 4.9.0 is the last version in the 4.x branch. You do not have the "automatic update" option beyond that version. You will need to upgrade to the 5.x branch. Currently the ISY994i most recent version is 5.3.4 (found here to get upgrade steps). Please note...there is possibly a LOT of user interaction needed to upgrade to the 5.x branch. Please read the post linked and the steps needed to upgrade. READ THEM FIRST! Don't read and proceed at the same time. Make sure you know what your steps are as they are important to follow ALL the steps. Most important step is to copy current programs to a text document for review once you're updated so you know they are working correctly once you're upgraded. You're a mac user so there are some differences with how that works compared to windows PCs, but overall it should be simple and straight forward. Make sure that you do NOT unzip the file you download for the firmware. It must stay in the compressed folder/file format that is downloaded. This is something mac users sometimes have issues with as the OS handles compressed files differently. Also, once you get to step 7 make sure you follow those directions. 7. Launch the 5.3.0 Admin Console and/or Dashboard by going to the following link: - https://isy.universal-devices.com/start.jnlp This will be the launcher (mentioned here). That should get you back into admin console. Again, MAC sometimes does, and sometimes doesn't work right. Since I don't use mac I don't know why/how some users can run this without issues and others have lots of problems. If you read the directions of how to upgrade to 5.x and still have problems then I would suggest you open a support ticket and request help with the upgrade. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com Final comment...if you've got a Windows PC available I would suggest running the upgrade from there. Seems to be less issues than those running Mac (just personal preference/experience from reading so many posts around here).

@xgfreon seems like it was a noise issue. First steps would have been to read the wiki for noise troubleshooting. Then there have been a lot of posts over the years of how to really dig deep and find just what's causing the noise. But, as you're probably aware chasing noise can be difficult and time consuming. I know @MrBill has posted a very detailed process for tracking down issue like this (I can't find it currently, but you seem to have resolved the issue so wouldn't help now). It might have saved you a lot of issues. At least you've got 3 PLMs, and hopefully they all work well! It's possible the brownout impacted the module you removed. It's also possible that other devices could have been impacted that can lead to issues down the road.

@xgfreon also, there had been a recent discussion about fanlink and keypad button scene setup. @Javi wrote an updated wiki page for it for the ISY994 v5 firmware design. There’s still a few different methods to achieve similar things, but that might get you going a slightly different route. I think @MrBill has you handled with your later question.