bsobel

Plug it in (really, thats all)

Scenes are an Insteon construct and are very fast, programs can lag a little bit (as the ISY has to receive the Insteon message, process it, and more importantly send a second (or more) Insteon message back on the wire). Scene members do all of their work based on the original Insteon message (and continue to work even if your ISY is off, not that it should be)...

If you don't mind running a box (I use Raspberry Pi's) I can pull together my Sonos integration scripts, you can play, group, etc and do TTS (at least against input scripts, I convert them and run them to the zones). Tie in to ISY is via device ID's and/or variables (e.g. you can say when switch X turns on then group these devices, select this favorite, play or you can say when variable X is 2 then play this favorite, etc)... Bill

The 'easiest' way would be two iolincs with a relay connected to the input where the relay coil is 115vac driven by the 'other' leg. So when one leg blips the other leg would see it on the iolinc and generate a signal.

I would strongly recommend NOT using any device that does not have a failsafe timer to turn itself off after some time period for Irrigation. I've seen too many horror stories...

FYI this has been posted quite a few times now. As to the issue, the newer versions of Java are improving their security profile by starting to require a manifest file. UDI will have to include that moving forward (and I am sure they will). But the change means apps shipped without it will have to be specifically allowed.

Just add the URL to your ISY to the Java Exception Site List. No upgrades or anything else is required.

Possibly silly question but did you: 'ColorTouch thermostats do not allow remote control commands by default. You must go into "Menu" - "Accessories" screen and turn ON "Local API" after connecting to the wireless network.'

I don't think the network resources allow for variable substitution. You'd have to create a different UDP resource for each variable value you'd want.

Got it. In that case rewire the switch so its just a controller by disconnecting the load wire (the red one) and connecting what was running to the lights into the black wire (e.g. make it so those lights always have power). Then you can do what you like (I've done this quite a bit for my ISY/Hue integrations) Then you can go crazy with various patterns, dim levels, etc. A keypad in place of the switchlinc is a great option is you can have each button do a different scene.

Dont do it, you'll get device not responding errors from the ISY UI when the switch to the bulbs is off. As for better scene controls, I don't see how this helps, can you give a longer example?

Good thought (this is certainly a weird one!) Bill

My guess is also a VERY noise ballast on one of those CFL's especially with the lockup issue now mentioned. Bill

Michel, the switch causing the issue is NOT an Insteon switch, just a dumb old switch...

If you move that switch (the one that causes the issue) to the middle (hold it there) does the toggle linc controlled lights turn off?

This the right code? This appears to be json and doesn't match the docs above at all....

Do you have a PIN set? You didn't include that parameter, perhaps its not erring even if needed?

My pleasure. This stuff is fun

Hi, didn't know about the mobilelinc use case when I posted that. So in that case two scenes is still probably best. Make the B buttons controllers in one scene and the C button responders (and the opposite in the other scene). Adjust the level of the responders to 0 as before. This will give you two scenes in the mobile app and when used the status should reflect properly on the keypads. Best, Bill

From your description I suspect you actually want to combine them into one scene with all B buttons and all C buttons as controllers. Then go into each B button and adjust the brightness for each device and set the brightness for each C button to 0. Then go into each C button and adjust to the lower brightness and set the B buttons to 0. When you are done you'll have one scene the activates to different brightness depending on what button was pressed and the opposite button will get turned off as you'd want.

Most curtain/drape controllers are low voltage but some are normal 110v controlled as well. When I had motorized curtains I had installed control lines and power lines to each window frame so I had the options of either later on...

Good catch ,)

This will work, but you can also remove the If test from the flash2 program and just have flash1 run the then path or else path based on the check that is already occurring.

I think this will do what you want: From Sunset to Sunrise (next day) Then Repeat 30 times fan on wait 30 mins fan off Else Fan off The Repeat 30 times accounts for up to 15 hours of darkness, but should get short circuited when the sunrise event occurs and runs the else clause to turn the fan off (it it was it was in an on cycle at the time)

You might want to consider a raspberry pi and throwing a reverse proxy on that, very lower power and I find them great companions to my ISY (I use them to filter and send alerts, manage my sonos, hue, etc tied to my ISY's) Bill