From: Eloy P. <pe...@ch...> - 2013-12-03 11:50:44
|
Thanks Kevin. Guess I'll find out soon because I bought a couple of these sensors. I figured their cost was nothing compared to the cost of cleaning up the mess caused by water damage. Cheers, Eloy Paris.- -------- Original message -------- From: Kevin Robert Keegan <ke...@kr...> Date: 12/02/2013 9:03 PM (GMT-06:00) To: Eloy Paris <pe...@ch...> Cc: MisterHouse Users <mis...@li...> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale I feel like some posted about the leak sensor before. Eitherway, yes Motion_Sensor is the way to go right now. In the future, it would be nice to add a battery level tracker to it. The leak sensor in theory has a heartbeat so that you can be sure it is still working. Although the remotelinc was supposed to have that heartbeat too, but it wasn't there. On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch...> wrote: Hello, Has anyone used the INSTEON water leak sensor with MisterHouse? http://www.smarthome.com/2852-222/p.aspx I don't recall a specific .mht file keyword for it but I would think it could be declared as some other existing device (like the motion sensor), or a specific object could be created for it based on an existing one (again, the motion sensor seems like a logical choice). Also, in case you were not aware, Smarthome is having a 20% off sale since last week. It will probably end tonight. Cheers, Eloy Paris.- ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk ________________________________________________________ To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 |
From: Eloy P. <pe...@ch...> - 2014-01-04 16:57:45
|
Hi Brad, H, Sorry, I have not had a chance yet to set up the INSTEON water leak sensors -- I received two but they are still in their original packaging. I'll post my findings as soon as I get a chance to try things out, though I don't know when that might be. Cheers, Eloy Paris.- On 01/03/2014 10:50 PM, Brad Yarotsky wrote: > I also have one and would be very interested. > > Thanks > Brad > > > Sent from Samsung Mobile > > > -------- Original message -------- > From: H Plato > Date:03/01/2014 7:56 PM (GMT-06:00) > To: Eloy Paris > Cc: MisterHouse Users > Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale > > Hi Eloy, did you get these working? I have one on order and hope to > get it next week. > > Sent from my mobile device. > > On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch... > <mailto:pe...@ch...>> wrote: > >> Thanks Kevin. Guess I'll find out soon because I bought a couple of >> these sensors. I figured their cost was nothing compared to the cost >> of cleaning up the mess caused by water damage. >> >> Cheers, >> >> Eloy Paris.- >> >> >> >> >> -------- Original message -------- >> From: Kevin Robert Keegan <ke...@kr... >> <mailto:ke...@kr...>> >> Date: 12/02/2013 9:03 PM (GMT-06:00) >> To: Eloy Paris <pe...@ch... <mailto:pe...@ch...>> >> Cc: MisterHouse Users <mis...@li... >> <mailto:mis...@li...>> >> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >> >> >> I feel like some posted about the leak sensor before. >> >> Eitherway, yes Motion_Sensor is the way to go right now. >> >> In the future, it would be nice to add a battery level tracker to it. >> The leak sensor in theory has a heartbeat so that you can be sure it >> is still working. Although the remotelinc was supposed to have that >> heartbeat too, but it wasn't there. >> >> >> On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch... >> <mailto:pe...@ch...>> wrote: >> >> Hello, >> >> Has anyone used the INSTEON water leak sensor with MisterHouse? >> >> http://www.smarthome.com/2852-222/p.aspx >> >> I don't recall a specific .mht file keyword for it but I would >> think it >> could be declared as some other existing device (like the motion >> sensor), or a specific object could be created for it based on an >> existing one (again, the motion sensor seems like a logical choice). >> >> Also, in case you were not aware, Smarthome is having a 20% off sale >> since last week. It will probably end tonight. >> >> Cheers, >> >> Eloy Paris.- >> |
From: H P. <hp...@gm...> - 2014-01-11 20:36:50
|
So I added the water sensor yesterday as a INSTEON_MOTIONSENSOR. Setup and link sync’ing seemed to work, I pressed the test button on the sensor and the MH object turned on, so that’s a good thing. The object hasn’t been set to off yet, so I’m going to have to put the thing in water to see if it sends an OFF when it is dry. On Jan 4, 2014, at 9:57 AM, Eloy Paris <pe...@ch...> wrote: > Hi Brad, H, > > Sorry, I have not had a chance yet to set up the INSTEON water leak sensors -- I received two but they are still in their original packaging. I'll post my findings as soon as I get a chance to try things out, though I don't know when that might be. > > Cheers, > > Eloy Paris.- > > On 01/03/2014 10:50 PM, Brad Yarotsky wrote: > >> I also have one and would be very interested. >> >> Thanks >> Brad >> >> >> Sent from Samsung Mobile >> >> >> -------- Original message -------- >> From: H Plato >> Date:03/01/2014 7:56 PM (GMT-06:00) >> To: Eloy Paris >> Cc: MisterHouse Users >> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >> >> Hi Eloy, did you get these working? I have one on order and hope to >> get it next week. >> >> Sent from my mobile device. >> >> On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch... >> <mailto:pe...@ch...>> wrote: >> >>> Thanks Kevin. Guess I'll find out soon because I bought a couple of >>> these sensors. I figured their cost was nothing compared to the cost >>> of cleaning up the mess caused by water damage. >>> >>> Cheers, >>> >>> Eloy Paris.- >>> >>> >>> >>> >>> -------- Original message -------- >>> From: Kevin Robert Keegan <ke...@kr... >>> <mailto:ke...@kr...>> >>> Date: 12/02/2013 9:03 PM (GMT-06:00) >>> To: Eloy Paris <pe...@ch... <mailto:pe...@ch...>> >>> Cc: MisterHouse Users <mis...@li... >>> <mailto:mis...@li...>> >>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>> >>> >>> I feel like some posted about the leak sensor before. >>> >>> Eitherway, yes Motion_Sensor is the way to go right now. >>> >>> In the future, it would be nice to add a battery level tracker to it. >>> The leak sensor in theory has a heartbeat so that you can be sure it >>> is still working. Although the remotelinc was supposed to have that >>> heartbeat too, but it wasn't there. >>> >>> >>> On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch... >>> <mailto:pe...@ch...>> wrote: >>> >>> Hello, >>> >>> Has anyone used the INSTEON water leak sensor with MisterHouse? >>> >>> http://www.smarthome.com/2852-222/p.aspx >>> >>> I don't recall a specific .mht file keyword for it but I would >>> think it >>> could be declared as some other existing device (like the motion >>> sensor), or a specific object could be created for it based on an >>> existing one (again, the motion sensor seems like a logical choice). >>> >>> Also, in case you were not aware, Smarthome is having a 20% off sale >>> since last week. It will probably end tonight. >>> >>> Cheers, >>> >>> Eloy Paris.- |
From: Kevin R. K. <ke...@kr...> - 2014-01-11 21:56:41
|
The "set" button on appliancelincs toggle on/off. Pressing the button again my get you an off message. Although it would be nice to know if it will naturally send an off message. On Sat, Jan 11, 2014 at 12:36 PM, H Plato <hp...@gm...> wrote: > So I added the water sensor yesterday as a INSTEON_MOTIONSENSOR. Setup and > link sync’ing seemed to work, I pressed the test button on the sensor and > the MH object turned on, so that’s a good thing. > > The object hasn’t been set to off yet, so I’m going to have to put the > thing in water to see if it sends an OFF when it is dry. > > > On Jan 4, 2014, at 9:57 AM, Eloy Paris <pe...@ch...> wrote: > > Hi Brad, H, > > Sorry, I have not had a chance yet to set up the INSTEON water leak > sensors -- I received two but they are still in their original packaging. > I'll post my findings as soon as I get a chance to try things out, though I > don't know when that might be. > > Cheers, > > Eloy Paris.- > > On 01/03/2014 10:50 PM, Brad Yarotsky wrote: > > I also have one and would be very interested. > > Thanks > Brad > > > Sent from Samsung Mobile > > > -------- Original message -------- > From: H Plato > Date:03/01/2014 7:56 PM (GMT-06:00) > To: Eloy Paris > Cc: MisterHouse Users > Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale > > Hi Eloy, did you get these working? I have one on order and hope to > get it next week. > > Sent from my mobile device. > > On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch... > <mailto:pe...@ch... <pe...@ch...>>> wrote: > > Thanks Kevin. Guess I'll find out soon because I bought a couple of > these sensors. I figured their cost was nothing compared to the cost > of cleaning up the mess caused by water damage. > > Cheers, > > Eloy Paris.- > > > > > -------- Original message -------- > From: Kevin Robert Keegan <ke...@kr... > <mailto:ke...@kr... <ke...@kr...>>> > Date: 12/02/2013 9:03 PM (GMT-06:00) > To: Eloy Paris <pe...@ch... <mailto:pe...@ch...<pe...@ch...> > >> > Cc: MisterHouse Users <mis...@li... > <mailto:mis...@li...<mis...@li...> > >> > Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale > > > I feel like some posted about the leak sensor before. > > Eitherway, yes Motion_Sensor is the way to go right now. > > In the future, it would be nice to add a battery level tracker to it. > The leak sensor in theory has a heartbeat so that you can be sure it > is still working. Although the remotelinc was supposed to have that > heartbeat too, but it wasn't there. > > > On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch... > <mailto:pe...@ch... <pe...@ch...>>> wrote: > > Hello, > > Has anyone used the INSTEON water leak sensor with MisterHouse? > > http://www.smarthome.com/2852-222/p.aspx > > I don't recall a specific .mht file keyword for it but I would > think it > could be declared as some other existing device (like the motion > sensor), or a specific object could be created for it based on an > existing one (again, the motion sensor seems like a logical choice). > > Also, in case you were not aware, Smarthome is having a 20% off sale > since last week. It will probably end tonight. > > Cheers, > > Eloy Paris.- > > > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > > |
From: Eloy P. <pe...@ch...> - 2014-01-11 22:17:20
|
H, Coincidentally, I also started playing with a water leak sensor yesterday. I manually linked it to the PLM and started to test. I think TriggerLinc is a better fit than the motion sensor. Here's what I have so far in my .mht file: INSTEON_TRIGGERLINC, 25.b0.fe:01, crawlspace_leak_dry, Leak_Sensors # 2213 v2.0 INSTEON_TRIGGERLINC, 25.b0.fe:02, crawlspace_leak_wet, Leak_Sensors # 2213 v2.0 INSTEON_TRIGGERLINC, 25.b0.fe:04, crawlspace_leak_heartbeat, Leak_Sensors # 2213 v2.0 I am seeing so odd things but I haven't had a chance to do more extensive tests. One odd thing is that I scanned the link table of the sensor and it came back empty (and this was after doing the manual link to the PLM). I don't know why. I'll send some print_log messages later (I'm on my way out now). Cheers, Eloy Paris.- On Sat, Jan 11, 2014 at 01:36:38PM -0700, H Plato wrote: > So I added the water sensor yesterday as a INSTEON_MOTIONSENSOR. Setup and link sync’ing seemed to work, I pressed the test button on the sensor and the MH object turned on, so that’s a good thing. > > The object hasn’t been set to off yet, so I’m going to have to put the thing in water to see if it sends an OFF when it is dry. > > > On Jan 4, 2014, at 9:57 AM, Eloy Paris <pe...@ch...> wrote: > > > Hi Brad, H, > > > > Sorry, I have not had a chance yet to set up the INSTEON water leak sensors -- I received two but they are still in their original packaging. I'll post my findings as soon as I get a chance to try things out, though I don't know when that might be. > > > > Cheers, > > > > Eloy Paris.- > > > > On 01/03/2014 10:50 PM, Brad Yarotsky wrote: > > > >> I also have one and would be very interested. > >> > >> Thanks > >> Brad > >> > >> > >> Sent from Samsung Mobile > >> > >> > >> -------- Original message -------- > >> From: H Plato > >> Date:03/01/2014 7:56 PM (GMT-06:00) > >> To: Eloy Paris > >> Cc: MisterHouse Users > >> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale > >> > >> Hi Eloy, did you get these working? I have one on order and hope to > >> get it next week. > >> > >> Sent from my mobile device. > >> > >> On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch... > >> <mailto:pe...@ch...>> wrote: > >> > >>> Thanks Kevin. Guess I'll find out soon because I bought a couple of > >>> these sensors. I figured their cost was nothing compared to the cost > >>> of cleaning up the mess caused by water damage. > >>> > >>> Cheers, > >>> > >>> Eloy Paris.- > >>> > >>> > >>> > >>> > >>> -------- Original message -------- > >>> From: Kevin Robert Keegan <ke...@kr... > >>> <mailto:ke...@kr...>> > >>> Date: 12/02/2013 9:03 PM (GMT-06:00) > >>> To: Eloy Paris <pe...@ch... <mailto:pe...@ch...>> > >>> Cc: MisterHouse Users <mis...@li... > >>> <mailto:mis...@li...>> > >>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale > >>> > >>> > >>> I feel like some posted about the leak sensor before. > >>> > >>> Eitherway, yes Motion_Sensor is the way to go right now. > >>> > >>> In the future, it would be nice to add a battery level tracker to it. > >>> The leak sensor in theory has a heartbeat so that you can be sure it > >>> is still working. Although the remotelinc was supposed to have that > >>> heartbeat too, but it wasn't there. > >>> > >>> > >>> On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch... > >>> <mailto:pe...@ch...>> wrote: > >>> > >>> Hello, > >>> > >>> Has anyone used the INSTEON water leak sensor with MisterHouse? > >>> > >>> http://www.smarthome.com/2852-222/p.aspx > >>> > >>> I don't recall a specific .mht file keyword for it but I would > >>> think it > >>> could be declared as some other existing device (like the motion > >>> sensor), or a specific object could be created for it based on an > >>> existing one (again, the motion sensor seems like a logical choice). > >>> > >>> Also, in case you were not aware, Smarthome is having a 20% off sale > >>> since last week. It will probably end tonight. > >>> > >>> Cheers, > >>> > >>> Eloy Paris.- > |
From: H P. <hp...@gm...> - 2014-01-12 17:16:50
|
Eloy, do you see ‘OFF’ messages as a triggerlinc? I put the sensor on a damp sponge (as the instructions recommend) and MH announces that there is water as the device gets turned on. I dried off the contacts, let it sit for a while and still no OFF command. Kevin, I also tried to press the set button again, that just sends ON commands. Does this device actually send OFF commands at all? On Jan 11, 2014, at 3:17 PM, Eloy Paris <pe...@ch...> wrote: > H, > > Coincidentally, I also started playing with a water leak sensor > yesterday. I manually linked it to the PLM and started to test. I think > TriggerLinc is a better fit than the motion sensor. Here's what I have > so far in my .mht file: > > INSTEON_TRIGGERLINC, 25.b0.fe:01, crawlspace_leak_dry, Leak_Sensors # 2213 v2.0 > INSTEON_TRIGGERLINC, 25.b0.fe:02, crawlspace_leak_wet, Leak_Sensors # 2213 v2.0 > INSTEON_TRIGGERLINC, 25.b0.fe:04, crawlspace_leak_heartbeat, Leak_Sensors # 2213 v2.0 > > I am seeing so odd things but I haven't had a chance to do more > extensive tests. One odd thing is that I scanned the link table of the > sensor and it came back empty (and this was after doing the manual link > to the PLM). I don't know why. > > I'll send some print_log messages later (I'm on my way out now). > > Cheers, > > Eloy Paris.- On Jan 11, 2014, at 2:56 PM, Kevin Robert Keegan <ke...@kr...> wrote: > The "set" button on appliancelincs toggle on/off. Pressing the button again my get you an off message. Although it would be nice to know if it will naturally send an off message. > > On Sat, Jan 11, 2014 at 01:36:38PM -0700, H Plato wrote: > >> So I added the water sensor yesterday as a INSTEON_MOTIONSENSOR. Setup and link sync’ing seemed to work, I pressed the test button on the sensor and the MH object turned on, so that’s a good thing. >> >> The object hasn’t been set to off yet, so I’m going to have to put the thing in water to see if it sends an OFF when it is dry. >> >> >> On Jan 4, 2014, at 9:57 AM, Eloy Paris <pe...@ch...> wrote: >> >>> Hi Brad, H, >>> >>> Sorry, I have not had a chance yet to set up the INSTEON water leak sensors -- I received two but they are still in their original packaging. I'll post my findings as soon as I get a chance to try things out, though I don't know when that might be. >>> >>> Cheers, >>> >>> Eloy Paris.- >>> >>> On 01/03/2014 10:50 PM, Brad Yarotsky wrote: >>> >>>> I also have one and would be very interested. >>>> >>>> Thanks >>>> Brad >>>> >>>> >>>> Sent from Samsung Mobile >>>> >>>> >>>> -------- Original message -------- >>>> From: H Plato >>>> Date:03/01/2014 7:56 PM (GMT-06:00) >>>> To: Eloy Paris >>>> Cc: MisterHouse Users >>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>> >>>> Hi Eloy, did you get these working? I have one on order and hope to >>>> get it next week. >>>> >>>> Sent from my mobile device. >>>> >>>> On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch... >>>> <mailto:pe...@ch...>> wrote: >>>> >>>>> Thanks Kevin. Guess I'll find out soon because I bought a couple of >>>>> these sensors. I figured their cost was nothing compared to the cost >>>>> of cleaning up the mess caused by water damage. >>>>> >>>>> Cheers, >>>>> >>>>> Eloy Paris.- >>>>> >>>>> >>>>> >>>>> >>>>> -------- Original message -------- >>>>> From: Kevin Robert Keegan <ke...@kr... >>>>> <mailto:ke...@kr...>> >>>>> Date: 12/02/2013 9:03 PM (GMT-06:00) >>>>> To: Eloy Paris <pe...@ch... <mailto:pe...@ch...>> >>>>> Cc: MisterHouse Users <mis...@li... >>>>> <mailto:mis...@li...>> >>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>> >>>>> >>>>> I feel like some posted about the leak sensor before. >>>>> >>>>> Eitherway, yes Motion_Sensor is the way to go right now. >>>>> >>>>> In the future, it would be nice to add a battery level tracker to it. >>>>> The leak sensor in theory has a heartbeat so that you can be sure it >>>>> is still working. Although the remotelinc was supposed to have that >>>>> heartbeat too, but it wasn't there. >>>>> >>>>> >>>>> On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch... >>>>> <mailto:pe...@ch...>> wrote: >>>>> >>>>> Hello, >>>>> >>>>> Has anyone used the INSTEON water leak sensor with MisterHouse? >>>>> >>>>> http://www.smarthome.com/2852-222/p.aspx >>>>> >>>>> I don't recall a specific .mht file keyword for it but I would >>>>> think it >>>>> could be declared as some other existing device (like the motion >>>>> sensor), or a specific object could be created for it based on an >>>>> existing one (again, the motion sensor seems like a logical choice). >>>>> >>>>> Also, in case you were not aware, Smarthome is having a 20% off sale >>>>> since last week. It will probably end tonight. >>>>> >>>>> Cheers, >>>>> >>>>> Eloy Paris.- >> |
From: Eloy P. <pe...@ch...> - 2014-01-12 17:36:01
|
Hi H, On Sun, Jan 12, 2014 at 10:16:40AM -0700, H Plato wrote: > Eloy, do you see ‘OFF’ messages as a triggerlinc? > > I put the sensor on a damp sponge (as the instructions recommend) and > MH announces that there is water as the device gets turned on. I dried > off the contacts, let it sit for a while and still no OFF command. > > Kevin, I also tried to press the set button again, that just sends ON > commands. > > Does this device actually send OFF commands at all? As I understand it, the device will only send a message to group 1 (dry) when the set button is pressed. I still have not had a chance to test this, though (sorry, busy weekend). The owner's manual says this related to "off" messages in the Troubleshooting section: Problem: Leak Sensor can turn responder on, but not off Cause: Leak Sensor is not designed to turn off responders. This prevents warning lights or other leak indication devices from turning off in the event the leak dries. I think this means that, once the sensor has detected water, the only way to reset it after the area has dried, is to tap the set button. Is it possible that you are seeing an "on" message sent to group 1 (dry) when the contacts are not sensing water and you tap the set button? I think the way it should work is this: Sensed water -> send "on" message to group 2 (wet) Not sensing water and set button is tapped -> send "on" message to group 1 (dry) Heartbeat -> send "on" message to group 4 (I haven't looked closely at the heartbeat message; I think it is also generated when the set button is tapped quickly; if this is the case then that would allow one to test the user code one sets up to handle the presence [or lack thereof] of the heartbeat). The commands are always "on", never "off". But they are sent to different groups to differentiate. Hopefully I'll have time to do more testing later today. Cheers, Eloy Paris.- > > On Jan 11, 2014, at 3:17 PM, Eloy Paris <pe...@ch...> wrote: > > > H, > > > > Coincidentally, I also started playing with a water leak sensor > > yesterday. I manually linked it to the PLM and started to test. I think > > TriggerLinc is a better fit than the motion sensor. Here's what I have > > so far in my .mht file: > > > > INSTEON_TRIGGERLINC, 25.b0.fe:01, crawlspace_leak_dry, Leak_Sensors # 2213 v2.0 > > INSTEON_TRIGGERLINC, 25.b0.fe:02, crawlspace_leak_wet, Leak_Sensors # 2213 v2.0 > > INSTEON_TRIGGERLINC, 25.b0.fe:04, crawlspace_leak_heartbeat, Leak_Sensors # 2213 v2.0 > > > > I am seeing so odd things but I haven't had a chance to do more > > extensive tests. One odd thing is that I scanned the link table of the > > sensor and it came back empty (and this was after doing the manual link > > to the PLM). I don't know why. > > > > I'll send some print_log messages later (I'm on my way out now). > > > > Cheers, > > > > Eloy Paris.- > > On Jan 11, 2014, at 2:56 PM, Kevin Robert Keegan <ke...@kr...> wrote: > > > The "set" button on appliancelincs toggle on/off. Pressing the button again my get you an off message. Although it would be nice to know if it will naturally send an off message. > > > > > > > On Sat, Jan 11, 2014 at 01:36:38PM -0700, H Plato wrote: > > > >> So I added the water sensor yesterday as a INSTEON_MOTIONSENSOR. Setup and link sync’ing seemed to work, I pressed the test button on the sensor and the MH object turned on, so that’s a good thing. > >> > >> The object hasn’t been set to off yet, so I’m going to have to put the thing in water to see if it sends an OFF when it is dry. > >> > >> > >> On Jan 4, 2014, at 9:57 AM, Eloy Paris <pe...@ch...> wrote: > >> > >>> Hi Brad, H, > >>> > >>> Sorry, I have not had a chance yet to set up the INSTEON water leak sensors -- I received two but they are still in their original packaging. I'll post my findings as soon as I get a chance to try things out, though I don't know when that might be. > >>> > >>> Cheers, > >>> > >>> Eloy Paris.- > >>> > >>> On 01/03/2014 10:50 PM, Brad Yarotsky wrote: > >>> > >>>> I also have one and would be very interested. > >>>> > >>>> Thanks > >>>> Brad > >>>> > >>>> > >>>> Sent from Samsung Mobile > >>>> > >>>> > >>>> -------- Original message -------- > >>>> From: H Plato > >>>> Date:03/01/2014 7:56 PM (GMT-06:00) > >>>> To: Eloy Paris > >>>> Cc: MisterHouse Users > >>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale > >>>> > >>>> Hi Eloy, did you get these working? I have one on order and hope to > >>>> get it next week. > >>>> > >>>> Sent from my mobile device. > >>>> > >>>> On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch... > >>>> <mailto:pe...@ch...>> wrote: > >>>> > >>>>> Thanks Kevin. Guess I'll find out soon because I bought a couple of > >>>>> these sensors. I figured their cost was nothing compared to the cost > >>>>> of cleaning up the mess caused by water damage. > >>>>> > >>>>> Cheers, > >>>>> > >>>>> Eloy Paris.- > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> -------- Original message -------- > >>>>> From: Kevin Robert Keegan <ke...@kr... > >>>>> <mailto:ke...@kr...>> > >>>>> Date: 12/02/2013 9:03 PM (GMT-06:00) > >>>>> To: Eloy Paris <pe...@ch... <mailto:pe...@ch...>> > >>>>> Cc: MisterHouse Users <mis...@li... > >>>>> <mailto:mis...@li...>> > >>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale > >>>>> > >>>>> > >>>>> I feel like some posted about the leak sensor before. > >>>>> > >>>>> Eitherway, yes Motion_Sensor is the way to go right now. > >>>>> > >>>>> In the future, it would be nice to add a battery level tracker to it. > >>>>> The leak sensor in theory has a heartbeat so that you can be sure it > >>>>> is still working. Although the remotelinc was supposed to have that > >>>>> heartbeat too, but it wasn't there. > >>>>> > >>>>> > >>>>> On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch... > >>>>> <mailto:pe...@ch...>> wrote: > >>>>> > >>>>> Hello, > >>>>> > >>>>> Has anyone used the INSTEON water leak sensor with MisterHouse? > >>>>> > >>>>> http://www.smarthome.com/2852-222/p.aspx > >>>>> > >>>>> I don't recall a specific .mht file keyword for it but I would > >>>>> think it > >>>>> could be declared as some other existing device (like the motion > >>>>> sensor), or a specific object could be created for it based on an > >>>>> existing one (again, the motion sensor seems like a logical choice). > >>>>> > >>>>> Also, in case you were not aware, Smarthome is having a 20% off sale > >>>>> since last week. It will probably end tonight. > >>>>> > >>>>> Cheers, > >>>>> > >>>>> Eloy Paris.- > >> > |
From: H P. <hp...@gm...> - 2014-01-12 18:26:42
|
Thanks Eloy, I think you’re right, there are messages to other groups. I only have one item defined in my items.mht: INSTEON_MOTIONSENSOR, 25.AB.F9, sensor_basement_water, Sensors #2213 REV2.0 And I see in the log that it is sending ‘grp: 02’ messages as well. Anyways, interested in what you find out. Do I have to relink the sensor and the PLM if I change the object type from MOTIONSENSOR to TRIGGERLINC? 01/12/14 11:16:25 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9000002cb1102 01/12/14 11:16:25 AM [Insteon::BaseInterface] DEBUG3: Message received with 2 hops left, delaying next transmit by 250 milliseconds to avoid collisions. 01/12/14 11:16:25 AM [Insteon::BaseInterface] Warn! Unable to locate object for source: 25abf9 and group: 02 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9000002cb1102 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate incoming message from an unknown device. Id: 25abf9 Grp: 02 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9223e0f411102 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received with 0 hops left, plus ACK will take 1 to deliver, delaying next transmit by 150 milliseconds to avoid collisions. 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate object for source: 25abf9 and group: 02 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9110102cb0600 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received with 2 hops left, delaying next transmit by 250 milliseconds to avoid collisions. 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate object for source: 25abf9 and group: 02 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9110102cb0600 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate incoming message from an unknown device. Id: 25abf9 Grp: 02 On Jan 12, 2014, at 10:35 AM, Eloy Paris <pe...@ch...> wrote: > Hi H, > > On Sun, Jan 12, 2014 at 10:16:40AM -0700, H Plato wrote: > >> Eloy, do you see ‘OFF’ messages as a triggerlinc? >> >> I put the sensor on a damp sponge (as the instructions recommend) and >> MH announces that there is water as the device gets turned on. I dried >> off the contacts, let it sit for a while and still no OFF command. >> >> Kevin, I also tried to press the set button again, that just sends ON >> commands. >> >> Does this device actually send OFF commands at all? > > As I understand it, the device will only send a message to group 1 (dry) > when the set button is pressed. I still have not had a chance to test > this, though (sorry, busy weekend). > > The owner's manual says this related to "off" messages in the > Troubleshooting section: > > Problem: Leak Sensor can turn responder on, but not off > > Cause: Leak Sensor is not designed to turn off responders. This prevents > warning lights or other leak indication devices from turning off in the > event the leak dries. > > I think this means that, once the sensor has detected water, the only > way to reset it after the area has dried, is to tap the set button. > > Is it possible that you are seeing an "on" message sent to group 1 (dry) > when the contacts are not sensing water and you tap the set button? > > I think the way it should work is this: > > Sensed water -> send "on" message to group 2 (wet) > > Not sensing water and set button is tapped -> send "on" message to group > 1 (dry) > > Heartbeat -> send "on" message to group 4 (I haven't looked closely at > the heartbeat message; I think it is also generated when the set button > is tapped quickly; if this is the case then that would allow one to test > the user code one sets up to handle the presence [or lack thereof] of > the heartbeat). > > The commands are always "on", never "off". But they are sent to > different groups to differentiate. > > Hopefully I'll have time to do more testing later today. > > Cheers, > > Eloy Paris.- > >> >> On Jan 11, 2014, at 3:17 PM, Eloy Paris <pe...@ch...> wrote: >> >>> H, >>> >>> Coincidentally, I also started playing with a water leak sensor >>> yesterday. I manually linked it to the PLM and started to test. I think >>> TriggerLinc is a better fit than the motion sensor. Here's what I have >>> so far in my .mht file: >>> >>> INSTEON_TRIGGERLINC, 25.b0.fe:01, crawlspace_leak_dry, Leak_Sensors # 2213 v2.0 >>> INSTEON_TRIGGERLINC, 25.b0.fe:02, crawlspace_leak_wet, Leak_Sensors # 2213 v2.0 >>> INSTEON_TRIGGERLINC, 25.b0.fe:04, crawlspace_leak_heartbeat, Leak_Sensors # 2213 v2.0 >>> >>> I am seeing so odd things but I haven't had a chance to do more >>> extensive tests. One odd thing is that I scanned the link table of the >>> sensor and it came back empty (and this was after doing the manual link >>> to the PLM). I don't know why. >>> >>> I'll send some print_log messages later (I'm on my way out now). >>> >>> Cheers, >>> >>> Eloy Paris.- >> >> On Jan 11, 2014, at 2:56 PM, Kevin Robert Keegan <ke...@kr...> wrote: >> >>> The "set" button on appliancelincs toggle on/off. Pressing the button again my get you an off message. Although it would be nice to know if it will naturally send an off message. >> >> >> >>> >>> On Sat, Jan 11, 2014 at 01:36:38PM -0700, H Plato wrote: >>> >>>> So I added the water sensor yesterday as a INSTEON_MOTIONSENSOR. Setup and link sync’ing seemed to work, I pressed the test button on the sensor and the MH object turned on, so that’s a good thing. >>>> >>>> The object hasn’t been set to off yet, so I’m going to have to put the thing in water to see if it sends an OFF when it is dry. >>>> >>>> >>>> On Jan 4, 2014, at 9:57 AM, Eloy Paris <pe...@ch...> wrote: >>>> >>>>> Hi Brad, H, >>>>> >>>>> Sorry, I have not had a chance yet to set up the INSTEON water leak sensors -- I received two but they are still in their original packaging. I'll post my findings as soon as I get a chance to try things out, though I don't know when that might be. >>>>> >>>>> Cheers, >>>>> >>>>> Eloy Paris.- >>>>> >>>>> On 01/03/2014 10:50 PM, Brad Yarotsky wrote: >>>>> >>>>>> I also have one and would be very interested. >>>>>> >>>>>> Thanks >>>>>> Brad >>>>>> >>>>>> >>>>>> Sent from Samsung Mobile >>>>>> >>>>>> >>>>>> -------- Original message -------- >>>>>> From: H Plato >>>>>> Date:03/01/2014 7:56 PM (GMT-06:00) >>>>>> To: Eloy Paris >>>>>> Cc: MisterHouse Users >>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>> >>>>>> Hi Eloy, did you get these working? I have one on order and hope to >>>>>> get it next week. >>>>>> >>>>>> Sent from my mobile device. >>>>>> >>>>>> On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch... >>>>>> <mailto:pe...@ch...>> wrote: >>>>>> >>>>>>> Thanks Kevin. Guess I'll find out soon because I bought a couple of >>>>>>> these sensors. I figured their cost was nothing compared to the cost >>>>>>> of cleaning up the mess caused by water damage. >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Eloy Paris.- >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -------- Original message -------- >>>>>>> From: Kevin Robert Keegan <ke...@kr... >>>>>>> <mailto:ke...@kr...>> >>>>>>> Date: 12/02/2013 9:03 PM (GMT-06:00) >>>>>>> To: Eloy Paris <pe...@ch... <mailto:pe...@ch...>> >>>>>>> Cc: MisterHouse Users <mis...@li... >>>>>>> <mailto:mis...@li...>> >>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>> >>>>>>> >>>>>>> I feel like some posted about the leak sensor before. >>>>>>> >>>>>>> Eitherway, yes Motion_Sensor is the way to go right now. >>>>>>> >>>>>>> In the future, it would be nice to add a battery level tracker to it. >>>>>>> The leak sensor in theory has a heartbeat so that you can be sure it >>>>>>> is still working. Although the remotelinc was supposed to have that >>>>>>> heartbeat too, but it wasn't there. >>>>>>> >>>>>>> >>>>>>> On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch... >>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> Has anyone used the INSTEON water leak sensor with MisterHouse? >>>>>>> >>>>>>> http://www.smarthome.com/2852-222/p.aspx >>>>>>> >>>>>>> I don't recall a specific .mht file keyword for it but I would >>>>>>> think it >>>>>>> could be declared as some other existing device (like the motion >>>>>>> sensor), or a specific object could be created for it based on an >>>>>>> existing one (again, the motion sensor seems like a logical choice). >>>>>>> >>>>>>> Also, in case you were not aware, Smarthome is having a 20% off sale >>>>>>> since last week. It will probably end tonight. >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Eloy Paris.- >>>> >> |
From: Eloy P. <pe...@ch...> - 2014-01-13 01:43:27
|
Hi H, I'm getting increasingly frustrated with the INSTEON Water Leak Sensor because I am getting mixed/odd results. I have the sensor sitting on water right now and the last message that was sent was an "on" message to the "dry" group (group #1). When I first put it on top of water I saw a message sent to the "wet" group (group #2) but then messages to the "dry" group followed. I don't get it. The sensor also seems to send "on" messages to the "dry" group when it's removed from water. Perhaps this is by design, though I am not sure. If this is the case then I don't understand the need for tapping the set button to reset the sensor after it has sensed water (per the instructions that came in the original package). In addition, after removing the sensor from water, every time I tap the set button the sensor seems to toggle the messages that it sends: I tap one time and it sends a message to the "dry" group followed by a heartbeat message a few seconds later. I tap a second time and it sends a message to the "wet" group followed by the heartbeat sensor a few seconds later. All in all, I think TRIGGERLINC is a much better fit than MOTIONSENSOR -- all you have to do is to define three objects: for groups 1, 2, and 4. That should get rid of the "Warn! Unable to locate object for source: 25abf9 and group: 02" message. I don't think you need to relink the sensor to the PLM if you change to TriggerLinc. I am not sure but I think the PLM needs the responder records for groups 2 and 4 (I'm sure others will keep me honest here). That is easily accomplished by running a "sync links" on the group 1 object. I think MH support for this device is ready (in the form of a TriggerLinc); I just need to figure out why the sensor itself (not MH) seems to be behaving erratically... I purchased two sensors so I'll be testing the other sensor as well to see if it behaves like the first. BTW, I also noticed that the sensor I have been playing with was re-transmitting messages. I think it was because it came linked to some other device that I don't have in my network. After I reset the device to factory defaults and re-linked to my PLM the retransmissions seem to have stopped. I'll post more as I find new information. Cheers, Eloy Paris.- On 01/12/2014 01:26 PM, H Plato wrote: > Thanks Eloy, I think you’re right, there are messages to other groups. I only have one item defined in my items.mht: > > INSTEON_MOTIONSENSOR, 25.AB.F9, sensor_basement_water, Sensors #2213 REV2.0 > > And I see in the log that it is sending ‘grp: 02’ messages as well. > > Anyways, interested in what you find out. Do I have to relink the sensor and the PLM if I change the object type from MOTIONSENSOR to TRIGGERLINC? > > 01/12/14 11:16:25 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9000002cb1102 > 01/12/14 11:16:25 AM [Insteon::BaseInterface] DEBUG3: Message received with 2 hops left, delaying next transmit by 250 milliseconds to avoid collisions. > 01/12/14 11:16:25 AM [Insteon::BaseInterface] Warn! Unable to locate object for source: 25abf9 and group: 02 > 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9000002cb1102 > 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate incoming message from an unknown device. Id: 25abf9 Grp: 02 > 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9223e0f411102 > 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received with 0 hops left, plus ACK will take 1 to deliver, delaying next transmit by 150 milliseconds to avoid collisions. > 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate object for source: 25abf9 and group: 02 > 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9110102cb0600 > 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received with 2 hops left, delaying next transmit by 250 milliseconds to avoid collisions. > 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate object for source: 25abf9 and group: 02 > 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9110102cb0600 > 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate incoming message from an unknown device. Id: 25abf9 Grp: 02 > > > > On Jan 12, 2014, at 10:35 AM, Eloy Paris <pe...@ch...> wrote: > >> Hi H, >> >> On Sun, Jan 12, 2014 at 10:16:40AM -0700, H Plato wrote: >> >>> Eloy, do you see ‘OFF’ messages as a triggerlinc? >>> >>> I put the sensor on a damp sponge (as the instructions recommend) and >>> MH announces that there is water as the device gets turned on. I dried >>> off the contacts, let it sit for a while and still no OFF command. >>> >>> Kevin, I also tried to press the set button again, that just sends ON >>> commands. >>> >>> Does this device actually send OFF commands at all? >> >> As I understand it, the device will only send a message to group 1 (dry) >> when the set button is pressed. I still have not had a chance to test >> this, though (sorry, busy weekend). >> >> The owner's manual says this related to "off" messages in the >> Troubleshooting section: >> >> Problem: Leak Sensor can turn responder on, but not off >> >> Cause: Leak Sensor is not designed to turn off responders. This prevents >> warning lights or other leak indication devices from turning off in the >> event the leak dries. >> >> I think this means that, once the sensor has detected water, the only >> way to reset it after the area has dried, is to tap the set button. >> >> Is it possible that you are seeing an "on" message sent to group 1 (dry) >> when the contacts are not sensing water and you tap the set button? >> >> I think the way it should work is this: >> >> Sensed water -> send "on" message to group 2 (wet) >> >> Not sensing water and set button is tapped -> send "on" message to group >> 1 (dry) >> >> Heartbeat -> send "on" message to group 4 (I haven't looked closely at >> the heartbeat message; I think it is also generated when the set button >> is tapped quickly; if this is the case then that would allow one to test >> the user code one sets up to handle the presence [or lack thereof] of >> the heartbeat). >> >> The commands are always "on", never "off". But they are sent to >> different groups to differentiate. >> >> Hopefully I'll have time to do more testing later today. >> >> Cheers, >> >> Eloy Paris.- >> >>> >>> On Jan 11, 2014, at 3:17 PM, Eloy Paris <pe...@ch...> wrote: >>> >>>> H, >>>> >>>> Coincidentally, I also started playing with a water leak sensor >>>> yesterday. I manually linked it to the PLM and started to test. I think >>>> TriggerLinc is a better fit than the motion sensor. Here's what I have >>>> so far in my .mht file: >>>> >>>> INSTEON_TRIGGERLINC, 25.b0.fe:01, crawlspace_leak_dry, Leak_Sensors # 2213 v2.0 >>>> INSTEON_TRIGGERLINC, 25.b0.fe:02, crawlspace_leak_wet, Leak_Sensors # 2213 v2.0 >>>> INSTEON_TRIGGERLINC, 25.b0.fe:04, crawlspace_leak_heartbeat, Leak_Sensors # 2213 v2.0 >>>> >>>> I am seeing so odd things but I haven't had a chance to do more >>>> extensive tests. One odd thing is that I scanned the link table of the >>>> sensor and it came back empty (and this was after doing the manual link >>>> to the PLM). I don't know why. >>>> >>>> I'll send some print_log messages later (I'm on my way out now). >>>> >>>> Cheers, >>>> >>>> Eloy Paris.- >>> >>> On Jan 11, 2014, at 2:56 PM, Kevin Robert Keegan <ke...@kr...> wrote: >>> >>>> The "set" button on appliancelincs toggle on/off. Pressing the button again my get you an off message. Although it would be nice to know if it will naturally send an off message. >>> >>> >>> >>>> >>>> On Sat, Jan 11, 2014 at 01:36:38PM -0700, H Plato wrote: >>>> >>>>> So I added the water sensor yesterday as a INSTEON_MOTIONSENSOR. Setup and link sync’ing seemed to work, I pressed the test button on the sensor and the MH object turned on, so that’s a good thing. >>>>> >>>>> The object hasn’t been set to off yet, so I’m going to have to put the thing in water to see if it sends an OFF when it is dry. >>>>> >>>>> >>>>> On Jan 4, 2014, at 9:57 AM, Eloy Paris <pe...@ch...> wrote: >>>>> >>>>>> Hi Brad, H, >>>>>> >>>>>> Sorry, I have not had a chance yet to set up the INSTEON water leak sensors -- I received two but they are still in their original packaging. I'll post my findings as soon as I get a chance to try things out, though I don't know when that might be. >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Eloy Paris.- >>>>>> >>>>>> On 01/03/2014 10:50 PM, Brad Yarotsky wrote: >>>>>> >>>>>>> I also have one and would be very interested. >>>>>>> >>>>>>> Thanks >>>>>>> Brad >>>>>>> >>>>>>> >>>>>>> Sent from Samsung Mobile >>>>>>> >>>>>>> >>>>>>> -------- Original message -------- >>>>>>> From: H Plato >>>>>>> Date:03/01/2014 7:56 PM (GMT-06:00) >>>>>>> To: Eloy Paris >>>>>>> Cc: MisterHouse Users >>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>> >>>>>>> Hi Eloy, did you get these working? I have one on order and hope to >>>>>>> get it next week. >>>>>>> >>>>>>> Sent from my mobile device. >>>>>>> >>>>>>> On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch... >>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>> >>>>>>>> Thanks Kevin. Guess I'll find out soon because I bought a couple of >>>>>>>> these sensors. I figured their cost was nothing compared to the cost >>>>>>>> of cleaning up the mess caused by water damage. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> Eloy Paris.- >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -------- Original message -------- >>>>>>>> From: Kevin Robert Keegan <ke...@kr... >>>>>>>> <mailto:ke...@kr...>> >>>>>>>> Date: 12/02/2013 9:03 PM (GMT-06:00) >>>>>>>> To: Eloy Paris <pe...@ch... <mailto:pe...@ch...>> >>>>>>>> Cc: MisterHouse Users <mis...@li... >>>>>>>> <mailto:mis...@li...>> >>>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>>> >>>>>>>> >>>>>>>> I feel like some posted about the leak sensor before. >>>>>>>> >>>>>>>> Eitherway, yes Motion_Sensor is the way to go right now. >>>>>>>> >>>>>>>> In the future, it would be nice to add a battery level tracker to it. >>>>>>>> The leak sensor in theory has a heartbeat so that you can be sure it >>>>>>>> is still working. Although the remotelinc was supposed to have that >>>>>>>> heartbeat too, but it wasn't there. >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch... >>>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> Has anyone used the INSTEON water leak sensor with MisterHouse? >>>>>>>> >>>>>>>> http://www.smarthome.com/2852-222/p.aspx >>>>>>>> >>>>>>>> I don't recall a specific .mht file keyword for it but I would >>>>>>>> think it >>>>>>>> could be declared as some other existing device (like the motion >>>>>>>> sensor), or a specific object could be created for it based on an >>>>>>>> existing one (again, the motion sensor seems like a logical choice). >>>>>>>> >>>>>>>> Also, in case you were not aware, Smarthome is having a 20% off sale >>>>>>>> since last week. It will probably end tonight. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> Eloy Paris.- >>>>> >>> > |
From: H P. <hp...@gm...> - 2014-01-13 03:26:35
|
Hi Eloy, I’ve set my water leak sensor the same as you and see if I get similar results. I set mine up in my items_mht as you have, and then selected ‘sync links’ on the new objects (sensor_basement_water, sensor_basement_water_wet and sensor_basement_water_hb). I see this in the logs: 01/12/14 08:20:08 PM Running: sensor basement water sync links 01/12/14 08:20:08 PM [Insteon::BaseController] WARN! The ALDB of $sensor_basement_water is unknown, links will be added to devices linked to this device, but no links will be added to $sensor_basement_water. Please rescan this device and attempt sync links again. 01/12/14 08:20:08 PM [Insteon::BaseController] Nothing to do when syncing links for $sensor_basement_water 01/12/14 08:20:08 PM $sensor_basement_water completed sync links 01/12/14 08:20:13 PM Running: sensor basement water wet sync links 01/12/14 08:20:13 PM [Insteon::BaseController] WARN! The ALDB of $sensor_basement_water_wet is unknown, links will be added to devices linked to this device, but no links will be added to $sensor_basement_water_wet. Please rescan this device and attempt sync links again. 01/12/14 08:20:13 PM [Insteon::BaseController] Nothing to do when syncing links for $sensor_basement_water_wet 01/12/14 08:20:13 PM $sensor_basement_water_wet completed sync links 01/12/14 08:20:19 PM Running: sensor basement water hb sync links 01/12/14 08:20:19 PM [Insteon::BaseController] WARN! The ALDB of $sensor_basement_water_hb is unknown, links will be added to devices linked to this device, but no links will be added to $sensor_basement_water_hb. Please rescan this device and attempt sync links again. 01/12/14 08:20:19 PM [Insteon::BaseController] Adding responder record to $PLM from $sensor_basement_water_hb group = 04; cmd = add; is_controller = 0; data3 = 00; 01/12/14 08:20:19 PM [Insteon_PLM] DEBUG2: Sending obj=$PLM; interface_data=41A20425abf9000000 incurred delay of 0.00 seconds; starting hop-count: ? 01/12/14 08:20:19 PM [Insteon_PLM] DEBUG3: Sending PLM raw data: 026f41a20425abf9000000 01/12/14 08:20:19 PM [Insteon_PLM] DEBUG3: Received PLM raw data: 026f41a20425abf9000000 01/12/14 08:20:19 PM [Insteon_PLM] DEBUG3: Saving parsed data fragment: 026f41a20425abf9000000 01/12/14 08:20:19 PM [Insteon_PLM] DEBUG3: Prepending prior data fragment: 026f41a20425abf9000000 01/12/14 08:20:19 PM [Insteon_PLM] DEBUG3: Received PLM raw data: 026f41a20425abf900000006 01/12/14 08:20:19 PM [Insteon_PLM] DEBUG3: Received PLM acknowledge: obj=$PLM; interface_data=41A20425abf9000000 01/12/14 08:20:19 PM $sensor_basement_water_hb completed sync links On Jan 12, 2014, at 6:43 PM, Eloy Paris <pe...@ch...> wrote: > Hi H, > > I'm getting increasingly frustrated with the INSTEON Water Leak Sensor because I am getting mixed/odd results. I have the sensor sitting on water right now and the last message that was sent was an "on" message to the "dry" group (group #1). When I first put it on top of water I saw a message sent to the "wet" group (group #2) but then messages to the "dry" group followed. I don't get it. > > The sensor also seems to send "on" messages to the "dry" group when it's removed from water. Perhaps this is by design, though I am not sure. If this is the case then I don't understand the need for tapping the set button to reset the sensor after it has sensed water (per the instructions that came in the original package). > > In addition, after removing the sensor from water, every time I tap the set button the sensor seems to toggle the messages that it sends: I tap one time and it sends a message to the "dry" group followed by a heartbeat message a few seconds later. I tap a second time and it sends a message to the "wet" group followed by the heartbeat sensor a few seconds later. > > All in all, I think TRIGGERLINC is a much better fit than MOTIONSENSOR -- all you have to do is to define three objects: for groups 1, 2, and 4. That should get rid of the "Warn! Unable to locate object for source: 25abf9 and group: 02" message. > > I don't think you need to relink the sensor to the PLM if you change to TriggerLinc. I am not sure but I think the PLM needs the responder records for groups 2 and 4 (I'm sure others will keep me honest here). That is easily accomplished by running a "sync links" on the group 1 object. > > I think MH support for this device is ready (in the form of a TriggerLinc); I just need to figure out why the sensor itself (not MH) seems to be behaving erratically... > > I purchased two sensors so I'll be testing the other sensor as well to see if it behaves like the first. > > BTW, I also noticed that the sensor I have been playing with was re-transmitting messages. I think it was because it came linked to some other device that I don't have in my network. After I reset the device to factory defaults and re-linked to my PLM the retransmissions seem to have stopped. > > I'll post more as I find new information. > > Cheers, > > Eloy Paris.- > > On 01/12/2014 01:26 PM, H Plato wrote: > >> Thanks Eloy, I think you’re right, there are messages to other groups. I only have one item defined in my items.mht: >> >> INSTEON_MOTIONSENSOR, 25.AB.F9, sensor_basement_water, Sensors #2213 REV2.0 >> >> And I see in the log that it is sending ‘grp: 02’ messages as well. >> >> Anyways, interested in what you find out. Do I have to relink the sensor and the PLM if I change the object type from MOTIONSENSOR to TRIGGERLINC? >> >> 01/12/14 11:16:25 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9000002cb1102 >> 01/12/14 11:16:25 AM [Insteon::BaseInterface] DEBUG3: Message received with 2 hops left, delaying next transmit by 250 milliseconds to avoid collisions. >> 01/12/14 11:16:25 AM [Insteon::BaseInterface] Warn! Unable to locate object for source: 25abf9 and group: 02 >> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9000002cb1102 >> 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate incoming message from an unknown device. Id: 25abf9 Grp: 02 >> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9223e0f411102 >> 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received with 0 hops left, plus ACK will take 1 to deliver, delaying next transmit by 150 milliseconds to avoid collisions. >> 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate object for source: 25abf9 and group: 02 >> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9110102cb0600 >> 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received with 2 hops left, delaying next transmit by 250 milliseconds to avoid collisions. >> 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate object for source: 25abf9 and group: 02 >> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9110102cb0600 >> 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate incoming message from an unknown device. Id: 25abf9 Grp: 02 >> >> >> >> On Jan 12, 2014, at 10:35 AM, Eloy Paris <pe...@ch...> wrote: >> >>> Hi H, >>> >>> On Sun, Jan 12, 2014 at 10:16:40AM -0700, H Plato wrote: >>> >>>> Eloy, do you see ‘OFF’ messages as a triggerlinc? >>>> >>>> I put the sensor on a damp sponge (as the instructions recommend) and >>>> MH announces that there is water as the device gets turned on. I dried >>>> off the contacts, let it sit for a while and still no OFF command. >>>> >>>> Kevin, I also tried to press the set button again, that just sends ON >>>> commands. >>>> >>>> Does this device actually send OFF commands at all? >>> >>> As I understand it, the device will only send a message to group 1 (dry) >>> when the set button is pressed. I still have not had a chance to test >>> this, though (sorry, busy weekend). >>> >>> The owner's manual says this related to "off" messages in the >>> Troubleshooting section: >>> >>> Problem: Leak Sensor can turn responder on, but not off >>> >>> Cause: Leak Sensor is not designed to turn off responders. This prevents >>> warning lights or other leak indication devices from turning off in the >>> event the leak dries. >>> >>> I think this means that, once the sensor has detected water, the only >>> way to reset it after the area has dried, is to tap the set button. >>> >>> Is it possible that you are seeing an "on" message sent to group 1 (dry) >>> when the contacts are not sensing water and you tap the set button? >>> >>> I think the way it should work is this: >>> >>> Sensed water -> send "on" message to group 2 (wet) >>> >>> Not sensing water and set button is tapped -> send "on" message to group >>> 1 (dry) >>> >>> Heartbeat -> send "on" message to group 4 (I haven't looked closely at >>> the heartbeat message; I think it is also generated when the set button >>> is tapped quickly; if this is the case then that would allow one to test >>> the user code one sets up to handle the presence [or lack thereof] of >>> the heartbeat). >>> >>> The commands are always "on", never "off". But they are sent to >>> different groups to differentiate. >>> >>> Hopefully I'll have time to do more testing later today. >>> >>> Cheers, >>> >>> Eloy Paris.- >>> >>>> >>>> On Jan 11, 2014, at 3:17 PM, Eloy Paris <pe...@ch...> wrote: >>>> >>>>> H, >>>>> >>>>> Coincidentally, I also started playing with a water leak sensor >>>>> yesterday. I manually linked it to the PLM and started to test. I think >>>>> TriggerLinc is a better fit than the motion sensor. Here's what I have >>>>> so far in my .mht file: >>>>> >>>>> INSTEON_TRIGGERLINC, 25.b0.fe:01, crawlspace_leak_dry, Leak_Sensors # 2213 v2.0 >>>>> INSTEON_TRIGGERLINC, 25.b0.fe:02, crawlspace_leak_wet, Leak_Sensors # 2213 v2.0 >>>>> INSTEON_TRIGGERLINC, 25.b0.fe:04, crawlspace_leak_heartbeat, Leak_Sensors # 2213 v2.0 >>>>> >>>>> I am seeing so odd things but I haven't had a chance to do more >>>>> extensive tests. One odd thing is that I scanned the link table of the >>>>> sensor and it came back empty (and this was after doing the manual link >>>>> to the PLM). I don't know why. >>>>> >>>>> I'll send some print_log messages later (I'm on my way out now). >>>>> >>>>> Cheers, >>>>> >>>>> Eloy Paris.- >>>> >>>> On Jan 11, 2014, at 2:56 PM, Kevin Robert Keegan <ke...@kr...> wrote: >>>> >>>>> The "set" button on appliancelincs toggle on/off. Pressing the button again my get you an off message. Although it would be nice to know if it will naturally send an off message. >>>> >>>> >>>> >>>>> >>>>> On Sat, Jan 11, 2014 at 01:36:38PM -0700, H Plato wrote: >>>>> >>>>>> So I added the water sensor yesterday as a INSTEON_MOTIONSENSOR. Setup and link sync’ing seemed to work, I pressed the test button on the sensor and the MH object turned on, so that’s a good thing. >>>>>> >>>>>> The object hasn’t been set to off yet, so I’m going to have to put the thing in water to see if it sends an OFF when it is dry. >>>>>> >>>>>> >>>>>> On Jan 4, 2014, at 9:57 AM, Eloy Paris <pe...@ch...> wrote: >>>>>> >>>>>>> Hi Brad, H, >>>>>>> >>>>>>> Sorry, I have not had a chance yet to set up the INSTEON water leak sensors -- I received two but they are still in their original packaging. I'll post my findings as soon as I get a chance to try things out, though I don't know when that might be. >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Eloy Paris.- >>>>>>> >>>>>>> On 01/03/2014 10:50 PM, Brad Yarotsky wrote: >>>>>>> >>>>>>>> I also have one and would be very interested. >>>>>>>> >>>>>>>> Thanks >>>>>>>> Brad >>>>>>>> >>>>>>>> >>>>>>>> Sent from Samsung Mobile >>>>>>>> >>>>>>>> >>>>>>>> -------- Original message -------- >>>>>>>> From: H Plato >>>>>>>> Date:03/01/2014 7:56 PM (GMT-06:00) >>>>>>>> To: Eloy Paris >>>>>>>> Cc: MisterHouse Users >>>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>>> >>>>>>>> Hi Eloy, did you get these working? I have one on order and hope to >>>>>>>> get it next week. >>>>>>>> >>>>>>>> Sent from my mobile device. >>>>>>>> >>>>>>>> On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch... >>>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>>> >>>>>>>>> Thanks Kevin. Guess I'll find out soon because I bought a couple of >>>>>>>>> these sensors. I figured their cost was nothing compared to the cost >>>>>>>>> of cleaning up the mess caused by water damage. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> >>>>>>>>> Eloy Paris.- >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -------- Original message -------- >>>>>>>>> From: Kevin Robert Keegan <ke...@kr... >>>>>>>>> <mailto:ke...@kr...>> >>>>>>>>> Date: 12/02/2013 9:03 PM (GMT-06:00) >>>>>>>>> To: Eloy Paris <pe...@ch... <mailto:pe...@ch...>> >>>>>>>>> Cc: MisterHouse Users <mis...@li... >>>>>>>>> <mailto:mis...@li...>> >>>>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>>>> >>>>>>>>> >>>>>>>>> I feel like some posted about the leak sensor before. >>>>>>>>> >>>>>>>>> Eitherway, yes Motion_Sensor is the way to go right now. >>>>>>>>> >>>>>>>>> In the future, it would be nice to add a battery level tracker to it. >>>>>>>>> The leak sensor in theory has a heartbeat so that you can be sure it >>>>>>>>> is still working. Although the remotelinc was supposed to have that >>>>>>>>> heartbeat too, but it wasn't there. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch... >>>>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>>>> >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> Has anyone used the INSTEON water leak sensor with MisterHouse? >>>>>>>>> >>>>>>>>> http://www.smarthome.com/2852-222/p.aspx >>>>>>>>> >>>>>>>>> I don't recall a specific .mht file keyword for it but I would >>>>>>>>> think it >>>>>>>>> could be declared as some other existing device (like the motion >>>>>>>>> sensor), or a specific object could be created for it based on an >>>>>>>>> existing one (again, the motion sensor seems like a logical choice). >>>>>>>>> >>>>>>>>> Also, in case you were not aware, Smarthome is having a 20% off sale >>>>>>>>> since last week. It will probably end tonight. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> >>>>>>>>> Eloy Paris.- >>>>>> >>>> >> > |
From: Eloy P. <pe...@ch...> - 2014-01-13 03:57:18
|
Hi H, Like you, I also got links added to my PLM after creating entries for the sensor in my .mht file and sync'ing links. I think that part is fine. It seems like what we are seeing in terms of sensor behavior is "normal". I found this thread that has good information: http://forum.universal-devices.com/viewtopic.php?f=27&t=10366 This post in particular describes what I *think* I am seeing: http://forum.universal-devices.com/viewtopic.php?p=80455#p80455 I finally figured out how to scan the link table. I thought I needed to put the sensor in setup mode (keep setup button pressed for a few seconds until LED starts flashing) and then use the scan link table voice command for the sensor. But no, that gave me an empty link table. Instead, what works for me is running the scan link table voice command for the sensor and then quickly tapping the setup button of the sensor (which causes the sensor to send a message and I guess wake up and go into listening mode). This way I was able to see what was present in the link table of a sensor that I just took out of the box and manually linked to the PLM: 01/12/14 10:28:31 PM [Insteon::BaseObject] The Link Table Version for $dishwasher_leak_dry has been updated to version number 19 01/12/14 10:28:31 PM [Insteon::AllLinkDatabase] Link table for $dishwasher_leak_dry health: good 01/12/14 10:28:31 PM [Insteon::AllLinkDatabase] [0x0fef] is empty 01/12/14 10:28:31 PM [Insteon::AllLinkDatabase] [0x0ff7] contlr(ff) record to $PLM, (d1:03, d2:00, d3:00) 01/12/14 10:28:31 PM [Insteon::AllLinkDatabase] [0x0fff] rspndr(01) record to 25b399 (02): onlevel=on and ramp=none (d3:00) That responder record to 25b399 is pretty weird. I have no such device, and as far as I can tell, the sensor does not support being a responder. Anyway, I performed a factory reset and now I only have the controller link to the PLM (after manually linking to the PLM). This is with my second sensor. The behavior I am seeing is similar to the behavior of the first sensor. This is what I see after putting the sensor on top of water: 01/12/14 10:49:28 PM [Insteon::BaseInterface] Received message from: $dishwasher_leak_wet; command: on; type: alllink; group: 02 01/12/14 10:49:28 PM [Insteon::BaseObject] $dishwasher_leak_wet::set_receive(on, $dishwasher_leak_wet) 01/12/14 10:49:29 PM [Insteon::BaseInterface] Received message from: $dishwasher_leak_dry; command: on; type: alllink; group: 01 01/12/14 10:49:29 PM [Insteon::BaseObject] $dishwasher_leak_dry::set_receive(on, $dishwasher_leak_dry) 01/12/14 10:49:29 PM [Insteon::BaseInterface] WARN! Dropped duplicate incoming message 25b2a0000001c71101, from $dishwasher_leak_dry 01/12/14 10:49:29 PM [Insteon::BaseInterface] Received message from: $dishwasher_leak_dry; command: on; type: cleanup; group: 01 01/12/14 10:49:29 PM [Insteon::BaseObject] Ignoring Received Direct AllLink Cleanup Message for $dishwasher_leak_dry since AllLink Broadcast Message was Received. 01/12/14 10:49:29 PM [Insteon::BaseInterface] Received message from: $dishwasher_leak_dry; command: link_cleanup_report; type: alllink; group: 01 01/12/14 10:49:29 PM [Insteon::BaseObject] DEBUG Received AllLink Cleanup Success for $dishwasher_leak_dry 01/12/14 10:49:30 PM [Insteon::BaseInterface] WARN! Dropped duplicate incoming message 25b2a0110101c70600, from $dishwasher_leak_dry So I get a message sent to the "wet" group but then I get messages sent to the "dry" group. I don't understand why. In some other tests I've only seen the messages sent to the "dry" group, which makes it even weirder. Darn; I still don't understand how this sensor is supposed to work. But at least MH seems to work fine with it. Cheers, Eloy Paris.- On 01/12/2014 10:26 PM, H Plato wrote: > Hi Eloy, > > I’ve set my water leak sensor the same as you and see if I get similar results. I set mine up in my items_mht as you have, and then selected ‘sync links’ on the new objects (sensor_basement_water, sensor_basement_water_wet and sensor_basement_water_hb). I see this in the logs: > > 01/12/14 08:20:08 PM Running: sensor basement water sync links > 01/12/14 08:20:08 PM [Insteon::BaseController] WARN! The ALDB of $sensor_basement_water is unknown, links will be added to devices linked to this device, but no links will be added to $sensor_basement_water. Please rescan this device and attempt sync links again. > 01/12/14 08:20:08 PM [Insteon::BaseController] Nothing to do when syncing links for $sensor_basement_water > 01/12/14 08:20:08 PM $sensor_basement_water completed sync links > 01/12/14 08:20:13 PM Running: sensor basement water wet sync links > 01/12/14 08:20:13 PM [Insteon::BaseController] WARN! The ALDB of $sensor_basement_water_wet is unknown, links will be added to devices linked to this device, but no links will be added to $sensor_basement_water_wet. Please rescan this device and attempt sync links again. > 01/12/14 08:20:13 PM [Insteon::BaseController] Nothing to do when syncing links for $sensor_basement_water_wet > 01/12/14 08:20:13 PM $sensor_basement_water_wet completed sync links > 01/12/14 08:20:19 PM Running: sensor basement water hb sync links > 01/12/14 08:20:19 PM [Insteon::BaseController] WARN! The ALDB of $sensor_basement_water_hb is unknown, links will be added to devices linked to this device, but no links will be added to $sensor_basement_water_hb. Please rescan this device and attempt sync links again. > 01/12/14 08:20:19 PM [Insteon::BaseController] Adding responder record to $PLM from $sensor_basement_water_hb > group = 04; cmd = add; is_controller = 0; data3 = 00; > 01/12/14 08:20:19 PM [Insteon_PLM] DEBUG2: Sending obj=$PLM; interface_data=41A20425abf9000000 incurred delay of 0.00 seconds; starting hop-count: ? > 01/12/14 08:20:19 PM [Insteon_PLM] DEBUG3: Sending PLM raw data: 026f41a20425abf9000000 > 01/12/14 08:20:19 PM [Insteon_PLM] DEBUG3: Received PLM raw data: 026f41a20425abf9000000 > 01/12/14 08:20:19 PM [Insteon_PLM] DEBUG3: Saving parsed data fragment: 026f41a20425abf9000000 > 01/12/14 08:20:19 PM [Insteon_PLM] DEBUG3: Prepending prior data fragment: 026f41a20425abf9000000 > 01/12/14 08:20:19 PM [Insteon_PLM] DEBUG3: Received PLM raw data: 026f41a20425abf900000006 > 01/12/14 08:20:19 PM [Insteon_PLM] DEBUG3: Received PLM acknowledge: obj=$PLM; interface_data=41A20425abf9000000 > 01/12/14 08:20:19 PM $sensor_basement_water_hb completed sync links > > > On Jan 12, 2014, at 6:43 PM, Eloy Paris <pe...@ch...> wrote: > >> Hi H, >> >> I'm getting increasingly frustrated with the INSTEON Water Leak Sensor because I am getting mixed/odd results. I have the sensor sitting on water right now and the last message that was sent was an "on" message to the "dry" group (group #1). When I first put it on top of water I saw a message sent to the "wet" group (group #2) but then messages to the "dry" group followed. I don't get it. >> >> The sensor also seems to send "on" messages to the "dry" group when it's removed from water. Perhaps this is by design, though I am not sure. If this is the case then I don't understand the need for tapping the set button to reset the sensor after it has sensed water (per the instructions that came in the original package). >> >> In addition, after removing the sensor from water, every time I tap the set button the sensor seems to toggle the messages that it sends: I tap one time and it sends a message to the "dry" group followed by a heartbeat message a few seconds later. I tap a second time and it sends a message to the "wet" group followed by the heartbeat sensor a few seconds later. >> >> All in all, I think TRIGGERLINC is a much better fit than MOTIONSENSOR -- all you have to do is to define three objects: for groups 1, 2, and 4. That should get rid of the "Warn! Unable to locate object for source: 25abf9 and group: 02" message. >> >> I don't think you need to relink the sensor to the PLM if you change to TriggerLinc. I am not sure but I think the PLM needs the responder records for groups 2 and 4 (I'm sure others will keep me honest here). That is easily accomplished by running a "sync links" on the group 1 object. >> >> I think MH support for this device is ready (in the form of a TriggerLinc); I just need to figure out why the sensor itself (not MH) seems to be behaving erratically... >> >> I purchased two sensors so I'll be testing the other sensor as well to see if it behaves like the first. >> >> BTW, I also noticed that the sensor I have been playing with was re-transmitting messages. I think it was because it came linked to some other device that I don't have in my network. After I reset the device to factory defaults and re-linked to my PLM the retransmissions seem to have stopped. >> >> I'll post more as I find new information. >> >> Cheers, >> >> Eloy Paris.- >> >> On 01/12/2014 01:26 PM, H Plato wrote: >> >>> Thanks Eloy, I think you’re right, there are messages to other groups. I only have one item defined in my items.mht: >>> >>> INSTEON_MOTIONSENSOR, 25.AB.F9, sensor_basement_water, Sensors #2213 REV2.0 >>> >>> And I see in the log that it is sending ‘grp: 02’ messages as well. >>> >>> Anyways, interested in what you find out. Do I have to relink the sensor and the PLM if I change the object type from MOTIONSENSOR to TRIGGERLINC? >>> >>> 01/12/14 11:16:25 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9000002cb1102 >>> 01/12/14 11:16:25 AM [Insteon::BaseInterface] DEBUG3: Message received with 2 hops left, delaying next transmit by 250 milliseconds to avoid collisions. >>> 01/12/14 11:16:25 AM [Insteon::BaseInterface] Warn! Unable to locate object for source: 25abf9 and group: 02 >>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9000002cb1102 >>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate incoming message from an unknown device. Id: 25abf9 Grp: 02 >>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9223e0f411102 >>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received with 0 hops left, plus ACK will take 1 to deliver, delaying next transmit by 150 milliseconds to avoid collisions. >>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate object for source: 25abf9 and group: 02 >>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9110102cb0600 >>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received with 2 hops left, delaying next transmit by 250 milliseconds to avoid collisions. >>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate object for source: 25abf9 and group: 02 >>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: 025025abf9110102cb0600 >>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate incoming message from an unknown device. Id: 25abf9 Grp: 02 >>> >>> >>> >>> On Jan 12, 2014, at 10:35 AM, Eloy Paris <pe...@ch...> wrote: >>> >>>> Hi H, >>>> >>>> On Sun, Jan 12, 2014 at 10:16:40AM -0700, H Plato wrote: >>>> >>>>> Eloy, do you see ‘OFF’ messages as a triggerlinc? >>>>> >>>>> I put the sensor on a damp sponge (as the instructions recommend) and >>>>> MH announces that there is water as the device gets turned on. I dried >>>>> off the contacts, let it sit for a while and still no OFF command. >>>>> >>>>> Kevin, I also tried to press the set button again, that just sends ON >>>>> commands. >>>>> >>>>> Does this device actually send OFF commands at all? >>>> >>>> As I understand it, the device will only send a message to group 1 (dry) >>>> when the set button is pressed. I still have not had a chance to test >>>> this, though (sorry, busy weekend). >>>> >>>> The owner's manual says this related to "off" messages in the >>>> Troubleshooting section: >>>> >>>> Problem: Leak Sensor can turn responder on, but not off >>>> >>>> Cause: Leak Sensor is not designed to turn off responders. This prevents >>>> warning lights or other leak indication devices from turning off in the >>>> event the leak dries. >>>> >>>> I think this means that, once the sensor has detected water, the only >>>> way to reset it after the area has dried, is to tap the set button. >>>> >>>> Is it possible that you are seeing an "on" message sent to group 1 (dry) >>>> when the contacts are not sensing water and you tap the set button? >>>> >>>> I think the way it should work is this: >>>> >>>> Sensed water -> send "on" message to group 2 (wet) >>>> >>>> Not sensing water and set button is tapped -> send "on" message to group >>>> 1 (dry) >>>> >>>> Heartbeat -> send "on" message to group 4 (I haven't looked closely at >>>> the heartbeat message; I think it is also generated when the set button >>>> is tapped quickly; if this is the case then that would allow one to test >>>> the user code one sets up to handle the presence [or lack thereof] of >>>> the heartbeat). >>>> >>>> The commands are always "on", never "off". But they are sent to >>>> different groups to differentiate. >>>> >>>> Hopefully I'll have time to do more testing later today. >>>> >>>> Cheers, >>>> >>>> Eloy Paris.- >>>> >>>>> >>>>> On Jan 11, 2014, at 3:17 PM, Eloy Paris <pe...@ch...> wrote: >>>>> >>>>>> H, >>>>>> >>>>>> Coincidentally, I also started playing with a water leak sensor >>>>>> yesterday. I manually linked it to the PLM and started to test. I think >>>>>> TriggerLinc is a better fit than the motion sensor. Here's what I have >>>>>> so far in my .mht file: >>>>>> >>>>>> INSTEON_TRIGGERLINC, 25.b0.fe:01, crawlspace_leak_dry, Leak_Sensors # 2213 v2.0 >>>>>> INSTEON_TRIGGERLINC, 25.b0.fe:02, crawlspace_leak_wet, Leak_Sensors # 2213 v2.0 >>>>>> INSTEON_TRIGGERLINC, 25.b0.fe:04, crawlspace_leak_heartbeat, Leak_Sensors # 2213 v2.0 >>>>>> >>>>>> I am seeing so odd things but I haven't had a chance to do more >>>>>> extensive tests. One odd thing is that I scanned the link table of the >>>>>> sensor and it came back empty (and this was after doing the manual link >>>>>> to the PLM). I don't know why. >>>>>> >>>>>> I'll send some print_log messages later (I'm on my way out now). >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Eloy Paris.- >>>>> >>>>> On Jan 11, 2014, at 2:56 PM, Kevin Robert Keegan <ke...@kr...> wrote: >>>>> >>>>>> The "set" button on appliancelincs toggle on/off. Pressing the button again my get you an off message. Although it would be nice to know if it will naturally send an off message. >>>>> >>>>> >>>>> >>>>>> >>>>>> On Sat, Jan 11, 2014 at 01:36:38PM -0700, H Plato wrote: >>>>>> >>>>>>> So I added the water sensor yesterday as a INSTEON_MOTIONSENSOR. Setup and link sync’ing seemed to work, I pressed the test button on the sensor and the MH object turned on, so that’s a good thing. >>>>>>> >>>>>>> The object hasn’t been set to off yet, so I’m going to have to put the thing in water to see if it sends an OFF when it is dry. >>>>>>> >>>>>>> >>>>>>> On Jan 4, 2014, at 9:57 AM, Eloy Paris <pe...@ch...> wrote: >>>>>>> >>>>>>>> Hi Brad, H, >>>>>>>> >>>>>>>> Sorry, I have not had a chance yet to set up the INSTEON water leak sensors -- I received two but they are still in their original packaging. I'll post my findings as soon as I get a chance to try things out, though I don't know when that might be. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> Eloy Paris.- >>>>>>>> >>>>>>>> On 01/03/2014 10:50 PM, Brad Yarotsky wrote: >>>>>>>> >>>>>>>>> I also have one and would be very interested. >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> Brad >>>>>>>>> >>>>>>>>> >>>>>>>>> Sent from Samsung Mobile >>>>>>>>> >>>>>>>>> >>>>>>>>> -------- Original message -------- >>>>>>>>> From: H Plato >>>>>>>>> Date:03/01/2014 7:56 PM (GMT-06:00) >>>>>>>>> To: Eloy Paris >>>>>>>>> Cc: MisterHouse Users >>>>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>>>> >>>>>>>>> Hi Eloy, did you get these working? I have one on order and hope to >>>>>>>>> get it next week. >>>>>>>>> >>>>>>>>> Sent from my mobile device. >>>>>>>>> >>>>>>>>> On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch... >>>>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>>>> >>>>>>>>>> Thanks Kevin. Guess I'll find out soon because I bought a couple of >>>>>>>>>> these sensors. I figured their cost was nothing compared to the cost >>>>>>>>>> of cleaning up the mess caused by water damage. >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> >>>>>>>>>> Eloy Paris.- >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -------- Original message -------- >>>>>>>>>> From: Kevin Robert Keegan <ke...@kr... >>>>>>>>>> <mailto:ke...@kr...>> >>>>>>>>>> Date: 12/02/2013 9:03 PM (GMT-06:00) >>>>>>>>>> To: Eloy Paris <pe...@ch... <mailto:pe...@ch...>> >>>>>>>>>> Cc: MisterHouse Users <mis...@li... >>>>>>>>>> <mailto:mis...@li...>> >>>>>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I feel like some posted about the leak sensor before. >>>>>>>>>> >>>>>>>>>> Eitherway, yes Motion_Sensor is the way to go right now. >>>>>>>>>> >>>>>>>>>> In the future, it would be nice to add a battery level tracker to it. >>>>>>>>>> The leak sensor in theory has a heartbeat so that you can be sure it >>>>>>>>>> is still working. Although the remotelinc was supposed to have that >>>>>>>>>> heartbeat too, but it wasn't there. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch... >>>>>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>>>>> >>>>>>>>>> Hello, >>>>>>>>>> >>>>>>>>>> Has anyone used the INSTEON water leak sensor with MisterHouse? >>>>>>>>>> >>>>>>>>>> http://www.smarthome.com/2852-222/p.aspx >>>>>>>>>> >>>>>>>>>> I don't recall a specific .mht file keyword for it but I would >>>>>>>>>> think it >>>>>>>>>> could be declared as some other existing device (like the motion >>>>>>>>>> sensor), or a specific object could be created for it based on an >>>>>>>>>> existing one (again, the motion sensor seems like a logical choice). >>>>>>>>>> >>>>>>>>>> Also, in case you were not aware, Smarthome is having a 20% off sale >>>>>>>>>> since last week. It will probably end tonight. >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> >>>>>>>>>> Eloy Paris.- >>>>>>> >>>>> >>> >> > |
From: Eloy P. <pe...@ch...> - 2014-01-14 18:31:47
|
Just to take MH out of the picture while I get used to the INSTEON water leak sensor, I manually linked a switch to the sensor, the idea being that the sensor will turn on the light when it senses water. I then by putting the sensor on top of water... In some cases the sensor failed to send a message to the wet group and instead it sent it to the dry group. Now, that's not very reassuring, is it? I guess I can program MH to warn me when messages are send to either group but that still does not address that the sensor is not doing what I think it is supposed to be doing. I'll contact Smarthome support to see what they have to say about this. Cheers, Eloy Paris.- On 01/12/2014 08:43 PM, Eloy Paris wrote: > Hi H, > > I'm getting increasingly frustrated with the INSTEON Water Leak Sensor > because I am getting mixed/odd results. I have the sensor sitting on > water right now and the last message that was sent was an "on" message > to the "dry" group (group #1). When I first put it on top of water I saw > a message sent to the "wet" group (group #2) but then messages to the > "dry" group followed. I don't get it. > > The sensor also seems to send "on" messages to the "dry" group when it's > removed from water. Perhaps this is by design, though I am not sure. If > this is the case then I don't understand the need for tapping the set > button to reset the sensor after it has sensed water (per the > instructions that came in the original package). > > In addition, after removing the sensor from water, every time I tap the > set button the sensor seems to toggle the messages that it sends: I tap > one time and it sends a message to the "dry" group followed by a > heartbeat message a few seconds later. I tap a second time and it sends > a message to the "wet" group followed by the heartbeat sensor a few > seconds later. > > All in all, I think TRIGGERLINC is a much better fit than MOTIONSENSOR > -- all you have to do is to define three objects: for groups 1, 2, and > 4. That should get rid of the "Warn! Unable to locate object for source: > 25abf9 and group: 02" message. > > I don't think you need to relink the sensor to the PLM if you change to > TriggerLinc. I am not sure but I think the PLM needs the responder > records for groups 2 and 4 (I'm sure others will keep me honest here). > That is easily accomplished by running a "sync links" on the group 1 > object. > > I think MH support for this device is ready (in the form of a > TriggerLinc); I just need to figure out why the sensor itself (not MH) > seems to be behaving erratically... > > I purchased two sensors so I'll be testing the other sensor as well to > see if it behaves like the first. > > BTW, I also noticed that the sensor I have been playing with was > re-transmitting messages. I think it was because it came linked to some > other device that I don't have in my network. After I reset the device > to factory defaults and re-linked to my PLM the retransmissions seem to > have stopped. > > I'll post more as I find new information. > > Cheers, > > Eloy Paris.- > > On 01/12/2014 01:26 PM, H Plato wrote: > >> Thanks Eloy, I think you’re right, there are messages to other groups. >> I only have one item defined in my items.mht: >> >> INSTEON_MOTIONSENSOR, 25.AB.F9, sensor_basement_water, >> Sensors #2213 REV2.0 >> >> And I see in the log that it is sending ‘grp: 02’ messages as well. >> >> Anyways, interested in what you find out. Do I have to relink the >> sensor and the PLM if I change the object type from MOTIONSENSOR to >> TRIGGERLINC? >> >> 01/12/14 11:16:25 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >> 025025abf9000002cb1102 >> 01/12/14 11:16:25 AM [Insteon::BaseInterface] DEBUG3: Message received >> with 2 hops left, delaying next transmit by 250 milliseconds to avoid >> collisions. >> 01/12/14 11:16:25 AM [Insteon::BaseInterface] Warn! Unable to locate >> object for source: 25abf9 and group: 02 >> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >> 025025abf9000002cb1102 >> 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate >> incoming message from an unknown device. Id: 25abf9 Grp: 02 >> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >> 025025abf9223e0f411102 >> 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received >> with 0 hops left, plus ACK will take 1 to deliver, delaying next >> transmit by 150 milliseconds to avoid collisions. >> 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate >> object for source: 25abf9 and group: 02 >> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >> 025025abf9110102cb0600 >> 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received >> with 2 hops left, delaying next transmit by 250 milliseconds to avoid >> collisions. >> 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate >> object for source: 25abf9 and group: 02 >> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >> 025025abf9110102cb0600 >> 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate >> incoming message from an unknown device. Id: 25abf9 Grp: 02 >> >> >> >> On Jan 12, 2014, at 10:35 AM, Eloy Paris <pe...@ch...> wrote: >> >>> Hi H, >>> >>> On Sun, Jan 12, 2014 at 10:16:40AM -0700, H Plato wrote: >>> >>>> Eloy, do you see ‘OFF’ messages as a triggerlinc? >>>> >>>> I put the sensor on a damp sponge (as the instructions recommend) and >>>> MH announces that there is water as the device gets turned on. I dried >>>> off the contacts, let it sit for a while and still no OFF command. >>>> >>>> Kevin, I also tried to press the set button again, that just sends ON >>>> commands. >>>> >>>> Does this device actually send OFF commands at all? >>> >>> As I understand it, the device will only send a message to group 1 (dry) >>> when the set button is pressed. I still have not had a chance to test >>> this, though (sorry, busy weekend). >>> >>> The owner's manual says this related to "off" messages in the >>> Troubleshooting section: >>> >>> Problem: Leak Sensor can turn responder on, but not off >>> >>> Cause: Leak Sensor is not designed to turn off responders. This prevents >>> warning lights or other leak indication devices from turning off in the >>> event the leak dries. >>> >>> I think this means that, once the sensor has detected water, the only >>> way to reset it after the area has dried, is to tap the set button. >>> >>> Is it possible that you are seeing an "on" message sent to group 1 (dry) >>> when the contacts are not sensing water and you tap the set button? >>> >>> I think the way it should work is this: >>> >>> Sensed water -> send "on" message to group 2 (wet) >>> >>> Not sensing water and set button is tapped -> send "on" message to group >>> 1 (dry) >>> >>> Heartbeat -> send "on" message to group 4 (I haven't looked closely at >>> the heartbeat message; I think it is also generated when the set button >>> is tapped quickly; if this is the case then that would allow one to test >>> the user code one sets up to handle the presence [or lack thereof] of >>> the heartbeat). >>> >>> The commands are always "on", never "off". But they are sent to >>> different groups to differentiate. >>> >>> Hopefully I'll have time to do more testing later today. >>> >>> Cheers, >>> >>> Eloy Paris.- >>> >>>> >>>> On Jan 11, 2014, at 3:17 PM, Eloy Paris <pe...@ch...> wrote: >>>> >>>>> H, >>>>> >>>>> Coincidentally, I also started playing with a water leak sensor >>>>> yesterday. I manually linked it to the PLM and started to test. I >>>>> think >>>>> TriggerLinc is a better fit than the motion sensor. Here's what I have >>>>> so far in my .mht file: >>>>> >>>>> INSTEON_TRIGGERLINC, 25.b0.fe:01, crawlspace_leak_dry, Leak_Sensors >>>>> # 2213 v2.0 >>>>> INSTEON_TRIGGERLINC, 25.b0.fe:02, crawlspace_leak_wet, Leak_Sensors >>>>> # 2213 v2.0 >>>>> INSTEON_TRIGGERLINC, 25.b0.fe:04, crawlspace_leak_heartbeat, >>>>> Leak_Sensors # 2213 v2.0 >>>>> >>>>> I am seeing so odd things but I haven't had a chance to do more >>>>> extensive tests. One odd thing is that I scanned the link table of the >>>>> sensor and it came back empty (and this was after doing the manual >>>>> link >>>>> to the PLM). I don't know why. >>>>> >>>>> I'll send some print_log messages later (I'm on my way out now). >>>>> >>>>> Cheers, >>>>> >>>>> Eloy Paris.- >>>> >>>> On Jan 11, 2014, at 2:56 PM, Kevin Robert Keegan >>>> <ke...@kr...> wrote: >>>> >>>>> The "set" button on appliancelincs toggle on/off. Pressing the >>>>> button again my get you an off message. Although it would be nice >>>>> to know if it will naturally send an off message. >>>> >>>> >>>> >>>>> >>>>> On Sat, Jan 11, 2014 at 01:36:38PM -0700, H Plato wrote: >>>>> >>>>>> So I added the water sensor yesterday as a INSTEON_MOTIONSENSOR. >>>>>> Setup and link sync’ing seemed to work, I pressed the test button >>>>>> on the sensor and the MH object turned on, so that’s a good thing. >>>>>> >>>>>> The object hasn’t been set to off yet, so I’m going to have to put >>>>>> the thing in water to see if it sends an OFF when it is dry. >>>>>> >>>>>> >>>>>> On Jan 4, 2014, at 9:57 AM, Eloy Paris <pe...@ch...> wrote: >>>>>> >>>>>>> Hi Brad, H, >>>>>>> >>>>>>> Sorry, I have not had a chance yet to set up the INSTEON water >>>>>>> leak sensors -- I received two but they are still in their >>>>>>> original packaging. I'll post my findings as soon as I get a >>>>>>> chance to try things out, though I don't know when that might be. >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Eloy Paris.- >>>>>>> >>>>>>> On 01/03/2014 10:50 PM, Brad Yarotsky wrote: >>>>>>> >>>>>>>> I also have one and would be very interested. >>>>>>>> >>>>>>>> Thanks >>>>>>>> Brad >>>>>>>> >>>>>>>> >>>>>>>> Sent from Samsung Mobile >>>>>>>> >>>>>>>> >>>>>>>> -------- Original message -------- >>>>>>>> From: H Plato >>>>>>>> Date:03/01/2014 7:56 PM (GMT-06:00) >>>>>>>> To: Eloy Paris >>>>>>>> Cc: MisterHouse Users >>>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>>> >>>>>>>> Hi Eloy, did you get these working? I have one on order and >>>>>>>> hope to >>>>>>>> get it next week. >>>>>>>> >>>>>>>> Sent from my mobile device. >>>>>>>> >>>>>>>> On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch... >>>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>>> >>>>>>>>> Thanks Kevin. Guess I'll find out soon because I bought a >>>>>>>>> couple of >>>>>>>>> these sensors. I figured their cost was nothing compared to the >>>>>>>>> cost >>>>>>>>> of cleaning up the mess caused by water damage. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> >>>>>>>>> Eloy Paris.- >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -------- Original message -------- >>>>>>>>> From: Kevin Robert Keegan <ke...@kr... >>>>>>>>> <mailto:ke...@kr...>> >>>>>>>>> Date: 12/02/2013 9:03 PM (GMT-06:00) >>>>>>>>> To: Eloy Paris <pe...@ch... <mailto:pe...@ch...>> >>>>>>>>> Cc: MisterHouse Users <mis...@li... >>>>>>>>> <mailto:mis...@li...>> >>>>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>>>> >>>>>>>>> >>>>>>>>> I feel like some posted about the leak sensor before. >>>>>>>>> >>>>>>>>> Eitherway, yes Motion_Sensor is the way to go right now. >>>>>>>>> >>>>>>>>> In the future, it would be nice to add a battery level tracker >>>>>>>>> to it. >>>>>>>>> The leak sensor in theory has a heartbeat so that you can be >>>>>>>>> sure it >>>>>>>>> is still working. Although the remotelinc was supposed to have >>>>>>>>> that >>>>>>>>> heartbeat too, but it wasn't there. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch... >>>>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>>>> >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> Has anyone used the INSTEON water leak sensor with MisterHouse? >>>>>>>>> >>>>>>>>> http://www.smarthome.com/2852-222/p.aspx >>>>>>>>> >>>>>>>>> I don't recall a specific .mht file keyword for it but I would >>>>>>>>> think it >>>>>>>>> could be declared as some other existing device (like the motion >>>>>>>>> sensor), or a specific object could be created for it based >>>>>>>>> on an >>>>>>>>> existing one (again, the motion sensor seems like a logical >>>>>>>>> choice). >>>>>>>>> >>>>>>>>> Also, in case you were not aware, Smarthome is having a 20% >>>>>>>>> off sale >>>>>>>>> since last week. It will probably end tonight. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> >>>>>>>>> Eloy Paris.- >>>>>> >>>> >> > |
From: Kevin R. K. <ke...@kr...> - 2014-01-14 20:03:36
|
On Tue, Jan 14, 2014 at 10:31 AM, Eloy Paris <pe...@ch...> wrote: > In some cases the sensor failed to send a message to the wet group and > instead it sent it to the dry group. Now, that's not very reassuring, is > it? Wow, that is epically bad. Alternatively, a triggerlinc has pin out options, I have never tried it, but you should be able to hook this up to a homemade water sensor. I hope smarthome is able to fix/clear up the issues with this device. |
From: H P. <hp...@gm...> - 2014-01-18 18:28:07
|
Hey Eloy, Did you manage to get ahold of smarthome about this? Is there a consistent pattern that you see from your devices? For the 2 tests that I did, I saw an ON to group 1 when it was wet, and then on to group 2 when the set button was pressed. I didn’t see any traffic when I dried off the contacts. Strangely enough, I get two alerts when water is applied using this usercode (maybe the object is set twice?) if (state_now $sensor_basement_water ) { print_log “WATER LEAK: water sensor is now $sensor_basement_water->{state}"; if ( state $sensor_basement_water eq 'on' ) { print_log “WATER LEAK: water sensor ON"; speak (rooms=> "all", mode=> "unmuted", text=>"Water detected on basement water sensor"); } } I think the ideal end state is that the device goes on until manually turned reset. That logic makes sense to me, as I would want to visually inspect the device prior to resetting it. It would be nice to have a single object that is on when water is detected and then off when the set button is pressed, rather than tracking two objects and usercode to either set the group 1 object to off or another generic object that would track ON/OFF. On Jan 14, 2014, at 11:31 AM, Eloy Paris <pe...@ch...> wrote: > Just to take MH out of the picture while I get used to the INSTEON water leak sensor, I manually linked a switch to the sensor, the idea being that the sensor will turn on the light when it senses water. I then by putting the sensor on top of water... > > In some cases the sensor failed to send a message to the wet group and instead it sent it to the dry group. Now, that's not very reassuring, is it? I guess I can program MH to warn me when messages are send to either group but that still does not address that the sensor is not doing what I think it is supposed to be doing. > > I'll contact Smarthome support to see what they have to say about this. > > Cheers, > > Eloy Paris.- > > On 01/12/2014 08:43 PM, Eloy Paris wrote: > >> Hi H, >> >> I'm getting increasingly frustrated with the INSTEON Water Leak Sensor >> because I am getting mixed/odd results. I have the sensor sitting on >> water right now and the last message that was sent was an "on" message >> to the "dry" group (group #1). When I first put it on top of water I saw >> a message sent to the "wet" group (group #2) but then messages to the >> "dry" group followed. I don't get it. >> >> The sensor also seems to send "on" messages to the "dry" group when it's >> removed from water. Perhaps this is by design, though I am not sure. If >> this is the case then I don't understand the need for tapping the set >> button to reset the sensor after it has sensed water (per the >> instructions that came in the original package). >> >> In addition, after removing the sensor from water, every time I tap the >> set button the sensor seems to toggle the messages that it sends: I tap >> one time and it sends a message to the "dry" group followed by a >> heartbeat message a few seconds later. I tap a second time and it sends >> a message to the "wet" group followed by the heartbeat sensor a few >> seconds later. >> >> All in all, I think TRIGGERLINC is a much better fit than MOTIONSENSOR >> -- all you have to do is to define three objects: for groups 1, 2, and >> 4. That should get rid of the "Warn! Unable to locate object for source: >> 25abf9 and group: 02" message. >> >> I don't think you need to relink the sensor to the PLM if you change to >> TriggerLinc. I am not sure but I think the PLM needs the responder >> records for groups 2 and 4 (I'm sure others will keep me honest here). >> That is easily accomplished by running a "sync links" on the group 1 >> object. >> >> I think MH support for this device is ready (in the form of a >> TriggerLinc); I just need to figure out why the sensor itself (not MH) >> seems to be behaving erratically... >> >> I purchased two sensors so I'll be testing the other sensor as well to >> see if it behaves like the first. >> >> BTW, I also noticed that the sensor I have been playing with was >> re-transmitting messages. I think it was because it came linked to some >> other device that I don't have in my network. After I reset the device >> to factory defaults and re-linked to my PLM the retransmissions seem to >> have stopped. >> >> I'll post more as I find new information. >> >> Cheers, >> >> Eloy Paris.- >> >> On 01/12/2014 01:26 PM, H Plato wrote: >> >>> Thanks Eloy, I think you’re right, there are messages to other groups. >>> I only have one item defined in my items.mht: >>> >>> INSTEON_MOTIONSENSOR, 25.AB.F9, sensor_basement_water, >>> Sensors #2213 REV2.0 >>> >>> And I see in the log that it is sending ‘grp: 02’ messages as well. >>> >>> Anyways, interested in what you find out. Do I have to relink the >>> sensor and the PLM if I change the object type from MOTIONSENSOR to >>> TRIGGERLINC? >>> >>> 01/12/14 11:16:25 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>> 025025abf9000002cb1102 >>> 01/12/14 11:16:25 AM [Insteon::BaseInterface] DEBUG3: Message received >>> with 2 hops left, delaying next transmit by 250 milliseconds to avoid >>> collisions. >>> 01/12/14 11:16:25 AM [Insteon::BaseInterface] Warn! Unable to locate >>> object for source: 25abf9 and group: 02 >>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>> 025025abf9000002cb1102 >>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate >>> incoming message from an unknown device. Id: 25abf9 Grp: 02 >>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>> 025025abf9223e0f411102 >>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received >>> with 0 hops left, plus ACK will take 1 to deliver, delaying next >>> transmit by 150 milliseconds to avoid collisions. >>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate >>> object for source: 25abf9 and group: 02 >>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>> 025025abf9110102cb0600 >>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received >>> with 2 hops left, delaying next transmit by 250 milliseconds to avoid >>> collisions. >>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate >>> object for source: 25abf9 and group: 02 >>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>> 025025abf9110102cb0600 >>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate >>> incoming message from an unknown device. Id: 25abf9 Grp: 02 >>> >>> >>> >>> On Jan 12, 2014, at 10:35 AM, Eloy Paris <pe...@ch...> wrote: >>> >>>> Hi H, >>>> >>>> On Sun, Jan 12, 2014 at 10:16:40AM -0700, H Plato wrote: >>>> >>>>> Eloy, do you see ‘OFF’ messages as a triggerlinc? >>>>> >>>>> I put the sensor on a damp sponge (as the instructions recommend) and >>>>> MH announces that there is water as the device gets turned on. I dried >>>>> off the contacts, let it sit for a while and still no OFF command. >>>>> >>>>> Kevin, I also tried to press the set button again, that just sends ON >>>>> commands. >>>>> >>>>> Does this device actually send OFF commands at all? >>>> >>>> As I understand it, the device will only send a message to group 1 (dry) >>>> when the set button is pressed. I still have not had a chance to test >>>> this, though (sorry, busy weekend). >>>> >>>> The owner's manual says this related to "off" messages in the >>>> Troubleshooting section: >>>> >>>> Problem: Leak Sensor can turn responder on, but not off >>>> >>>> Cause: Leak Sensor is not designed to turn off responders. This prevents >>>> warning lights or other leak indication devices from turning off in the >>>> event the leak dries. >>>> >>>> I think this means that, once the sensor has detected water, the only >>>> way to reset it after the area has dried, is to tap the set button. >>>> >>>> Is it possible that you are seeing an "on" message sent to group 1 (dry) >>>> when the contacts are not sensing water and you tap the set button? >>>> >>>> I think the way it should work is this: >>>> >>>> Sensed water -> send "on" message to group 2 (wet) >>>> >>>> Not sensing water and set button is tapped -> send "on" message to group >>>> 1 (dry) >>>> >>>> Heartbeat -> send "on" message to group 4 (I haven't looked closely at >>>> the heartbeat message; I think it is also generated when the set button >>>> is tapped quickly; if this is the case then that would allow one to test >>>> the user code one sets up to handle the presence [or lack thereof] of >>>> the heartbeat). >>>> >>>> The commands are always "on", never "off". But they are sent to >>>> different groups to differentiate. >>>> >>>> Hopefully I'll have time to do more testing later today. >>>> >>>> Cheers, >>>> >>>> Eloy Paris.- >>>> >>>>> >>>>> On Jan 11, 2014, at 3:17 PM, Eloy Paris <pe...@ch...> wrote: >>>>> >>>>>> H, >>>>>> >>>>>> Coincidentally, I also started playing with a water leak sensor >>>>>> yesterday. I manually linked it to the PLM and started to test. I >>>>>> think >>>>>> TriggerLinc is a better fit than the motion sensor. Here's what I have >>>>>> so far in my .mht file: >>>>>> >>>>>> INSTEON_TRIGGERLINC, 25.b0.fe:01, crawlspace_leak_dry, Leak_Sensors >>>>>> # 2213 v2.0 >>>>>> INSTEON_TRIGGERLINC, 25.b0.fe:02, crawlspace_leak_wet, Leak_Sensors >>>>>> # 2213 v2.0 >>>>>> INSTEON_TRIGGERLINC, 25.b0.fe:04, crawlspace_leak_heartbeat, >>>>>> Leak_Sensors # 2213 v2.0 >>>>>> >>>>>> I am seeing so odd things but I haven't had a chance to do more >>>>>> extensive tests. One odd thing is that I scanned the link table of the >>>>>> sensor and it came back empty (and this was after doing the manual >>>>>> link >>>>>> to the PLM). I don't know why. >>>>>> >>>>>> I'll send some print_log messages later (I'm on my way out now). >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Eloy Paris.- >>>>> >>>>> On Jan 11, 2014, at 2:56 PM, Kevin Robert Keegan >>>>> <ke...@kr...> wrote: >>>>> >>>>>> The "set" button on appliancelincs toggle on/off. Pressing the >>>>>> button again my get you an off message. Although it would be nice >>>>>> to know if it will naturally send an off message. >>>>> >>>>> >>>>> >>>>>> >>>>>> On Sat, Jan 11, 2014 at 01:36:38PM -0700, H Plato wrote: >>>>>> >>>>>>> So I added the water sensor yesterday as a INSTEON_MOTIONSENSOR. >>>>>>> Setup and link sync’ing seemed to work, I pressed the test button >>>>>>> on the sensor and the MH object turned on, so that’s a good thing. >>>>>>> >>>>>>> The object hasn’t been set to off yet, so I’m going to have to put >>>>>>> the thing in water to see if it sends an OFF when it is dry. >>>>>>> >>>>>>> >>>>>>> On Jan 4, 2014, at 9:57 AM, Eloy Paris <pe...@ch...> wrote: >>>>>>> >>>>>>>> Hi Brad, H, >>>>>>>> >>>>>>>> Sorry, I have not had a chance yet to set up the INSTEON water >>>>>>>> leak sensors -- I received two but they are still in their >>>>>>>> original packaging. I'll post my findings as soon as I get a >>>>>>>> chance to try things out, though I don't know when that might be. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> Eloy Paris.- >>>>>>>> >>>>>>>> On 01/03/2014 10:50 PM, Brad Yarotsky wrote: >>>>>>>> >>>>>>>>> I also have one and would be very interested. >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> Brad >>>>>>>>> >>>>>>>>> >>>>>>>>> Sent from Samsung Mobile >>>>>>>>> >>>>>>>>> >>>>>>>>> -------- Original message -------- >>>>>>>>> From: H Plato >>>>>>>>> Date:03/01/2014 7:56 PM (GMT-06:00) >>>>>>>>> To: Eloy Paris >>>>>>>>> Cc: MisterHouse Users >>>>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>>>> >>>>>>>>> Hi Eloy, did you get these working? I have one on order and >>>>>>>>> hope to >>>>>>>>> get it next week. >>>>>>>>> >>>>>>>>> Sent from my mobile device. >>>>>>>>> >>>>>>>>> On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch... >>>>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>>>> >>>>>>>>>> Thanks Kevin. Guess I'll find out soon because I bought a >>>>>>>>>> couple of >>>>>>>>>> these sensors. I figured their cost was nothing compared to the >>>>>>>>>> cost >>>>>>>>>> of cleaning up the mess caused by water damage. >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> >>>>>>>>>> Eloy Paris.- >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -------- Original message -------- >>>>>>>>>> From: Kevin Robert Keegan <ke...@kr... >>>>>>>>>> <mailto:ke...@kr...>> >>>>>>>>>> Date: 12/02/2013 9:03 PM (GMT-06:00) >>>>>>>>>> To: Eloy Paris <pe...@ch... <mailto:pe...@ch...>> >>>>>>>>>> Cc: MisterHouse Users <mis...@li... >>>>>>>>>> <mailto:mis...@li...>> >>>>>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I feel like some posted about the leak sensor before. >>>>>>>>>> >>>>>>>>>> Eitherway, yes Motion_Sensor is the way to go right now. >>>>>>>>>> >>>>>>>>>> In the future, it would be nice to add a battery level tracker >>>>>>>>>> to it. >>>>>>>>>> The leak sensor in theory has a heartbeat so that you can be >>>>>>>>>> sure it >>>>>>>>>> is still working. Although the remotelinc was supposed to have >>>>>>>>>> that >>>>>>>>>> heartbeat too, but it wasn't there. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch... >>>>>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>>>>> >>>>>>>>>> Hello, >>>>>>>>>> >>>>>>>>>> Has anyone used the INSTEON water leak sensor with MisterHouse? >>>>>>>>>> >>>>>>>>>> http://www.smarthome.com/2852-222/p.aspx >>>>>>>>>> >>>>>>>>>> I don't recall a specific .mht file keyword for it but I would >>>>>>>>>> think it >>>>>>>>>> could be declared as some other existing device (like the motion >>>>>>>>>> sensor), or a specific object could be created for it based >>>>>>>>>> on an >>>>>>>>>> existing one (again, the motion sensor seems like a logical >>>>>>>>>> choice). >>>>>>>>>> >>>>>>>>>> Also, in case you were not aware, Smarthome is having a 20% >>>>>>>>>> off sale >>>>>>>>>> since last week. It will probably end tonight. >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> >>>>>>>>>> Eloy Paris.- >>>>>>> >>>>> >>> >> > |
From: Eloy P. <pe...@ch...> - 2014-01-19 14:36:19
|
Hi H, On 01/18/2014 01:27 PM, H Plato wrote: > Hey Eloy, > > Did you manage to get ahold of smarthome about this? Nope, I have not had a chance to contact Smarthome support to ask why the sensors are behaving the way I observed... > Is there a consistent pattern that you see from your devices? For the > 2 tests that I did, I saw an ON to group 1 when it was wet, and then > on to group 2 when the set button was pressed. This doesn't make sense, right? I mean, the wet group is group #2 so when it's wet there should be a message going to group #2; or at least one message. Or I am missing something??? One thing, though -- when I consecutively press the set button I do see alternating messages to groups 1 and 2, i.e. one press generates a message to group #1 and the next press generates a message to group #2. > I didn’t see any traffic when I dried off the contacts. Strangely enough, I get two alerts when water is applied using this usercode (maybe the object is set twice?) > > if (state_now $sensor_basement_water ) { > print_log “WATER LEAK: water sensor is now $sensor_basement_water->{state}"; > > if ( state $sensor_basement_water eq 'on' ) { > > print_log “WATER LEAK: water sensor ON"; > speak (rooms=> "all", mode=> "unmuted", text=>"Water detected on basement water sensor"); > > } > } Do you mean that you see this in your print log: WATER LEAK: water sensor is now on WATER LEAK: water sensor ON Or that you get the above messages twice? As I understand it, the sensor will never send an 'off' message to groups 1 or 2, so the "if ( state $sensor_basement_water eq 'on' )" check is unnecessary (it will always be on). > I think the ideal end state is that the device goes on until manually > turned reset. That logic makes sense to me, as I would want to > visually inspect the device prior to resetting it. It would be nice > to have a single object that is on when water is detected and then > off when the set button is pressed, rather than tracking two objects > and usercode to either set the group 1 object to off or another > generic object that would track ON/OFF. Wouldn't this be easy to accomplish by using some logic that looks at the state changes of the group 1 and group 2 objects? I haven't tested my sensors in a few days (they're still sitting on my desk) so they should be dry. I'll conduct a couple of additional test to see in what mood they're in today and send back the results. Right now my testing is simple -- if the sensor detects water then a light connected to an ApplianceLinc should turn on, i.e. no MH in the picture. It doesn't get any simpler than this. Cheers, Eloy Paris.- > > > On Jan 14, 2014, at 11:31 AM, Eloy Paris <pe...@ch...> wrote: > >> Just to take MH out of the picture while I get used to the INSTEON water leak sensor, I manually linked a switch to the sensor, the idea being that the sensor will turn on the light when it senses water. I then by putting the sensor on top of water... >> >> In some cases the sensor failed to send a message to the wet group and instead it sent it to the dry group. Now, that's not very reassuring, is it? I guess I can program MH to warn me when messages are send to either group but that still does not address that the sensor is not doing what I think it is supposed to be doing. >> >> I'll contact Smarthome support to see what they have to say about this. >> >> Cheers, >> >> Eloy Paris.- >> >> On 01/12/2014 08:43 PM, Eloy Paris wrote: >> >>> Hi H, >>> >>> I'm getting increasingly frustrated with the INSTEON Water Leak Sensor >>> because I am getting mixed/odd results. I have the sensor sitting on >>> water right now and the last message that was sent was an "on" message >>> to the "dry" group (group #1). When I first put it on top of water I saw >>> a message sent to the "wet" group (group #2) but then messages to the >>> "dry" group followed. I don't get it. >>> >>> The sensor also seems to send "on" messages to the "dry" group when it's >>> removed from water. Perhaps this is by design, though I am not sure. If >>> this is the case then I don't understand the need for tapping the set >>> button to reset the sensor after it has sensed water (per the >>> instructions that came in the original package). >>> >>> In addition, after removing the sensor from water, every time I tap the >>> set button the sensor seems to toggle the messages that it sends: I tap >>> one time and it sends a message to the "dry" group followed by a >>> heartbeat message a few seconds later. I tap a second time and it sends >>> a message to the "wet" group followed by the heartbeat sensor a few >>> seconds later. >>> >>> All in all, I think TRIGGERLINC is a much better fit than MOTIONSENSOR >>> -- all you have to do is to define three objects: for groups 1, 2, and >>> 4. That should get rid of the "Warn! Unable to locate object for source: >>> 25abf9 and group: 02" message. >>> >>> I don't think you need to relink the sensor to the PLM if you change to >>> TriggerLinc. I am not sure but I think the PLM needs the responder >>> records for groups 2 and 4 (I'm sure others will keep me honest here). >>> That is easily accomplished by running a "sync links" on the group 1 >>> object. >>> >>> I think MH support for this device is ready (in the form of a >>> TriggerLinc); I just need to figure out why the sensor itself (not MH) >>> seems to be behaving erratically... >>> >>> I purchased two sensors so I'll be testing the other sensor as well to >>> see if it behaves like the first. >>> >>> BTW, I also noticed that the sensor I have been playing with was >>> re-transmitting messages. I think it was because it came linked to some >>> other device that I don't have in my network. After I reset the device >>> to factory defaults and re-linked to my PLM the retransmissions seem to >>> have stopped. >>> >>> I'll post more as I find new information. >>> >>> Cheers, >>> >>> Eloy Paris.- >>> >>> On 01/12/2014 01:26 PM, H Plato wrote: >>> >>>> Thanks Eloy, I think you’re right, there are messages to other groups. >>>> I only have one item defined in my items.mht: >>>> >>>> INSTEON_MOTIONSENSOR, 25.AB.F9, sensor_basement_water, >>>> Sensors #2213 REV2.0 >>>> >>>> And I see in the log that it is sending ‘grp: 02’ messages as well. >>>> >>>> Anyways, interested in what you find out. Do I have to relink the >>>> sensor and the PLM if I change the object type from MOTIONSENSOR to >>>> TRIGGERLINC? >>>> >>>> 01/12/14 11:16:25 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>>> 025025abf9000002cb1102 >>>> 01/12/14 11:16:25 AM [Insteon::BaseInterface] DEBUG3: Message received >>>> with 2 hops left, delaying next transmit by 250 milliseconds to avoid >>>> collisions. >>>> 01/12/14 11:16:25 AM [Insteon::BaseInterface] Warn! Unable to locate >>>> object for source: 25abf9 and group: 02 >>>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>>> 025025abf9000002cb1102 >>>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate >>>> incoming message from an unknown device. Id: 25abf9 Grp: 02 >>>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>>> 025025abf9223e0f411102 >>>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received >>>> with 0 hops left, plus ACK will take 1 to deliver, delaying next >>>> transmit by 150 milliseconds to avoid collisions. >>>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate >>>> object for source: 25abf9 and group: 02 >>>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>>> 025025abf9110102cb0600 >>>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received >>>> with 2 hops left, delaying next transmit by 250 milliseconds to avoid >>>> collisions. >>>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate >>>> object for source: 25abf9 and group: 02 >>>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>>> 025025abf9110102cb0600 >>>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate >>>> incoming message from an unknown device. Id: 25abf9 Grp: 02 >>>> >>>> >>>> >>>> On Jan 12, 2014, at 10:35 AM, Eloy Paris <pe...@ch...> wrote: >>>> >>>>> Hi H, >>>>> >>>>> On Sun, Jan 12, 2014 at 10:16:40AM -0700, H Plato wrote: >>>>> >>>>>> Eloy, do you see ‘OFF’ messages as a triggerlinc? >>>>>> >>>>>> I put the sensor on a damp sponge (as the instructions recommend) and >>>>>> MH announces that there is water as the device gets turned on. I dried >>>>>> off the contacts, let it sit for a while and still no OFF command. >>>>>> >>>>>> Kevin, I also tried to press the set button again, that just sends ON >>>>>> commands. >>>>>> >>>>>> Does this device actually send OFF commands at all? >>>>> >>>>> As I understand it, the device will only send a message to group 1 (dry) >>>>> when the set button is pressed. I still have not had a chance to test >>>>> this, though (sorry, busy weekend). >>>>> >>>>> The owner's manual says this related to "off" messages in the >>>>> Troubleshooting section: >>>>> >>>>> Problem: Leak Sensor can turn responder on, but not off >>>>> >>>>> Cause: Leak Sensor is not designed to turn off responders. This prevents >>>>> warning lights or other leak indication devices from turning off in the >>>>> event the leak dries. >>>>> >>>>> I think this means that, once the sensor has detected water, the only >>>>> way to reset it after the area has dried, is to tap the set button. >>>>> >>>>> Is it possible that you are seeing an "on" message sent to group 1 (dry) >>>>> when the contacts are not sensing water and you tap the set button? >>>>> >>>>> I think the way it should work is this: >>>>> >>>>> Sensed water -> send "on" message to group 2 (wet) >>>>> >>>>> Not sensing water and set button is tapped -> send "on" message to group >>>>> 1 (dry) >>>>> >>>>> Heartbeat -> send "on" message to group 4 (I haven't looked closely at >>>>> the heartbeat message; I think it is also generated when the set button >>>>> is tapped quickly; if this is the case then that would allow one to test >>>>> the user code one sets up to handle the presence [or lack thereof] of >>>>> the heartbeat). >>>>> >>>>> The commands are always "on", never "off". But they are sent to >>>>> different groups to differentiate. >>>>> >>>>> Hopefully I'll have time to do more testing later today. >>>>> >>>>> Cheers, >>>>> >>>>> Eloy Paris.- >>>>> >>>>>> >>>>>> On Jan 11, 2014, at 3:17 PM, Eloy Paris <pe...@ch...> wrote: >>>>>> >>>>>>> H, >>>>>>> >>>>>>> Coincidentally, I also started playing with a water leak sensor >>>>>>> yesterday. I manually linked it to the PLM and started to test. I >>>>>>> think >>>>>>> TriggerLinc is a better fit than the motion sensor. Here's what I have >>>>>>> so far in my .mht file: >>>>>>> >>>>>>> INSTEON_TRIGGERLINC, 25.b0.fe:01, crawlspace_leak_dry, Leak_Sensors >>>>>>> # 2213 v2.0 >>>>>>> INSTEON_TRIGGERLINC, 25.b0.fe:02, crawlspace_leak_wet, Leak_Sensors >>>>>>> # 2213 v2.0 >>>>>>> INSTEON_TRIGGERLINC, 25.b0.fe:04, crawlspace_leak_heartbeat, >>>>>>> Leak_Sensors # 2213 v2.0 >>>>>>> >>>>>>> I am seeing so odd things but I haven't had a chance to do more >>>>>>> extensive tests. One odd thing is that I scanned the link table of the >>>>>>> sensor and it came back empty (and this was after doing the manual >>>>>>> link >>>>>>> to the PLM). I don't know why. >>>>>>> >>>>>>> I'll send some print_log messages later (I'm on my way out now). >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Eloy Paris.- >>>>>> >>>>>> On Jan 11, 2014, at 2:56 PM, Kevin Robert Keegan >>>>>> <ke...@kr...> wrote: >>>>>> >>>>>>> The "set" button on appliancelincs toggle on/off. Pressing the >>>>>>> button again my get you an off message. Although it would be nice >>>>>>> to know if it will naturally send an off message. >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> On Sat, Jan 11, 2014 at 01:36:38PM -0700, H Plato wrote: >>>>>>> >>>>>>>> So I added the water sensor yesterday as a INSTEON_MOTIONSENSOR. >>>>>>>> Setup and link sync’ing seemed to work, I pressed the test button >>>>>>>> on the sensor and the MH object turned on, so that’s a good thing. >>>>>>>> >>>>>>>> The object hasn’t been set to off yet, so I’m going to have to put >>>>>>>> the thing in water to see if it sends an OFF when it is dry. >>>>>>>> >>>>>>>> >>>>>>>> On Jan 4, 2014, at 9:57 AM, Eloy Paris <pe...@ch...> wrote: >>>>>>>> >>>>>>>>> Hi Brad, H, >>>>>>>>> >>>>>>>>> Sorry, I have not had a chance yet to set up the INSTEON water >>>>>>>>> leak sensors -- I received two but they are still in their >>>>>>>>> original packaging. I'll post my findings as soon as I get a >>>>>>>>> chance to try things out, though I don't know when that might be. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> >>>>>>>>> Eloy Paris.- >>>>>>>>> >>>>>>>>> On 01/03/2014 10:50 PM, Brad Yarotsky wrote: >>>>>>>>> >>>>>>>>>> I also have one and would be very interested. >>>>>>>>>> >>>>>>>>>> Thanks >>>>>>>>>> Brad >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Sent from Samsung Mobile >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -------- Original message -------- >>>>>>>>>> From: H Plato >>>>>>>>>> Date:03/01/2014 7:56 PM (GMT-06:00) >>>>>>>>>> To: Eloy Paris >>>>>>>>>> Cc: MisterHouse Users >>>>>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>>>>> >>>>>>>>>> Hi Eloy, did you get these working? I have one on order and >>>>>>>>>> hope to >>>>>>>>>> get it next week. >>>>>>>>>> >>>>>>>>>> Sent from my mobile device. >>>>>>>>>> >>>>>>>>>> On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch... >>>>>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>>>>> >>>>>>>>>>> Thanks Kevin. Guess I'll find out soon because I bought a >>>>>>>>>>> couple of >>>>>>>>>>> these sensors. I figured their cost was nothing compared to the >>>>>>>>>>> cost >>>>>>>>>>> of cleaning up the mess caused by water damage. >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> >>>>>>>>>>> Eloy Paris.- >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -------- Original message -------- >>>>>>>>>>> From: Kevin Robert Keegan <ke...@kr... >>>>>>>>>>> <mailto:ke...@kr...>> >>>>>>>>>>> Date: 12/02/2013 9:03 PM (GMT-06:00) >>>>>>>>>>> To: Eloy Paris <pe...@ch... <mailto:pe...@ch...>> >>>>>>>>>>> Cc: MisterHouse Users <mis...@li... >>>>>>>>>>> <mailto:mis...@li...>> >>>>>>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> I feel like some posted about the leak sensor before. >>>>>>>>>>> >>>>>>>>>>> Eitherway, yes Motion_Sensor is the way to go right now. >>>>>>>>>>> >>>>>>>>>>> In the future, it would be nice to add a battery level tracker >>>>>>>>>>> to it. >>>>>>>>>>> The leak sensor in theory has a heartbeat so that you can be >>>>>>>>>>> sure it >>>>>>>>>>> is still working. Although the remotelinc was supposed to have >>>>>>>>>>> that >>>>>>>>>>> heartbeat too, but it wasn't there. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch... >>>>>>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>>>>>> >>>>>>>>>>> Hello, >>>>>>>>>>> >>>>>>>>>>> Has anyone used the INSTEON water leak sensor with MisterHouse? >>>>>>>>>>> >>>>>>>>>>> http://www.smarthome.com/2852-222/p.aspx >>>>>>>>>>> >>>>>>>>>>> I don't recall a specific .mht file keyword for it but I would >>>>>>>>>>> think it >>>>>>>>>>> could be declared as some other existing device (like the motion >>>>>>>>>>> sensor), or a specific object could be created for it based >>>>>>>>>>> on an >>>>>>>>>>> existing one (again, the motion sensor seems like a logical >>>>>>>>>>> choice). >>>>>>>>>>> >>>>>>>>>>> Also, in case you were not aware, Smarthome is having a 20% >>>>>>>>>>> off sale >>>>>>>>>>> since last week. It will probably end tonight. >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> >>>>>>>>>>> Eloy Paris.- >>>>>>>> >>>>>> >>>> >>> >> > |
From: H P. <hp...@gm...> - 2014-01-26 00:51:38
|
I get 2 after ON messages when water is detected…however this could be my user code, I’ll look into this more. I’ve been trying to turn the water leak sensor off through the web interface with no success. $sensor_basement_water is defined as a Triggerlinc, however when I try this command: http://mh/SET?$sensor_basement_water?off it doesn’t turn off. Being able to manually turn it off is an OK workaround until the at-device method is fully understood. Can you turn off your triggerlinc via the web? Interestingly enough, the Heartbeat device seems to reliably get an ON message once a day… Sensor basement water hb states 01/24/14 06:26:58 PM on set_by=$sensor_basement_water_hb 01/23/14 06:36:39 PM on set_by=$sensor_basement_water_hb 01/22/14 06:46:20 PM on set_by=$sensor_basement_water_hb 01/21/14 06:56:01 PM on set_by=$sensor_basement_water_hb 01/20/14 07:05:42 PM on set_by=$sensor_basement_water_hb 01/19/14 07:15:23 PM on set_by=$sensor_basement_water_hb 01/18/14 07:25:05 PM on set_by=$sensor_basement_water_hb 01/17/14 07:34:46 PM on set_by=$sensor_basement_water_hb 01/16/14 07:44:28 PM on set_by=$sensor_basement_water_hb 01/15/14 07:54:09 PM on set_by=$sensor_basement_water_hb On Jan 19, 2014, at 7:36 AM, Eloy Paris <pe...@ch...> wrote: > Hi H, > > On 01/18/2014 01:27 PM, H Plato wrote: > >> Hey Eloy, >> >> Did you manage to get ahold of smarthome about this? > > Nope, I have not had a chance to contact Smarthome support to ask why the sensors are behaving the way I observed... > >> Is there a consistent pattern that you see from your devices? For the >> 2 tests that I did, I saw an ON to group 1 when it was wet, and then >> on to group 2 when the set button was pressed. > > This doesn't make sense, right? I mean, the wet group is group #2 so when it's wet there should be a message going to group #2; or at least one message. Or I am missing something??? > > One thing, though -- when I consecutively press the set button I do see alternating messages to groups 1 and 2, i.e. one press generates a message to group #1 and the next press generates a message to group #2. > >> I didn’t see any traffic when I dried off the contacts. Strangely enough, I get two alerts when water is applied using this usercode (maybe the object is set twice?) >> >> if (state_now $sensor_basement_water ) { >> print_log “WATER LEAK: water sensor is now $sensor_basement_water->{state}"; >> >> if ( state $sensor_basement_water eq 'on' ) { >> >> print_log “WATER LEAK: water sensor ON"; >> speak (rooms=> "all", mode=> "unmuted", text=>"Water detected on basement water sensor"); >> >> } >> } > > Do you mean that you see this in your print log: > > WATER LEAK: water sensor is now on > WATER LEAK: water sensor ON > > Or that you get the above messages twice? > > As I understand it, the sensor will never send an 'off' message to groups 1 or 2, so the "if ( state $sensor_basement_water eq 'on' )" check is unnecessary (it will always be on). > >> I think the ideal end state is that the device goes on until manually >> turned reset. That logic makes sense to me, as I would want to >> visually inspect the device prior to resetting it. It would be nice >> to have a single object that is on when water is detected and then >> off when the set button is pressed, rather than tracking two objects >> and usercode to either set the group 1 object to off or another >> generic object that would track ON/OFF. > > Wouldn't this be easy to accomplish by using some logic that looks at the state changes of the group 1 and group 2 objects? > > I haven't tested my sensors in a few days (they're still sitting on my desk) so they should be dry. I'll conduct a couple of additional test to see in what mood they're in today and send back the results. Right now my testing is simple -- if the sensor detects water then a light connected to an ApplianceLinc should turn on, i.e. no MH in the picture. It doesn't get any simpler than this. > > Cheers, > > Eloy Paris.- > >> >> >> On Jan 14, 2014, at 11:31 AM, Eloy Paris <pe...@ch...> wrote: >> >>> Just to take MH out of the picture while I get used to the INSTEON water leak sensor, I manually linked a switch to the sensor, the idea being that the sensor will turn on the light when it senses water. I then by putting the sensor on top of water... >>> >>> In some cases the sensor failed to send a message to the wet group and instead it sent it to the dry group. Now, that's not very reassuring, is it? I guess I can program MH to warn me when messages are send to either group but that still does not address that the sensor is not doing what I think it is supposed to be doing. >>> >>> I'll contact Smarthome support to see what they have to say about this. >>> >>> Cheers, >>> >>> Eloy Paris.- >>> >>> On 01/12/2014 08:43 PM, Eloy Paris wrote: >>> >>>> Hi H, >>>> >>>> I'm getting increasingly frustrated with the INSTEON Water Leak Sensor >>>> because I am getting mixed/odd results. I have the sensor sitting on >>>> water right now and the last message that was sent was an "on" message >>>> to the "dry" group (group #1). When I first put it on top of water I saw >>>> a message sent to the "wet" group (group #2) but then messages to the >>>> "dry" group followed. I don't get it. >>>> >>>> The sensor also seems to send "on" messages to the "dry" group when it's >>>> removed from water. Perhaps this is by design, though I am not sure. If >>>> this is the case then I don't understand the need for tapping the set >>>> button to reset the sensor after it has sensed water (per the >>>> instructions that came in the original package). >>>> >>>> In addition, after removing the sensor from water, every time I tap the >>>> set button the sensor seems to toggle the messages that it sends: I tap >>>> one time and it sends a message to the "dry" group followed by a >>>> heartbeat message a few seconds later. I tap a second time and it sends >>>> a message to the "wet" group followed by the heartbeat sensor a few >>>> seconds later. >>>> >>>> All in all, I think TRIGGERLINC is a much better fit than MOTIONSENSOR >>>> -- all you have to do is to define three objects: for groups 1, 2, and >>>> 4. That should get rid of the "Warn! Unable to locate object for source: >>>> 25abf9 and group: 02" message. >>>> >>>> I don't think you need to relink the sensor to the PLM if you change to >>>> TriggerLinc. I am not sure but I think the PLM needs the responder >>>> records for groups 2 and 4 (I'm sure others will keep me honest here). >>>> That is easily accomplished by running a "sync links" on the group 1 >>>> object. >>>> >>>> I think MH support for this device is ready (in the form of a >>>> TriggerLinc); I just need to figure out why the sensor itself (not MH) >>>> seems to be behaving erratically... >>>> >>>> I purchased two sensors so I'll be testing the other sensor as well to >>>> see if it behaves like the first. >>>> >>>> BTW, I also noticed that the sensor I have been playing with was >>>> re-transmitting messages. I think it was because it came linked to some >>>> other device that I don't have in my network. After I reset the device >>>> to factory defaults and re-linked to my PLM the retransmissions seem to >>>> have stopped. >>>> >>>> I'll post more as I find new information. >>>> >>>> Cheers, >>>> >>>> Eloy Paris.- >>>> >>>> On 01/12/2014 01:26 PM, H Plato wrote: >>>> >>>>> Thanks Eloy, I think you’re right, there are messages to other groups. >>>>> I only have one item defined in my items.mht: >>>>> >>>>> INSTEON_MOTIONSENSOR, 25.AB.F9, sensor_basement_water, >>>>> Sensors #2213 REV2.0 >>>>> >>>>> And I see in the log that it is sending ‘grp: 02’ messages as well. >>>>> >>>>> Anyways, interested in what you find out. Do I have to relink the >>>>> sensor and the PLM if I change the object type from MOTIONSENSOR to >>>>> TRIGGERLINC? >>>>> >>>>> 01/12/14 11:16:25 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>>>> 025025abf9000002cb1102 >>>>> 01/12/14 11:16:25 AM [Insteon::BaseInterface] DEBUG3: Message received >>>>> with 2 hops left, delaying next transmit by 250 milliseconds to avoid >>>>> collisions. >>>>> 01/12/14 11:16:25 AM [Insteon::BaseInterface] Warn! Unable to locate >>>>> object for source: 25abf9 and group: 02 >>>>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>>>> 025025abf9000002cb1102 >>>>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate >>>>> incoming message from an unknown device. Id: 25abf9 Grp: 02 >>>>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>>>> 025025abf9223e0f411102 >>>>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received >>>>> with 0 hops left, plus ACK will take 1 to deliver, delaying next >>>>> transmit by 150 milliseconds to avoid collisions. >>>>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate >>>>> object for source: 25abf9 and group: 02 >>>>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>>>> 025025abf9110102cb0600 >>>>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] DEBUG3: Message received >>>>> with 2 hops left, delaying next transmit by 250 milliseconds to avoid >>>>> collisions. >>>>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] Warn! Unable to locate >>>>> object for source: 25abf9 and group: 02 >>>>> 01/12/14 11:16:26 AM [Insteon_PLM] DEBUG3: Received PLM raw data: >>>>> 025025abf9110102cb0600 >>>>> 01/12/14 11:16:26 AM [Insteon::BaseInterface] WARN! Dropped duplicate >>>>> incoming message from an unknown device. Id: 25abf9 Grp: 02 >>>>> >>>>> >>>>> >>>>> On Jan 12, 2014, at 10:35 AM, Eloy Paris <pe...@ch...> wrote: >>>>> >>>>>> Hi H, >>>>>> >>>>>> On Sun, Jan 12, 2014 at 10:16:40AM -0700, H Plato wrote: >>>>>> >>>>>>> Eloy, do you see ‘OFF’ messages as a triggerlinc? >>>>>>> >>>>>>> I put the sensor on a damp sponge (as the instructions recommend) and >>>>>>> MH announces that there is water as the device gets turned on. I dried >>>>>>> off the contacts, let it sit for a while and still no OFF command. >>>>>>> >>>>>>> Kevin, I also tried to press the set button again, that just sends ON >>>>>>> commands. >>>>>>> >>>>>>> Does this device actually send OFF commands at all? >>>>>> >>>>>> As I understand it, the device will only send a message to group 1 (dry) >>>>>> when the set button is pressed. I still have not had a chance to test >>>>>> this, though (sorry, busy weekend). >>>>>> >>>>>> The owner's manual says this related to "off" messages in the >>>>>> Troubleshooting section: >>>>>> >>>>>> Problem: Leak Sensor can turn responder on, but not off >>>>>> >>>>>> Cause: Leak Sensor is not designed to turn off responders. This prevents >>>>>> warning lights or other leak indication devices from turning off in the >>>>>> event the leak dries. >>>>>> >>>>>> I think this means that, once the sensor has detected water, the only >>>>>> way to reset it after the area has dried, is to tap the set button. >>>>>> >>>>>> Is it possible that you are seeing an "on" message sent to group 1 (dry) >>>>>> when the contacts are not sensing water and you tap the set button? >>>>>> >>>>>> I think the way it should work is this: >>>>>> >>>>>> Sensed water -> send "on" message to group 2 (wet) >>>>>> >>>>>> Not sensing water and set button is tapped -> send "on" message to group >>>>>> 1 (dry) >>>>>> >>>>>> Heartbeat -> send "on" message to group 4 (I haven't looked closely at >>>>>> the heartbeat message; I think it is also generated when the set button >>>>>> is tapped quickly; if this is the case then that would allow one to test >>>>>> the user code one sets up to handle the presence [or lack thereof] of >>>>>> the heartbeat). >>>>>> >>>>>> The commands are always "on", never "off". But they are sent to >>>>>> different groups to differentiate. >>>>>> >>>>>> Hopefully I'll have time to do more testing later today. >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Eloy Paris.- >>>>>> >>>>>>> >>>>>>> On Jan 11, 2014, at 3:17 PM, Eloy Paris <pe...@ch...> wrote: >>>>>>> >>>>>>>> H, >>>>>>>> >>>>>>>> Coincidentally, I also started playing with a water leak sensor >>>>>>>> yesterday. I manually linked it to the PLM and started to test. I >>>>>>>> think >>>>>>>> TriggerLinc is a better fit than the motion sensor. Here's what I have >>>>>>>> so far in my .mht file: >>>>>>>> >>>>>>>> INSTEON_TRIGGERLINC, 25.b0.fe:01, crawlspace_leak_dry, Leak_Sensors >>>>>>>> # 2213 v2.0 >>>>>>>> INSTEON_TRIGGERLINC, 25.b0.fe:02, crawlspace_leak_wet, Leak_Sensors >>>>>>>> # 2213 v2.0 >>>>>>>> INSTEON_TRIGGERLINC, 25.b0.fe:04, crawlspace_leak_heartbeat, >>>>>>>> Leak_Sensors # 2213 v2.0 >>>>>>>> >>>>>>>> I am seeing so odd things but I haven't had a chance to do more >>>>>>>> extensive tests. One odd thing is that I scanned the link table of the >>>>>>>> sensor and it came back empty (and this was after doing the manual >>>>>>>> link >>>>>>>> to the PLM). I don't know why. >>>>>>>> >>>>>>>> I'll send some print_log messages later (I'm on my way out now). >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> Eloy Paris.- >>>>>>> >>>>>>> On Jan 11, 2014, at 2:56 PM, Kevin Robert Keegan >>>>>>> <ke...@kr...> wrote: >>>>>>> >>>>>>>> The "set" button on appliancelincs toggle on/off. Pressing the >>>>>>>> button again my get you an off message. Although it would be nice >>>>>>>> to know if it will naturally send an off message. >>>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> On Sat, Jan 11, 2014 at 01:36:38PM -0700, H Plato wrote: >>>>>>>> >>>>>>>>> So I added the water sensor yesterday as a INSTEON_MOTIONSENSOR. >>>>>>>>> Setup and link sync’ing seemed to work, I pressed the test button >>>>>>>>> on the sensor and the MH object turned on, so that’s a good thing. >>>>>>>>> >>>>>>>>> The object hasn’t been set to off yet, so I’m going to have to put >>>>>>>>> the thing in water to see if it sends an OFF when it is dry. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Jan 4, 2014, at 9:57 AM, Eloy Paris <pe...@ch...> wrote: >>>>>>>>> >>>>>>>>>> Hi Brad, H, >>>>>>>>>> >>>>>>>>>> Sorry, I have not had a chance yet to set up the INSTEON water >>>>>>>>>> leak sensors -- I received two but they are still in their >>>>>>>>>> original packaging. I'll post my findings as soon as I get a >>>>>>>>>> chance to try things out, though I don't know when that might be. >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> >>>>>>>>>> Eloy Paris.- >>>>>>>>>> >>>>>>>>>> On 01/03/2014 10:50 PM, Brad Yarotsky wrote: >>>>>>>>>> >>>>>>>>>>> I also have one and would be very interested. >>>>>>>>>>> >>>>>>>>>>> Thanks >>>>>>>>>>> Brad >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Sent from Samsung Mobile >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -------- Original message -------- >>>>>>>>>>> From: H Plato >>>>>>>>>>> Date:03/01/2014 7:56 PM (GMT-06:00) >>>>>>>>>>> To: Eloy Paris >>>>>>>>>>> Cc: MisterHouse Users >>>>>>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>>>>>> >>>>>>>>>>> Hi Eloy, did you get these working? I have one on order and >>>>>>>>>>> hope to >>>>>>>>>>> get it next week. >>>>>>>>>>> >>>>>>>>>>> Sent from my mobile device. >>>>>>>>>>> >>>>>>>>>>> On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch... >>>>>>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Thanks Kevin. Guess I'll find out soon because I bought a >>>>>>>>>>>> couple of >>>>>>>>>>>> these sensors. I figured their cost was nothing compared to the >>>>>>>>>>>> cost >>>>>>>>>>>> of cleaning up the mess caused by water damage. >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> >>>>>>>>>>>> Eloy Paris.- >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -------- Original message -------- >>>>>>>>>>>> From: Kevin Robert Keegan <ke...@kr... >>>>>>>>>>>> <mailto:ke...@kr...>> >>>>>>>>>>>> Date: 12/02/2013 9:03 PM (GMT-06:00) >>>>>>>>>>>> To: Eloy Paris <pe...@ch... <mailto:pe...@ch...>> >>>>>>>>>>>> Cc: MisterHouse Users <mis...@li... >>>>>>>>>>>> <mailto:mis...@li...>> >>>>>>>>>>>> Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> I feel like some posted about the leak sensor before. >>>>>>>>>>>> >>>>>>>>>>>> Eitherway, yes Motion_Sensor is the way to go right now. >>>>>>>>>>>> >>>>>>>>>>>> In the future, it would be nice to add a battery level tracker >>>>>>>>>>>> to it. >>>>>>>>>>>> The leak sensor in theory has a heartbeat so that you can be >>>>>>>>>>>> sure it >>>>>>>>>>>> is still working. Although the remotelinc was supposed to have >>>>>>>>>>>> that >>>>>>>>>>>> heartbeat too, but it wasn't there. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch... >>>>>>>>>>>> <mailto:pe...@ch...>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> Hello, >>>>>>>>>>>> >>>>>>>>>>>> Has anyone used the INSTEON water leak sensor with MisterHouse? >>>>>>>>>>>> >>>>>>>>>>>> http://www.smarthome.com/2852-222/p.aspx >>>>>>>>>>>> >>>>>>>>>>>> I don't recall a specific .mht file keyword for it but I would >>>>>>>>>>>> think it >>>>>>>>>>>> could be declared as some other existing device (like the motion >>>>>>>>>>>> sensor), or a specific object could be created for it based >>>>>>>>>>>> on an >>>>>>>>>>>> existing one (again, the motion sensor seems like a logical >>>>>>>>>>>> choice). >>>>>>>>>>>> >>>>>>>>>>>> Also, in case you were not aware, Smarthome is having a 20% >>>>>>>>>>>> off sale >>>>>>>>>>>> since last week. It will probably end tonight. >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> >>>>>>>>>>>> Eloy Paris.- >>>>>>>>> >>>>>>> >>>>> >>>> >>> >> > |
From: Kevin R. K. <ke...@kr...> - 2014-01-26 17:31:03
|
On Jan 25, 2014 4:51 PM, "H Plato" <hp...@gm...> wrote: > Can you turn off your triggerlinc via the web? > Hmm, I have to check. I don't remember how I coded it, but probably not done that is not really supported by the device. You should be able to call set_receive on it to change the MH state. |
From: Kevin R. K. <ke...@kr...> - 2014-01-27 00:10:09
|
Yeah, that last error is a correct statement of fact. The only thing you can do, is change the MH's internal state for the device. You can do this by calling $object->set_receive(OFF); This will not send any message to the device, but will only change MH's understanding of the device's state. This is not technically how MH was designed to operate, so there is nothing in the web interface for calling any of this. Another suggestion, would be to create a "tracking" object that you can set. $tracking = new Generic_Item; $tracking->states('on', 'off'); $water_sensor->tie_event('$tracking->set($State)'); You can then hide the water sensor. And control the "state" of it using the tracking item. Hope that makes sense. On Sun, Jan 26, 2014 at 12:09 PM, H Plato <hp...@gm...> wrote: > I’m trying to turn it off via button_action.pl which calls it via > > $object->set(“$state”,’web’); > > I’m unfamiliar with set_receive > > I also made that change to button_action.pl, > > sleep(2) if $object->isa(‘Insteon::BaseObject’); > > When I try and change the triggerlinc I get this in the logs: > > 01/25/14 05:12:25 PM [Insteon::BaseObject] failed state validation with > state= > > and then a few minutes later > > 01/25/14 05:17:31 PM [Insteon::BaseObject] $sensor_basement_water is not a > responder and cannot be set to a state. > > On Jan 26, 2014, at 10:30 AM, Kevin Robert Keegan <ke...@kr...> > wrote: > > > On Jan 25, 2014 4:51 PM, "H Plato" <hp...@gm...> wrote: > > Can you turn off your triggerlinc via the web? > > > > Hmm, I have to check. I don't remember how I coded it, but probably not > done that is not really supported by the device. > > You should be able to call set_receive on it to change the MH state. > > > |
From: H P. <hp...@gm...> - 2014-01-27 14:38:54
|
That makes sense. It would be nice to get these water sensors figured out — that said, since these devices never send an OFF signal, would it really be that bad if the internal state was changed? If the device got wet again, it would just send another ON. A generic object to display status is possible — but masks the underlying problem that these devices don’t send an OFF signal. Would it make sense to create a derived object for the water leak from triggerlinc that allows a regular set command? Or is triggerlinc even the best fit object? If there was an object, it would be nice to include heartbeat warnings, as it looks like those get consistently send 23 hours and 50 minutes. Thoughts? On Jan 26, 2014, at 5:09 PM, Kevin Robert Keegan <ke...@kr...> wrote: Yeah, that last error is a correct statement of fact. The only thing you can do, is change the MH's internal state for the device. You can do this by calling $object->set_receive(OFF); This will not send any message to the device, but will only change MH's understanding of the device's state. This is not technically how MH was designed to operate, so there is nothing in the web interface for calling any of this. Another suggestion, would be to create a "tracking" object that you can set. $tracking = new Generic_Item; $tracking->states('on', 'off'); $water_sensor->tie_event('$tracking->set($State)'); You can then hide the water sensor. And control the "state" of it using the tracking item. Hope that makes sense. On Sun, Jan 26, 2014 at 12:09 PM, H Plato <hp...@gm...> wrote: > I’m trying to turn it off via button_action.pl which calls it via > > $object->set(“$state”,’web’); > > I’m unfamiliar with set_receive > > I also made that change to button_action.pl, > > sleep(2) if $object->isa(‘Insteon::BaseObject’); > > When I try and change the triggerlinc I get this in the logs: > > 01/25/14 05:12:25 PM [Insteon::BaseObject] failed state validation with > state= > > and then a few minutes later > > 01/25/14 05:17:31 PM [Insteon::BaseObject] $sensor_basement_water is not a > responder and cannot be set to a state. > > On Jan 26, 2014, at 10:30 AM, Kevin Robert Keegan <ke...@kr...> > wrote: > > > On Jan 25, 2014 4:51 PM, "H Plato" <hp...@gm...> wrote: > > Can you turn off your triggerlinc via the web? > > > > Hmm, I have to check. I don't remember how I coded it, but probably not > done that is not really supported by the device. > > You should be able to call set_receive on it to change the MH state. > > > |
From: Kevin R. K. <ke...@kr...> - 2014-01-28 00:36:13
|
> > Would it make sense to create a derived object for the water leak from > triggerlinc that allows a regular set command? Or is triggerlinc even the > best fit object? If there was an object, it would be nice to include > heartbeat warnings, as it looks like those get consistently send 23 hours > and 50 minutes. > Creating a WaterSensor object wouldn't be an issue, it probably would not be derived from the triggerlinc, but that isn't a big deal. I am still a little uncomfortable with the idea of using the set function to reset MH's status while not altering the device. It would really be an outlier in that we would be encouraging the status between MH and the device to become out-of-sync. This is partially why I advocated for the tracking object, as the abstracted layer recognizes the distinction between what we represent in MH and what is in fact reality. The motion sensors have long been able to send only ON commands, granted this is an optional setting, but when in this mode, MH respects their reported state. Maybe I am trying to be too formalistic. |
From: H P. <hp...@gm...> - 2014-01-28 03:04:10
|
It makes sense, and nothing wrong with wanting to do things right! The way this thing works, it will never be off (unless the ‘dry’ address actually works, however Eloy’s testing seemed somewhat inconsistent), so I don’t know if there is any downside to being ‘out of sync’ as the MH object will have to always be ON. What about a ‘complex object’? For example the ANALOG_SENSOR item has a few components inside it. It listens for xap temperature values, and this can be queried through $object->temperature. The actual state is user defined. As this water sensor still isn’t that straightforward (it seems non-deterministic what ON messages are sent to group 1 and then to group 2), An object that is set to wet or dry (that can be set by manual methods — to allow web control or script control) that is also set by insteon ON messages. Since mine has a reliable heartbeat, having a $object->heartbeat method would be good to test each New_minute to see if the battery is dead. This approach might be regressive based on messages on the list over the past few months about having more simple objects rather than fewer complex ones... That said, in absence of anything else, this is probably the type of usercode I’d sketch up - a generic item set to wet or dry that changes based on group 1 messages from a water sensor as a triggerlinc. I’d also set up a 25 hour timer based on heartbeat messages. This would work for my use, but I’m wondering if something more robust might be useful as these leak sensors are cheap and I think quite useful. Any other ideas or suggestions from those that have these sensors? On Jan 27, 2014, at 5:36 PM, Kevin Robert Keegan <ke...@kr...> wrote: > Would it make sense to create a derived object for the water leak from triggerlinc that allows a regular set command? Or is triggerlinc even the best fit object? If there was an object, it would be nice to include heartbeat warnings, as it looks like those get consistently send 23 hours and 50 minutes. > > Creating a WaterSensor object wouldn't be an issue, it probably would not be derived from the triggerlinc, but that isn't a big deal. > > I am still a little uncomfortable with the idea of using the set function to reset MH's status while not altering the device. It would really be an outlier in that we would be encouraging the status between MH and the device to become out-of-sync. This is partially why I advocated for the tracking object, as the abstracted layer recognizes the distinction between what we represent in MH and what is in fact reality. The motion sensors have long been able to send only ON commands, granted this is an optional setting, but when in this mode, MH respects their reported state. > > Maybe I am trying to be too formalistic. |
From: H P. <hp...@gm...> - 2014-01-04 01:56:14
|
Hi Eloy, did you get these working? I have one on order and hope to get it next week. Sent from my mobile device. > On Dec 3, 2013, at 4:50 AM, Eloy Paris <pe...@ch...> wrote: > > Thanks Kevin. Guess I'll find out soon because I bought a couple of these sensors. I figured their cost was nothing compared to the cost of cleaning up the mess caused by water damage. > > Cheers, > > Eloy Paris.- > > > > > -------- Original message -------- > From: Kevin Robert Keegan <ke...@kr...> > Date: 12/02/2013 9:03 PM (GMT-06:00) > To: Eloy Paris <pe...@ch...> > Cc: MisterHouse Users <mis...@li...> > Subject: Re: [mh] INSTEON Water Leak Sensor/Smarthome 20% off sale > > > I feel like some posted about the leak sensor before. > > Eitherway, yes Motion_Sensor is the way to go right now. > > In the future, it would be nice to add a battery level tracker to it. The leak sensor in theory has a heartbeat so that you can be sure it is still working. Although the remotelinc was supposed to have that heartbeat too, but it wasn't there. > > >> On Mon, Dec 2, 2013 at 12:28 PM, Eloy Paris <pe...@ch...> wrote: >> Hello, >> >> Has anyone used the INSTEON water leak sensor with MisterHouse? >> >> http://www.smarthome.com/2852-222/p.aspx >> >> I don't recall a specific .mht file keyword for it but I would think it >> could be declared as some other existing device (like the motion >> sensor), or a specific object could be created for it based on an >> existing one (again, the motion sensor seems like a logical choice). >> >> Also, in case you were not aware, Smarthome is having a 20% off sale >> since last week. It will probably end tonight. >> >> Cheers, >> >> Eloy Paris.- >> >> ------------------------------------------------------------------------------ >> Rapidly troubleshoot problems before they affect your business. Most IT >> organizations don't have a clear picture of how application performance >> affects their revenue. With AppDynamics, you get 100% visibility into your >> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! >> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk >> ________________________________________________________ >> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > |