ShawnW

I'm afraid science (& economics) disagree with you. Without getting into an ill-placed debate, I think most would simply prefer the extra hour of sunlight to be after work in the evening, not in the morning while we're sleeping or working. Also, traffic patterns prove that twice as many lives would be saved in the evening drive than the morning drive, and people spend more time shopping (spending money) in the evening, more energy is saved with light in the evening than morning,... Almost every benefit is given by the evening sun, and society largely agrees.

What the HECK is a stream deck????? @TRI0N

Oh @larryllix - I send our buddy Ford an email about it every month! It must be killed. Please everyone! Write your politician and them to stop the annual changes!!!

Hi @johnnyt - @larryllix has gone back from Polisy to 994. In my opinion - with the number of Z-Wave you have and the massive number of Programs you have, I couldn't even imagine trying to go backwards with that!!! One thing I might do in your situation though, make a list of part numbers of Z-Wave devices you have and then do some searches for those part numbers in the forums to see if anyone has had problems with them in eisy or migration specifically. It seems to be where most of the recent pain comes from and much less so the operating system. I too have given up the idea of a 'dry run' - it would most likely cause way more pain than it's worth, and could literally hamper your actual migration when you do it. Good luck - let us know how it goes! Shawn

Kinda interesting for you all maybe - I never do the java cache clear thing - after update I simply use the Cloud version of the Admin Console for one day, and on Day 2 the IoX FInder has updated itself to the proper matching version. Not sure how/why exactly but I don't complain! Anyone else's behave like this? You should try it to see if you get the same @brians . Shawn

So true. When you go from a typical deadbolt to any kind of smart lock, you need to first take the quality of your door's positioning up a huge notch. This applies even for situations of standing outside the door and hitting the 'lock' button, because if it fails to hit the hole it will often give up trying before you have a chance to adjust physical pressure on the door!! I've been using smart locks (ONLY for having a keypad and keyfob options) for a good ten years now and with every one I've always had to take a grinder to the deadbolt bolt to add a substantial chamber/angle to it to add some forgiveness (narrowing the width at the start by at least 25%). As @Geddyeluded to, programming deadbolts to lock remotely and rely on it is asking for frequent failure. Something the industry has massively failed on is giving proper feedback of locking attempts - I personally just want to KNOW if the lock is indeed 'LOCKED' and many brands give you only electronic feedback of whether it "sent" a lock request/attempt to the lock - rarely ever any positive signal of accomplishment ie true deadbolt position. If anyone out there knows of a decent IoX-compatible deadbolt that truly reports correct deadbolt status PLEASE let us all know. Until then, I keep dreaming of ways to get contacts or sensing placed inside the doorframe to 'look' for the physical deadbolt (hint, there's no good options for this either). THANKS!!

Water Valve Add-On Eco Net Controls EBV-105 Plug-In Switch Leviton DZPA1-2BW Temp Sensor Sensative Strips Comfort Outdoor Plug-In Switch EvaLogik ZW97 Open/Close Sensor EcoLink DWZWAVE2.5-ECO Chime Siren EcoLink ISZW7-ECO Future-Deadbolt Lock Yale YRD216-ZW2-619 Hi guys. I feel like it might be time to migrate to my Polisy/ZMatter from my 994 but want to ask if this short list of Z-Wave items currently work? – work well? Work barely? Problematic? Or not at all? I own all these items and all but one of them are deployed on my 994. Some of them I’d call critical – well mostly just the Ecolink Open/Close sensors, because I’d hate to physically replace them all!! The other ones would suck to replace mostly because of the money waste. Pretty much all these items are involved in many programs and would certainly break functions if they didn’t work or migrate so there’d be a bunch of pain there. I feel like the lack of an IoX update in 2 weeks must mean that things are stabilizing? It seems like most of the 5.5.7 problems are related to specific Z-Wave items and not “global” problems? I have been thoroughly reading most of the IoX Support forums and many others since fall and havn’t seen any of these (listed) items mentioned, but I’m not sure if that’s because they work well OR if I’m the only one using them! Any feedback MUCH appreciated! Shawn

