madcodger

Thank You.

Hi all. What is the recommended/best way to completely reset an ISY-994 device so that all user-identifiable information is wiped out of it, but leaving it in excellent shape for resale? Thanks in advance for help and guidance on this. On a side note, I have two ISY-994s (z-wave version) for sale, if anyone is interested. They have always been kept on a UPS and to the best of my knowledge are in excellent condition. I purchased both within the past two years, and one only about a year ago. I don't use Insteon anymore so do not have a PLM for either.

I can't speak to Polisy directly, but when I needed an additional ISY for similar reasons (a building that required it, on the same property and LAN as the original ISY, primarily to use data from my Davis VP2) I was told a second polyglot device was needed. I added a second RPi running polyglot, which wasn't a big deal. As I understand it, that means a second Polisy would also be needed unless some changes to the current architecture are introduced, but others here can confirm this. Of course, a RPi won't be an option for v3 of polyglot, as UDI has previously announced. I think this is a big drawback to the ISY, and it was the final straw in my decision to migrate away from the platform, sadly (along with continued reliance on the java-based admin console and lack of robust support for mobile devices, all of which I view as antiquated). I need multiple ISYs and have no trouble purchasing them. But if I then need to also purchase a Polisy for each ISY, and must put up with a lack of development in other areas as well, that creates a whole new situation that I have personally found unappealing. Others think I'm wrong. The market, as always, will decide. Good luck with your situation.

If you don't have several other, well-placed, z-wave devices to form a mesh, then a thermostat as a single z-wave device is a horrible idea. You either need several z-wave devices in almost all settings, or none. The technology is designed to operate as a wireless mesh, and ignoring that is what brings headaches to those who just try to have one or two devices. If your contractor doesn't really understand z-wave, don't let him/her give you advice about it. There are other decent thermostat options that frankly have no dependency on the ISY, but that could be made to work with it - albeit only via the cloud in some situations - if desired (Ecobee comes to mind). For most people, that's often a better plan. I use GoControl z-wave thermostats and really like them, but they are part of a very stable z-wave mesh.

Personally, I found that the best method was to go to the download page for whatever release of ISY firmware you are using, and download whatever link to the admin console they have there. Still having a java-based admin console is not the best approach, in my view, but users have no control or options re that.

Amen! And, most uses of 2FA allow it to be optionally set so that it is required only when the user is using a new device (or has cleared their cache). Perhaps the problem is at least in part the java-based admin console, but I don't know that to be the case. 2FA would be a very nice addition.

They have excellent customer service for things they deem to be a problem. They're a smart group of folks, and likely very well intentioned, but if they don't agree that they HAVE a problem they just ignore it. They don't seem to think their instructions and documentation (a form of user interface) are a problem, while others disagree. Most of those "others" just give up and move on to some other platform/device/system. I'm just suggesting that if enough customers say, "Hey -- wait a minute...", it might one day have an effect. I hang in there because I think they're worth it. I continue to voice my observations and concerns for the same reason. It's not that I think they're "bad". It's that I think they can be better, and many would benefit if they were.

The ongoing, perpetual problem. Voiced many times. Consistently ignored. I suggest filing a support ticket. When they have to deal with enough of them, they'll start thinking about how to prevent them.

Thanks. I finally got so disgusted with trying to find a local Elk dealer/installer (in case something happened to me, I want my wife to have a local service person), that I just gave up and swapped out the Napco with a DSC, so I could use an Envisalink (which is sort of a slow dud, frankly, and wasn't even close to being "worth it" as it required replacement of a perfectly good Napco Gemini, which I greatly regret). Shame, because I loved my self-installed Elk in two previous homes. But as a company, they are a shadow of what they were 10-15 years ago, in terms of customer support. I don't like the DSC half as much. But at least I have a local service company to work on it if needed. Elk was not very helpful in connecting me with a local person in my fairly rural location. There's a company ripe for being sold, in my view. Perhaps a new owner would do something with it. They were amazing, "back in the day". Now? Meh.

If you mean the use of the "Programs" capability of the ISY, I don't recall any differences other than the expanded set of external data sources and the additional devices that v5 enables. If you are referencing the ability to write code for the device, sorry - you need someone else's opinion/experience for that one. I'm no help there.

I, too, often find it difficult to understand (or sometimes even find) information made available by UDI. Great engineers, rock solid devices, very fair pricing - but things like manuals and user experience are not their forte, in my humble opinion. So, don't hold your breath there. The wiki is likely some help, but be patient in reading it. UDI is a company of engineers and programmers, almost exclusively. That creates both benefits and challenges. That said... The biggest difference I see is that v5 gives one the ability to access and use "external" solutions/data sources with the ISY, through an API (Application Programming Interface), if the external solution provides one. For example, my ISY can now obtain weather info from my on-site weather station and information about my non-Elk alarm system, because v5 allows for this while v4 does not (and because some great hobbyist users on this forum created "nodeservers" that enable this - kudos to them!). So, if you want to have your ISY work with "external" data, upgrade. If not, v4 is certainly solid and proven. Good luck either way.

I see the points. Fair enough. What I've recently come to realize is that UDI is focused on markets other than the home automation enthusiast. Great for them, I hope. But it tells me I need to keep that in mind unless I personally plan to open a utility company.

UDI very (in)famously refuses to commit to even likely release dates for anything. And I share your frustration (as I type this on an iPad).

So, I checked my Java memory. Maxed out - highest possible allocation. Cache cleared again (I've lost count of the number of times). No real change. I now have skads of additional z-wave "devices", for which I have no need, and that seem to do nothing of any practical use. They're all now moved to a giant folder. It's like having a piece of furniture with several drawers that hold the items you wish to use, and one colossal junk drawer that takes up more space than anything else.

I appreciate the suggestion. Thank you for that. I am skeptical, though, that this is the issue. It would mean that the already generous setting that I've had (forever, and that works for everything else I do) is now insufficient? Hmmm.... I'd complain about this "upgrade", but it would do no good.