vbPhil

@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.

When I login to the ISY Portal I'm getting this message from Tiny Cloud. Can't figure out if it's from UDI or the Microsoft Edge browser. I don't have any association with Tiny Cloud products that I'm aware of. Any ideas?

When in the ISY Portal to configure a new switch with Alexa I'm not seeing any of my Virtual switches set up with the Virtual Node server. Will a virtual Switch not work with Alexa or am I missing something?

So when did Michel say this and why didn't he tell me that?

My original topic on this from Nov 14 2021 was never answered and subsequently closed. Today I have an update to say that I was able to create an ISY Network Resource following the Hue Version 2 API using SSL and HTTPS. The difference between then and now is I'm on Polisy with IoT and before I couldn't get a Network Resource using SSL to work on the ISY994i. A few main differences between V1 and V2 are: V2 uses SSL (https) the Path is different; for a light it's: /clip/v2/resource/light/.... the authentication key goes in the header as hue-application-key Go here for more, https://developers.meethue.com/develop/hue-api-v2/

Installing the Leviton ZW4SF-1BW Decora Smart 4 Speed Fan Controller with Z-Wave Technology switch on my patio Montecarlo ceiling fan has made it run smoother and less noisy. This Montecarlo is an outdoor, reversible, 3-speed, pull-chain model that I've had for many, many years. We run it mainly in low speed and it was always making some kind of noise from groaning to shaking. But now, setting it for high speed and using the Leviton for speed control it's running like a smooth top. On low speed you can hardly notice that it's running. I say all this as a recommendation of the Leviton z-wave switch. It installed without a hitch in Polisy IoT with ZooZ stick and has been responding beautifully.

Just a thought, as a test, add something to the else statement. Maybe the notification isn’t working. Not likely but something I would try.