Dean

I reached out to RCS and they said I should follow up with the company that sold it to me. I'll contact Smarthome today. Sent from my iPhone using Tapatalk

I've looked on the Forums, but cannot find this problem from anyone else. My z-wave thermostat programs are working fine to set the setpoint, etc. The problem is that the thermostat is ignoring the fact that the temperature is colder than the setting and doesn't turn off. For example, the setpoint is at 75, but the room temperature is 71. Temperature in room is accurate. I've seen calibration procedures when room temperature isn't correct, but nothing when this happens. Any ideas?

I wanted to go back and close the loop on this thread. I did finally determine the problem. I did a search through all of the programs and found an older program that ran during the night. For some reason, it was actually resetting the buttons status. Once I deleted that program, everything has been fine. So, stray programs that are not being used need to be disabled or deleted.

I had tried this before, but couldn't remember what happened, so I added the steps to set the backlight for the OFF button to On 15/Off 5. I checked the program and it worked exactly as it should, as the backlights came on as programmed. However, when I got up this morning, all of the fan lights on the button were dark/off/no lights. One more bit of information, I have 3 fan/lights under the deck. All 3 lights and Fan 1 are controlled by this 6 button KPL. The other 2 fans are controlled by an 8 button device with the top 4 controlling fan 2 and the bottom 4 controlling fan 3. The buttons all work great to control the lights and the fans. However, both of these KPLs behave the same way as to no "OFF" light lit in the morning. I've looked everywhere to see if there is another program issuing some type of command, but can't find anything. I incorporated the set backlight levels program into the same program that turns all the downstairs lights, etc. off after 1 am, if I have left them on. The backlight commands are the last three lines in that program and occur after the scene commands to set the fans off. One other note. If I remove the 3 backlight commands and run the program, the backlights behave as they should, with the OFF light on the buttons coming on to full 15 brightness. Something has to be changing this later in the "wee hours" of the morning, after the program runs. Don't you think? Here is the code. Downstairs Lights Off After Midnight - [iD 004C][Parent 0048] If Time is 1:00:00AM Then Set Scene 'Downstairs Lights' Off Set Scene 'Guest BR Lights' Off Set Scene 'Guest Bathroom Lights' Off Set Scene 'Terrace Fan 1 Off' On Set Scene 'Terrace Fan 2 Off' On Set Scene 'Terrace Fan 3 Off' On Set 'Terrace Main Lights Button / Terrace Fan 1 Button - Off' On 15 / Off 5 (Backlight Level) Set 'Terrace Fan 2 Button - High / Terrace Fan 2 Button - Off' On 15 / Off 5 (Backlight Level) Set 'Terrace Fan 3 Button - High / Terrace Fan 3 Button - Off' On 15 / Off 5 (Backlight Level) Else - No Actions - (To add one, press 'Action')

Sorry that I forgot to update the status of this post, but after a few days, it started working correctly. Has worked correctly since.

I have a 6 button KPL that controls a ceiling fan and its light. Standard setup with High, Medium, Low, Off in a scene. All settings appear to be correct in each scene. I've triple checked that the controller in the scene is also set at the appropriate level, e.g. High, Medium, etc. for that particular scene, the fan would be High and the button labeled High would be on, etc. The fan and lights work fine and when I press the High button, the button lights up, etc. Now, when I turn the fan Off, the Off Light does illuminate, showing the fan is off. However, the next morning, when I look at the button, none of the fan lights are illuminated. The Off Light button should be on, since that is the way I left it. I do have a program that runs at 2 pm that sets the scene "Terrace Fan OFF' to the on position, in the event I have left the fan on overnight. Not sure why that would make a difference, but just throwing it in there. Any ideas why the fan buttons are losing their state and ALL going off on the KPL? The next day, when I press any fan speed button, it lights and the operation returns to normal with the appropriate button being lit to denote the status. I can also control the fan and state of the buttons from the console. If the lights are unlit, I can turn on a scene and the appropriate light goes on and the fan starts.

Very good instructions. I think I did as instructions said by clicking on the controller in the scene, then clicking Copy Scene Attributes. However, the buttons still did not control the scene. It still worked fine from the ISY. Did I miss or misunderstand something?

I'm having a similar problem in that the scene works fine, but the fan does not turn on from any of the button speeds. Here's the strange part. If I turn on the fan from the console or from Mobilinc, the keypadlinc does turn the fan off! The keypadlinc was giving problems, so I did a factory reset, then restored. It was after the restore that it stopped working correctly. Does it sound like I need to delete the scenes and start over?

Thanks for the compliment. This was one of the only thing I had a say in when we "downsized" to this house a couple of years back. There's a bedroom downstairs too, so you're right, it would be tough to be relegated to the basement! I think you're right on the leak sensor(s). I have two that I haven't assigned to a location as yet. I'll probably switch those out, as they seem to be working fine from those locations. Thanks again for all your help!

Here is a photo of the area of the bar in question. I have noted the location of the access point, etc. One update . . . the sensor still did not send the heartbeat, therefore the variable stayed at 2. I have a spare leak sensor which is new. I installed it as a seperate instance and placed it under the bar. It has operated fine. I think the leak sensor in question is faulty. How do I explain that when it does behave correctly when I place it into a small amount of water and then dry it off.

