larryllix

You stated earlier that you run two routers with different network page addresses on them. I doubt they will ever talk to each other. Most routers cannot support 512 addresses. I haven't found you stating what your network subnet mask is and most routers will not allow you to cross IP address pages like that. If you are running two routers and both are wireless with their WiFi radios turned on you are going to have problems unless one is configured as a bridge. Your Linksys router may not have that capability. If the notifications are your main problem perhaps a call to UDI tech help would likely get this sorted out for you in a a few minutes. Have you tried that, yet? I know you are frustrated but once things start to click it happens at an accelerated rate with lots of smiles...and some more frustrations sometimes. Hate to see you give it up.

If you want the light density at a given point you have to detect it at that spot.

I found that my X10 MS units can turn on an Insteon LampLinc quite quickly but the ISY would never know about it. The output of the MS is the only indication something has happened. A program has three (obviously) sections. The "If" section contains TRIGGERS and some can be turned into conditions to also control the program execution path. When a trigger event occurs the whole If section gets evaluated. Depending the outcome of the logic appraisal of the whole If section the 'Then' or the 'Else' section is executed. One section is always executed for every trigger event. So if you have a STATE variable "Wantit "and a WallSwitch. If WallSwitch is switched On AND Wantit = 1 When WallSwitch sends a command that it has been turned on and Wantit is 1 then the 'Then' will run. If Wantit is not 1 the "Else" will run. When Wantit changes from anything else to 1, Wallswitch will never be just switched on at the exact same instant so "Else" will always run. Yeah it takes some swallowing to get used to it but it works well in most cases.

Agreed. The program should have been true for 30 minutes. The difference between the time range "to" trigger (sunrise plus 1 hour) and the OR clause (sunrise plus 30 min). I think it took LeeG to state this more clearly.

Your first post you stated "Locally my ISY has sunrise posted as 7:30:30 AM and the time was 9:00 AM when I checked this again this morning to find it didn't run." The Program Summary only shows the last program state ran and the time it ran. The Program flag in the tree directory only shows the last run "Then" or "Else" section also. If you "to" time trigger triggers the "else" clause that is all you can see at 9:00 AM. I believe your Or condition clause (in question) did run and change the variable to 0. You just can't see the history at 9:00 AM. Do you have an X10 beeper? Or create a lamp blinker program as a test indicator and insert it into your "then" clause so you see the time it executes tomorrow. Then you may catch it in the act. No sleeping in for the wicked.

Yes. Are you sure it didn't? If you looked after the last run "else" how would you know? IOW: do your lights behave the way you want them to and the observer just doesn't see it? Edit: The variable should not lie and be a good indicator as it should stay where it is put. hmmmm... are we back to the fridge light going out when we close the door problem?

Nice stu! Good reminder. I had forgotten those calendar options were even there. I have only used them once as the year has no wild card option so the user has to update them every year or they won't work. I guess a series of Season based time blocks ORed together covers some compensation of declination of the sun travel path (ecliptic). Now can we compensate for full solar eclipses with some ISY program math?

I have been misreading your intent on this one but I think I have the function clearer now. I see this (now) program as the second half of a flag (Dark) controller that only turns the flag Off when it is light in the morning. This line "To Sunrise + 1 hour (same day)" evaluates to run the "Else" section at 8:30:30 AM When you check the program status later in the day (9:00AM) the program may have ran the "True" section but the running of the "Else" would supersede all record of it running true. My guess is that you will need to remove the "to" time trigger in your "If" section. It cannot function as you have no "Else" section code. That is all the "to" times do when used as triggers.

OK I must be misinterpreting your desired function here. Are these times supposed to only flag a small section of time (each morning) when your Dark flag is false? ($s.Dark = 0) Perhaps you can explain the function in more detail as you see and want it.

Maybe??? You have the Insteon MS units. They don't detect "Light" conditions with On status . They detect "Dark" with On status. Take your MS into a darkened closet to test function. The response is about 3-5 minutes IIRC.

Just some observations. You have "sunrise" in both the "to" and "from". Is this is a typo here or just a morning program trigger? If your luminance sensor changes status and runs the "else" section while the 5 minutes are timing the sequence will be cancelled. Why would we need or want the additional 5 min delay?

I have 10 MS with light/dark sensors that report in and base many of my dark based conditional on a constant. $cDARK_THESHOLD. Note that the counter has a saturation point less than the number of inputs so it can self correct for comm problems. If ( Control 'Afternoon Bedroom / Dark.Afternoon BR' is switched On Or Control 'Evening Bedroom / Dark.Evening BR' is switched On Or Control 'Gathering Room / Dark.GathRm' is switched On Or Control 'Library / Dark.Libr' is switched On Or Control 'Lower Landing / Dark.LLand' is switched On Or Control 'Master Bedroom / Motion.MBR / Dark.MBR' is switched On Or Control 'Mudroom / Motion.MudRm / Dark.MudRm' is switched On Or Control 'Rec Room / Motion.RecRm / Dark.RecRm' is switched On Or Control 'Utility Room / Dark.Utility' is switched On Or Control 'Workshop / Motion.Shop / Dark.Shop' is switched On ) And $Dark_Counter < 7 Then $Dark_Counter += 1 $Dark_Counter Init To $Dark_Counter Else - No Actions - (To add one, press 'Action') Libr and Util are not likely to ever indicate Not Dark. If $Dark_Counter > $cDARK_THESHOLD Then Wait 1 second Set 'Gathering Room / PotLight over Table' 5% (Backlight Level) Wait 2 seconds Set 'Gathering Room / PotLights over Chairs' 7% (Backlight Level) Wait 2 seconds Set 'Gathering Room / PotLight over Desk' 5% (Backlight Level) Wait 2 seconds Set 'Foyer / Front Porch Lights' 5% (Backlight Level) Wait 2 seconds Set 'Gathering Room / PotLights over TV' 5% (Backlight Level) Wait 2 seconds Set 'Mudroom / Mudroom Potlights' 5% (Backlight Level) Else - No Actions - (To add one, press 'Action')

