Kentinada

Can you point me to the devices by chance? Sent from my iPad using Tapatalk

Is the zwave compatible with the ISY? How about Mobilinc? Sent from my iPad using Tapatalk

It is not changing states from awake to leave to return to sleep at the defined times. If I go through the process to set the time again, it jumps to the right phase. But it won't do it automatically. Defective thermostat maybe? Sent from my iPad using Tapatalk

Is the NEST thermostat compatible with the ISY994i? I'm not too thrilled with the INSTEON 2441TH.

One more question and I'll quit bugging you on this topic. So by adding the repeat, that says to me that this Low Bat is not an event that triggers this code to run like other events. e.g. when my garage door goes up or down, I have code to tell me the door is open or closed. Rather, this low battery event must be caught once it gets set to On. Is that right?

So Teken, should this simple program work then? If Status 'Outdoors / Front Door Motion-Low Bat' is On Then Send Notification to 'Kent Txt' content 'Low Battery'

Larrylix, I have 3 MS right now and I'm just trying to find a way to be alerted when the battery is getting low rather than having to discover it by trial and error. Gee, this motion sensor doesn't seem to be working anymore. Guess I better check the battery. If that is the way, then oh well. I'll live.

Stusviews - thanks for the tip on copying code and pasting here. Here is my full program as it stands now. Front Door LBC - [iD 0007][Parent 0001] If Status 'Outdoors / Front Door Motion-Low Bat' is On Then Send Notification to 'Kent Txt' content 'Low Battery' Wait 12 hours Run Program 'Front Door LBC' (Then Path) Else Wait 12 hours Run Program 'Front Door LBC' (Then Path) LeeG - Maybe this is more a problem of not understanding when programs run. So do I have it right that this code above would run if and only when the 'Outdoors / Front Door Motion-Low Bat' goes to an On state? From what stusviews stated above, it would seem to indicate that the device changes to On one time and then goes back to Off. So wouldn't this program run when that event occurred? And I agree the Else clause is worthless as written. In fact, if stusviews is correct about the one time change, the Wait 12 hours isn't necessary either. The program would be triggered when the Low Bat indicator changes to On and I'd get the notice. I must still be missing something if it isn't this simple. And once the device changes from Off to On and back to Off, how would it ever do this again? If I put a new battery in, what happens in the MS that resets itself to check this and change one time? Thanks for any more help you can provide.

Here is my program ( I couldn't find any way to copy and paste my program here) If Status 'Outdoors/Front Door Motion-Low Bat' is On Then Send notification blah blah blah Wait 12 hours Run Program 'Front Door LBC' (Then Path) [which is this program] Else Wait 12 hours

Ok, maybe I didn't describe this too well. I have a motion sensor which I would to have notify me when the battery is low so I know to replace it. I attached a screen shot. See the device called Front Door Motion-Low Bat. It says it's off which I take to mean the battery is fine. I test this in a short program by checking to see if Front Door Motion-Low Bat is On. If so, it sends me a text. Otherwise it waits 12 hours and tests again. I get the text every 12 hours saying the battery is low BUT the Low Bat status is ALWAYS Off. Apparently the program is not the way to check if the battery is low. Ideas? Sent from my iPad using Tapatalk

I have a very short program that checks the status of the Insteon Motion Sensor Loew Battery indicator. If it's On, it sends me a text so I know it's low and needs to be replaced. If it's not, it waits 12 hours and checks again. I am getting a text indicating that the Low Battery is On even though it shows it's off in the Admin Console. What's up with this?

I have a gas, two stage furnace. Sounds like INSTEON is the easiest way to go. Thanks for the info.

I searched this forum for information on this question and there are so many threads out there on thermostats, I'm hoping you'll humor one more. I have a 4 zone heating/cooling system in my home with simple programmable thermostats. I have an ISY994i and many INSTEON devices I control. I'd like to add thermostats to that list. Is the INSTEON 2441TH the way to go? Is NEST compatible with the ISY994i? Are there better options than INSTEON? Any help would be greatly appreciated. Thanks!

Never mind. Problem solved. Somehow the scene got removed from the button I was using to test on RL#2. All is working now. Whew! Thanks for everyone's help.

LeeG, I had done a reset on both and now have done Restore Device on both. RL#1 works fine. RL#2 does not. Even the all on and all off don't work. It does a successful write updates to the device but it doesn't work. The address of the new PLM is 34.E7.BB. The Device Links Table from RL#2 is here: https://monosnap.com/file/8H89r1d2BxL3zOXIObVzuaMTRtU9TM

Well I tried but it got this error. In case the link didn't work, here is a link from my dropbox: https://www.dropbox.com/s/s2tv09naap98zx3/Screen%20Shot%202015-08-05%20at%207.43.25%20AM.jpg?dl=0

Well I moved the RL to a different location and this time it worked. It wrote the updates. That's the good news. The bad news is none of the 6 buttons work to turn on devices assigned to those buttons. BUT if I press the ALL ON button, all devices controlled by the RL come on and ALL OFF turns them all off. Progress I guess. Now I need to figure out why buttons 1-6 don't work. Suggestions on where to look?

Well I did that - unplugged everything and plugged it back in - no luck.

I put the RemoteLinc 1 at the opposite end of our ranch house as the PLM. It finally did finish the Write Updates. However, now none of the action buttons work. Ugh again! I put RemoteLinc 2 in the same spot and tried to update it and it still won't finish. I never had this issue with the old PLM. Should I try unplugging it and the ISY and start over?

Brian H, tried that. No luck. Ugh.

I also try running the Diagnostics show device link table and it errors out saying Failed writing device link [-200000/-51] and Failed reading device link [-200000/-5]. Not sure if that helps or not. Techman, the motion sensors are done. It's just the RemoteLinc's now I am having issues with.

Thanks. I moved them farther away and still no luck. I did all my motion sensors from my office and they updated fine. It's just my RemoteLinc's that won't update. Do I have to delete them and re-add them? Pain but I could do it I suppose.

And I followed the instructions posted by paulbates above (followed the link to the wiki) and now my RemoteLinc's won't take the update when I put them in programming mode and tell the Admin console to Write updates to the device. It goes through but the little 1011 icon is still in front of the device. Does the same thing on both RemoteLincs and yet I have Remote Linc 2 that updated fine. Ideas? UPDATE: looks like it gets to 80% on status bar and then it quits.

Can I put motion sensors, which are not in easily accessible locations, in programming mode from the Admin console? Or do I really have to physically open them and press the button inside?

The last cap in the list at the top of this thread (UTS1C100MDD 10uF 16 volt) is not available at Mouser. Is there an alternative cap or alternative supplier for all the caps?