dbwarner5

@ShawnWJavi did a great job of pointing out the pros and cons. However, since the biggest con of an ISY based security is its overall lack of true security protocols, I wouldn't hesitate to use one of your 6 button keypads, where the letter D, becomes Disarm. I use an elk system, and yes I have keypads by the proper doors, but I also have 3 keypads where I can press the D to disarm the alarm. I would highly doubt anyone who breaks into your house would know that those buttons will do what they will do. My view is that I am trying to accomplish the following: -Ease of disarm for visitors and wife -Protect through sirens/ etc the average burglar and inform me of any intrusion -NOT protect me against a professional burglar who really thinks I have something of value other than household goods. The programs that I have follow the protocols below: -Who unlocks the door via zwave lock--> category 1: me and wife, cat 2, long term visitor (kids), cat 3, short term visitors like a cat sitter or plant waterer, or good friend dropping something off etc. -Based on the above category of user the following happens: Cat 1: Disarm, turn on lights if dark, turn on water pump, unlock several doors, turn on heat, etc. Cat 2: similar to cat 1 but more general lighting. Cat 3: lots of lights, inside and out, water pump on, disarm, then watch for the door to be locked again via the touchpad and then re-arm the system, turn off water pump, eventually turn off the lights, leave heat alone. I init the security status type (home away, home cat, etc) so I know how to set it back when needed. Lastly, if the security is set at Home, and I need to get up and let the cat in at 2am (ugh!), I simply press the D on my keypad near my bed, and the security goes off, and then if I press the D again within 15 minutes, the security re-arms. Security gets armed at night through an Alex command of Goodnight, with runs ISY programs that controls lights for getting ready for bed adn then 10-15 minutes later sets up nightlights around the house and monitors all lights to reset them back to nightlight setting after 20 minutes if someone gets up and leaves a light on, thermostat adjustments, outside lights adjust etc. When we leave for vacation etc, I use UD Mobile where I have a program for each state I want the elk to go into on my favorites page. Hope this gives you some ideas!

lol.. I am not sure.. it always seems like the initial is 4 +1.. in this instance when I clicked on upgrade packages, I got one beep... long pause (30-60 seconds ) two (or three) more beeps that were slow... then after another few minutes I got the 4 (+1) beeps. that is when I unplugged it and rebooted it.. During the reboot, fairly soon into it, I got another 4 beeps.

@macjeffJust finished the upgrade. My z-wave devices took a while to populate and then still a few would not populate all fields: locks and thermostat. I restarted the AC and now they are all working as expected. One oddity was that after the four beeps, I unplugged the Polisy, and replugged it in. Shortly after I got four more beeps. But everything including NS all started up and are reporting correctly.

May have spoke too soon. Since that last post, the IoX has rebooted 3 times. All three times I have been experimenting with the File / Themes / Theme size option. Each time I change it, it asks me to quit the AC. Per earlier posts, I was careful to only quit the AC via the File / Exit command versus Command Q (on Mac). However upon restarting the AC, all nodes were empty, as the IoX was going through a start up process. After 10 minutes, all is running again. Strange. Not sure what triggered the reboots; The quitting of the AC or the change of the theme size. Cheers.

My upgrade from 5.5.5 to 5.5.6 experience on IoX Polisy -Loaded AC and clicked on upgrade packages. Polisy acted as expected.. beeps, etc, unplugged and restarted it. -Loaded AC and found none of my PG3 nodes were connecting. Also I could not locally connect to PG3. It was unresponsive. Pg2 however was working just fine. -Unplugged Polisy, let it reboot. Still no PG3 -Loaded AC again and hit upgrade packages a SECOND TIME. Never heard any beeps etc, however after a delay PG3 was working again. Ecobee NS had to be manually restarted. ST inventory would not connect to AC. Reloaded AC, after a delay, everything is working just as expected. Now on 5.5.6 and all NS running.

