lilyoyo1

It's your temp causing it to turn back on. I'd have a secondary program that temporarily disabled your program if you manually turn it off

It sounds good and exciting but the work still has to be done. For a new person still finding their way; it can be daunting. There are many ways to accomplish what you are trying to do as everyone's posts can attest to. Before jumping in, I would sit down and think your whole theater routine out. While it may seem like a simple thing to add a motion sensor , there are other variables at play. Youll want to consider how much time do you need the lights on? How will the lights turn off, turn back on once done, What happens when you leave the room? Those are just the basic things. While automation is great, the worse thing is the need to do extra steps that you ordinarily would not have to because of it. Once you've answered those questions, you can move to the next step which is figuring out how to accomplish your goals. It may require investing in new hardware, waiting to gain more experience programming, or revamping your approach. Taking the time to properly plan will save you greatly on all fronts.

If they are used at night why are you having them trigger during the day time while the chickens are out?

Yes. It's still a standard switch. Just more options

That's what I do with my theater. I have a kpl with the activity the room will be used for programmed in certain buttons. If I'm watching a movie, it'll open up the screen and projector, turn on everything needed for a movie and put the lights on a timer. Hitting pause during this time will turn the lights on 30% so someone can go to the bathroom etc. If we're just entertaining or just want to watch TV the same thing happens. It'll turn on the TV and cable box along with seeing the lights to where we want them.

Changing control to status should work. Regardless off how it's turned on the fan will turn off after 25 minutes.

I would write a separate program if status of the fan is on then wait 10 seconds shut off. Add that to Alexa and see what happens

Did you add the switch or the program to the portal

For colors it would be the limitations on what you can choose via parameters and so forth vs hue or lifx where you can get much more colors and saturation

I haven't used these but from past experience, I would go with hue over those especially if you want colors. Reading the details of those bulbs, you would want to use them with their switches for best response times but that time would mostly be equal to that of using hue with insteon so it's a wash

Right click on the device in the admin console there is also an option to disable the device

What happens if you disable switch 13 and then retry

I have the 500. It does not support OTA but Michel has stated it will at some point.

I use the isy for everything regardless of size. I trust their programming more than I trust insteon's. Especially for a home I won't be at, reliability is Paramount

No more issues than any other device

I have a couple. I don't have a problem with their speed. Everything triggers within a second. The tilt sensor post doesn't work

I think you should. Especially for cases like this, it would help

I agree with Oberkc. Why muddy the waters when we don't know what he has, proficiency level with programming, or desire to spend what it takes if he doesn't have necessary equipment.

Most likely that's from your previous setup. I'm assuming since it imported that way (the isy "rebuilds" the scene for the new structure), the isy see's that as their default settings vs a new scene which would have different information. If you want uniformity then it wouldn't hurt to update thisnsonit all looks the same. Otherwise I wouldn't worry about it since it works

On/off when controller is turned on or off. The best way to learn is create a scene and see what reach option does

Default is what a device does by default in regards to turning on/off for example, you have kpl button vC that turns on a group of lights. In the list you would see button C set to default while you configured it as the controller.

There is no "best". It all depends on how you're setting your device up. For example, if you have 2 insteon switches and you just want them to respond how they would straight from the box with on/off commands, then native works. If you have 2 insteon switches and want one to turn the other on at 50%, then used you would use command. The above example apply to compatible zwave devices as well.

I didn't think insteon still made that system for them. The isy recognizes it probably because it is insteon based but it's not an insteon device. The Braun (insteon) firmware is different than standard insteon firmware.

Short answer no. Motion sensors can't tell what you are doing/trying to do at any given moment. The best you can hope for is to position the sensor in a way that it only picks up movement at the door way. If you are using something like example above then it's possible What I did for mine was put a kpl outside of the room (the switches are outside) with different scenes in it. Watch TV, watch movie, watch firestick, etc. Depending on what I choose, it automatically sets the room up the way I want. For example, my watch movie will drop down the projector and screen, turn on the lights and set an auto off. Hitting play on the remote will also trigger the lights off

If your sensors are directly linked to your lights , you'll lose the speed of direct links as the isy becomes the middle man to relay your signals to devices. I don't mix (double duty) my alarm sensors with jobs my automation sensors should be doing (and vice versus) While it can be done successfully, one errant command/program that causes a false alarm simply isn't worth it.