Xathros

Oberkc- Wswartz already has a Scene1 defined - See his first post - The blue boxes. I was simply making use of it to turn on/off the KPL button when the overlapping Scene2 or something else turned on/off SW1. -Xathros

There is your problem! The trick here is to AVOID the router's DNS cache at all costs. Set the ISY with a static IP and DNS of 8.8.8.8 and I bet it will work. I bet your 99 was static addressed with external DNS and the 994 is DHCPd. This has worked without fail for me with each and every ISY firmware version 3.2.6 through 3.3.8 -Xathros

I would like to point out that it is possible (and fairly common) for the load and hot to be in one (switch or junction) box with just a run of 14/3 to the remote switch box(s). I had two 3 way circuits in my place wired this way before Insteon upgrades. -Xathros

wrj0- I just checked my setup again and it is still working. I see that I have an extra header in my resource that I don't see in yours that says: "Connection: close" Otherwise all is the same with the exception of Auth, Variable ID and dyndns name. What do you have configured for DNS in the ISY? I'm using 8.8.8.8 but have tested with 4.2.2.2 and 4.2.2.1 which work for me as well. -Xathros

The answer to this question could dictate a solution. If it does not matter, simply make KPL1D a responder to scene 2 (which would cause KPL1D to come on and off with scene 2, probably my preference). If you would prefer KPL1D to stay off in response to scene 2, but want KPL1D to turn off when scene 2 goes off, this suggests to me that a scene will not work and that you would need a program, such as: As I see it, KPL1D is an indicator showing that the load on switch 1 is on. I would want KPL1D to come on any time switch 1 goes on, including with scene 2 Except you cannot turn on/off a KPL secondary button with a direct command so instead: If Status SW1 is Off Then Set Scene1 off That said, I have to agree with oberkc and others above in that KPL1D should be a responder in Scene2 and follow the actual status of SW1 regardless of which scene turns SW1 on/off. You might even consider making KPL2C a responder in Scene1 since when Scene1 is on, Scene2 is partially on. -Xathros

wswartz- The 6% on with LED dim/brighten issue is one that several of us experienced over the last few firmware revs and it appears to be resolved in 3.3.8 -Xathros

apostolakisl- Thanks for chiming in here. Not having an ELK, I was in over my head on this one. I am planing for an ELK install at my place hopefully within a year or so and will certainly benefit from that info. -Xathros

The bottom of my last post should solve this for you. -Xathros

scubaguyjohn- None of the 4 cam types that I own cache any images prior to an upload request and I don't remember that being listed as a feature on any that I have looked at so which gives me the impression that that is not a common feature. The /REST interface is a method for communicating with the ISY via HTTP. You can turn On/Off/Brighten/Dim devices/scenes, get or set the values of variables, cause programs to run, get the current status of devices or programs all via http urls. For controlling the cams, you would need to ISY Network module add-on. This allows you to send network commands from the ISY to other network devices like cameras. I used the Firefox's web developer tool to look at the command that the camera's web interface was sending to the cam when I asked it to point the camera to a preset then duplicated that with a network resource rule. Now when I call that rule, the cam turns to that position. I created a rule for each cam and position I wanted to use. Another rule for Enable upload on motion, one to disable, again for each camera. Then its just a matter of writing ISY programs to watch for motion/activity and call the network resources as necessary. -Xathros

At the moment, there is no way of sensing motion at the cam and notifying the ISY without a third party monitoring the cam and alerting the ISY via the rest interface. I tested this using my pogoplug. I configured the cams to upload images to the ftp running on my pogoplug. I have a script that watches for files in the ftp folders and issues a rest command to the ISY when files are detected. While this works, the lag from actual motion to ISY reaction was variable from 5 up to 15 seconds and I decided that was more or less useless. Now I just rely on standard motion sensors and other insteon traffic. As for the integration of video and lighting, I have my ISY point my PTZ cams based on motion detected by motion sensors or when certain switches are controlled or garage doors open/close or triggerlincs turn on. If the house is in away mode or vacant mode the ISY enables the record on video motion feature of the cams and if after sunset , ISY brings up suitable lighting so that I can capture a good image of whats going on. If the house was just vacant and not in away mode, after a 2 minute delay, i stop capturing images on video motion detected otherwise I continue to capture until a manual reset. -Xathros

I would choose the one that the load is connected to just in case the lights were turned on with a direct command from the ISY to the load controlling switch/dimmer. -Xathros

Michel- I saw the same thing when I upgraded from the 99 to the 994. I believe I was on 3.2.6 then as well. -Xathros

Hi jmed999- I don't have an ELK or the link between ELK and ISY so I'm just speculating here. Looks to me like the ISY has no reason to look at the IF conditions on most of your programs until an output changes status or the console is asked to display the current status. At this time the IFs are evaluated and either the then or else clauses run. I suspect that the elk outputs are handled by the ISY much like device status where they trigger on a change of status but unlike devices, they do not have an initial status at startup so the first time the ISY looks at them after startup it will trigger as a change regardless of what the status actually was. Again, this is all speculation on my part. The only solution I can think of would be to have a program run at startup then in turn calls each of your other program IF paths to initialize things but this may have the same effect of doing things based on the current condition of the elk outputs. It will just get it over with up front rather than later when you load the console. I have a similar situation where I would get a ton of notifications based on the current state of affairs at startup. My solution was to add a Notification Enable/disable integer variable where 1=enabled, 0=disabled. I set the init to 0. I have a startup program that runs the IF tests on the programs that notify then I set the var to 1 after the tests are done. From there on out I get notified on changes - just not the flood at startup. You didn't post the programs related to Kristen so I can't determine why that one didn't notify when the others did. No else clause on that one maybe? -Xathros