It's a wooden custom cabinetry bar with granite tops. The sink is a metal bar sink. I have the leak sensor sitting underneath the cabinet, just below the drain and water pipes. To the left of the sink is a stainless steel dishwasher and to the left of that a stainless steel bar refrigerator. I'll provide pictures when I return home later today. Strange thing is that it worked fine for a long time and has just started displaying this behavior. I can't think of anything that has changed in that area.

1. Yes, it did change state, going from Dry-on to Dry-off, etc. It blinked every XX seconds. No fluttering. 2. Pressing the set button did cause the status to change back to Dry-On, etc. 3. Here's where it gets kind of strange. I placed the leak detector in the same dish in water underneath the sink at the bar. That's about 20 feet from my office. (always convenient to have a bar near the office, but I digress) When I placed it in the water, the status did not change in the console, but I did immediately get the text message telling me there was a leak detected at that location. I then took the sensor out from under the bar and sat it on the cabinet and repeated the test. Status changed in the console and the text message came, When I dried and reset the leak sensor, it behaved correctly. That being said, I have an access point plugged into the wall not 5 feet from the bar sink. Of course, there is a dishwasher and and refrigerator in its path of direct sight from the access point to the sensor underneath the bar. I also have the paceyben Somfy bridge in the outlet just above the sink, although I don't know if that relays a signal. I'm going to leave it on the top of the cabinet for the 26 hours and see what happens, unless you have another suggestion. Thanks again for all your help!

So, after the 26 hours, it went back to displaying the same behavior, so I'm back to square one. I have to think these two are defective. I don't see a production date, but the revision is 4714REV2.3.

I'll wait the 26 hours (or so) and see if the message goes away regarding the heartbeat. If not, I think I will delete those two and add them back. Thanks again for all the help!

Yes, the variables changed appropriately in the Admin Console when I placed it into the water and then when I dried it off and pressed the set button. Text messages performed correctly, as well. Also, the leak sensor that showed both Dry and Wet On at the same time . . . I deleted it and added it back in. That fixed the issue with that sensor, as it now shows Dry-On and Wet-Off. It also passed the water test.

By the way, I tried placing the leak sensor that showed Dry-On and Wet-On at the same time into the water. It immediately switched Dry to Off and sent the appropriate text message. When I dried it off and pressed the set button, it toggled back to Dry-On, but Wet stayed in the off position. So, the Wet-On is there all the time. Sign me - "Puzzled in Atlanta"

Placed it into water and it immediately switched to Wet-On and sent the appropriate text message. I dried it, then pressed the set switch and it returned to Dry-On.

All of my leak sensors are v.43. I tried to toggle on another sensor and it didn't toggle either. You know, I just noticed that one of my leak sensors is showing Dry - On, Wet - On and Heartbeat - Off. I tried a hard reset and it stayed the same. I'm struggling to understand how I would ever be confident enough to install a whole house cutoff valve. I can't see how these would not be communicating, given the number of devices that I have and also a couple of access points to make sure that I had bridged the two phases.

1. Done, no problems. 2. Change the variable value back to 1, but pressing the set button to toggle from wet to dry did not change the state in the Admin console. Dry stayed on and wet stayed off. Heartbeat still shows on. 3. I've tried a hard reset, but have not tried to remove and re add back. I will try that later today. Thanks for your guidance. BTW, all code for each sensor (I have 10) is identical and these are the only 2 that are not playing well with others.

All of the "Variable Control 2" programs use "Control". I'm using the programs from Belias. Here's what I have. AC-Variable Control 2 - [iD 00E7][Parent 0082] If Control 'Sensors - Leak / Leak-AC-Dry / Leak-AC-Wet' is switched On Or Control 'Sensors - Leak / Leak-AC-Dry / Leak-AC-Wet' is switched Off Then $s_LeakAC = 1 Wait 25 hours and 10 seconds $s_LeakAC = 2 Else - No Actions - (To add one, press 'Action')

I'm showing a last run time of 2:09 pm on 6/3/2016 on both sensors, give or take a few seconds. That means it hasn't run in in over 10 days. Both summaries show a status of "True". Regarding the communication, see the last post where I mentioned that I moved both sensors to my desk. Also, I replaced both batteries with new batteries that showed full charge.

Yes, I found that in one of the Forum posts and actually picked up the leak sensors, switched to new batteries and placed them on my desk. I have at least 50-75 devices in my system, so "something" should be nearby for it to pick up a signal. I also tried the factory reset, etc. Edit: I have an RF 2 wire switch right behind my desk, but will also try plugging in a lamplinc module near the desk.

I have a couple of leak sensors that do not seem to be behaving well. I'm using the communication programs that have been posted for the leak sensors by Belias, but two sensors constantly report a status of 2, causing the messages to be triggered. When I view them in the ISY Admin Console, both sensors show "Heartbeat - On", just like all of the other leak sensors. Is there something I am missing? I've tried factory reset to no avail. All of my leak sensors are v.43. I've searched through the Forum sections, but can't find a similar problem. If the heartbeat status is ON, why would it say that the Heartbeat was missed?