LeeG Posted January 29, 2013 Posted January 29, 2013 Then Repeat Every 2 minutes and 30 seconds Send Notification to 'Default' content 'Water Sensor wet' Actually with the Wait of 2 minutes the email would come every 4 minutes 30 seconds if the Wait is included.
RichTJ99 Posted January 30, 2013 Posted January 30, 2013 Last question on this. Why is it only going off once & then not sending another email? The sensor is sitting on a wet plate & is in the 'on' mode for wet. If Status 'Main: Basement Water-Wet' is On Then Send Notification to 'Entire House Email' content 'Main Basement: Water Sensor wet' Repeat Every 1 minute Else - No Actions - (To add one, press 'Action')
LeeG Posted January 30, 2013 Posted January 30, 2013 The Repeat goes BEFORE the statement(s) to repeat. If Status 'Main: Basement Water-Wet' is On Then Repeat Every 1 minute Send Notification to 'Entire House Email' content 'Main Basement: Water Sensor wet' Else - No Actions - (To add one, press 'Action')
RichTJ99 Posted January 30, 2013 Posted January 30, 2013 Does it make any difference if I have control vs status? I am still not clear on the difference but I have a similar program using triggerlincs & you helped me set it up using the control switched on/not switched off. If Control 'Main: Basement Water-Wet' is switched On And Control 'Main: Basement Water-Wet' is not switched Off Then Repeat Every 1 minute Send Notification to 'Entire House Email' content 'Main Basement: Water Sensor wet' Else - No Actions - (To add one, press 'Action')
LeeG Posted January 30, 2013 Posted January 30, 2013 If Control only looks at commands coming from the device being tested. A command must flow from the device and it must match the specified command to trigger the Program. If the device sends two On commands for example because its paddle/button/sensor is turned On twice (tapping On paddle twice - not Fast On) the Program is triggered twice. If Status looks at the ISY Current State column information. Anytime the Current State information changes the Program is triggered. The example above where the device is turned On twice by tapping paddle twice triggers the Program only once. Status has to change to trigger the Program. The second On paddle press does not trigger the Program because it was already On from the first On paddle press. When other Controllers can change the state of the tested device such that the Current State column information changes the Program is triggered. Thus If Status can cause a Program to trigger either when the device itself is turned On/Off with its paddle/button/sensor or is turned On/Off by another Controller. In this specific case the Leak Sensor nodes are Controller Only nodes, they have no Responder capability. They cannot be turned On/Off by another Controller so only changes the Leak Sensor initiates causes Current State column (Status) to change. Which a Program uses, If Control or If Status, depends on what you want to trigger the Program. The Leak Sensor is somewhat unique because it does not normally generate two On commands in a row and it is not a Responder so If Control and If Status come close to working the same. However, all the rules apply from an ISY perspective. If Control is looking at commands flowing from the device, If Status is checking the information in the Current State column of the device. EDIT: in the last posted example the line for 'is not switched Off' serves no purpose.
dennisric Posted January 31, 2013 Posted January 31, 2013 I just received my Leak Sensors. I was able to add to the ISY994i/pro and it sees the two nodes wet and dry. I am not getting any status for on or off showing in the ISY. I put sensor on wet paper towel and LED flashed no on status showing. I then tried by pressing the set button and still get no ON or OFF status. I purchased six of these and tried two with the same results. What am I doing wrong???
LeeG Posted January 31, 2013 Posted January 31, 2013 Need to test in water for actual wet/dry test. A damp towel does not provide enough conductivity between the two metal feet. Not much water needed, about 1/8 inch in a plate. Not deep enough to get inside the device. Just enough to make a water bridge between the two metal feet. However, if Set button tap is not registered by a change in both the Dry and Wet nodes it sounds like it is out of RF range.
dennisric Posted January 31, 2013 Posted January 31, 2013 I am in the same room with an access point so RF is not a problem. In the ISY it does not initially show any status on or off for the wet or dry. Shouldn't it show wet as off and dry as on by what I have read here so far? And then when it contacts water it will show on for dry and off for wet. I have also tried in direct water but still no status. Thanks
dennisric Posted January 31, 2013 Posted January 31, 2013 Oh by the way also using latest firmware 3.3.10
LeeG Posted January 31, 2013 Posted January 31, 2013 The initial Current State values for both nodes will be blank until some communication is received from the Leak Sensor. What does Help | About show for Firmware and UI levels? With the Leak Sensor in linking mode (Set button press until LED is blinking continuously), right click Dry node and select Diagnostics | Show Device Links Table. Post the results. Unless the forum has been fixed it will not accept an image file. Either the image has to be placed on a hosting site or Save the Show results and post the file. It will be an XML file which must be posted with all the XML tags. EDIT: I changed the above to use Dry node for Show Device Links Table. The Wet node does not have the Diagnostic choice.
dennisric Posted January 31, 2013 Posted January 31, 2013 Device links table: 0:0ff8:00 00 00.00.00 00 00 00 ISY links table: shows same as above with my PLM listed twice RF is no problem thru whole house. I am using three remotelincs and they work anywhere plus from outside.
LeeG Posted January 31, 2013 Posted January 31, 2013 The Leak Sensor Link Database was not created. Are there any Green Icons to the left of either the Dry or Wet nodes? If a Pro ISY are RF device updates turned off? Perhaps the Leak Sensor timed out of manual linking mode before the link records could be created. Put the Leak Sensor into link mode and right click the Dry node, select Restore Device to rebuild the Leak Sensor link database. Run another Show Device Links Table after the Restore Device to verify there are two E2 Controller link records in the device itself.
dennisric Posted January 31, 2013 Posted January 31, 2013 WOW! That was it. The device didn't get the update. Now showing status. Thanks big time LeeG Can always find help here from a great group of people.
LeeG Posted January 31, 2013 Posted January 31, 2013 Glad that was the problem. You mentioned there are multiple Leak Sensors. Only one RF only device can be added at a time. If more than one RF only device is put into linking mode at the same time they cancel each other out making writes to the device impossible.
dennisric Posted January 31, 2013 Posted January 31, 2013 Could the names of the nodes be changed to show the actual status of it. Such as rename dry node to wet and rename wet node to dry then when it detects water the wet node would show ON. And when it is dry the dry node would show ON. Sounds more logical to me. Why is it backwards. Or is this a change that has to be done in the firmware.
LeeG Posted January 31, 2013 Posted January 31, 2013 Once the Leak Sensor has been tested in water (not a damp towel) the nodes will have this Status In water, Wet node On, Dry node Off Out of water, Wet node Off, Dry node On
dennisric Posted January 31, 2013 Posted January 31, 2013 I did a good test in water, you are right. But I see that as long as it is wet the LED keeps flashing on the sensor meaning that it has to constantly send signal to give wet status. So much for a ten year battery if it gets wet and stays wet for several hours. I am rethinking my purchase of these. I think Smarthome is not that smart. How much thinking goes into their products before putting them to market. I think these should lock into the wet mode until user does a press of the set button to reset the sensor. You could get a small leak which dries and then turns into a bigger leak later. Maybe they try to push things out too fast. Well the thirty day money back is OK with me, just have the cost of shipping back and must put insurance on also. I sent some stuff back once and they claimed they never received them. I was out about a hundred bucks. Not impressed with these. Just to add I took the bottom off and I can't believe that the sensor tabs on the bottom are just pressure set to the main board. These should be hard wired to the board. Something as important as a water sensor should have good reliable connection. If I keep these I will make a modification and solder some good wire leads to connect them. Made very CHEAP! Some insurance companies will give a discount if you have water detection setup.
LeeG Posted January 31, 2013 Posted January 31, 2013 As far as the wet detection goes, it depends on what is in the water. The event trace was started when I initially read your last post. Once the Leak Sensor turned Wet On and stabilized no additional messages were generated until I remove the Leak Sensor from the water. About 10 minutes elapsed once the Leak Sensor stabilized Wet until I removed it from the water and it went Dry. Group 2 On is Wet, Group 1 On is Dry. As water sensors go this one is a significant improvement over others Smarthome has marketed. Some of the water sensors that connected to I/O Lincs would not trip even when the senor was submerged in water. This one works pretty well compared to others I have tested. I guess most anything would be better than what they had before. It will also depend on how much stuff is in the water. The subdivision is on a community well which has very good water as far as bad chemicals are concerned but it is well water. I run the water through a good charcoal whole house filter. My water may have more mineral content than a municipal water supply. Wed 01/30/2013 10:21:05 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.02 CB 11 02 LTONRR (02) Wed 01/30/2013 10:21:05 PM : [std-Group ] 21.7A.CC-->Group=2, Max Hops=3, Hops Left=2 Wed 01/30/2013 10:21:05 PM : [ 21 7A CC 2] DON 2 Wed 01/30/2013 10:21:05 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.02 CB 11 02 LTONRR (02) Wed 01/30/2013 10:21:05 PM : [std-Group ] 21.7A.CC-->Group=2, Max Hops=3, Hops Left=2 Wed 01/30/2013 10:21:05 PM : [iNST-DUP ] Previous message ignored. Wed 01/30/2013 10:21:06 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.02 CB 11 02 LTONRR (02) Wed 01/30/2013 10:21:06 PM : [std-Group ] 21.7A.CC-->Group=2, Max Hops=3, Hops Left=2 Wed 01/30/2013 10:21:06 PM : [ 21 7A CC 2] DON 2 Wed 01/30/2013 10:21:06 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.02 CB 11 02 LTONRR (02) Wed 01/30/2013 10:21:06 PM : [std-Group ] 21.7A.CC-->Group=2, Max Hops=3, Hops Left=2 Wed 01/30/2013 10:21:06 PM : [iNST-DUP ] Previous message ignored. Wed 01/30/2013 10:21:06 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.02 CB 11 02 LTONRR (02) Wed 01/30/2013 10:21:06 PM : [std-Group ] 21.7A.CC-->Group=2, Max Hops=3, Hops Left=2 Wed 01/30/2013 10:21:06 PM : [ 21 7A CC 2] DON 2 Wed 01/30/2013 10:21:06 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.02 CB 11 02 LTONRR (02) Wed 01/30/2013 10:21:06 PM : [std-Group ] 21.7A.CC-->Group=2, Max Hops=3, Hops Left=2 Wed 01/30/2013 10:21:06 PM : [iNST-DUP ] Previous message ignored. Wed 01/30/2013 10:21:08 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.02 CB 11 02 LTONRR (02) Wed 01/30/2013 10:21:08 PM : [std-Group ] 21.7A.CC-->Group=2, Max Hops=3, Hops Left=2 Wed 01/30/2013 10:21:08 PM : [ 21 7A CC 2] DON 2 Wed 01/30/2013 10:21:09 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.02 CB 11 02 LTONRR (02) Wed 01/30/2013 10:21:09 PM : [std-Group ] 21.7A.CC-->Group=2, Max Hops=3, Hops Left=2 Wed 01/30/2013 10:21:09 PM : [iNST-DUP ] Previous message ignored. Wed 01/30/2013 10:31:20 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.01 CB 11 01 LTONRR (01) Wed 01/30/2013 10:31:20 PM : [std-Group ] 21.7A.CC-->Group=1, Max Hops=3, Hops Left=2 Wed 01/30/2013 10:31:20 PM : [ 21 7A CC 1] DON 1 Wed 01/30/2013 10:31:20 PM : [ 21 7A CC 1] ST 255 Wed 01/30/2013 10:31:20 PM : [ 21 7A CC 2] ST 0 Wed 01/30/2013 10:31:22 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.01 CB 11 01 LTONRR (01) Wed 01/30/2013 10:31:22 PM : [std-Group ] 21.7A.CC-->Group=1, Max Hops=3, Hops Left=2 Wed 01/30/2013 10:31:22 PM : [iNST-DUP ] Previous message ignored. Wed 01/30/2013 10:31:22 PM : [iNST-SRX ] 02 50 21.7A.CC 11.00.01 CB 06 00 (00) Wed 01/30/2013 10:31:22 PM : [std-Group ] 21.7A.CC-->11.00.01, Max Hops=3, Hops Left=2 Wed 01/30/2013 10:31:23 PM : [iNST-SRX ] 02 50 21.7A.CC 11.00.01 CB 06 00 (00) Wed 01/30/2013 10:31:23 PM : [std-Group ] 21.7A.CC-->11.00.01, Max Hops=3, Hops Left=2 Wed 01/30/2013 10:31:23 PM : [iNST-DUP ] Previous message ignored.
az1324 Posted January 31, 2013 Posted January 31, 2013 I did a good test in water, you are right. But I see that as long as it is wet the LED keeps flashing on the sensor meaning that it has to constantly send signal to give wet status. So much for a ten year battery if it gets wet and stays wet for several hours. I am rethinking my purchase of these. I think Smarthome is not that smart. How much thinking goes into their products before putting them to market. I think these should lock into the wet mode until user does a press of the set button to reset the sensor. You could get a small leak which dries and then turns into a bigger leak later. Maybe they try to push things out too fast. Well the thirty day money back is OK with me, just have the cost of shipping back and must put insurance on also. I sent some stuff back once and they claimed they never received them. I was out about a hundred bucks. Not impressed with these. Just to add I took the bottom off and I can't believe that the sensor tabs on the bottom are just pressure set to the main board. These should be hard wired to the board. Something as important as a water sensor should have good reliable connection. If I keep these I will make a modification and solder some good wire leads to connect them. Made very CHEAP! Some insurance companies will give a discount if you have water detection setup. As long as it is wet, it will send wet messages every 15 seconds. Wouldn't you rather it keep trying to notify you of a problem than conserve its battery? If your small leak dries but then turns into a big leak then it will start notifying you again (you've already been notified about the small leak). So I don't really see a problem here.
ejh Posted February 10, 2013 Posted February 10, 2013 I've added 2 Leak sensors. However I'm unable to see the status of either. I did link 1 sensor WET node to a light and when the sensor is placed in a dish of water the light will immediately turn on. I've tried deleting and re-adding the device as well as looking at the link tables of the Dry node. Link Table of device 0 0FF8 : E2 01 1C.FB.8D FF 1F 01 1 0FF0 : E2 01 1C.FB.8D FF 1F 02 2 0FE8 : 00 00 00.00.00 00 00 00 Same as above in PLM Linking looks OK?? I know I'm receiving the signal as the linked lamp does turn on. The above table is for the second device that is not linked to the lamp so there is no entry for the lamp. Still no status of either device WET or DRY. Any suggestions are welcome.
LeeG Posted February 10, 2013 Posted February 10, 2013 Could be a finger check but the link records are not correct. They should be 0FF8 : E2 01 19.70.06 FF 1F 01 0FF0 : E2 02 19.70.06 FF 1F 02 Also the PLM links must be Responder links A2 01 ...... and A2 02 ...... When the link records are correct be sure the Leak Sensor is near a Dual Band device. After the Leak Sensor has been successfully added a tap of the Set button will alternate between Wet and Dry messages which can be traced with the Event Viewer set to LEVEL 3.
ejh Posted February 10, 2013 Posted February 10, 2013 Well cut and paste got me again. On the Device links it is 01 the 02 in the respective lines. However in the PLM the are E2 not A2. Is see nothing in the Event viewer for either device at L3 Both devices show E2 in the PLM Thanks for the help.
ejh Posted February 10, 2013 Posted February 10, 2013 After reading my post bad spelling may make things unclear The device links are as you suggested E2 01 and second line E2 02 The PLM links are not as you thought they should be they are E2 ..... Then E2....... Not A2.... A2.... I am about 6 feet away from one of my dual band devices and about 20 feet away from the dual band PLM. I do not think it is a signal issue. I think what I'm see is both links as controller and none as responder? However putting one device linked to a light in a dish of water will light the lamp. It will not shut it off I need to command it off manually.
LeeG Posted February 10, 2013 Posted February 10, 2013 The PLM link records must be Responder link records which start with A2. Have no explanation for what you are seeing in the PLM unless some manual linking was done. The PLM will not pass inbound messages from the Leak Sensor to the ISY application without A2 Responder link records with the Leak Sensor Insteon address 873 : 0369 : A2 01 21.7A.CC 10 08 3E 874 : 036A : A2 02 21.7A.CC 10 08 3E
Recommended Posts