Xathros

Hi Jerry- I believe this is the normal behavior of th IOLinc module. In momentary mode, the ISY turns the relay on (and sets the status as On) then the IOLink turns the relay off after the preset timeout period. Since the relay node of the IOLinc is a responder only, no message is sent out to update the ISY's status. This is really not an issue as it doesn't affect the operation of the IOLinc. If you prefer to see the relay node as Off, as do I, you can add a "Wait 5 seconds" after you set the relay On and set it back off (which will only update the status as reflected by the ISY). -Xathros

Exactly! -Xath

Yes! As long as all of your thermostat programs include a From-to time range AND the KPL-Button status in the If section. What happens when you toggle the KPL button On or Off is every enabled program that includes the status of that button in it's IF section is triggered and evaluated. When turning off the KPL-G "Away" button, the single Thermostat-Away program is triggered and runs false (else) since the button is now off. All of the other Home Thermostat programs trigger most run false because you are outside of their time range and one will run true because you are inside it's time range AND KPL-G is Off. It is important to note based on you above comments that while the Away mode button is on, the Stat will stay set at 62 for however long the button is on-. Hours, Days ... Years, does not matter. The other (home) programs will still trigger at their start and end times but will all run false until the KPL button is turned off. I do something similar but my house has three modes: Occupied, Vacant and Away. Occupied = Your Home mode. Vacant I suspect = your Away and Away for me means for an extended period (Vacation, weekend away etc). Vacant locks my doors, sets back HVAC to moderate levels, enables security cams. Away sets back the HVAC further (keep pipes from freezing/fish from boiling), locks doors, enables security cams AND runs some randomized lighting to simulate occupancy during the evening/night. My Occupancy/Vacant status is automated - Away is set via program from my iPhone. -Xathros

Thanks for the complement Lee! JSP0511- It sounded to me like you wanted your thermostat to be at 62 for the duration of the "Away mode". If that is the case, then you will only need one extra program (as I posted above) to handle the stat while your away. If you want multiple timed set points while away, then that may require more programs. You can either build those programs to include the status of the "Away" KPL button as I did or you can create 2 program folders (One for away and the other for home) and set folder conditions based on the KPL button status ("If Status KPL-G is On" for the Away folder and "If Status KPL-G is Off" for the Home folder). The second approach (folders) may be cleaner if you are going to have a bunch of different setpoints / times of day while in away mode. Either approach will net the same functional results. -Xathros

Using one of your programs as a basis - modify the rest as follows: Week Day- If On Mon, Tue, Wed, Thu, Fri From 7:01:00AM To 3:30:00PM (same day) And Status 'Main Floor / Thermostat / Thermostat - Main' is Mode Heat And Status KPL-G is Off Then Set 'Main Floor / Thermostat / Thermostat - Main' 57° (Heat Setpoint) Else - No Actions - (To add one, press 'Action') Then add some away programs: Away-Thermostat- If Status 'Main Floor / Thermostat / Thermostat - Main' is Mode Heat And Status KPL-G is On Then Set 'Main Floor / Thermostat / Thermostat - Main' 62° (Heat Setpoint) Else - No Actions - (To add one, press 'Action') Away-Lighting: If Status KPL-G is On And Time is From Sunset +1 hour To Sunrise -1 hour (Next Day) Then Set scene Foyer Light On Else Set Scene Foyer Light Off -Xathros

Sorry, thats all I have for ideas on this one. Will have to wait for Michel. -Xathros

Look behind the applet window. Is there an ISY finder window? If so, use that to add the IP address of your ISY then connect from there. -Xathros

LeeG- Based on your previous findings, that is pretty much what I expected. Although, I would have expected the single query duplicate to be marked as such. I wonder if the PLM sees things differently if one ACK arrives on the powerline and another arrives via RF. -Xathros

I do understand the limitation. I highly suspect that this wasn't a problem before the advent of Dualband devices. It was when I added my 2 Fanlincs that I started noticing double responses to various events. (Motion detectors triggering twice in the same second, RL2 buttons registering twice etc). I don't see any way to resolve this beyond a delay to allow the duplicates to pass. I wonder if UDI could either insert delays between queries to the nodes of multi-node devices or shuffle the order of queries such that no two nodes of the same device are queried in sequence in the 3am query. -Xathros

I wonder if the same conditions can be detected with other multi-node queryable items like KPLs or Fanlincs. Really seems like a design flaw in insteon not carrying a node id in the ACK message. -Xathros

Gotcha! I was looking at it from a 99 vs 994 perspective not an old firmware vs new firmware perspective. Thanks! -Xathros

There is, sorta... You can use notifications to write directly to a file on the ISY's webserver. Very much like what you are doing now with your notifications but should be 0 latency. I do something very similar with network resources writing to a syslog server running on my RaspberryPi. Makes for lots of network resources or custom notifications but is very useful for debugging purposes. Here is the wiki link for writing to a file: http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking#Create_File_and_Send_Notification -Xathros

