Xathros

Thanks so much Wes. That is exactly the kind of info I hoped you would provide. -Xathros

The 3-5 minutes is an extreme case and most ADSL connections come up in easily under a minute but its not uncommon to see these delays. I suspect in a restored power situation its worse due to all of the ADSL modems in the area trying to register on the DSLAM at once creating a flood of traffic and possibly noise/crosstalk on some of the longer copper runs. I can usually count on 8-10 support calls after a power outage most usually fixed with a "Did you restart the computer, printer, set top box etc. ?" -Xathros

Glad I could be of assistance. -Xathros

Clarence, Michel- There may be a bit more to compatibility than that. None of the IP cameras that I have seen speak Insteon and are therfore not really Insteon compatible contrary to Smarthome's marketing fluff. They claim compatibilty based on the fact that their SmartLinc/Software package has IP Cam support for their cams over ethernet (Not insteon). All of that said, If using the ISY's Network Resources module, some camera interfaces may be friendlier than others. I wonder if Wes (of MobiLinc) could comment on this since he has some recent experience with a large number of cams. I worked on beta testing the MobilInc IP Cam plug in for Wes. He indicated that the Smarthome cams were rebranded Foscam cams which he uses and was happy with. My Smarthome cams arrived yesterday but I haven't had an opportunity to install and test them yet. I will follow up in a day or two. -Xathros

Hi Phil- Here ya go: Test Schedule If $sBreaker_Notify is 1 Then Repeat Every 1 hour Run Program 'BreakerTest1' (If) Run Program 'BreakerTest2' (If) Else - No Actions - (To add one, press 'Action') I used a state Variable to allow me to enable/disable the testing easily. This also allows me to force a test with MobiLinc by toggling this variable off/on. Or I could just run each of the test programs manually as well. BreakerTest1 (disable this program and BreakerTest2- They will be called by the schedule and do not need to run otherwise) If Status 'Basement / Alyssa's Room / Alyssa's Room' is not Responding Then Send Notification to 'My Cell' Else - No Actions - (To add one, press 'Action') Make a BreakerTest2 for the other circuit just like BreakerTest1 Hope this helps. -Xathros

hbsh01- Setting the static address at the ISY and outside of the routers DHCP pool WILL fix this issue. This is how I have mine configured and I have never had a problem reaching the ISY from inside or out as long as my router is up and running. Michel- Here in rural VT, many of my customers are served by ADSL connections. Depending on the CPE equipment provided and distance to the DSLAM it can take 3-5 minutes for the ADSL to establish a connection to the DSLAM and retrieve an IP. Some of these devices won't offer DHCP until they have established the connection back to the DSLAM leaving the local network in limbo in a restored power scenario. Even my cable modem won't offer a real IP to my router until it has established links up/dn with the cable co's head end. That can take upwards of a minute sometimes. -Xathros

I believe (With the possible exception of what we are testing above) that "Next Day" is always the Day after Today when the IF evaluates to True. So if your program looks like: If On Wed, Thu, Fri From Sunset + 4 hours and 1 minute To 11:55:00AM (next day) Then Set Scene 'Living Room / Test' On Else Set Scene 'Living Room / Test' Off Then the scene would be on from early Thrs morning till 11:55 Thrs morning then the same for Fri and Sat based on a sunset time of less than 4:01 prior to midnight. -Xathros

hbsh01- Good question! My gut feeling says Saturday but I will have to run a test of this scenario to be sure. It's possible that this will never run since Sunset+4:01 is Sat and the first condition says on Fri. I have built a test for tonight and I'll let you know what happens. EDIT: The following seems to indicate that it WILL run early Sat morning: -Xathros

Also, in your Java settings, do you have a proxy configured ? If so, try setting that to "Direct Connection" and see if it makes a difference. I'm not sure exactly where to look on Win7 but on my MAC, it's in the Java Preferences, Network Tab, Network Settings Button. I would imagine it's something very similar in the Java Control Panel on Win7. Hope this helps. -Xathros

What Antivirus / Firewall software are you using ? -Xathros

Wes, the creator of Mobilinc, was telling me that these were just re-branded Foscam cams. They do appear to be the same from the pictures and specs. -Xathros

I'm afraid that the "Insteon Compatability" is referring to HouseLinc's ability to view and manipulate the IP camera over the IP network. I don't believe there is any actual Insteon Power Line or RF capabilities in this unit. I skimmed the PDF manual and saw nothing at all indicating real Insteon features. I'd be very happy to be wrong as I had similar thoughts to yours when I read that bullet point. Regardless, I will be getting one of these soon and will update here if nobody else confirms this before then. -Xathros

