[RELEASE] Aeotec Water Sensor 6

syepes · February 14, 2020, 1:00am

Features:

Availability of all device parameters
Driver automatic version check (every 7 days at noon)
Configurable logging levels
Added probe support (Needs more testing)

Status: Fully tested and working

Todo: Nothing for the moment

Download: GitHub

evanandmaryanne · February 27, 2020, 7:43pm

I have the dock and external probes so I will see how it acts.

I had previously found this code from @BorrisTheCat:

github.com

borristhecat/HUBITAT/blob/master/Aeon%20Water%20sensor%206.groovy

/* Edited for hubitat by borristhecat
*/

metadata {
  definition (name: "Aeon Water Sensor 6", namespace: "robertvandervoort", author: "Robert Vandervoort", ocfDeviceType: "x.com.st.d.sensor.moisture") {
    capability "Battery"
    capability "Power Source"
    capability "Configuration"
    capability "Notification"
    capability "Sensor"
    capability "Switch"
    capability "Shock Sensor"
    capability "Temperature Measurement"
    capability "Water Sensor"
    capability "Zw Multichannel"
    
	attribute "switch1", "enum", ["on", "off"]
	attribute "switch2", "enum", ["on", "off"]
    
	command "configure"

This file has been truncated. show original

For some reason though the probes don't seem to work properly.

evanandmaryanne · February 28, 2020, 12:16pm

@syepes I tested your code with the dock and external probes and probe 1 does not work.

syepes · February 28, 2020, 12:21pm

I don't personally have the probes, so that aspect is not really tested.
But I can try add support for them, could you please enable the "trace" logLevel and send me all the generated logs during 1h or 2h for the device.

DM or email me the logs directly, just not to flood the thread with tracing info.

syepes · February 29, 2020, 11:12am

@evanandmaryanne
Try the last driver version and set both Probe 1 Value and Probe 2 Value to Presence of water: 0xFF, Absence of water: 0x00, then Wakeup the device you the config is synced.

After this please test the probes and send me the logs in trace mode.

Regards,
Seb

BorrisTheCat · February 29, 2020, 12:06pm

Logs

@syepes you definitely deserve a @king for this driver its been sitting dumb at my place for ages

syepes · February 29, 2020, 12:26pm

@BorrisTheCat
Thanks for the logs I'll have a look at this later tonight and try to add a fully functional support for the probes.

planetix · February 29, 2020, 5:18pm

I have the probes and am using it with your driver from a week ago. When I test dunked each in a glass of water the sensor did trip wet/dry, it just didn't specify which probe, or that there are probes at all.

Would it be helpful if I tested the new driver and sent logs as well, or should I wait?

syepes · February 29, 2020, 6:34pm

@planetix
Thanks for the feedback.
Yes please, try the last version of the driver and send me the logs when triggering each of the probes independently.

Also note that what probe should be seen on the value of the variable probe

github.com

syepes/Hubitat/blob/master/Drivers/Aeotec/Aeotec Water Sensor 6.groovy#L183-L187


  result << createEvent(name: "probe", value: "1", descriptionText: "Detected water on probe 1", displayed: true)
} else if (cmd.size == 2) {
  result << createEvent(name: "probe", value: "2", descriptionText: "Detected water on probe 2", displayed: true)
} else if (cmd.size == 3) {
  result << createEvent(name: "probe", value: "3", descriptionText: "Detected water on both probes", displayed: true)

EAN · April 19, 2020, 4:50pm

@syepes you rock, thanks for making this available!!

Does version 1.0.3 work with the probes now?

syepes · April 19, 2020, 10:43pm

@EAN The last version does, note that I don't own them but someone has already tested it and it works.

EAN · April 25, 2020, 1:47pm

@syepes weird, i'm using version 1.0.3 but it's not working for me. Probe 1 logs an event only after i hit the configure button and probe 2 doesnt log an event at all. Also, even though i set the setting to Fahrenheit, it looks like it's still capturing temperature in Celsius.

pjam73 · April 26, 2020, 2:25am

Why are you checking cmd.size for values of 1, 2 or 3 when detecting which probe is wet - shouldn't it be cmd.scaledConfigurationValue? That would explain why people say the probe detection isn't working.

olliesshop · April 29, 2020, 7:26pm

I need some help on why my sensor does not show wet when the sensor is actually wet. I have the latest driver 1.0.3 and the other states seem to be working fine. Also, I'm not using a probe, just putting the sensor down in some water.

What's interesting is if I use the Generic Water Sensor driver, it works fine. It will show wet and also will also send an alert.

My assumption is I don't have it configured correctly, but I haven't been able to figure it out.

syepes · April 29, 2020, 10:24pm

Very strange, could you please follow the following steps and pm or attachment the full device logs.

set the logging to trace
click the refresh and configuration buttons
move the device (vibration) to Wake it up..
wait 1min
send me all the generated logs

Normally this should reset/force the reconfiguration, but I can check with the logs

olliesshop · April 29, 2020, 11:07pm

PM sent of the trace log.

walksonair · May 5, 2020, 4:41pm

I'm also having issues using the driver and seeing some errors in the logs...

java.lang.NullPointerException: Cannot invoke method multiply() on null object on line 490

java.lang.NullPointerException: Cannot invoke method toInteger() on null object on line 227 (parse)

syepes · May 5, 2020, 7:02pm

You are getting this error certainly because you have just switched from another driver and you have not established (saved) this drivers settings.

Doing the following should remove the errors:

Click the button: Preferences --> Save Preferences
Click the Refresh and configuration buttons

walksonair · May 5, 2020, 9:53pm

Thanks, I guess I didn't wait long enough to test it. Those messages no longer appear in the logs.

I do have another error when I tested it (undocked, just the sensor) in water and FWIW the status info on the device page does not get updated to WET:

dev:14092020-05-05 14:49:58.614 infoShock detected
dev:14092020-05-05 14:49:58.596 tracezwaveEvent(NotificationReport) - cmd: NotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:7, event:3, sequence:false, eventParametersLength:0, eventParameter:[])
dev:14092020-05-05 14:49:58.593 debugparse() - description: 'zw device: 4D, command: 7105, payload: 00 00 00 FF 07 03 00 , isMulticast: false'
dev:14092020-05-05 14:49:58.585 debugparse() - parsed to cmd: NotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:5, event:0, sequence:false, eventParametersLength:0, eventParameter:[]) with result: [['name':'water', 'value':'dry', 'descriptionText':'Sensor is dry'], ['name':'probe', 'value':'dry']]
dev:14092020-05-05 14:49:58.582 infoWater cleared
dev:14092020-05-05 14:49:58.580 tracezwaveEvent(NotificationReport) - cmd: NotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:5, event:0, sequence:false, eventParametersLength:0, eventParameter:[])
dev:14092020-05-05 14:49:58.577 debugparse() - description: 'zw device: 4D, command: 7105, payload: 00 00 00 FF 05 00 00 , isMulticast: false'
dev:14092020-05-05 14:49:45.322 errorgroovy.lang.MissingMethodException: No signature of method: hubitat.zwave.commands.notificationv3.NotificationReport.call() is applicable for argument types: (hubitat.zwave.commands.configurationv1.ConfigurationGet) values: [ConfigurationGet(parameterNumber:136)]
Possible solutions: wait(), any(), wait(long), any(groovy.lang.Closure), each(groovy.lang.Closure), grep() on line 285 (parse)
dev:14092020-05-05 14:49:45.311 debugparse() - parsed to cmd: NotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:7, event:3, sequence:false, eventParametersLength:0, eventParameter:[]) with result: [['name':'shock', 'value':'detected', 'descriptionText':'Shock detected']]
dev:14092020-05-05 14:49:45.289 infoShock detected
dev:14092020-05-05 14:49:45.284 tracezwaveEvent(NotificationReport) - cmd: NotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:7, event:3, sequence:false, eventParametersLength:0, eventParameter:[])
dev:14092020-05-05 14:49:45.279 debugparse() - description: 'zw device: 4D, command: 7105, payload: 00 00 00 FF 07 03 00 , isMulticast: false'
dev:14092020-05-05 14:49:45.265 infoWater detected

system · September 23, 2022, 3:44pm

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.