larryllix

OK I'll try to start out simple and add from there. You will not be able to do any dimming if you already have the MS and your lights in a scene. This is now out of ISY's hands but there is a way to do it as described in my other post above. You didn't say what didn't work for you. Get rid of the first two programs They aren't needed with your bottom one added. Take out lines that refer to them I added a fail safe 2 hour timer in case you forget the lights are in override. Watch the parenthesis placements. They are important. Your MS needs to be set to never send Off. Kitchen Cabinet Motion - [iD 0014][Parent 000A] If Control 'Kitchen / Motion-Sensor' is switched On Then Disable Program 'Kitchen Cabs ON?' Set 'Kitchen / Kitchen Cabinets' 75% <------- this doesn't work 'cause MS scene will keep changing level without ISY Wait 5 minutes Set Scene 'Kitchen / Kitchen Motion Night Light' Off Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------- Kitchen Cab Switch Override - [iD 000D][Parent 000A] If ( Control 'Kitchen / Kitchen Cabinets' is switched Fast On Or Control 'Kitchen / Kitchen Cabinets' is switched On Or Control 'Kitchen / Kitchen Cabinets' is switched Fade Up Or Control 'Kitchen / Kitchen Cabinets' is switched Fade Down ) AND Control 'Kitchen / Kitchen Cabinets' is NOT switched Fast Off <---these run Else for Fast Off & Off AND Control 'Kitchen / Kitchen Cabinets' is NOT switched Off Then Disable Program 'Kitchen Cabinet Motion' Wait 2 hours Set Scene 'Kitchen / Kitchen Motion Night Light' Off <-----lest yee forget with usual automatic Enable Program 'Kitchen Cabinet Motion' Else Set Scene 'Kitchen / Kitchen Motion Night Light' Off <----turn the light and scene off from switch too Enable Program 'Kitchen Cabinet Motion'

I have several Cree bulbs that worked flawlessly at first but after a few month began to flicker somewhat when dimmed certain levels.

Now that your thinking logic fog is clearing it is easy to see how this can be simplified back into one program, if desired. Lighted Entry - [iD 0003][Parent 0001] If From Sunset To Sunrise (next day) And Status 'Garage Door-Sensor' is not On And Elk Zone 'Garage Door' is Violated Then Set Scene 'Entry Light' Fast On Wait 15 minutes Set Scene 'Entry Light' Fade Down Wait 5 seconds Set Scene 'Entry Light' Fade Stop Else - No Actions - (To add one, press 'Action').

Would ISY re-ask for an IP address if the router is slower booting and ISY didn't get one on boot-up? In the case it didn't rebooting the router may work. Do you have remote access to the router?

You need all three to perform #1 basic on/off functions, #2 The manual override = lock on, #3 change brightness for different parts of the day. Substitute your own component names. I have just called these LIGHT, MS and MS/LIGHT for the scene First you need to have a scene, you create in ISY and include your MS as a controller and your kitchen light as a responder. This also assumes you have a main light in the kitchen controlled by a SwitchLink wall switch (connected to the main kitchen cabinet lights) for a manual control, and an MS and you want them both to control the same light. LIGHT.auto (enabled) -------------- If Control MS is switched On Then Wait 45 seconds <---------------make it 5 minutes for a kitchen Run this program (Else Path) <------ turns off the light and displays program as red colour for Admin Console Else Set Scene MS/LIGHT Off Manual override (enabled) ---------------------- If ( Control LIGHT is switched On <---- add other devices to manually override the auto program using 'OR'... 'if On' ) And ( Control LIGHT is not switched Off <-----switching off runs else and stops then <-----add in other manual off devices using 'OR'..... 'is not Off' ) Then Set LIGHT Fast On <----makes it 100% brightness and fast Disable Program 'LIGHT.auto' <-----no more MS activations while in manual control Disable Program 'Light Level adjust' <-----no more auto level changing from program below In Scene 'MS' Set Light to 100% (On Level) <---- further hits on light stays 100%, watch MS name is in scene pulldown Wait 2 hours <------just in case you forget it is in manual Run Program manual override (Else Path) <---jump to else below Else Set LIGHT Off <----------------manual control is over = turn it off Run Program 'Light Level adjust' (If) <----- set the scene dimming levels back dependant on the time of day Wait 1 second <------ let it finish Enable Program 'Light Level adjust' <---- OK now we want the levels to be self adjusting again Enable Program 'LIGHT.auto' <------------- now we want the MS to control the light again Light Level adjust (enabled) ----------------------- If From 10:30:00PM <- pick level change times To 9:30:00AM (next day) Then In Scene 'MS' Set LIGHT 5% (On Level) <----watch the name of the LIGHT not being a scene but in scene pulldown list Else In Scene 'MS' Set 'LIGHT' 70% (On Level) <-----same as above

