vbPhil

Thanks for the suggestions. I was committed to the ZooZ, ZSE42. I'll try the others at a later time, especially the Ecolink since it comes with a probe already attached. Meanwhile I soldered a couple wires to the probe contacts and attached a 300-ohm twin-lead cable to use as the probe. Working great so far.

I had been thinking that with other z-wave devices the extra nodes that showed up were valid for the device, but the ISY didn't support them. But when I saw CO & Smoke Detection on this one, I knew it wasn't right and wondered why nodes labeled that way. What determined the text to use, the ISY or is it internal from the device? Any idea?

I installed a ZooZ ZSE42 Water Detector sensor and was surprised at all the nodes it created. I emailed ZooZ about it and since they haven't tested it with an ISY they're claiming ignorance. They did say it only detects water. Is there any explanation as to why the extra nodes were created, especially the CO and Smoke Detection? I understand from other z-wave devices that I've installed the extra nodes are just there but aren't used and can be deleted. I guess I'd like the Polisy-ISY to do better or is it just a weakness with the z-wave design?

Is there a way to list all devices in one screen like you can in the Admin Console in order to see the overall status? Now it appears that the top-level view is just showing all my Folders, so I have to drill down in each folder to see the device status.

Thanks. I'm curious about how many times your sensors have actually triggered from an event. For my case they will trigger several times a day so I would expect decreased battery life.

Has anyone tried soldering a couple wires to the ZSE42's probes in order to sense water at a distance? I don't have one yet so I'm unfamiliar with its construction and operation. I'm currently using a Wireless Tag moisture Sensor to detect when a water barrel is full. I soldered a couple wires to the existing probe in order to sense down in the barrel. When the barrel is full, I trigger a valve and pump to empty it. All is working fine except when the Wireless Tag malfunctions like it did yesterday when it lost Internet connection and then the barrel overflows until somebody notices it. Needless to say, I'd like to eliminate the cloud and was thinking of the ZSE42.

@JimboAutomatesI studied up on the HSV color space. The Kasa NS works with HSV the only difference I see is in the max value for Saturation and Value (brightness). Mostly what I find online is their max values can be either 1 or 100 where the ISY uses 254. So, you can convert easy enough depending on what color chart is being used.

ooops. I'm using PG3. I grabbed the wrong forum.

I'm using the NS but NRs would be good to use as well.

Been trying to figure out what format of color values to use; XY, HSV, RGB. HSV seems to sort of work but then I haven't found an HSL color chart that the ISY values correspond to. Any help would be appreciated. Thanks

Another thought. Maybe you made the key panel a responder when you added it to the scene. Some devices can be either in a scene and when added to the scene you select what it is to be.

The ramp and dim levels are set on the responder not the controller of a scene.

I just realized what you were showing in your image. you've got a controller selected and there's no parameters showing. What do you have selected in Navigator (left hand panel)?

I personally use Network Resources to turn my "Hue scenes" on and off. So, I tried your example where you add the Hue node (light) to an ISY scene. With that it looks like you're only able to set one command on the Hue light for the scene. I don't see how that is much useful. Also, I'm not sure what "default" means. Where would the default values be set?

Yes, the command always completes. I'll check the logs. Nothing out of the ordinary in the ISY or NS log.

I synchronize quite often, whenever I make changes, but it doesn't seem to help. BTW, I don't get the error all the time so it's hard to find any clues. I never seem to get the error from an Insteon node only the Virtual Node.

yes.

Just a thought that you are probably already aware of, but the ISY is always a scene controller as well as any other controllers added to the scene. Each controller has its own set of parameters so when you select that controller in the Admin Console its settings are displayed and can be adjusted. Make sure that all your controllers for the scene have the same settings or whatever is desired.

When I activate a Virtual Switch thru UD Mobile, I'm getting a 404 status returned and the action tied to the switch is completed correctly. Any ideas of the cause?

I can see in the Kasa log where the ST value is being flipped back to 100 after it was correctly set to off. (See highlighted in magenta)

I just checked on the smart plug and its status is now stuck again. I captured the log package and it's attached in case you can take a look. I was toggling both sockets on and off. The status in the Kasa iPhone App was changing but not in the ISY. Kasa_7-11-2022_31149_PM.zip

I have the Kasa Outdoor Smart Plug, Smart Home Wi-Fi Outlet with 2 Sockets, EP40 and the status value is getting stuck. One of the outlets, which is on all day, gets stuck as ON. The other outlet, which is usually OFF all day, gets stuck as OFF. If I restart the Node Server, it will correct itself but then sometime later it reverts back to being stuck. When I toggle the outputs manually with the ISY the outlet condition does change and the status switches correctly for just a second but then flips back to the stuck value. I checked the Node "ST" value in the Kasa Node Server, and it is indicating the same stuck values, i.e. 100 for ON and 0 for OFF.

I turned off all extensions and the message went away. I then turned on the extensions, one at a time, but the message never came back. So, it appears to have healed itself. Thanks for the reply. All is good again.

Here's the URL. It's the same one I've always used. I'll check on the extensions. I don't recall making any changes to my browser but who knows what's going on in the background. This just started, say in the last couple weeks or so.

Thanks, that worked. It took a few times to figure out how to enter the addressing information. Here's what worked for a virtual switch. Actually, the information needed is found in AC not PG3. PG3 doesn't include the n006_ prefix for the addresses but it is required when doing the AC Add node.