Xathros

ejh3- I have the same concern and developed the following two programs that I use for my back porch floods day and night: Back Porch Daytime Timer If From Sunrise + 1 second To Sunset - 1 second (same day) And Status 'Back Porch / Back Porch Flood Light' is On Then Set Scene 'Back Porch / Back Porch' Off Else - No Actions - (To add one, press 'Action') Back Porch Night Timer If From Sunset To Sunrise (next day) And Status 'Back Porch / Back Porch Flood Light' is On Then Wait 15 minutes Set Scene 'Back Porch / Back Porch' Off Else - No Actions - (To add one, press 'Action') I have a few more programs that disable and re-enable the above programs as necessary. Hope this helps. -Xathros

Johnnyt- I currently have just under 100 programs. Many of these I hope to eliminate as the ISY's capabilities mature. Once we have the ability to do variable assignment to/from devices and maybe get some string variable support, I suspect I could cut my program count in half. Not knowing what exactly you are doing with programs I can't venture a guess as to how that could effect your program count. In the short term, I see my program count increasing somewhat as I continue to build out my Insteon network and need to keep track of more devices and data. The feeling I get is that a large program count isn't necessarily a problem unless you have many trigger at once or as in your case where it causes a repetitive update delay. I see this with Mobilinc. The more devices, programs and variables I have, the longer it takes to sync up with current statuses. Not really a big issue for me unless I'm on on a weak 3g/edge connection at the time. -Xathros

For what it's worth, I have a 994i-Pro with 90+ programs, 60+ network resources, 80 variables, 60 nodes and have a CAI web control board in near constant communication with the ISY. I haven't noticed a performance issue with the ISY under these conditions. I did upgrade from a 99i earlier this year. I can say that the Admin console "feels" quicker to respond than it did on the 99i. There have been some firmware updates since then so I can't say for sure that the improved feel is due to the 994 over the 99. Guess I need to set up the 99 as a test bed. I just don't have enough leftover Insteon parts to make that worth while yet. -Xathros

I would use 2 10K ohm resistors between +5v and Each of the I3 and I4 inputs then place your dry contacts between ground and each input. Make sense ? -Xathros

No Problem. Happy to help. I assume you just changed the timeserver to the ip address that I supplied a few replies back on the clock thread. If that is the case, that may stop working if that time server moves. Now that you have fixed the DNS at the ISY, you can change that server back to time.nist.gov or pool.ntp.org as the ISY can now resolve the current address for a named server. -Xathros

And, If you use the network module and have anything in the webserver folder, you will need to copy that down and upload it to the 994 after you are set up. The backup does not copy anything in the webserver. -Xathros

This is what I get from that link using firefox: This is an unformatted XML listing and seems quite readable to me. Program ID is the number you want. -Xathros

With Automatic (DHCP) turned off, the ISY wants you to specify all of the network settings (Static addressing). Without knowing how your router is configured, It's had to tell you how to fill those fileds but I can give you an example. Assuming that your router's LAN address is: 192.168.1.1 and your DHCP pool starts at 192.168.1.100 then the following should work: IP Address: 192.168.1.50 Subnet mask: 255.255.255.0 Gateway: 192.168.1.1 DNS: 8.8.8.8 If your router's address and DHCP are different, you will need to edit the above accordingly. I think you may have already added the 8.8.8.8 to your router in trying to resolve your clock issue from another thread here. You might just try again before making any additional changes and see if the DNS change at the router solves this problem as well since I suspect both problems were due to the same issue. -Xathros

I think the more important question is what do you have for a router and how is it configured? Before adding the 8.8.8.8, your router was likely supplying it's LAN address as the DNS server via DHCP and then doing the lookup itself. Many cheap routers don't do a very good job of DNS. The 8.8.8.8 is Google's public DNS server and has proven to be quite reliable unlike the DNS servers at either of my local ISP's that are slow to update, slow to respond and are sometimes unavailable. If your router is using your ISP's DNS only, you might consider adding the 8.8.8.8 to the list for it to fall back on or put it up front as the primary. I always specify the DNS in the ISY so it doesn't need to rely on my router for that. Almost every time I have seen the red ! my error log showed a DNS lookup error (Timeout I suspect) and since I have set the DNS at the ISY I have had very few failures. -Xathros

carealtor- On the configuration tab of the admin console, enter 8.8.8.8 in the dns field and try again after the ISY reboots. -Xathros