Here is how I have accomplished this This is the basic MS lamp control program. A scene link between the MS and lamp already exists so the response is immediate. MBR Lamp.auto - [ID 009D][Parent 000A] If Control 'Master Bedroom / Motion.MBR' is switched On Then Wait 45 seconds Run Program 'MBR Lamp.auto' (Else Path) Else Set Scene 'Master Bedroom / MBR Passtrough' Off . . This is the manual override program from a remote. Note I still have a 2 hr. timer to shut off in case you forget and walk away or fall asleep. It also has code to shut down and revive the third Lamp Level Adjust program. MBR Lamp.manual - [ID 0038][Parent 000A] If Control 'Master Bedroom / MBR KeyPad.A' is switched On And Control 'Master Bedroom / MBR KeyPad.A' is not switched Off Then Set 'Master Bedroom / MBR Wall Lamp' Fast On Disable Program 'MBR Lamp.auto' Disable Program 'MBR Lamp Level adjust' In Scene 'Master Bedroom / Motion.MBR' Set 'Master Bedroom / MBR Wall Lamp' 100% (On Level) Wait 2 hours Run Program 'MBR Lamp.manual' (Else Path) Else Set 'Master Bedroom / MBR Wall Lamp' Off Run Program 'MBR Lamp Level adjust' (If) Wait 1 second Enable Program 'MBR Lamp Level adjust' Enable Program 'MBR Lamp.auto' Lamp will get direct hit by MS so adjusted scene level so it can't be noticed. . . Program to adjust levels for different times of the day. A 60W bulb glaring you in the face at 2:00 am is not nice. Note: This system uses three levels of brightness. Manual uses 100%,automatic uses 15% and 70%. MBR Lamp Level adjust - [ID 0084][Parent 000A] If From 10:30:00PM To 9:30:00AM (next day) Then In Scene 'Master Bedroom / Motion.MBR' Set 'Master Bedroom / MBR Wall Lamp' 15% (On Level) Else In Scene 'Master Bedroom / Motion.MBR' Set 'Master Bedroom / MBR Wall Lamp' 70% (On Level)

Did you mean "SecureView"? Does this mean the cam can trigger a variable in ISY via REST? Model number please?

If the camera doesn't have that feature I don't see another method.

There is nothing in a program that causes a folder condition to be evaluated. If a folder contained 15 programs which one would cause reevaluation of the folder logic. Only state variables cause evaluation of usage conditions. The folder condition is only evaluated in advance when triggered from a variable change, not when a program runs.

Change your variable to a state variable and try it. Integer variable changes do not trigger reevaluation.

I doubt that an integer variable would work but I don't use folder logic. The ISY system is not going to continuously evaluate a condition but rather an event has to trigger ISY to evaluate the condition and set the true or false result. I dont know why folder logic work any different than program if logic. I am on mobile right now so I can't easily give you a reference to the wiki or manual.

Should this variable not have to be a state variable to trigger the folder state to false?

I have always had the lights on in the bathroom as a problem since starting HA back in the 70s. When your house has automatic lights everywhere except a few (eg. in the bathroom), guests, especially, can't be expected to remember what lights they turned On and to turn off again. I remember overhearing one of my teenage kids telling his guest, "If you didn't turn it on, then don't turn it off" Polterguests are the worst for that.

ISY and each device must be linked together before they can play together. After linking, if you operate any device ISY will know about it, and also, each device can be operated from ISY manually or by program control.

Some manuals will call this "factory reset". This is always a good idea with any new Insteon device before using it with ISY. They can come doing things that are not supposed to be possible. I have had a few now that did weird things. When you create a direct link between two Insteon devices and then create another scene inside ISY you have created two different scenes/links inside the end device. Most devices can support up to 256 scenes in each device. It is best to create them only inside ISY and then have ISY install them. You keep control of the links, it makes it much easier to do and ISY knows what is happening when devices talk to each other.

Sure enough, but I didn't understand your retort because you apparently didn't know all the parameters I needed to make me understand your point until we bantered . Yeah it is definitely an art reading between the lines.

It should be mentioned with the program above (LeeG) technique that something has to initiate the program the first time to get a notification or 'Send X10 'A10/All Lights On (5)'' by starting the Wait timer. This can either be a Heartbeat, to kick things off, a call in the initialisation of ISY (after power up), or the user running "Then" section manually. If the program is not running true then neither of the three ever happened.

Usually people asking for help are doing so because they don't even know what questions to ask.

This (Setpoint Up 1°) has never worked with my two different versions of the 2441ZTH (note 'Z') with ISY. I haven't tested this with the newer releases 4.3.1 ++.

You would require the Network Module installed in ISY. Then you can send almost any style command you desire.

A blinking LED on an Insteon device usually means it is still in linking mode and will not report regular operations to ISY. A blinking LED on an Insteon device usually means it is still in linking mode and will not report regular operations to ISY.

Then comms to ISY are OK. I don't know what a red flasher on a door sensor means. Did you read the online manual? The paper that comes with it is almost completely useless so find the one on the SmartHome,com site included with the sales info. save it in a folder. They can disappear.

ISY doesn't use TCP to talk Insteon. Your error looks like it is between your app and ISY. Have you changed locations between your LAN and WAN IP addresses during communications?

I believe I have stated this before but... HomeKit should accelerate the use of ISY HA as users sadly invest lots of bucks in hardware only to find problems and want independence from the cloud. Meanwhile they will have purchased a few Insteon devices and the swing over to ISY should be a natural progression. Why did SH never create a controller with advanced logic copying the same no HA path as X10 went? Was it to leave room for third party developers, like UDI, and Apple, to "partner" with their technology? Originally I purchased two Hubs for my son and myself. After 20 minutes of playing I realised from my old X10 experience that I would be bored with the Hub within two days. Adding cloud advanced logic, actually making the system HA would drive me bonkers. I don't like the delays in ISY making a decision about my lights after seeing motion. Imagine the cloud making that decision in the middle of the night? The light might be on after you pee and are heading back to bed. I am not going to wear a watch to bed and my mobile phone is never close by when I sleep. My guess is somebody pushed Apple's buttons promising HA glory. "Welcome to out home! Here are your slippers and wristwatch so my home can spy on you." Geesh I find my bedroom lamps disconnected everytime my guests leave already. Not everybody likes HA. Not even my kids that have Internet addictions.

With all the pure white Insteon devices, all white IPhone, and white background the photos look like something from heaven in the movies. I am surprised the iPad doesn't have big wings coming out it's backside but then that could limit sales to Christian countries. ha-ha. The knowledgebase link on the SH page is a dead link. Good one! SH does it again.