Athlon Posted March 31, 2017 Posted March 31, 2017 I had to cut power today a few times while installing some new switches and noticed when I put the power back on my two 2672-222 v.48 bulbs were on each time. Will this program turn them off after a power failure? Is there a better solution? Startup - [ID 0020][Parent 0001][Run At Startup] If Status 'Speaker Light 1' > 1% Or Status 'Speaker Light 2' > 1% Then Set Scene 'Speaker Lights' Off Else Set Scene 'Speaker Lights' Off
stusviews Posted March 31, 2017 Posted March 31, 2017 I'd use "not off" instead of "> 1%." Anytime the light turned on, it would then turn off. There's no way to keep the light on with your program. I'm not sure how you included "Run At Startup?" Is that a v5 command?
Athlon Posted March 31, 2017 Author Posted March 31, 2017 Ha! You're everywhere tonight!! (thank you for your help with my wiring issue) I right clicked on the program on the Summary Page under Programs and chose 'Enable Run At Startup'. I found out how to do that while searching here for a solution to my question in this thread. I'll make that change to my program now. If I disappear on you tonight it's because my wife and I are going out shortly.
stusviews Posted March 31, 2017 Posted March 31, 2017 Thanks for the right click tip. My wife has a broken ankle, we'll be eating in tonight, but getting delivery from an upscale restaurant
larryllix Posted April 1, 2017 Posted April 1, 2017 I had to cut power today a few times while installing some new switches and noticed when I put the power back on my two 2672-222 v.48 bulbs were on each time. Will this program turn them off after a power failure? Is there a better solution? Startup - [ID 0020][Parent 0001][Run At Startup]If Status 'Speaker Light 1' > 1% Or Status 'Speaker Light 2' > 1% Then Set Scene 'Speaker Lights' Off Else Set Scene 'Speaker Lights' Off I have a suspicion that may not work at all.This is dependent on the order ISY boots up in and I don't think it knows device statuses until much later after running the "Run at startup" programs. More investigation required. IIRC there may be a startup order list on the ISY wiki. Michel posted it once a long way back. I have Hue bulbs that do that, and I just turn them off (no conditions) knowing they will alwways be on after a power failure. That has worked in the middle of the night a few times. Very annoying.
Athlon Posted April 1, 2017 Author Posted April 1, 2017 The lights turn off after start up, however they will not stay on using either '> 1%' or 'not off'. I'll play around with this and post a solution if I can figure it out.
Athlon Posted April 1, 2017 Author Posted April 1, 2017 I've tried a couple of different ways to do this, but still no success. With my latest scheme I broke the program into 2 programs, 'Startup1' & 'Startup2'. The lights go off on startup, but they also go off whenever I turn them on. Startup1: Startup1 - [ID 0021][Parent 0001][Run At Startup] If Status 'Speaker Light 1' is not Off Or Status 'Speaker Light 2' is not Off Then Run Program 'Startup2' (If) Else - No Actions - (To add one, press 'Action') Startup2: (which I have disabled) Startup2 - [ID 0020][Parent 0001][Not Enabled][Run At Startup] If Status 'Speaker Light 1' is not Off Or Status 'Speaker Light 2' is not Off Then Set Scene 'Speaker Lights' Off Else Set Scene 'Speaker Lights' Off
Athlon Posted April 1, 2017 Author Posted April 1, 2017 In reading my post, I see where I still have 'Run At Startup' enabled for both programs. I forgot to turn that off in my second program. I'm going to turn that off and try it again.
Athlon Posted April 1, 2017 Author Posted April 1, 2017 I'm stuck - with my current programs the lights will not stay on after they shut off when the ISY reboots. Current programs: Startup1: Startup1 - [ID 0021][Parent 0001][Run At Startup] If Status 'Speaker Light 1' is not Off Or Status 'Speaker Light 2' is not Off Then Run Program 'Startup2' (If) Else - No Actions - (To add one, press 'Action') Startup2: Startup2 - [ID 0020][Parent 0001][Not Enabled] If Status 'Speaker Light 1' is not Off Or Status 'Speaker Light 2' is not Off Then Set Scene 'Speaker Lights' Off Else - No Actions - (To add one, press 'Action')
paulbates Posted April 1, 2017 Posted April 1, 2017 I think why you're stuck is that the ISY doesn't know how to tell the difference between It accidentally came on You meant for it to Here's are two different ideas: Disable the 'Startup' program, but leave it set to "Run on startup". That should cause the program to run on restart (power fail) but not as a normal course of ISY operation. If the above doesn't work, Set a variable when a switch actually activates the scene turns on. Then check the variable with your "starup" program. Do not use "Init to" with this variable, that way it goes to 0 on a power fail and the starup program will know. Paul
Athlon Posted April 1, 2017 Author Posted April 1, 2017 Thanks Paul - you must have posted while I was trying different things. I got it to work! The lights come on when power is restored. The ISY turns them off when it starts back up. A minute later all programs that control those lights work normally. Startup1 - [ID 0021][Parent 0001][Not Enabled][Run At Startup] If Status 'Speaker Light 1' is not Off Or Status 'Speaker Light 2' is not Off Then Run Program 'Startup2' (If) Wait 1 minute Disable Program 'Startup2' Else - No Actions - (To add one, press 'Action') Startup2 - [ID 0020][Parent 0001][Not Enabled] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Scene 'Speaker Lights' Off Else - No Actions - (To add one, press 'Action') The use of the 'Disable Program' function did the trick!
Teken Posted April 1, 2017 Posted April 1, 2017 For the benefit of the forum members can you list out the hardware and production date of this Insteon LED bulb. You already noted the firmware as being v.48 from the ISY Series Controller. Normally the bulb will recall the last known state from either on vs off. There is a parameter which if invoked tells the bulb to return to a on state when power is applied. These options are software based, and can only be changed if the controller supports them. Unfortunately, UDI has not decided to support these critical features along with many others that impact several other Insteon products. There is no good reason for such features and options to be left out when they are clearly noted in the developers API notes! This only hobbles the product and frustrates the end user when problems like these arise . . .
Athlon Posted April 1, 2017 Author Posted April 1, 2017 @Teken - happy to do so - is that info on the bulb? I bought them from Smarthome about 3 months ago.
Teken Posted April 1, 2017 Posted April 1, 2017 @Teken - happy to do so - is that info on the bulb? I bought them from Smarthome about 3 months ago. Yes, its a little white sticker on the base of the bulb. You should not be surprised if it fell off though and isn't present!
Athlon Posted April 1, 2017 Author Posted April 1, 2017 Intertek 3193579 R4.2S 2016 There's also a warning about not using these under water, but after reading some of your posts in other threads I assume you already know that.
Teken Posted April 1, 2017 Posted April 1, 2017 Intertek 3193579 R4.2S 2016 There's also a warning about not using these under water, but after reading some of your posts in other threads I assume you already know that. LOL . . . As an aside my friend had her little daughter over a few nights ago. I had left the monitor on and running and when I came back the little girl was trying to smash my screen in! I later found out she saw your little bug running around the screen and this is why she was smashing it to try to catch and squish it! You owe me a $350 new HD monitor . . . LOL
Athlon Posted April 1, 2017 Author Posted April 1, 2017 I can't stop laughing - tears are running down my face....
Teken Posted April 1, 2017 Posted April 1, 2017 I can't stop laughing - tears are running down my face.... Yeah mine too when I saw her palm marks in the screen . . .
Recommended Posts
Archived
This topic is now archived and is closed to further replies.