Yeah, it shows up in InControl, so it's joined, but switching the view to list still doesn't show any changes when I set the sensor off. I'll have to try excluding it and reincluding it tonight, otherwise I'm chalking it up as a dud and exchanging it.
Utilitech (Everspring) Water Sensor
- 145 Views
- Last Post 20 August 2015
weidnerj
posted this
17 July 2015
My suggestion would be to put your ICHA from tile to list from going to Devices to the right of that menu is a toggle menu that will let you switch from tile to list mode. Then test it and see if the value changes from no water to water test because in list mode you can see the actual values.
rscott
posted this
20 July 2015
Is anyone successfully using one of these with InControl? I picked one of these up at Lowes to monitor my septic sump. It paired fine and shows up in InControl, but when I submerge the end of the sensor, it starts beeping, but it doesn't show up as tripped in InControl. Did I stumble across a defective unit? or is there a trick to the config?
Also, be sure to associate the sensor with your USB stick.
NFOtte
posted this
22 July 2015
Yeah, it shows up in InControl, so it's joined, but switching the view to list still doesn't show any changes when I set the sensor off. I'll have to try excluding it and reincluding it tonight, otherwise I'm chalking it up as a dud and exchanging it.
Axial-User
posted this
24 July 2015
Joining it isn't enough for sensors. You have to do the autoconfigure (or manually associate it). I have a couple Aeon sensors. They won't report tripped unless they are associated (this is not the same as just adding it to your network).
NFOtte
posted this
05 August 2015
Ah, it wouldn't auto-configure when I first paired it, and subsequent attempts to associate it failed as well. It seems that while the Z-Stick thought the Utilitech had joined the network, the Utilitech didn't think it had done anything. Tried having the Utilitech join the network again a number of times before it finally registered with the Utilitech (and then I got to have fun with the Zensys tools to remove the four phantom "Alarm Sensors").
jalexander319
posted this
08 August 2015
I think I am having a similar issue. I have the Utilitech water sensor. I paired it with the zstick. It shows up in incontrol(free version) and if I trip it, I can see the value of the "water leak alarm" change from 0 to 255.
But, I can't seem to get a scene to trigger and email me a current device state. I created a scene, added the "alarm" as a device, created a trigger for any change, and added the email state script to the pre and post script sections. I successfully sent a test email.
When I trip the sensor, nothing happens with the exception that I see the value change to 255. I would expect to at least see something show up in events if it activated the scene.
Do I need a paid version of incontrol? I was hoping to try it out before buying and would like to see it in action first.
I will be scouring the web for answers this weekend, but I have a 2 year old and wife that keeps me busy, so I appreciate any help you can provide.
Thanks,
-Jeff
Edit: I activated the trial Pro version. I read something about the free version not supporting sensors. But I am having the same issue. I can press the button on the sensor and then click associations in incontrol, and it populates a list and my zstick controller is checked.
weidnerj
posted this
08 August 2015
I think I am having a similar issue. I have the Utilitech water sensor. I paired it with the zstick. It shows up in incontrol(free version) and if I trip it, I can see the value of the "water leak alarm" change from 0 to 255.
But, I can't seem to get a scene to trigger and email me a current device state. I created a scene, added the "alarm" as a device, created a trigger for any change, and added the email state script to the pre and post script sections. I successfully sent a test email.
When I trip the sensor, nothing happens with the exception that I see the value change to 255. I would expect to at least see something show up in events if it activated the scene.
Do I need a paid version of incontrol? I was hoping to try it out before buying and would like to see it in action first.
I will be scouring the web for answers this weekend, but I have a 2 year old and wife that keeps me busy, so I appreciate any help you can provide.
Thanks,
-Jeff
Edit: I activated the trial Pro version. I read something about the free version not supporting sensors. But I am having the same issue. I can press the button on the sensor and then click associations in incontrol, and it populates a list and my zstick controller is checked.
Have you tried to set the scene to trigger at 255 instead of any change?
Do you have any other zwave devices that you can manipulate like a light switch or outlet that you can use as a test device. Water detected, turn on a light? Then if you can get that test scene to work, then add in E-mail?
jalexander319
posted this
08 August 2015
Have you tried to set the scene to trigger at 255 instead of any change?
Do you have any other zwave devices that you can manipulate like a light switch or outlet that you can use as a test device. Water detected, turn on a light? Then if you can get that test scene to work, then add in E-mail?
Yes. I originally created a trigger for 255. I will try that again, as I may have made other changes since then.
I do not have any other zwave devices. I wanted to see how this worked before I bought more. And there are so many options out there, I am still researching them. I am interested in zwave electrical outlets, but so far, all of them I have looked at only have one socket that is zwave controlled, and the other is always on. Not sure if this is some sort of code requirement or something.
I do have a Nest thermostat. Since I am using the trial pro version, I hope I can get the plugin to test it. Maybe I can then create a chain reaction using that?
I see that for the water sensor, it shows 2 different "attributes". One for the Battery, which shows 100%. And the other for "Water Leak Alarm" which shows 0 when open and 255 when closed. I am wondering how you use those individually in a scene. How wold I create something that says "if the battery gets below 20%, email me"? It seems like the scene just sees the device itself, not the individual attributes of the device. Maybe I am missign something. I hope I am. That woud mean it is just a simple mistake.
rscott
posted this
08 August 2015
Have you tried to set the scene to trigger at 255 instead of any change?
Do you have any other zwave devices that you can manipulate like a light switch or outlet that you can use as a test device. Water detected, turn on a light? Then if you can get that test scene to work, then add in E-mail?
Yes. I originally created a trigger for 255. I will try that again, as I may have made other changes since then.
I do not have any other zwave devices. I wanted to see how this worked before I bought more. And there are so many options out there, I am still researching them. I am interested in zwave electrical outlets, but so far, all of them I have looked at only have one socket that is zwave controlled, and the other is always on. Not sure if this is some sort of code requirement or something.
I do have a Nest thermostat. Since I am using the trial pro version, I hope I can get the plugin to test it. Maybe I can then create a chain reaction using that?
I see that for the water sensor, it shows 2 different "attributes". One for the Battery, which shows 100%. And the other for "Water Leak Alarm" which shows 0 when open and 255 when closed. I am wondering how you use those individually in a scene. How wold I create something that says "if the battery gets below 20%, email me"? It seems like the scene just sees the device itself, not the individual attributes of the device. Maybe I am missign something. I hope I am. That woud mean it is just a simple mistake.
If it's not already, can you set the device to a "Binary sensor" and then report back if the checkmark changes to checked when the water leak is triggered? If it does not, then you'll need to create a device from that "water leak alarm" reading and then base your trigger solely on that.
jalexander319
posted this
08 August 2015
If it's not already, can you set the device to a "Binary sensor" and then report back if the checkmark changes to checked when the water leak is triggered? If it does not, then you'll need to create a device from that "water leak alarm" reading and then base your trigger solely on that.
I didn't realize that those were little blue buttons. I see the green plus sign on them now. So I created a new device based off of the "Water Leak Alarm" attribute of the original device. Then, if I tripped the alarm, I could see the status of the device change in the main window, along with where it displays the information in the far right pane.
I deleted the old scene and created a new one. But still nothing happens. I added the new water leak alarm device. I added the emailcurrentdevicestatus script to pre-scripts. I checked the "no change" box in the advanced settings since it is just an alarm that is reporting its status (I think that is correct, right?) I added a device trigger and set it to trigger on close. There is a box labeled "disabled" that was checked. I unchecked it. And that is it for the scene.
In the main device window, for the device properties, I left it at defaults. I had checked "enable push updates", but I have it unchecked until I get it working.
Anything else I can try?? I am going to reboot my machine since I haven't since I installed incontrol. I didn't think it should be necessary, but it couldn't hurt to do it since I am having issues.
rscott
posted this
08 August 2015
Anything else I can try?? I am going to reboot my machine since I haven't since I installed incontrol. I didn't think it should be necessary, but it couldn't hurt to do it since I am having issues.
Can you go to tools/options and enable the one that logs extra scene data? That will log if a scene was triggered or not to your logfile.txt (found in your InControl folder). Check there to see if it has anything written about it when you trigger the scene - this will tell us if the trigger is doing anything or not.
What kind of device is the "new device" you created from the leak alarm reading?
jalexander319
posted this
08 August 2015
Can you go to tools/options and enable the one that logs extra scene data? That will log if a scene was triggered or not to your logfile.txt (found in your InControl folder). Check there to see if it has anything written about it when you trigger the scene - this will tell us if the trigger is doing anything or not.
What kind of device is the "new device" you created from the leak alarm reading?
I tried both an alarm device and a binary device. Looks like there is some useful info in the log. Here is the last snippet. Looks like it is activating the scene, but it is trying to run the activate scene script and not the emaildevicestatus script?
8/8/2015 1:26:13 PM: Properties requested for device 34b525b7-fae6-4f37-9d2d-ca43388eb726
8/8/2015 1:26:13 PM: Found device: yes
8/8/2015 1:26:13 PM: getDeviceDetails: 1
8/8/2015 1:26:13 PM: getDeviceDetails: 2
8/8/2015 1:26:13 PM: getDeviceDetails: 3
8/8/2015 1:26:13 PM: getDeviceDetails json: {"lastCommunication":"2000-01-01T00:00:00","queuedCommandCount":0,"pollTimeSeconds":0,"isSleeping":false,"pollDevice":false,"smartRoutePolling":false,"enableReporting":false,"mobileHidden":false,"shortId":3,"auditNode":false,"pushUpdates":false,"allowRoomManagerUse":true,"queueCommandsUntilWake":false,"neverUseSecureComms":false}
8/8/2015 1:34:28 PM: Service appears to be running already. Will not attempt restart.
8/8/2015 1:35:04 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 1:35:04 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 1:35:04 PM: SceneTrigger Sump Pump Alarm: NodeIds is required Rule Data. Rule will not run.
8/8/2015 1:35:04 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 1:35:04 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 1:35:04 PM: SceneTrigger Sump Pump Alarm: NodeIds is required Rule Data. Rule will not run.
8/8/2015 1:35:05 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 1:35:05 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 1:35:05 PM: SceneTrigger Sump Pump Alarm: NodeIds is required Rule Data. Rule will not run.
8/8/2015 1:35:05 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 1:35:05 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 1:35:05 PM: SceneTrigger Sump Pump Alarm: NodeIds is required Rule Data. Rule will not run.
8/8/2015 1:35:21 PM: SceneTrigger Sump Pump Alarm: Device Water Leak Alarm changed to 255. Running script activateScene.cs.
8/8/2015 1:35:21 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 1:35:21 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 1:35:21 PM: SceneTrigger Sump Pump Alarm: NodeIds is required Rule Data. Rule will not run.
8/8/2015 1:35:21 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 1:35:21 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 1:35:21 PM: SceneTrigger Sump Pump Alarm: NodeIds is required Rule Data.
jalexander319
posted this
08 August 2015
I am looking at the emailcurrentdevicestate script now. I am assuming that I should not need to edit it? Is that correct?
rscott
posted this
08 August 2015
You should not need to edit it that script.
The log output you provided seems like it's coming from the "rules" section... Just in case, you should delete anything in there and use only pure scene and scene triggers for this setup.
jalexander319
posted this
08 August 2015
You should not need to edit it that script.
The log output you provided seems like it's coming from the "rules" section... Just in case, you should delete anything in there and use only pure scene and scene triggers for this setup.
I saw that too. But the only rules are ones that were already there by default and I unchecked the enable checkboxes. They are labeled as Sunrise, Sunset, and Vacation Mode. I will go ahead and delete them now. I rebooted my server, but no change.
jalexander319
posted this
08 August 2015
I deleted the rules, closed incontrol, renamed logfile.txt to logfileold.txt. I then restarted incontrol and shorted the water sensor. This is all that is in the log now...
8/8/2015 2:07:38 PM: doServiceTest()
8/8/2015 2:07:38 PM: Service appears to be running already. Will not attempt restart.
8/8/2015 2:07:44 PM: DirectConnect: New client connected from 127.0.0.1
8/8/2015 2:08:01 PM: SceneTrigger Sump Pump Alarm: Device Water Leak Alarm changed to 255. Running script activateScene.cs.
8/8/2015 2:08:01 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 2:08:01 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 2:08:01 PM: SceneTrigger Sump Pump Alarm: NodeIds is required Rule Data. Rule will not run.
8/8/2015 2:08:01 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 2:08:01 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 2:08:01 PM: SceneTrigger Sump Pump Alarm: NodeIds is required Rule Data. Rule will not run.
rscott
posted this
08 August 2015
I deleted the rules, closed incontrol, renamed logfile.txt to logfileold.txt. I then restarted incontrol and shorted the water sensor. This is all that is in the log now...
8/8/2015 2:07:38 PM: doServiceTest()
8/8/2015 2:07:38 PM: Service appears to be running already. Will not attempt restart.
8/8/2015 2:07:44 PM: DirectConnect: New client connected from 127.0.0.1
8/8/2015 2:08:01 PM: SceneTrigger Sump Pump Alarm: Device Water Leak Alarm changed to 255. Running script activateScene.cs.
8/8/2015 2:08:01 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 2:08:01 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 2:08:01 PM: SceneTrigger Sump Pump Alarm: NodeIds is required Rule Data. Rule will not run.
8/8/2015 2:08:01 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 2:08:01 PM: SceneTrigger Sump Pump Alarm: Script activateScene.cs requests targetNodes, but none were supplied.
8/8/2015 2:08:01 PM: SceneTrigger Sump Pump Alarm: NodeIds is required Rule Data. Rule will not run.
Which version of InControl are you on? Can you verify if it's the latest from www.incontrolha.com?
jalexander319
posted this
08 August 2015
Which version of InControl are you on? Can you verify if it's the latest from www.incontrolha.com?
4.0.5640.36169 is what is displayed in the title bar.
rscott
posted this
08 August 2015
It should work fine in that version. Here's how mine is setup:
On my garage door, I've got a reading called "Barrier state" - I clicked the icon next to it and created a new device named "Garage Barrier State" - I just left it as the default "levelDisplayer" type
http://snag.gy/KkjqN.jpg
I created a new scene with a pre-script using "EmailSceneStatusReport.cs."
http://snag.gy/XtNIl.jpg
I then created a trigger using that new device. Here's how it looks:
http://snag.gy/GEG2p.jpg
With nothing else in place, I can activate the scene by closing or opening the garage door and I'll get a generic email with nothing in it.
My logfile shows this indicating successful activation of the scene:
8/8/2015 2:11:56 PM: SceneTrigger Barrier State Change: Device Garage Barrier State changed to 0. Running script activateScene.cs.
jalexander319
posted this
08 August 2015
That sounds pretty much like what I did. No idea why it isn't working. I'm going to take a break from it for now and work on one of the many other projects I have going on, several of which are a higher priority for the wife. Thanks for your help.
