ddaggett1

Upgraded eisy, and the upgrade appeared to complete. But, after the upgrade, I cannot add any new devices. I'm getting the error message "cannot determine device link table address." I've tried a mini remote, an outlet linc, and a lamplinc, and none of them will add. I had no problem adding devices today, before the upgrade. Thoughts? I've tried to reset the devices, and I've tried to reboot the eisy and the powercycled the PLM.

Thanks, I'll try to do the backup from the polisy again and start fresh with the eisy after a reset. I thought I had done the zwave backup the first time, but not positive. With regard to the Zmatter board, the one in the polisy is internal, and the one with the eisy is an external dongle, and so they're separate boards.

So I'm guessing maybe there was nothing to migrate? But, if that's the case, is there any way to transfer the zwave devices from the polisy to the eisy?

Thanks. It was the internal zmatter board for the polisy.

Thanks to both of you for your suggestions. I tried to do the migration to eisy, but it was a complete bust. Nothing worked. I may have the wrong cable for my PLM - I tried a console cable (USB to RJ45) as I had that, but I have ordered a cable from UD. If anyone knows if a regular USB-RJ45 console cable should work, however, that would be nice to know. With regard to z-wave, the "migrate" button described in the eisy documentation is NOT on the polisy that I'm migrating from, and I'm running the most current version of the admin console. Given that, I'm guessing that the backup was not a migration backup. But, if the button is not on the screen, I'm not sure how I would have created a migration backup. Any thoughts? Thanks!

I currently have two separate UD deployments - a large (150+ device) deployment running on polisy at our home and a smaller (30+ device) deployment running on an ISY at our lake house. I just purchased an eisy. The easiest thing to do would be to just replace the isy with the eisy and call it done. But, if the eisy is a more powerful device than the polisy, I'm thinking I may be better off migrating the polisy to the eisy and then moving the polisy to the lake house. I have two questions - first, is that the right choice (i.e., to have the eisy powering the larger installation)? Second, and if so, can I migrate from polisy to eisy and maintain my z-wave devices? I don't want to have to redo those if I can avoid it. But, there is no "migration" option on the admin console configuration tab (as I migrated to z-matter, I think, when I first setup the polisy a year ago). The polisy is running v 5.6.4. Thanks!

Thanks, all! I'll give that a try.

Thanks - the ticket submission issue was definitely a "font thing." Thanks for that, and I just submitted a ticket for the flickering. Now, if I could just fix that

Every time I write to a device from the admin console, or a program writes to a device (e.g., to turn a light on or off), certain other devices start to flicker. Any thoughts? BTW, I tried to submit a ticket, but the "submit a new ticket" button appears to be gone from the UI. Any thoughts? Thanks! BTW, I'm running on Polisy with 5.5.3.

Ahhhh... I thought the migration tool was ready. That's what I was trying to do, and that's what I thought the "5.5.2 is ready" announcement said/meant (see the first sentence of the linked page below ). These are all clearly first world problems - at least for me - so not the end of the world if UD doesn't respond to my ticket immediately. That said, the migration tool pretty clearly isn't ready or stable, so if you're trying to migrate as contemplated in the announcement link above, it may not work. I really do appreciate the level of effort and commitment from UD support, however - they are truly unique in that way. Thanks for all the hard work, and I'm sure we'll get it working eventually Happy New Year!

So, I've upgraded to 5.5.2 (no problems), and then I restored from my ISY backup, and I saw all the Z-Wave nodes. But, other than that, the restore was completely useless, as none of the 80+ Z-Wave nodes appear to be working and none of the Z-Wave UIs for each of the 80+ nodes appear to populate at all. Thus, I would consider the migration to be a complete failure so far, at least for me. I'll file a ticket.

Got it - thanks! It works!

I've got an interesting problem/bug when trying to program for the hidden door sensors. I include a statement that is essentially "if status door sensor is on" then do x. When I save the program, however, I come back and the statement now reads "if status door sensor is 100%". I have four door sensors, and the programming has the same problem for all of them, so I'm assuming there is a firmware bug for the ISY? Any thoughts? BTW, I'm on 4.6.2 firmware. Thanks!

I just tracked down the installation manual. It is here https://www.vistapro.com/Files/inst/MT-CTS-Inst.pdf. Apparently it will work with a dimmer ON THE SUPPLY SIDE Thanks for tall the help!

