Xathros

Also, verify that the load is a functional incandescent bulb by plugging directly into the outlet to test. I went through this headache with an X10 device years ago only to find out my bulb was bad. Live and learn... -Xathros

Delete your old icon. Open a browser and go to: http:///admin/admin.jnlp Accept any certificates and/or confirm any security exceptions and save the resulting file to your desktop or other preferred location. Hope this helps. -Xathros

Also, what is the load ? -Xathros

Sounds like it was a fun project. I'm glad you got it all working! -Xathros

Using oberkc's code as it is cleaner and more elegant than mine, you can modify as follows: if status 'elevator 1-opened' is off then wait 13 seconds Set Scene 'Basement Scene 1 - Group' Fade Down else Set Scene 'Basement Scene 1 - Group' Fade Up I used 13 seconds as there is already a 2 second delay in the initial program. I didn't understand your desire for a 15 second delay on the lights off but you could easily add a wait on the else if needed. -Xathros

Create a scene in the ISY and add all of those switches as controllers to that scene. If it's only one ceiling light, then only one of the switches should be physically wired to the light. If multiple lights, then the other lights could either wired to other switches or could share the one. Whatever works best for your situation. -Xathros

Proving once again, there is more than one way to skin a cat. Nice solution. -Xathros

Oops. My bad. Change "Control" to "Status" on 1B. That way the Call to 1C is canceled if the button is released within the 2 sec initial delay. -Xathros

csetter911 Here is a solution to your problem. Change the Floor 1B program as follows: "Floor 1B" Program: If Control 'Elevator 1-Opened' is Off Then Wait 2 seconds Run Program Floor 1C (Then Path) "Floor 1C" Program: if then wait 2 seconds Set Scene 'Basement Scene 1 - Group' Fade Down else This way, the off program is isolated from the resent on command by separating the programs and adding another delay. Releasing the button after 2 secs does turn the lights on again but they are already on - who cares. If you press and hold your button for 2 secs but less than 4 secs the lights will turn off and stay off after 4 seconds. Hope this helps. -Xathros

I got my new cams configured yesterday and so far I'm quite happy with them. The image quality is much better than my old Trendnet cams though still only 640x480, The PTZ motors are almost silent. They seem to respond faster to PTZ commands via the web interface or Mobilinc and they certainly work better over a 3G connection than my older cams. I have not yet had an opportunity to test the 2way audio feature nor have I investigated any deeper integration using network resources yet. -Xathros

My bad! Several other people here had run into issues with Java 7 and the ISY. They were able to resolve by rolling back to Java 6. I guess some progress has been made since then with Java 7. -Xathros

Thanks Wes. I have a few old Trendnet fixed position cams with IO that I attempted to do that with. Turns out the IO was more "O" than "I" and I couldn't trigger uploading with an input. The IOLincs on my garage doors were originally purchased for triggering the cams. The new PTZ cams with IR night vision should be much more functional and better looking. I'm confident that I can accomplish what I want without the IO as long as I can figure out the commands to send via network resources. I'll have to start capturing and analyzing some traffic. I'll take a closer look at the Panasonic cams. Maybe I'll have to trade up. -Xathros

Maybe I'm missing something here but why not just reverse the program logic from "Status TriggerLinc is On" to "Status TriggerLinc is Off" ? -Xathros

Clarance, Wes- I have some similar desires for my new cams but with a slightly different need for network resources. Since the cams can trigger and record/alert on motion by themselves, I don't need the ISY to respond to that but rather I would like to have the ISY force the cams to record (to FTP) in certain situations. So I'd be looking for network resource configuration(s) to start and stop recording based on other conditions that the ISY already monitors and also, the ability to call a camera PTZ stored position as well. This way if my ISY is in Away mode and an outside door is opened I can point the cams in the appropriate direction and begin recording before someone walks into the view of a cam. -Xathros

Awesome! I have two of these showing a red glow around the fan mounts and the wife seems overly bothered by the one above our bed. The sooner, the better -Xathros

Looks like he has Java 7 Update 5. -Xathros

You are correct. Roll back to Java 6 and you should be fine again. -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