I've been an ISY user for maybe 4 years now and have been on these forums most of that time. I have never before or since found another community as welcoming and friendly as this. After all this time I still learn something new here almost everyday. I'm proud to be a part of this community and a member of the ISY family. -Xathros

Yes, in theory. The issue I alluded to above is related to how the UPS and PLM react to each other. As you have no doubt seen in many other threads here, a UPS can cause significant comm problems if not filtered. If you filter the UPS and your PLM is on the UPS, you have effectively broken you powerline communications between the PLM and the rest of your Insteon network. To resolve this, you would either use a dual band PLM (2413S) on the UPS and an access point not on the UPS but within RF range to bridge the USP/Filter via RF. Best setup in my mind would be 2 access points on opposite phases at the service cabinet and the ISY, PLM (2413), Modem, Router on a shelf next to the service cabinet all on the UPS. If you are still using an older 2412S PLM like me, you could add another access point plugged right into the PLM to jump out over the UPS/Filter via RF. The other issue with the internet test is related to your router. Some routers try to be helpful and cache DNS lookups. If yours does, then the test may indicate a false positive even when your internet is down. This works for me using a dd-wrt based Linksys WRT54-GL and currently with DD-WRT x86 v24-Sp2 running on a mini PC. I think it DID NOT WORK on an Actiontec combo modem/router but that is a vague memory. the fail report may be in that same thread that I linked to earlier. -Xathros

This surprises me from one who likes to tinker such as you. Hehe. Me too, kinda. I do really enjoy the stability and reliability that comes from iOS however. Been down the jailbreak road a few times and have decided that it's not worth the effort. I still have my old Nokia N810 but don't generally carry that anymore. I have been able to do most of what I want externally and just use the iPhone/iPod/iPad to trigger those external scripts/functions. That said, an app like tasker would be most welcome. -Xathros

No need for the network module for this. /REST commands are directly supported by the base ISY configuration. As for TASKER, Dunno, I'm on iOS and us iOS users don't get to have nice things like TASKER since old mother Apple need to save us from ourselves.

I tend to agree and in that vein, I also have a few DS1822's wired back to my CAI Webcontrol to monitor a few critical locations and alert me if out of bounds. Most likely overkill as this is my primary residence and in the last 2 months it's had a total of 5 hours unoccupied but I figured a few extra safeguards for damn near free isn't a bad idea. -Xathros Sorry MstrD! Didn't mean to steal your thread.

I would suspect weak communications if it takes more than one attempt to restore the device. -Xathros

OK. I don't have one of the 2487S KPL's to test with here but I would expect it to work the same as the lower amperage KPL's that I do have. Try right clicking on it's primary node in the network tree and select Query Insteon Engine. After that, return to your program and see if the backlight options are there. -Xathros

Hi jmed999- Power restored is simple. Just write a program to send a notification and make that run at startup. Power out is slightly more complex. Assuming that your insternet (Modem, router, switches) and ISY, PLM are UPS powered (some issues with this), you can write a program as follows: Program: CheckPower If Status [i]Some Insteon Device[/i] is Responding Then wait 2 minutes Run CheckPower (If path) Else Notify - Your Cell - Power Lost As for the internet, I built a test that works for me and some others that depends on a DNS lookup to prove internet connectivity and set a variable. This works for some but depends on the ability to get a true response from an external DNS server without your Router or modem answering from cache. Requires UDI Network resources module. Here is the thread on that: http://forum.universal-devices.com/viewtopic.php?f=26&t=9201&hilit=check+internet -Xathros

Looks to me like you are adjusting House Floods - Kitchen not Stairway KPL. I suspect House Floods - Kitchen are not on a KPL. -Xathros

MstrD- Thanks for the writeup on the Nest. I've been watching those and am very interested in the pogo scripts to translate for the Nest. I'll be watching this for sure. My ISY has become unresponsive on 2 occasions now. I don't think it crashed but rather got too busy with IP network stuff (DirecTV Flooding?) to do anything and required a reboot to recover. I do think a backup plan is always a good idea with critical systems like heat. My backup is an old bimetal mechanical thermostat installed in the basement (most likely place to freeze in my place) set at 50F. This works in parallel with my ISY/Venstar. If the temp in the basement ever gets that low it is because the Venstar/ISY failed to call for heat and the old mechanical thermostat will pick up the slack. I have a second one of these old stats in my breezeway near my pellet stove in SERIES with an IOlinc that I use to simulate a thermostat based on data from the Venstar in the next room. This mechanical stat is set to 80F and will shutdown the pellet stove should the ISY/Venstar/IOLinc fail to. -Xathros

Upgraded from 3.3.7 without any problems. Everything seems ok so far. I'll test the back lights when I get home tonight. -Xathros

The following format works for me: https://myusername:mypass@mydomain.no-i ... 67/cmd/DON -Xathros