BigRic

@Michel Kohanim and @lilyoyo1, thanks for the guidance! I must have missed a step. I just reset the dongle again, again excluded one of the devices and this time, the dialog closed as it's supposed to. I then included the same device and again, the dialog closed and now it shows in the device list! Thanks again!

@Michel Kohanim, the dialog shows properly when excluding or including. Simply nothing shows up when I toggle those devices accordingly. @lilyoyo1, I just reset the dongle about an hour ago and then tried re-learning the closest device again (it's pretty close; within about 20'). Same issue; nothing seems to be detected by the ISY.

@Michel Kohanim, I may be doing something wrong, but that's what I tried and the ISY does not seem to see them at all. My understanding for these units (mostly GE toggles and some monoprice outlets) is that any host can set the exclude mode (which I did using the SmartThings, since ISY didn't seem to be speaking to them at all). When I excluded them there, they reported back as "successful", leading me to think they'd again be available to include on the ISY. When I re-run device discovery on the ISY, nothing happens at all. I've set the log to debug hoping I'd see something there when I make the attempt, but I don't. Running out of ideas... New to z-wave troubleshooting (I've had most of these in place for 2+ years, so I don't really think about them much). Perhaps I'm misunderstanding the process in some way?

@Michel Kohanim, they would not restore and when I sync'd, they all went away. I used my SmartThings to send a handful of them disassociate commands (not sure of the right term this sec) then tried to add them new to the ISY by putting it in learning/add device mode and trying to associate those devices as new. The ISY sees nothing (that I can tell) when I do this. I gave up on trying to get the old device list working as I figured I was beyond being able to fix. I tried restoring an old offline backup, but no luck.

Sure @Michel Kohanim...

Since upgrading my unit to a 500 series zWave, I'm not able to remove or add any zwave devices (however, if I try to add or remove from SmartThings, it sees them just fine). In the admin console, I don't see anything when in linking/adding mode.

I blew up my entire zwave environment, thinking I had a 500-series when I didn't. Was not able to go back and all of my devices are offline now. I'm assuming I'm going to have to clear the controller settings on each device and then re-learn them to the new 500 series controller?

So, I thought (based on the date) that I had a 500-series dongle, but don't. Ended up blowing up my config. I reverted back to the prior build (rev c) and reloaded my backup, as well as tried reloading the backup of my zwave. None of my ZW devices are back online (all show an exclamation point) and I'm not sure what to do next. Any thoughts? I tried a "sync", but then all of them went away...

@Michel Kohanim- thanks for the email reference. Just sent a copy off to you. Only thing odd to me is the DNS errors (I've changed them to another resolver, but not sure it's related). Thanks to the other for their responses too. @rccoleman- I've got backups from many, many dumps but since it occurred both before and after the upgrade, my guess is I'd have to start over if corruption is the issue. My environment is not very complex, so I could do that. Just hate to have to start over if it can be avoided.

I've had my ISY for some time. About 8 months ago, the powerline controller it was connected to (and getting power from) died. I plugged it in with a DC power supply and all seemed to be okay. Now, every couple of days (up to 3 weeks), it stops responding to Alexa commands and I'm not able to login via the admin console. I power cycle it and it comes back for a random period of time (working fine the whole time) and then the problem comes back. I've tried multiple power supplies and it does not seem to lose power at all. I recently moved to the beta firmware hoping it might fix the problem, but it still occurs. Any ideas? Where would one look as once I have to boot the device, I'm assuming any logs are gone... Thanks in advance!

That was it! Thanks so much for the help... I wasn't paying attention to that button in the middle of the device screen. Changed it to "Switch", rescanned devices and added 7 new routines (2x3 doors + 1 for all doors). Very cool...

Thanks for the feedback. Can you guide me a bit on how to change how a program is presented? When I go into my.isy.io to add a mapping to Alexa, the garage door programs only show under the "program" tab; meaning I can't add them to the devices tab. In the amazon portal, the only option I have for those items (listed as "program") is to "forget' them. Is there something further back on the ISY that I need to change? Thanks in advance! Edit: Looks like the phone is slightly different than the web version of the portal. On the web, the device shows "program" as part of the description - looks like it's automatically appended by the ISY/Alexa link. On the phone, when you open a device it shows the type as "other" with the same "program" as part of the description. Does not appear to be editable.

Just an update on this topic and thanks again to those who responded. For some reason, the Alexa "routines" do not allow for controlling the relay device I'm using via the ISY (ISY basically sends basic commands via tcp with commands specific to each of the three ports). It seems that these network devices are not yet supported (I'm assuming it might be on the ISY side and how it presents devices to Alexa via the app integration). Just updated to v3 of the ISY app but still no luck. Guess I'll have to sit tight on this one for now...

Thanks DonM - That's next on my plan, but I first wanted to make sure the relays would work with the buttons (I've heard that many had problems getting this to work). I don't think I've used "routines" before, so thanks DRPRM1 for that comment. I will look into how that works later today!

Good evening all, I deployed a 3-port network connected relay that's wired across the terminals of each garage door switch. With Alexa, I can say "turn on garage door 1" and it runs the network script to do a momentary "press" of the switch. It's the same command (open) to run it again, basically closing the door. Has anyone found a way to create an alias like "open" or "close" to be the same as "turn on"? It would be much more natural (I do it all the time to no avail)? Looking for ideas... Thanks, BigRic