Techman Posted May 8, 2016 Share Posted May 8, 2016 Being that the 2441ZTH thermostat doesn't have a low battery or heartbeat node I use a simple program to monitor communications. This assumes that the humidity will change at least once within a 6 hour period which then restarts the 6 hour timer loop. Program Thermostat monitor IF Status 'wireless thermostat' >5% (Humidity) Then Wait 6 hours Send notification to 'your email' content 'Wireless thermostat Communication failure' Run Program 'Thermostat monitor' (IF) Else no action Link to comment
PhanTomiZ Posted May 25, 2016 Share Posted May 25, 2016 Hi, I know this isn't about the wireless tstat, but I have a Remotelinc 2 keypad 4 scene that I'd like to monitor the battery. My wife went to use it yesterday; she was frustrated that it didn't work so she unplugged my lamp module and plugged the light into the wall. . This is a first with my Insteon products. She used to do this when I used X10. Never knew why my appliances and lights weren't working, only to find the modules unplugged and sitting on the floor. Anyhow, do you have such a program to check battery status of a Remotelinc 2 keypad? Thanks PhaTomiZ Link to comment
paulbates Posted May 25, 2016 Share Posted May 25, 2016 Hi- Unfortunately that product does not provide battery alerts. You have to keep track on a calendar and keep it charged regularly. I have one in our bed room for my wife to use for the attic fan, its the same thing. I charge it in the spring and it lasts the year. I know its "old school", but I have a spreadsheet for battery powered HA items and charge/change them on a schedule and not wait for an indicator to come on, Charging the remote is on that list. I've had fewer problems with Insteon battery powered devices approaching it that way. Paul Link to comment
PhanTomiZ Posted May 25, 2016 Share Posted May 25, 2016 I was just thinking about a program to count the amount of button presses before needing a charge. You think 5000 presses would be enough before sending an email notification to charge the unit? Link to comment
paulbates Posted May 25, 2016 Share Posted May 25, 2016 That's an interesting idea! However 5000 seems like a lot. If you averaged 4 presses a day, that would be 1250 days or 3.5 years. Mine doesn't make it over a year. The manual says 9 - 12 months per charge. Maybe start with 1000 and then see how long the charge takes. The manual says the charge should take an hour.. so use that as a factor to increase or decrease the count. e.g.. if it takes the full hour, lower the count and give it some room. If it takes half an hour, up it to 2500. I would leave extra room so you're definitely charging before it runs out. Maybe its pressed a lot more than 4 times a day.. measure that and adjust the program accordingly. Also, remember to use the "init to" function in your program after incrementing the variable you're counting with. Otherwise, the ISY will lose its memory of the count if you reboot or have a power outage Paul Link to comment
larryllix Posted May 25, 2016 Share Posted May 25, 2016 Mine go dead about every 4 months whether I use them or not. Link to comment
paulbates Posted May 25, 2016 Share Posted May 25, 2016 Wow. I've had mine for 2 years. It came charged and I charged it once this spring. I had an X10 key chain remote I replaced it with, I didn't change its battery that frequently either. Paul Link to comment
larryllix Posted May 25, 2016 Share Posted May 25, 2016 Yeah, I have many of the X10 keychain dongles and only some have had one battery change since the 1980s and still work. I have two RemoteLinc 4 rocker keypads and both get used about once per month, maybe. The oldest one has been recharged about 4 times in the last year and a half, and the other one has been recharged twice in the last year since purchase. They really need to be double sided taped to the side of an end or night table so they are in a consistent place for reliable usage but then the charger would need to come to them, every charge. Link to comment
PhanTomiZ Posted May 25, 2016 Share Posted May 25, 2016 That's an interesting idea! However 5000 seems like a lot. If you averaged 4 presses a day, that would be 1250 days or 3.5 years. Mine doesn't make it over a year. The manual says 9 - 12 months per charge. Maybe start with 1000 and then see how long the charge takes. The manual says the charge should take an hour.. so use that as a factor to increase or decrease the count. e.g.. if it takes the full hour, lower the count and give it some room. If it takes half an hour, up it to 2500. I would leave extra room so you're definitely charging before it runs out. Maybe its pressed a lot more than 4 times a day.. measure that and adjust the program accordingly. Also, remember to use the "init to" function in your program after incrementing the variable you're counting with. Otherwise, the ISY will lose its memory of the count if you reboot or have a power outage Paul First off...Many thanks for the "init to" function. I started keeping track of my furnace/air conditioner and dehumidifier cycles and cycle times, but after I updated to the next firmware version, I lost it all. This should protect these numbers from disappearing right? Just setup a quick program. Here is what my program looks like. Would you do it any different? Just seems like a repetition of many lines... RemoteLinc 2 If Status 'Mini Remote A 27 18 F9 1' is not Off Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote A Down 27 18 F9 2' is not Off Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote B Up 27 18 F9 3' is not Off Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote C Down 27 18 F9 6' is not Off Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote C Up 27 18 F9 5' is not Off Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote D Down 27 18 F9 8' is not Off Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote D Up 27 18 F9 7' is not Off Or Status 'Mini Remote A 27 18 F9 1 / Mini RemoteB Down 27 18 F9 4' is not Off Or Status 'Mini Remote A 27 18 F9 1' <= 100% Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote A Down 27 18 F9 2' <= 100% Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote B Up 27 18 F9 3' <= 100% Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote C Down 27 18 F9 6' <= 100% Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote C Up 27 18 F9 5' <= 100% Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote D Down 27 18 F9 8' <= 100% Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote D Up 27 18 F9 7' <= 100% Or Status 'Mini Remote A 27 18 F9 1 / Mini RemoteB Down 27 18 F9 4' <= 100% Then Wait 1 second $Mini_Remote_Linc += 1 $Mini_Remote_Linc Init To $Mini_Remote_Linc Else - No Actions - (To add one, press 'Action') Mini RemoteLinc 2 Charge Battery If $Mini_Remote_Linc is 1500 Then Send Notification to 'Default' content 'Default Subject' Else - No Actions - (To add one, press 'Action') Variable Link to comment
paulbates Posted May 25, 2016 Share Posted May 25, 2016 First off...Many thanks for the "init to" function. I started keeping track of my furnace/air conditioner and dehumidifier cycles and cycle times, but after I updated to the next firmware version, I lost it all. This should protect these numbers from disappearing right? That's correct. I do the same with Furnace/Air/humidify/fan and sprinkler control & reporting. Just setup a quick program. Here is what my program looks like. Would you do it any different? Just seems like a repetition of many lines... RemoteLinc 2 If Status 'Mini Remote A 27 18 F9 1' is not Off Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote A Down 27 18 F9 2' is not Off Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote B Up 27 18 F9 3' is not Off Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote C Down 27 18 F9 6' is not Off Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote C Up 27 18 F9 5' is not Off Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote D Down 27 18 F9 8' is not Off Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote D Up 27 18 F9 7' is not Off Or Status 'Mini Remote A 27 18 F9 1 / Mini RemoteB Down 27 18 F9 4' is not Off Or Status 'Mini Remote A 27 18 F9 1' <= 100% Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote A Down 27 18 F9 2' <= 100% Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote B Up 27 18 F9 3' <= 100% Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote C Down 27 18 F9 6' <= 100% Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote C Up 27 18 F9 5' <= 100% Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote D Down 27 18 F9 8' <= 100% Or Status 'Mini Remote A 27 18 F9 1 / Mini Remote D Up 27 18 F9 7' <= 100% Or Status 'Mini Remote A 27 18 F9 1 / Mini RemoteB Down 27 18 F9 4' <= 100% Then Wait 1 second $Mini_Remote_Linc += 1 $Mini_Remote_Linc Init To $Mini_Remote_Linc Else - No Actions - (To add one, press 'Action') Mini RemoteLinc 2 Charge Battery If $Mini_Remote_Linc is 1500 Then Send Notification to 'Default' content 'Default Subject' Else - No Actions - (To add one, press 'Action') Variable I've only used the mini remote for on/off. Another way is us "Control" and catch it in the act. You probably won't see some of these, like 'Fade' or 'Fast on' normally. You don't have to code for the ones that you don't use. Here are the possibilities: Paul Link to comment
PhanTomiZ Posted May 26, 2016 Share Posted May 26, 2016 Hi, Made a few small changes before going to bed...Got rid of the "is not Off" and only needed to keep the "<=100%". That should cover all scenarios. I replaced the Status with Control and saw no difference. Why would you suggest "Control"? Thanks for the different angle. PhanTomiZ Link to comment
larryllix Posted May 26, 2016 Share Posted May 26, 2016 If no change in status is had status will not trigger the program to keep track. Control will count signals sent regardless of status change in the end device. Link to comment
rafarataneneces Posted August 4, 2016 Share Posted August 4, 2016 Since the Insteon Wireless Thermostat is a complete failure 1) Can I use a REAL WIRED Insteon Thermostat and use it as Master/Slave for another Insteon Thermostat? I was thinking since the Insteon Thermostat is reliable, then maybe that could be done Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.