TJF1960

Sorry, I also meant to ask if the network module is listed under "Product" in the same "About" window. It sounds like you will need to contact UDI though, it should not have taken this long for it to appear. Look for any of Michel's posts and click on "open a ticket" in his signature line.

Hello rohan208, what is the gui version reported as? Help>About: UI should report as "Insteon_UD994 v.4.0.5" Also, just to be clear, you were able to manually upgrade to 4.0.5 right?

I emailed them a few questions a couple of weeks ago and found them to be pretty slow in response. I did ask them about having the Rest sent from the tag manager and not the cloud because I was interested in the fastest response possible, here was his reply: "If you check the "call from tag manager" option in URL calling, the server will still have to load your setting from the database to construct the URL and other parameters, and then send it to the tag manager for it to call. Obviously tag manager does not have a storage to store all the URL settings." So basically it sounds like if the cloud is down or they go down and out the unit is completely worthless. Tim

Another possibility could be (depending on the version) is that the off button has been accidently put in the non-toggle mode.

Using IE10, look at the address bar at the top of the page, the icon next to the refresh icon is the compatability view button. Click on that which will refresh/resize the page and you will see the missing buttons/info.

Hi Michel, Fingers crossed...Did they give any sort of ETA? Thanks, Tim

Hi IndyMike, Thanks very much for your reply. I agree the program may not trigger very often (or at all if WB fixes the problem) but I already had the weather program on the pogoplug in place sending variable updates to the ISY so all I really had to do was a slight mod to the weather program, create a variable and then create the ISY program. Didn't take much time at all. I did send WB an email about the rainfall not reporting and they sent an email back saying that the problem was at the station and they were working on it but its not the first time they have had problems. I noticed that by mid day the second day of rain that WB was reporting .11" but that was off based on weather underground reporting. Anyway I was just looking for a quick backup in case it were to happen again. It did work, the sprinklers didn't fire the next day whereas they would have. Thanks again for all of your contributions and hard work, Tim

It appears my weather bug station (KBAB) is not reporting current rain data again. The next closest station also is not reporting rainfall. Weather Underground is however. So I have modified my weather program on the pogoplug to parse the days rainfall and send it to an integer variable on the ISY. The weather program strips the decimal and leading zero before sending to the variable. So .42" = 42 in the variable. I have been following the advice IndyMike has been giving other forum members (btw, Big thanks to you IM) and have set the following in the climate module: Water Applied per ir. cycle: 0.386" Allowable Dep. 0.27" My thinking is to create an ISY program which will run an irr. cycle complete at the end of the day if the Weather Underground reports more than .386" of rain but the Weather Bug doesn't. For example: If Time is 11:55:00PM And $iPogoWeather_RainAmountToday >= 38 And Module 'Climate' Rain Today < 0.38 " Then Irrigation - Cycle Complete Else - No Actions - (To add one, press 'Action') Does this sound about right or am I incorrect in my thinking? Thanks, Tim

I can confirm exactly what Andyf0 is seeing with my switchlinc relay with sense, also .v37 while my switchlinc relay without sense indicate fine. Tim

Hi Xathros, Sorry to be hard headed but can you explain that a little more...I am having trouble understanding this comment about variables only being positive numbers. Thanks, Tim

http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Linking_a_KeypadLinc

Two thoughts..can you write a prgm that when you turn the lamp off, after a certain time, that will automatically arm the alarm. I don't have the Elk but I seem to recall reading that the ISY could arm and disarm it. If Time is from 9:30pm to 5:30am (next day) And Control 'RemoteLinc button' is Turned Off And 'Elk' is Disarmed Then Arm Elk Else nothing Otherwise the same program can be used to flash the light. Just change Arm Elk to Then Turn light on Wait 1 sec Turn Light Off

Give this a try. Create an Integer variable (such as iSump). Then add it to the program as such: If Status 'synclinc' is On And iSump = 0 Then Send Notification to 'Joe' content 'Sump On' Set iSump = 1 Else - No Actions - (To add one, press 'Action') Do the same for the off program but reverse the Integer values.

Hi Walt, Wow, that was quick! It took them literally 4 or 5 business days to respond to my request. I cannot offer any assistance and I read in another thread that Michel was out until tomorrow I believe, just to let you know. I am sure he will be able to get you fixed up though. Tim

Good deal! It did take them 4 or 5 days to reply back to me. I was really suprised my area is good to go because it is a simi rural area here. Here's to hoping your area is good to go as well!

