larryllix

Doesn't this just sound like a more modern router is on the horizon?

Check your wiring, especially where you may have disturbed connections wiring your IOLinc. It is very doubtful that stray RF emissions could activate a garage door opener with the rolling security code features used these days. I have owned garage door openers for over 28 years and never experienced one open by itself. We have left them open by mistake a few times though. Early electronics failure maybe? Time will demonstrate that one. As stated above it is doubtful it came from your ISY. I would be eyeballing the wiring around the terminals with a strong light for stray strands of copper or connections that are loose and moved. The IOLinc has some quite small terminations to watch out for. Another definite possibility is your close jamming detection. These can be current or mechanical detection methods, adjustable by the user, need to be checked every few years, and with some wind or door movement trigger the door to reverse it's perceived closing direction, depending on internal logic. Check for a spider making a winter's nest in your beam units or lens..

I a also using Java 8 u25 on Win 7 x64 with ISY 4.2.17 and it works fine. I would say it works more reliably than my Java 7 on another computer. Java 8 has self-updated more than three times now and now self-cleans all old versions of Java. Welcome to the 90's, Java!

The reason the two 120v legs, in a building, fed by a single-phase electrical grid distribution transformer, or not, cannot be connected together is because they are 180 degrees out of phase with each other, making them different phases. Most people know them as "phases" because they are different phases. Usually the two phases are fed from a single phase transformer referring to the high voltage primary of the street distribution transformer but that is not the area of the electrical system being discussed here. The two phases in a residence may also be fed from two different phases on a high voltage grid system making them 120 degrees apart. The constant injection of cultural based terminology does nothing to further discussions and is only semantics. "Phase" is a commonly understood and accepted term for discussions, regardless of the high-voltage source, and requires no further clarification. "Leg" or "side" require clarification or further context to understand what is being referred to. In the flow of this conversation either would be understood by others.

I have to wonder that a new firmware version caused the speed to change on something.

You should go into your router setup and find the Mac address for your ISY and assign a permanent IP address for your ISY in your DHCP table to assign it the same IP every time. Every time your ISY reboots it will get the lease of that IP address and it will work with your router. Now when you do Port Forwarding in your router you will always know the ISY IP and Mac address, depending on how your assignments work in your router table. Pick a port for your ISY to "punch through" your firewall. The default is 443 but I used a higher address (4 digits) to make it less hackable. This should be the same port picked inside your ISY for external/secure access. Shut off your WiFi on your cell phone to force and prove external connections. Run MobiLinc Open your MobiLinc setup and set the https:// address to the IP address your ISP leased to you. The IP address (not 0.0.0.0) and the Port address must both show in the "About" info in your ISY or your ISY does not have External Internet Access turned on. Set your IP address and the port you opened up in your router Forwarding. Click Link update at the bottom of the MobiLinc page after entering numbers. You should set access to secure (https = Hyper Text Markup Protocol Secure) only. Once connections are established turn MobiLinc connections back to automatic and turn your WiFi back on in your cell phone.

If it doesn't (trigger all seasons) many people have been spending way too much time, writing complex and massive programs, and asking to implement wildcards in dates in ISY updates. By the textual logic demonstrated it shouldn't be seasonal but it wouldn't be the first time I have been surprised by some ISY syntax.

Some observations - you have no external IP address in ISY: Turn on Internet access. - in MobiLinc you are using the internal address of your ISY for the external connection. Use 0.0.0.0 until you get the Internal one working. Turn off automatic selection and select local only for now. Once that works enable external https stuff. I always have to disable my cell's WiFi to test that. - your ISY firmware and GUI versions do not match. You should update your ISY with the latest version to get any new support offered and be compatible. ** Take that second line out of your router!! That allows anybody access to your LAN from port 80 to 443 through your firewall .Basically a non-existent firewall with invitations sent out here. Not a good thing as much of you internal things won't even be passworded. Also you may want to blur pictures or change some of the IP information posted here when you are done for future hacking made easy.

No. One simple or compound logic "If" per program. With no date or time wildcards in ISY, yet, you will have to update your programs ever year. Create a folder and drop them all into that folder for tidy.

Status 3 indicates that the heartbeat monitor program is not running. not a leak sensor problem. Without rehashing all the program logic in my head IIRC the watchdog program has to be forced to run the first time by another program that gets executed on power up of the ISY. Perhaps this option was not set to accomplish that.

Send beer!

I run Java 8 on a Win 7x64 system and also Java 7 on a Win 7x32 system. The Java 8 system has less problems with the Admin Console but mostly the same type of problems with the app sleeping or being backgrounded for a while. Java 8 has been updated on my system a few times now.

Ouch! I have never looked inside one but aren't these units all 0.05" pin spacing and with the leadless solder being promoted today I wouldn't even attempt it.

Your parentheses are in the wrong places. Try this If ( X10 'A15/Off (11)' is Received Or X10 'A/All Units Off (13)' is Received Or X10 'A/All Lights Off (1)' is Received ) And $KEYPADLINC_D_CABINET_LIGHTS_OFF_TIMER is 0 In Boolean logic the AND operator takes precedence over the OR operator so that your last X10 trigger was the only one being ANDed with the ....TIMER is 0

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?