Do you have your IP address of your ISY locked down in the DHCP table in your router? If your dynamically allocated IP in your ISY changes, allowing the old IP through, it will not help.

Legacy support shows company "heart" when presented as "also supports older".

Nice! No mention of X10 as an additional system brag.

OK some basics you may need to understand. Status is a program trigger only when the status of a device changes. Switches is a program trigger only when a signal is sent that can change the status of a device whether the status changes or not. eg: A lamp is off. status = off A switch sends a lamp on. Lamp turns On. Switches On triggers, Status On triggers A switch sends an on signal. Lamp is already On. Switches On triggers, Status On doesn't trigger Integer and State variables have a similar situation Integer variables do NOT cause program triggers. State variables cause triggers unless the program is disabled. In your first program you use a state variable that can stop your program 'Then' execution when it changes And ( $KEYPADLINC_D_CABINET_LIGHTS_OFF_TIMER is 0 ) When this State variable changes to not 0 (=1 below) "Else" will immediately run and 'Then' will immediately stop running. $KEYPADLINC_D_CABINET_LIGHTS_OFF_TIMER = 1 Run Program 'Keypadlinc_D_Cabinet_Lights_Off_Timer_Reset' (Then Path) The last line may never run.

Halogen is another form of incandescent. No noise generated.

On eBay almost every bulb is advertised a CREE now. The white LEDs used are made by Cree but the bulbs are made by every Tom's Dick that's Harry.

Do you factory reset every device before linking it into your system?

Nice. Keep in mind the "off" times should not overlap with the other light cycles or you may get unexpected "Off" times. This can be a gottcha' for random time®s especially.

The only port forwarding I have is in my router. A router has a firewall that doesn't let anything through that isn't initiated inside, and by, my house internal LAN equipment. Port forwarding is a feature, in a router, that allows certain data through when it's initiated externally from the Internet side . So if my ISY has been assigned an IP address of 192.168.0.28 by my router (DHCP) and my router has been assigned an IP address of 123.456.7.89 on the Internet by my ISP (DHCP) then my port forwarding may look something like this. convert external IP 123.456.7.89 on port 8099 (chosen arbitrarily by you) to internal 192.168.0.28 port 80 (chosen inside ISY) This will allow external browsers (and Admin Console, Mobilinc) traffic using the URL http://123.456.7.89:8099'>http://123.456.7.89:8099 to be converted by your router and dumped on your LAN as http://192.168.0.28:80 and get through to your ISY. This all works very well while your IP loaned to you by your ISP doesn't change. Usually when there is a power outage your IP address is re-issued and now your external software is lost, doesn't know it's way home, and cannot connect to your new external IP address. In comes the DDNS (Dynamic Domain Name Service). Most newer routers support DDNS with built in firmware that keeps a cloud service notified what IP address it has been assigned externally (by your ISP). Instead of your cell phone talking to http://123.456.7.89:8099 and being lost, it talks to http://www.YourRouterName.noip.com:8099, which keeps track of what IP your router is at dynamically, and just passes the data through to it. My Netgear router comes with a free service to do this. They spammed me a few times at first but it works well. In my case, with my ISP, I could survive without my free cloud DDNS service if my power never failed for more than a few minutes.

Unplug them and find out. Most "surge protectors" do not protect against surges at all by definition. They are mostly spike clippers that short out high voltage spikes at the top of the waveform. These are probably doing nothing behind a filter that should remove most of the them anyway. However, there are some that actually smooth out spikes and glitches with real filtering components and they can be a problem to Insteon signals.

Also note that LeeG's suggestion has nothing in the "Else" section? At 10:29:59PM the "else" is going to execute due to being triggered by the time end and the whole "if" logic evaluating to false. At the end of the "Then" section you can add "run Program_name (else)" if you want the folder icons to show colours reflecting their last Light Bulb control states. The MS will always show "On" after adjusting that setting.

"Insteon Protocol Bible" definition. Besides, which unit would ACK and say the transmission was received OK? I have an "Every Light" scene that contains a few dozen devices. If the operation is very important use an individual command. It could be done but see sentence one.

Sounds like you are doing OK with the whole thing! Bravo! Another tip. Most ballpoint pen ink can cover Great Stuff splotches on blue jeans but have to be redone after several washes each time, I have a few of them. Keep the varsol or paint thinner handy and have a second party check you over immediately after use.