Hi- The PC is only required to configure and program the ISY. Once configured, the PC is not required and ISY will run happily by itself. All of the programs reside in the ISY. -Xathros

I have to question the statement made by the OP that AtHome works with the 99i but not the 994. I didn't think there were any differences between the 99i and the 994 that would prevent something like that from working. I know the 994 is capable of more than the 99 but from what I've seen, anything that works on a 99 will work just fine on a 994. I would have to guess that there were port or IP address changes when the 994 was installed and AtHome needs to be reconfigured to match. All of that said, Mobilinc in my opinion is the best choice. -Xathros

Hi, I have found the low batt notifications to be quite unreliable on these motion sensors. The major issue with these is that they will only turn on the low batt node once and if that event is missed, there won't be another sent. That said, there a a few approaches to this. First you will need to configure one or more custom notifications that can ben sent when a low batt condition is detected. Then a program like the following is the simplest: If Control 'Basement / Shop / Shop Motion / Shop Motion-Low Bat' is switched On Then Repeat Every 12 hours Resource 'NOTIFY - UTLITY - Basement Motion - Low Battery' Else - No Actions - (To add one, press 'Action') In that example, I am using network resources to send a prowl notification to my iPhone. You could just as easily sent a text or email message instead (and not need the network module to do that). This will notify every 12 hrs once a low batt event has been detected but as I said above, if that event is missed, this won't be of any value. Another approach would be to set countdown timers that reset each time there is motion detected and send a notification whenever a counter reaches zero. Start the counters with a high enough value that under normal conditions they will not reach zero unless the battery quits and they stop sending motion events. This works fairly well in higher traffic areas, will be rock solid reliable but does delay the notification until the counter expires. Hope this helps. -Xathros

If you are on Lion or Mtn Lion, you should install Java 1.7.25 from Oracle. UDI has been recommending that users uninstall the 1.6 branch of Java on the MAC but software update keeps putting it back and it hasn't caused me any grief so I just left well enough alone with that. -Xathros

Another remote possibility is that NTP is updating the ISY's clock and skipping the trigger time. This would assume that the ISY clockis drifting enough in a 24hr period and that NTP is updating around the same time that your program should trigger. You could disable NTP for a day or two and see how much clock drift you see. Then maybe change the frequency of updates in an attempt to avoid the mindnigt-ish update. -Xathros

The downgrade recommendation was one I had made a month or two ago to another user that was swapping a 99i for a 994. I remember Michel saying that there had been some database changes and that if you wanted to go back to the 3.3.10 FW from the 4.x betas, you should restore a 3.3.10 backup after the downgrade. This lead me to believe that the safest upgrade path on a new 994 from a 3.3.10 99i would be to start with the 994 at 3.3.10, restore the 99i backup then upgrade the 994 to 4.x from there. This may have been unnecessary. Michel- could you comment on this? -Xathros

Could you test one of the four that didn't work in a location where one of the others worked and see if you get different results? It could just be marginal communications to the locations where the four failed. -Xathros

The From ... To is also a trigger and triggers twice - Once at the From time and again at the To time. If the only condition was the From...To, then the program would trigger and run true at the From time and trigger and run false at the To time. As LeeG posted the program, the program will always run false at sunrise time regardless of the nightlight status. And besides, the very first program the OP posted would still turn the light off at Sunrise based on it's else clause. -Xathros

I don't think that would be a problem here. The if will reevaluate false at sunrise during the 10 minute wait and the light will not be turned back on. Looks fine to me as LeeG has it. -Xathros

Perfect. The filterlinc should be helping in this case. -Xathros

dstanley- Normally, the filterlinc is used to prevent noise or attenuation caused by a device like a UPS from reaching the powerline. Filtering the PLM eliminates the PLM's ability to communicate on the powerline. If the UPS is used for the ISY and other network gear, plug the UPS into the filtered outlet on the filterlinc and the PLM into the Passthru outlet on the filterlinc. This will isolate the USP from the line and allow the PLM direct access to the line. A few users here have purposely filtered the PLM to force it to communicate over RF instead of the powerline. While this may help in some situations, I believe that this will make things worse on many older Insteon networks where there are few if any dual band devices. This would also require a 2413S dual band PLM to work in this configuration. -Xathros

derw- Correct depends on a clearer definition of exactly what you want to accomplish. That will do what you stated but if at 8:31 you were to turn on button B, only the button would light because it is no longer 8:30. The only time this will work is when the B button is already on when the time becomes 8:30. A more common scenario might be: If Time is from 8:30pm to 10:30pm same day and Status KPL-B is on Then Set backroom light On Set dining room ceiling light on This way you can turn on those lights during the time window if needed rather than just at 8:30 if the button is already on. Again, it really depends on what you want to accomplish. oberkc- I believe that only the primary node on a KPL dimmer can have a status of >0% & <100% while the secondary nodes are all either On or Off. -Xathros

Try setting a static IP address for your ISY and use 8.8.8.8 for the DNS server address. Check Tools / Error Log and see if there is anything there to indicate what the failure is. -Xathros