Yeah, that's what can go wrong when you let lawyers and former professional computer programmers (me, basically) loose with the electronic components. My electrician who installed almost all of my Insteon hardware (after he fixed my first two installations) made me promise I wouldn't work on anything anymore that required turning off the breakers. It's a pretty robust installation at this point - when I print out the topology from ISY, it is 17 pages long (and most of it works!). Anyhow, the landscape lighting transformers are supposed to be high end, and if you open the access covers, there is simply a receptacle for a NEMA plug. What had been there previously was a simple, mechanical timer, which didn't seem 12V specific. Soooooo... The LampLinc plug fit in the same receptacle.... Sooooooooo...... Anyhow, thanks to all for the advice, and I have now removed them from the system and have the landscape lighting (temporarily) plugged back into the mechanical timers. But, back to the real question (and deflecting the discussion from just how stupid my initial install was - yep, pretty dumb, in retrospect, but kudos to the guys at Insteon as it actually worked, at least until recently when I apparently added too many lights). I realize that the solution is absolutely NOT to remove lights and plug the LampLinc's back in. But, what I'm wondering is if I get the electrician (first positive move on my part ) to install high wattage SwitchLinc dimmers (not the normal ones, but the high wattage ones) on the supply side of the transformers, do people think that has a reasonable shot of working? I can provide additional data on the transformers if that would help. Thanks again - this is a really helpful user community, and I'm glad that I can contribute something (at least a little levity ) from time to time! Take care, and thanks!

This is probably another stupid question. We have have a fair amount of 12v landscape lights. We added some additional lights today, and all have LED dimmable bulbs. I was using a LampLinc to control and dim the lights, with the LampLinc plugged into the output side of my 12v lighting transformers (I have 3). I'm not sure if I should have been using it on the output side of a 12v system, but it has been working for several weeks. Anyhow, when the lights were supposed to come on tonight, there was strange behavior - one of the strings came on, just for a moment, and then went out. Another came on would stay on for about 30 seconds, then the LampLinc would turn off (red led) and then power cycle endlessly like that. It does not appear to be an issue with the lights themselves, as they work fine when I plug them directly into the transformer. Thus, I have a few questions: I'm assuming this is a LampLinc issue, but I'm guessing the problem is I'm using it for something it's not made for. Any suggestions on how to make this setup work? I tried to put the LampLinc on the other input side of the transformer, but I saw the same behavior. Thanks in advance for any assistance you can provide!

Howdy. I have a hopefully easy question. I've been researching replacing smoke alarms in our house. The existing units are about 12 years old and due (I think) for replacement. The existing system is hardwired. After several hours of research, it looks (to me) like the current state of technology is that (a) there are very few hardwired combo smoke alarm / CO units, and ( none of those appear to talk to ISY directly. Insteon has a bridge product, but it does not work with the new hardwired smoke alarm / CO units from First Alert, and there is no older generation First Alert combo smoke/CO alarm (which would work with the Insteon bridge) that is hardwired. The new FirstAlert hardwired smoke/CO units only talk using the Apple protocol, and there is no good way to make that talk with the ISY. Nest has a hardwired smoke/CO unit, but I'm not seeing any way to connect that to the ISY either. Any suggestions for a hardwired smoke/CO alarm that will talk with the ISY? I have not bought any smoke alarm hardware yet, but the ISY system is for keeps and I'm not changing that part of the home automation Thanks!

Thanks all! I really appreciate the comments and advice (and I'll back up my computer )!

So, I've had my ISY 994i/IR PRO for a few years now. We have close to a hundred Insteon devices and everything is (or was) working great. The PLM, however, has just failed. I've researched this online and it looks like, to fix it, I would be using a soldering iron, which is typically where I draw the line. As such, I've ordered a new PLM from Amazon and a backup so that I've got a ready spare in case this ever happens again. So far, so good. But, I've been wondering about a backup for the ISY itself. Is there a way to purchase a backup, have it enabled for the same modules I have already purchased, and either have it as a hot spare, or ready to be put into service as a spare with minimal configuration if the ISY we're currently using ever fails? Overall, the product works great, but it is sad when everything stops working, and I'm willing to buy redundant hardware to make sure that never happens. Any suggestions would be appreciated (and apologies if there is a Wiki or other feedback on this - I couldn't find anything, although I thought I had asked a similar question once before). Thanks!

Howdy. I've got 70+ Insteon devices and I tried the motion sensor in the mailbox trick, but it is not being seen by the ISY. It is not the particular sensor, and I've tried two of them, and neither registers. The mailbox (old fashioned steel mailbox on post on the curb) is about 40 feet from the house, and about 60 feet from the nearest other Insteon device. I ordered an Insteon range extender that I can plug in so that the motion sensor in the mailbox will then be about 40 feet from the closest Insteon device, but I'm wondering if I'm just wasting my time on it (e.g., because it will never register from inside of a steel mailbox?). Any thoughts? Thanks!

Is there a listing somewhere of the default values under Advanced Configuration? Also, is there a command to write changes to the ISY-994i so that they are not lost on reboot? Thanks!