GlowingHair

@Ross It's pretty straightforward. To get the temperature from a Z-Wave sensor into an integer variable (60), Basic authorization was used.

@MBrzeski Not for this specific device, but I ran into the same situation with other devices and used a Network Resource and REST to get the values I wanted into variables. Have you tried that?

@JJJ I'm not familiar with Lutron switches, but in Insteon world, I believe using "switched" (control) in the if statement means just that, that the switch is switched, physically. Using "status" in the if statement would cover all possibilities, e.g., physically switching, Alexa/GH commands, etc. To cover all bases, status and control can both be used in the if statement.

@ThisIsTheWay Are you switching the device or the scene in the Admin Console? If it's the device, wouldn't just the device respond? If it's the scene, both the keypad button and device should respond - is that the case?

Cool! It's been working for me now, too. (Didn't chime in before - seemed like enough you had it managed. Thanks)

@smokegrub 90% of the time, my finder is blank when starting. I hit refresh and it populates. Have you tried that? Also, I have saved the configuration so it can be loaded if necessary. If I recall, I've only had to do that 3-4 times.

My routines are triggering, but about 1-3 minutes after they should. Luckily, for me at least, they aren't for anything critical, just convenient.

@Techman Perfect! Thank you so much. Definitely going to bookmark this. Edited to add: I still wasn't satisfied, so did a little more searching, and what I found is to use http://ip.addr.of.isy/rest/nodes/ (thanks, @MrBill), and I added the specific address to that to return the specific device's properties. This is what I recall using before, but had forgotten.

@Techman Thanks, but I already know how to do that. What I need to know is how to list the properties so I know which property to assign to the variable. Of the three I listed in the original post, only two do I know off the top of my head (or by referring to existing NR); the third I found in my search of the forum, so could use that for my immediate need. However, I would like to be able to list all the available properties so it is easier to find what I need to use. Make sense?

I thought I had run across a way to list z-wave device node properties, like CLITEMP (temperature), CLIHUM (humidity), BATLVL (battery level), etc. Is there some command that can be issued in a browser to list he properties (that's what I seem to recall seeing, though I can't remember the details)? I tried several searches and couldn't find what I was looking for, although I did find the correct property in another post by accident so I could get my network resource working. Any help would be greatly appreciated. Thank you.

@TysonEwanchuk I have an ecobee and am pleased with. There is a Polyglot nodeserver for it; I don't use it, though, since my needs are too simple to bother.

@Michel Kohanim Very clever. So very clever. I salute you.

It looks like you may be able to do it via an Alexa routine.

Since you have upgraded to the later z-wave board, I think you also need to upgrade the ISY to 5.3.x. IIRC, there were many issues in 5.2 and 5.1.

I think it's on Amazon's side, at least mostly. I have a routine NOT tied to ISY (it's ALL Amazon) that is failing, too.

I second wireless tags.

Like @larryllix, I still use KumoApps. My first use for these tags was to install them in my trash and recycle bins so I know when the trucks have emptied the bins, saving navigating a steep, sometimes slippery, driveway for no reason. The second use is carrying one in my handbag so the system knows if I'm home or not. The remaining tags just provide information that I haven't used yet.

Why not write a program to execute shortly after the ISY restarts to disable the problem programs? No harm/no foul if they are already disabled. That's assuming the ISY also loses power.

Check GitHub for PyISY; it provides many functions, including running programs and stuffing variables.

When I still had regular toggle switches that could cause issues when in a wrong position, I had covers so they couldn't be easily toggled. it boggled my mind how many people will flip a switch, not see anything happen, then leave it in that position! I would discover it when a light that should come on at sunset, didn't. Everything is "smart" now, and programmatically automated, so no longer an issue, but what a pain until I reached full automation.

In the 4.x release, I had to use a network resource to be able to use the humidity, in an email in my case.

I had the same issue a couple of years ago and resolved it the same way, i.e., deleting an unused device and adding the new one. This got a bit tedious, so I upgraded to pro, and haven't had the issue since. I think I was under by de ice count, but may have been pushing it by node count. I find it was money well spent upgrading to pro. if you are already using pro, I have no other solution.

Were you already logged into the portal when you were adding the new devices? I have done that before inadvertently, and a logout/login to the portal resulted in the new devices being displayed.

I use the topology report to list devices (and scenes) and copy the programs folder (from the top level), to the clipboard then to a text file. Both of these files can be put into Excel and manipulated as wanted.

Can you share how you are using a CAO tag for your dryer, please? I have tried different approaches using one, but have never gotten consistent results. Thanks for your help.