I too suffer with horribly unpredictable AT&T SMS delays. Not just from the ISY or even the Email to SMS gateway but straight SMS sent from other AT&T phones. It's AT&T's network.I've found that if there is a MicroCell involved, the situation is worse and often messages won't deliver until I have left the vicinity of the MicroCell and pick up a real cell tower instead. Sometimes it works as it should. No rhyme or reason. All of that said, I have found that MMS messages are far more reliable on the AT&T network though still not immune from late delivery and as an added bonus, they all arrive from the same address rather than random numeric addresses. MMS can be sent through the AT&T Email to MMS gateway at: your_10_digit_number@mms.att.net I believe this is due to the fact that MMS messages require an IP Data connection to AT&T central servers rather than a cellular voice control channel connection to a distributed network of towers that may or may not be aware of pending messages. Just a somewhat educated guess. Anyway, Hope this helps. -Xathros

I do believe that this is the amount of time the ISY will look back into the past on power up to find items that need to be "Caught Up" to current. Without this, how would the ISY know where to begin catching up the schedules ? -Xathros EDIT: Here is what the Wiki has to say: Catch up schedules at Restart - When this box is checked (default) the ISY will attempt to run all programs that are time dependent beginning at midnight until the present time. Missed Schedule Grace Period - If Catch up schedules at restart is not checked or if a program is not run because the ISY is busy this will check for programs that were scheduled to run from the period specified until the present time. Default is 15 minutes.

Awesome! Excellent post! -Xathros

OK. Your Java cache is not clearing or the link you are using is pulling a 3.2.6 console from somewhere other than your ISY. Do you have another user account on your PC ? If so, log out of yours and into the other account and try to access the ISY at http:///admin and see what we get for FW/UI versions. Again replace with the actual IP address of your ISY. What are the first 2 sections of the ISY's IP ? 192.168 ? -Xathros

It may, but, it is likely not necessary to solve your original problem. The important thing is that the firmware version and the user interface versions match exactly otherwise you will get unexpected results in unpredictable ways as we have seen already with the traces LeeG asked for. If you plan to add any of the newer Insteon devices that use the new I2CS protocol, you will need to upgrade the firmware and UI before you will be able to use those newer devices with the ISY. At this point, lets just get what you already have back to working order. If your FW and UI versions are now both saying 2.6.18, then we have solved the first part of the puzzle and you can resume trying to link your new Remotelinc and update your other 2 devices. Please run a trace at Level 3 and post the trace of that for LeeG to review in case of link / update failures. -Xathros

Are you getting 2.6.18 for both lines now ? or do you still see 3.2.6 for the UI ? If 2.6.18 on both then we are making progress in the right direction. Don't worry, we will get this figured out. -Xathros

That is the right procedure. Have you already tried to upgrade the firmware to 3.2.6 ? -Xathros

So just to make sure, you cleared the Java cache using the Java applet from the Windows Control Panel Correct ? Not just clearing the browser cache. If so, I'm at a loss as to how you are getting the 3.2.6 UI from the ISY. After clearing the cache and then accessing the link, do you see the Java logo spin for a bit while the browser re-downloads the admin console from the ISY or does the console just open up right away and prompt for your user/pass ? -Xathros

Did you clear your Java cache first ? If you did and you are accessing using the link above, your UI should be reading 2.8.16 as well. What OS are you running on your computer ? -Xathros

Thanks. I'll find and bookmark that page. I do remember seeing it a while back and now I vaguely remember it being "relay devices first" but some how turned that into "Switchlink devices first" in my mind. Thanks for setting me straight. -Xathros

mdyod- You need to edit the link to include the ip address of your ISY. It should look something like: http://192.168.1.101/admin once you replace your.ISY.ip.address with your ISY's actual IP address. -Xathros

GreyFox- You could delete all of the devices from the admin console then add them back selecting "Remove Existing Links". You still have to rebuild everything from scratch but this "should" clear all the old links. If I was doing this, I would factory reset all of the devices before adding them back to be sure that there are no garbage links left. When we moved into our new home last fall, I went through this process with all of the gear I pulled from the old home. As I installed each device, I did a factory reset then added it to the ISY (which I factory reset first). This way everything was like new with no phantom links or X10 stuff to worry about. -Xathros

LeeG- I didn't realize that the Toggleinc Relay had moved to I2CS already. Thanks for that tidbit. -Xathros