madcodger

Just a thought... If you want to control a thermostat (or many other devices), you can either pick one that doesn't use the cloud but that may have fewer features (e.g., the trusty z-wave GoControls) and know that it is going to continue to work for you as long as the device itself functions OR you can pick one that is cloud/API - based (likely with more features), but realize that you are taking on the risk of that API changing in the future. We should have all learned this from Nest, MyQ, etc. Personally, after long arguing in favor of the cloud, I've shifted to being a fan of more local control despite thinking that devices like the ecobee are good for most people who don't use a HA controller. (I recommended them to a friend a couple of days ago). If a connection is based on some company's API, it's subject to their whims, strategy changes, outright greed, etc. And, of course, they depend on the internet itself functioning. Choose accordingly, balancing features against that risk.

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.

Please post when you have sold this. I have two 994s to sell but don't want to interfere with your sale if possible so am holding off on listing them for a few days.

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.

Good news, though. Thanks for the update!

Did not know that. I've found that there is a difference in quality from one z-wave manufacturer to another, so I've enjoyed the ability to have a choice in that. But if there's a critical component with only one source, that certainly creates its own vulnerabilities, of course.

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 proprietary nature of Insteon products, combined with many failures of switches in the "Icon" line produced by that manufacturer, is what drove me to z-wave for my most recent two properties. I miss some things that worked well with Insteon, but overall am happy with the change. I don't miss Smarthome, that's for sure.

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.

Thanks for your input.

The point about consumer routers/APs being a problem is excellent. But like most aspects of tech, that is likely to improve over time. So, to some degree, this is an issue of "where the puck IS, today". The question for a tech company, I propose, is where will the puck be in the future? Not my problem to a large extent, but it is the problem of a company I'd like to see remain successful. So, I bring up the idea and appreciate the debate. And, I note that I may be completely wrong in my thinking. As for the "Oh, that company probably won't even be around in a year" comments, I usually just smile. I've been on the planet long enough to have heard that many times. There is little ability to predict it, given anything any of us know. I lost count of the number of times I heard it about Apple. And I remember people saying that Enron was the way of the future. So... Anyway, support it, don't support it, do as you wish, UDI, and best wishes for your course of action. Personally, I think wifi support is worth exploring. Perhaps Leviton would be a better sort of partner, if "corporate stability" is the overarching factor. I just see the price point of Insteon and z-wave devices remaining high without any big improvements in reliability or utility (admittedly, I haven't tried the new 700 z-wave devices) while the price point of wifi falls even as reliability improves. The best CEO I ever worked for taught me to spot vectors, and follow them. When I look at these, I don't like where they go for some existing tech. Just sayin'...

@simplextech, we're certainly good. I would be happy to look at suppliers other than Wyze, and suggested them only based on limited experience with the devices and their price point. I've no experience with TP-link devices for this purpose (I have a couple of their hubs and a wifi USB, and they work well). I also have no experience with Shelly (although I once knew a young lady by that name, but that's definitely off topic). Anyway... I'm just suggesting that moving beyond Insteon and Z-wave might be a reasonable move for UDI. If the devices are reliable, the price point is attractive, and units are easy obtained, I certainly have no real preference for a particular brand.

This is an excellent point! But then again, isn't this similar to what UDI did with Elk alarm systems? Try getting your DSC or Napco or other brand to connect in the same way one can connect an Elk. Similarly, we once had Ham weather as our only option for "integrated" climate info, until they became an undesirable partner for UDI. And what about Insteon? That's a sole source product if ever there was one! UDI has aligned with single or small numbers of suppliers in the past, and perhaps that could be done again. My primary point is that wifi switches and other devices are much more reliable than in the past, and the UDI customer base might benefit from being able to use them. They have better range than z-wave, equal reliability in my experience, and a much more attractive price point. If I had to suggest a supplier, I'd take a hard look at Wyze. I've been experimenting with their plugin modules, and I'm impressed. And the price point is incredibly attractive. So, while your point is certainly valid, I don't think it rules out wifi. It's just a situation where UDI might need to limit the number of potential partners.

I see that @Michel Kohanim "liked" the comment from @MWareman about using Alexa to integrate wifi plugs with ISY. I also "liked" the comment and appreciate the workaround, but suggest that it may be a better option for UDI to consider "direct" support for wifi devices, making them as easy to add, maintain, and use as Insteon or z-wave devices. I know many here say that wifi is not suitable for plugs, switches, and dimmers, but my recent experiment with this does not support that. I added two Leviton wifi plugin modules to my system last year so that, if necessary, I could reboot a locked-up ISY remotely. That has not proven necessary thanks to the reliability of the ISY, but the wifi devices themselves have always been reachable. More recently, I added a "tiny office" to our property, so that I could work closer to the lake, away from the main house and garage buildings. It's well out of range for z-wave, but was just barely within range for wifi, so I added four very inexpensive Wyze wifi plugin-ins there to see if I could control a few things. They worked well, even with somewhat spotty wifi (now much improved with a powerline wifi extender). And, they can be puchased for as little as $7.50 each! So, given the reliability we are now seeing from wifi switches, coupled with their dramatically lower cost compared to z-wave and Insteon, it seems to be in the best interest of both UDI and its customers for UDI to consider adding "direct" wifi support. One can certainly do it via the Alexa workaround, but when "workaround" is the way to accomplish something, it is not a far step for the customer to think, "Why do I need that other thing. (the ISY). Better to prevent that, while also improving support and options for customers, I suggest.