My Bad. I meant to have that run the 'Downstairs Light Motion' ELSE path not the THEN path. This way it will do a 15 minute countdown then turn off UNLESS there is motion to cancel the wait. The IF looks like it would work as well. Thanks for catching my error. -Xathros

carealtor- My best guess is that you are having DNS failure/timeout issues. You could try adding 8.8.8.8 in the DNS field or update the DNS servers in your router to begin with 8.8.8.8 For a test, replace the time server (time.nist.gov) with 207.200.81.113 (the current ip address of time.nist.gov) and see if it will sync. If it does, then this indicates a DNS problem. -Xathros

Try this: http:///rest/programs?subfolders=true That should return a list of all programs with their ID's -Xathros

jak1975- I use the following with gmail: Server: smtp.gmail.com Port: 587 UserID: full gmail email address Password: (my password) From: My Name (Actually, My ISY's Name) - Just not blank. Timeout: 1000ms TLS checked Very important: Make sure that the subject and body fields of the custom notification are not blank. Hope this helps. -Xathros

I would modify the first program as follows: Program: Down Stairs Lite Sched If From 6:00:00PM To 9:45:00PM (same day) Then Set 'Devices / Dwn Stairs Lite' On Disable Program 'Down Stairs Lite Motion' Else Set 'Devices / Dwn Stairs Lite' Off Enable Program 'Down Stairs Lite Motion' Run Program 'Down Stairs Lite Motion' Then Path This way, if there is no motion, the light still turns off at 10Pm but if there is activity in that area, the light will not turn off at 10 and require someone to move to turn it back on. -Xathros

Very good points, neither of which I had considered. -Xathros

I guess I missed that or at least forgot about it after all the back and forth. My bad. -Xathros

Hi Michel- Prowl does not use user/pass but simply the API key for auth. I have many network resource rules configured for prowl that all work fine (after the first test fails usually). Here is what they look like for ref: -Xathros EDIT: Re: my comment about the first test usually failing, I haven't created any new rules on 3.3.3 or 3.3.4 so don't know if the first test fail is still an issue. Not that it was a big issue to begin with.

if status bathroom light is off then wait 10 minutes set bathroom fan off else If the light is turned back on during the wait, status changes and the wait is canceled. Should do exactly what you want. -Xathros

I've been watching this thread and wondering why all the fuss over a relay. I believe we already have a doorbell button, an IOLinc a bell/chime and a transformer. Maybe we could just reorganize a bit and have the button connect to the IOLinc input only and the relay output of the IOLinc close the 24VAC circuit from the transformer to the bell/chime. Set the IOLinc options to "Relay follows input". Advantage: No extra relay needed, Insteon control of the bell/chime for other audio notification purposes and Insteon notification of the button press. Other than a possible minor rewire, am I missing something here? -Xathros

osurh18- Yes and that depends on what you mean by "work with". The only thing Insteon about these cams is that some of Smarthome's software packages have IP camera support built into them. They do not control the cams with Insteon network commands but rather over the ethernet/WiFi network. You can use the ISY network module and write some rules to do position control, enable/disable uploading etc. -Xathros

No Problem. Always happy to help. Glad we got ya fixed up. -Xathros

What I do is access my isy via its ip address like this: http:///admin/admin.jnlp or via it DynDNS external address: https:///admin/admin.jnlp Obviously replacing the with its actual IP or the name with it's actual name. This downloads an admin.jnlp file. Double click this file and it will download the admin console, complain about not being able to create a shortcut (this seems to be a MAC&Java 7 issue) then launch into the console without the ISY Finder. Exit the console and place the admin.jnlp file on the dock just to the left of the trash and to the right of the dock divider. It won't place anywhere left of the dock divider since it's a file not an app. Clicking this will launch directly into the console from here on out till the next release at which point you dump the jnlp, clear the java cache and repeat the above procedure. Hope this helps. -Xathros

Yes. Ctrl x says Exit (This means hold down the Ctrl key and press x) You will see a question appear in the bottom section of the terminal. Y answers the question and says write Changes Return Accepts the existing filename and writes out the changes and completes the process. After that, you can quit the terminal and you are all set. -Xathros

place the cursor on the beginning of the line that reads: 127.0.0.1 localhost Press Return then move the cursor up to the new blank line and start typing your new data in. Press tab between 127.0.0.1 and your hostname. -Xathros