Two cents on this: 1) for IoX Launcher, after you have added all the routes you may want (http://xxx.xxx.xx.xx:8080, https://my.isy.io/isy/xxxxxxx, and https://xxx.xxx.xx.xx:8443), then save it to an easy location.. Any time they dont come up, just hit load and choose the file you saved, 2) Avoid all of the above by going to http://xxx.xxx.xx.xx:8080/admin.jnlp in your browser and a file will download that will immediately take you to your isy w/o having to rely on anything els. (all xx's are your local ip address for your IoX.)

Only issue noticed is a mismatch of ISY firmware between IoX and PG3, on Polisy. Doesn't seem to be affecting anything though. Have restarted PG3. No change.

try typing this into your browser, replacing the x's with your isy address. it should download a local JAVA file that should access it. Be sure to clean out your JAVA cache first. http://x.x.x.x:8080/admin.jnlp

Upgraded on Polisy in about 5 minutes. Only issue was that none of my Zwave devices reported to the AC. A restart of the AC, and they all came back.

One thing I do for any variable that has a longer "shelf life" of any real time, where a power outage could occur, in the THEN or ELSE, where you change the variable, also Init it to itself immediately in the next line. These options are in the AC under the arrow. Example for VAR1 IF xxx THEN Var1 =14 Var1 Init to Var1 This will set the Start up value to 14 for the variable that you want to preserve/

Check them for errors. Go to Summary Tab in Programs and click on the status column, then all of the out of memory programs will be together. You can then click each one and select edit and look at them. Sometimes if a device or scene or variable was originally in the program and it gets deleted or somehow unassociated, you will see that message. Open the program and you should see an error message within the lines. If not sometimes just hit Update to any line after clicking on it and to cause the program to need to be resaved, and then do a save. This also may restore the program for you. Doubtful it is truly out of memory. A good habit to do is to Right click on the top programs folder and go to the bottom where it says "copy folder to clipboard" adn then go to a text editor and past. This way you can always open up a copy of the programs next to the AC and see if something got changed etc.

I bought one, new from amazon in sept 2019 for $63! use it at a second home. cant believe they are over 300 now

Samsung smarthings hub on amazon $315 https://www.amazon.com/Samsung-SmartThings-Generation-GP-U999SJVLGDA-Automation/dp/B07FJGGWJL Abut the same as a the newest offering from UDI.

Found what appears a CAI network device was bombarding the IoX and not allowing it to run properly. Working on verifying this is the cause.

Just rebooted. Still have starting subscriptions on AC, Web portal allows access but error logs are not that helpful from there. Expect it to crash again soon. Will open a ticket in the morning.

Interesting that as I unplug it, to reboot it, it is quite warm.

~shut down again on me since my last post.. no automations are running, however a pushover notification came through. AC cant find ISY, UDMobile stuck on starting subscriptions, and this time, the Portal says ISY is not online. Here is my error log from earlier. It was working sometime before 11am, and when I got home at 230 it was no longer working. I will reboot it and get access to the error log again. thanks. will probably open ticket tomorrow if nothing obvious pops out to anyone here. ISY Error Log.v5.5.3__Tue 2023.01.17 02.57.33 PM.txt

Had this problem before. Been doing regular updates. Am on 5.5.3. Came home today to find IoX not working. Could not access it, but through terminal it was running. Tried to restart through terminal. Nothing. Power cycled. All came up as expected. Was working on a different issue where many of my devices are showing in the Event Viewer "Link for responder xx xx xx x not found, where I was systematically going through each device and restoring them when the AC lost its connection. Upon restarting the AC, I get stuck on "starting subscriptions". UD Mobile is did the same. The Portal Web Access still allowed me to control lights. Tried to restart AC and this time, IoX cant be found. Will need to power cycle the Polisy again. Any help / ideas? Thanks.

Reinforcing what @Goose66 said above. I recently added MyQ and due to the long polling periods, I found I could not use the "state" of the door as a trigger in a program w/o strange / unwanted results. I am sure one could program around it with delays and multiple disabled programs etc, but luckily I have wired sensors to my elk for state of the door. Otherwise, the open / close commands work well. I used to use an elk output to "short across" an extra garage door transmitter that I soldered wires to. But it wasn't 100% reliable for some reason: ISY to Elk NS to output to transmitter to garage door opener.... So I have now switched my programming so that if the MyQ NS is online, then use it, otherwise, use the Elk output as I havent physically uninstalled it. This way if the Internet is down or the NS goes down, I have a "local" solution that will work. Generally I wold recommend the MyQ NS though. Havent had any issues with it.

@Jimbo.Automates Hi Jim, I have restarted a few times, also stopped, and started a few times, upgrade isnt happening. Am nervous to do a uninstall, reinstall same slot as the Elk is by far the most integrated and used NS throughout my programs. Thoughts? thanks.

Interesting because I started this thread, but it is working for me now on5.5.2. I dont remember what I did to get it going again.

@brians see this post. I was able to somehow "trick" UD mobile into being a toggle switch. Read down a few posts to my final solution that is working perfectly

Read through the below post, now closed. One quick question, if the NS cant control the size of the output, can it control the number or width of the columns? there is plenty of room to make this NS show as 4 or maybe even 5 columns, which would then allow all the data to be shown before it runs off the bottom. An obvious question which you have probably thought through, but I didnt see it covered in the post, so thought I would ask. Thanks! sorry to hear people are having trouble with Eisy NS like this one.

I only have 3 battery devices, all locks and they went fine. But I understand others are having difficulty with other battery devices and UDI is working on it.

With all the multitude of posts / threads and variations of conversions going on, I thought I would try to capture my experience in the above conversion. I am by no means an expert, and your conversion needs may be very different than mine, but having drawn on so many other people’s experience on the forums and having a very successful conversion, I thought I would share my steps and learnings. Here is what is did and what I learned: Backup up key items: IoX Backup Programs folder, copy to clipboard and paste into text editor A screenshot of all my zwave devices by going to MyLighting and sorting by type and then finding all Z related nodes Resources export Screen shot of IP addresses from Config menu 2) In AC, clicked on upgrade packages Nothing happened. Light on Polisy stayed steady. 3) Followed this post by Michel K to SSH into Polisy and performed STEP 2 only. sudo pkg install -r udi pkg sudo /usr/local/etc/udx.d/static/udxops.sh upgrade.polisy 4) Lots of activity after the above, but upon the recommendation of @Geddy, I ran the above commands TWICE. There was further activity the second time. So something got cleaned up. 5) Opened the AC it showed BUSY for about 30 minutes. But then stopped and all was working on 5.5.2 with the exception of my node servers on PG3. Had to open PG3 and manually restart them all. Am still using the Zoos dongle at this point. 6) Once I determined things were operating as expected, I re-performed my backups to have this next increment before I migrated the Z-wave. 7) Within the AC, I now clicked on the Migrate z-wave button and followed the directions that popped up EXACTLY. Read closely. The only exception is that I had previously installed the zmatter board, so I skipped that step. Once the Polisy was showing a steady light and several beeps occurred, and after I cleared my Java cache, I re-opened the AC and found that my password wasn’t working as it took THREE attempts for it to open (w/o typos) and nothing was there. Thought it was Bricked. However learned from @jjc60631 that this process somehow reset my username / password back to admin / admin. With admin / admin, I was back in, however the BUSY started and kept repeating. This went on for a very long time, so I then within the AC, I clicked on Restart IoX under the Config menu. 9) After several beeps and 10-15 minutes I signed back in under admin / admin and was rewarded with a much shorter busy of about 10 minutes and everything was there, except for node servers, because the username / password of IoX did not match PG3s info. Changed my username / password back to original and with 5 minutes all my NSs restored. 10) All of my z-wave devices had been converted along with lots of new / additional sub nodes that were all scattered everywhere. To better understand everything, I then went to every zwave node and right clicked / Group devices. This organized back to a way I could understand them. 11) Upon inspection about ½ of my zwave devices were labeled as “Placeholder” in the center of the top main screen when selected. (See below after updating) 12) Went to each Node that had placeholder and right clicked and selected Zwave/synchronize / Update with interview. This fixed them all. Am aware there are problems with certain zwave devices, but I must not have any of those as I have no problems at all. Communication with them all is greatly improved. 13) Some additional learnings / cleanup: All Zwave scenes and programs for zwave devices stayed intact! VERY PLEASANTLY SURPRISED!! However, Amazon links that had zwave devices all have to be redone in the Portal, deleted from Alexa app, rediscovered and then any routines in Alexa redone...... (PIA) UD mobile zwave links all break. I "synchronized" the app, but then all my favorites where I had customized displays, colors and words, all disappeared and need to be recreated. .. (PIA) Programs with locks all needed fixing as the new Zwave device nodes changed considerably requiring different IF's and THEN choices to affect the original program. All programs with z-wave devices should be checked. Resources with references to Zwave devices also need updating to address the new node definition.