Hi Walt, Not sure if you had come across this page or not http://www.pge.com/myhome/saveenergymoney/energysavingprograms/han/eligibility/index.shtml but you can fill out your info and pge will let you know if you are in a HAN service area or not. I had the same problem with phone numbers and cs agents I spoke with.

So if I understand correctly, then based on your program the only time the tstat fan will switch back to Auto is 20 minutes after the Sensor is Off. If the sensor is cycling every 4-5 minutes for the next 6 hours then the tstat fan will not shut off for approx. 6 hours. If that is what you had in mind I think it should work perfectly.

Might I suggest, and using your first program in the first post as a guide, create a new State variable named something like “sOutsideTempOver60 and then a new program outside of your conditional folders such: If Module ‘Climate’ Temperature>=60 Then Set ‘sOutsideTempOver60’ 1 Else Set ‘sOutsideTempOver60’ 0 Then in your first program replace the Module ‘Climate†Temp line with “sOutsideTempOver60 is 1†This way the only time your AC program will re evaluate due to outside temp will be when the outside temp crosses over or under 60 degrees. Also, If you do not want the AC program to re evaluate at 5AM or 8AM as it is doing now you can remove that schedule and replace using the folder condition as such: If Folder ‘Armed Away’ is True And sTempOver60 is 1 Then Set 'Indoor / HVAC / Main House / HVAC Main House' Fan Auto Set 'Indoor / HVAC / Main House / HVAC Main House' Mode Auto Wait 3 seconds Set 'Indoor / HVAC / Main House / HVAC Main House' 80° (Cool Setpoint) Set 'Indoor / HVAC / Main House / HVAC Main House' 60° (Heat Setpoint) Else - No Actions - (To add one, press 'Action') Now with the conditions in this program the only time the program will evaluate true is when the alarm is first armed away and the outside temp is over 60 or if the alarm is in the armed mode while the temp crosses over 60.

Yes it has been my experience. But like I said, comm issues will alter the results of the program. Good question about the order. I just tested the order and it did not make a difference. I am not sure exactly why it works this way. Perhaps since programs are event triggered the first trigger sets the evaluation in motion and at the time of the trigger the status of the lite was off which caused the program to evaluate as false. Then the status changed of the light triggering the second evaluation again as false because at that moment the control was not being switched on. Plus, I keep going back in my head to what the op has stated that these same programs work fine in other parts of his house and that this problem occurred after he replaced a SL with a DB SL which suggests either the DB SL is defective, his wiring is defective or something in the powerline has changed causing poor comm issues.

oberkc, if I understand what you are saying correctly then I sadly have to disagree with you this time. I have seen this type of program structure work in the past. I have also seen comm. problems cause the program to malfunction if there were less than 1 or 2 hops left. I just ran a test with this program: If Status 'WR Bench Lite' is On And Control 'WR Bench Lite' is switched On Then Set 'Vent Fan' On Else - No Actions - (To add one, press 'Action') When the Bench lite is off and the switch is turned On the program executes Else (actually it executes false twice). If the Bench Lite is On and is switched On the program executes Then (and stays true). If the Bench Lite is On and the switch is turned Off the program executes Else. In the first test where the light was off and the switch was turned on, the switch turning on caused the program to evaluate but at the exact moment the switch was turned on the status of the light in fact was off so the program evaluated false. When the status of the light updated to On the program re-evaluated but because the program evaluated when the status change occurred the control switching on didn't occur the program evaluated false again. To test I added an integer variable to the Else condition which would +1 for every evaluation which ran the Else.

The reason for this is that once the program runs true it changes the variable state (of which it is monitoring in the IF)..which causes the program to run again, this time false. If the programs were working perfectly when the old switchlinc was in place and if the electrical connections are good and tight on the new dualband I would suspect the new dualband and would suggest either reinstalling the old switchlinc as an added test or if you have another dualband available try installing that one and testing. Odds may be slim that the dualband is defective..but its a possiblility.

Upgrade went without a hitch. Finder launches right into admin console without prompting. Thanks, Tim

johnnyt, This bug only occurs when you manually query a device not when the query is part of a program.

Hi Xathros, I ran into this a few months back. If you manually query a device it will trigger a program then/else. But the nightly queries do not. Nor do device queries via a program. Tim

I would try to swap one of the lights with an incandescent to see if the added load dampens the flickering of the LEDs.