Thanks @bpwwer - that answers a lot of questions for me. The phantom UUID in the database was the older one with the unrecognizable UUID and old IoX version - I deleted that one. The "new" one that appeared when I hit the 'Auto Discover ISY's' button has the correct IoX version 5.5.7 and the "correct" UUID (ie the serial number printed on the bottom of my Polisy). So the Auto-Discover button worked correctly. Thanks!

I probably should have included this in my original, but @bpwwer does it make sense that the 3 ISY's listed all had different 'serial' numbers (whatever we call the 12-digit #) ? THANKS!

Ok, maybe I've had a few wobbewy pops tonight, but I think my Polisy and ISY994i have mated and produced an offspring... The upgrade seemed to go fine, and after logging into PG3 I tried the Auto-Discover ISY's button. To my surprise, there are now 3 listed instead of the previous 2 I've always had. I'm quite confident that I only have 2 in use and connected to my network. It lists my 994 at being at 5.3.4, then my Polisy Pro at 5.5.7, then a mystery device at 5.4.5 ?? Clearly I'm missing some bit of info on this subject and you're all laughing at me now?

Hi guys. THANK YOU to @Javi @oberkc and @dbwarner5 for your awesome feedback. I have a couple followup questions on the basics. Before I do I want describe my plan -SUPER simple plan: Insteon Keypads, door/window sensors, and some sirens. Oh, and the ISY/IoX of course. I really just want to set some Armed modes, whether Away, or Home, etc., and set off a siren if something is opened during those states. I like the idea of ELK, but i can't justify the cost based on what I want to do, and should already be able to do with what I have. Here's where you guys can help me - what type/method of programming do I use to swap between these modes? My original plan was to set a variable to a certain number that aligns with each mode, then use programs to decide what to do based on that variable (I've only ever used Integers, but based on wiki reading I should be using State??). However Oberkc suggested Disabling/Enabling specific programs - I hadn't considered this - would this be better/more reliable? Are there other ways of activating this that I should consider? I appreciate any and all input! Me for perspective: ISY user decade+, 40-50 programs, 18 Variables, 62 Insteon, & 20 ZWave devices - 2 node servers on my Polisy Pro and soon to IoX. Still LOTS to learn!

Hi all. I've been building to get to a point where my IoX (soon to be, currently still ISY) can be used as a security alarm using door & window open/close sensors, 8-Button keypads, and several sirens to activate for home intrusion/break-ins. I eventually would like to create 3 'zones' for my home and both garages where there'd also be motion detectors in the garages. It should be noted that I'm often in or checking into my main attached garage during late hours where I may have already set the home to "Armed-Home", but I digress. I'm looking for any example programs (or even methodology or discussion) that create typical alarm settings - ie DisArmed / Armed-Home-Asleep / Armed-Home-Awake / Armed-Away. In my mind I have all the pieces & sensors already that I should be able to this with only my ISY, the items listed above, and some simple programs. While I do love creating simple/moderate programs with my ISY, when it comes to the item of security I don't want to re-invent the wheel or make a major mistake. I checked the Forums rather thoroughly and I'm pretty certain I'm posting in the right spot. ANY help anyone can offer will be GREATLY appreciated!! Thanks. Shawn

Hi @captainc . Have you tried this yet? I was about to order a few of them but stopped when I saw this post. Please update, thanks!! Or anyone else using it?

Hi @leecast . Last year I too wanted to program based on temperature for several powered items such as heating wires in my sump pump lines and I purchased a "Strips Comfort" by Sensative. They're quite unique compared to most items out there - they're long and very skinny about 1/2" wide, about the thickness of a credit card, and about 7" long. They're white and can be mounted with included adhesive, or screwed with a mounting plate. The coolest part I think is the lifetime battery that is claimed for up to ten years. Obviously I can't test that fully, but I've had 3 of them for a year now and all three are still at 100% battery. OH, and the best part is I use them outside through cold Canadian winters - most temp sensors are not rated to go anywhere near that cold. I also have them at a decent distance with no nearby Z-Wave items and they don't have communication issues. So overall I'm very happy with them. Two more things - these "Comfort" versions also have light measuring sensors that I don't use but clearly work, and there is another version available that also has a moisture sensor (ie. water leak) built in. Good luck! Shawn

THANK YOU @brians and @Techman ! You guys are awesome! I can't wait to play! Shawn!

That would be awesome - thank you for offering @Techman . That was my concern also.

Thanks @Techman ! One last question please - do you think that it (ZW SS7) would react/notice fast enough to catch a typical sump pump activation? My sump only runs for about 5 seconds or so each time and its fairly critical that I catch each one - my current synchrolink is flawless and being Insteon it's also virtually instantaneous - I'm very concerned that the nature of ZWave w ISY994 (soon-ish to be Polisy) will mean that it won't notice every time it runs. Please let me know your thoughts on the reaction time of the ZW SS7 - I don't have any spare synchrolinks and am quite aware of their longevity reputation. THANKS again! Shawn

Thank you @DennisC .

Wow. Not sure what you mean by 'useless statements' and 'hidden questions', or why you say it like that, but let me see if I can start over (I had copied @johnnyt 's (followup) questions exactly as he wrote them, but will I will rewrite them here in my words and with more background info). Background - currently have a 994i with 500 Z-W board, a couple dozen Z-Wave devices installed on it, and probably 80 Insteon devices as well. I also have a Polisy and have already physically installed the ZMatter board, currently running 5.5.5 but have ONLY installed a few Z-Wave devices onto that Polisy/ZMatter. I did this originally just to test everything to make sure IoX and ZMatter were working (all seemed to work well), but now bring up these 2 new questions about finally migrating all remaining Insteon & ZW devices from the 994i to the Polisy/ZMatter: #1 - the ISY migration instructions say "do not install zmatter board until told to do so". Since I’ve already installed & tested it, does this mean that when I start my “main” migration of 994i with 500ZW to IoP that I'll have to uninstall the zmatter board, then reinstall it when told to do so in the migration instructions? (or possibly something else like factory reset the ZMatter board?) #2 - to put it as simply as possible, does the migration from an ISY994i w 500ZW overwrite any Zwave devices that are already installed on the Polisy/ZMatter, OR, does the migration ADD all the ZWave devices from the ISY994i w 500ZW to the ZWave devices already installed on the Polisy/ZMatter? I too would have assumed that any migration would overwrite anything existing on the Polisy/ZM, but I can also see it possible (speaking generally and theoretically) that it would simply add the ISY/ZW devices rather than overwrite them, so felt it was a worthwhile question. Thank you all in helping me replace my assumptions with confirmed answers. Cheers!

Both these questions were asked by @johnnyt in the baby steps post but they didn't get answered and the post was closed. These are great questions that I would LOVE to know the answer to as I'm in the exact same situation (still using 994 but Polisy with ZMatter is waiting to go and I'm just stalling on the migration). If anyone can answer these would be a great help: [ after setting up ZMatter on Polisy and installing a few Z_wave devices to test it, then...] " My 1st question there is related to the ISY migration instructions (for later) that said "do not install zmatter board until told to do so". Just to confirm - does that mean when I'm ready to migrate 994i to IoP I'll have to uninstall the zmatter board then reinstall it when told to do so, or was that step (or should I say delayed step) just to get through the addition of some core 5.5.x new stuff and not applicable anymore? And second, would the devices I had linked to IoP/Zmatter show up after the migration, or will everything on the zmatter board get overwritten (or the board get factory reset) by the ISY migration process? It would be nice if they remained connected as it would offer the possibility of setting up a bunch of things before I migrate that I could actually use after I migrate without having to uninstall (exclude) and reinstall (re-include) those devices and lose the device IDs I had used in programs. I know (or at least think) any programs would be overwritten so I would just export those then import them after the migration. " THX

Hi @Techman - just to clarify, how exactly do you use this switch 7 as you would a Synchrolinc? Is it as simple as a program that If Status or If Current Current > xxx, Then ... ? Thanks. Shawn

@johnnyt Hi there! I was also in your EXACT situation in the fall with my Polisy (being very out of date, needing chip shipped to Canada, etc.), so I understand your hesitation. As of today, I am also in your (today's) exact situation - still using my ISY and have a Polisy w ZMatter with a couple node servers. The only difference is that I HAVE been keeping my Polisy up to date and am currently at 5.5.5. I can tell you that in your situation I don't expect you would have any issues updating your Polisy to 5.5.5 at this point based on my experience. I've been reading the forums a lot the last few months and it seems that most of the issues are with migrating from ISY994 to IoX on either Polisy or EISY. I have a 'bunch' of Zwave devices and so I've been biding my time and waiting to migrate. I've decided that when I do the migration I will do a partial migration - any of my ZWave devices that have S2 and or are not functioning in the way that i think they should, those devices will be un-installed fully before I migrate, then will re-add them to the new system when migration is complete. That's about half of my ZWave devices. I also did as you suggested and after installing ZMatter I installed a couple Insteon and ZWave devices to it from scratch to make sure the new ZMatter board was working well - seems like a very smart test to me. There's only been a couple people on the forum mention that the board didn't work for them, but I would still do this test if I were you (can't hurt). Do this after getting your Polisy fully up to date to 5.5.5 first. The only other advice I'd give is make sure you use the 'upgrade packages' from within your Polisy's IoP and give it a LOT of time - ie, given how long it's been for you, I would start it in the evening and just let it run overnight (or at least several HOURS untouched), but it should get there eventually on its own. ALWAYS backup first!! Good luck sir! And let us know how it went. Shawn

Hi Tim. Could you please keep this post updated as you work through your PLM issue? I suspect a lot of people will find this info helpful come April.... THANKS TimWing!

Dude.... "I know they are busy" ?? It's Christmas Eve, UD has just launched the EISY and ZMatter (before 95% of the industry), they are swamped trying to support that product and software updates, and you're [publicly!] complaining that you don't have shipping confirmation for an order that you tried to change after-the-fact, on the second busiest shipping week of the year, for a product that wasn't even supposed to ship yet for another week, to a company that has an exemplary customer service reputation ?!?!? You know, I'm just as eager as the next guy and am also planning on doing lots of programming this week while I'm off, but man, take a step back and have another look at the situation.... this is a classic can't see the 'Forest for the trees' scenario. These people have been working their butts off for us for months and deserve some Christmas/Holiday time off like the rest of us. Happy Holidays everyone.

HI. I'm going to attach the log file - hopefully I'm doing this right as this is my first node server. I've been through the wikis, forums, and installed this node server at least 20 times trying different things. I'm out of things to try. The "current status" is ALWAYS Disconnected. When I fill out the Configuration, save, then hit 'start', it claims to start, and the Uptime will count for about 3 seconds before returning to "Not Running" and Uptime "None". It never creates any nodes here, or on the ISY, though the ISY does 'see' the VUE Node Server, but that's it. Other notes: I'm still using my external ISY as I want to learn one step at a time. Also, I my Emporia kit is a 4-outlet (w energy monitoring) kit, and that's it - no actual "Vue". I have no issue viewing the outlets on the Emporia App or Website. What does the "Load Profile" button do? (for me, nothing, but I don't even know the purpose). THANK YOU! Shawn VUE_12-20-2022_114922-AM.zip