Support for Everspring ST812 flood sensor

[Szymon Kobalczyk]

I have an everspring ST812 mounted in our boilde room. It will be associated with main water valve actuator so this should operate witout controller.
However I want to get some notifications or trigger other actions via openHAB.

From docs at http://www.homeseer.com/pdfs/Everspring/ST812.pdf
it uses ALARM_REPORT and SENSOR ALARM REPORT that I didn't found supported on Z-wave binding page.

Hope someone could add support for this sensor.

Thanks,
-Szymon

[Chris Jackson]

I suspect that HomeSeer is just naming things differently - they’ve added REPORT to the class name, but this is a function of the individual classes. So, the ALARM, and SENSOR_ALARM classes are supported and you should be able to use this device (I don’t have one, but others do so ought to be able to help).

Chris

[Roy Svendsen]

I also have one, but still didn't manage. Tryed both alarm and sensor_alarm.

I'll try again since im also want this to work.

What I see is when I press the button on the sensor i report both battery ans alarm/sensor_alarm, but I only manage to get battery out so far.

Look again tomorrow or the next day after.

Roy

Sendt fra min Sony Xperia™-smarttelefon

---- Chris Jackson skrev ----

I suspect that HomeSeer is just naming things differently - they’ve added REPORT to the class name, but this is a function of the individual classes. So, the ALARM, and SENSOR_ALARM classes are supported and you should be able to use this device (I don’t have one, but others do so ought to be able to help).

Chris

--
You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

[Szymon Kobalczyk]

I managed to get it working. In that doc I noticed that it has two association groups. It sends the mentioned alarm commands to 1st one, but can also send BASIC command to the 2nd group. In my network I have Vera as primary controller and openHAB is listening via Z-Stick. So I assigned the Z-Stick to 2nd group.

Then I configured this item:

Switch Flood_Alarm_Event "Flood_Sensor" (gFF_Laundry) { zwave="11:respond_to_basic=true,refresh_interval=300" }

I'm not sure these additional options are strictly necessary so maybe you can confirm this.

Of another note, the node wasn't recognized in habmin although device is found in database. Perhaps thats normal in battery operated nodes (I have only this one and a Duwi remote).

-Szymon

[Chris Jackson]

Of another note, the node wasn't recognized in habmin although device is found in database. Perhaps thats normal in battery operated nodes (I have only this one and a Duwi remote). 

No - battery devices will show up fine in HABmin as well (once initialised - which can take a little longer than mains devices)... The most likely reason is that Fibaro use multiple sets of codes to identify their products and your device is probably just not in the database. Can you post the Type/Id that HABmin is reporting and I'll add it...

Cheers

Chris

[Szymon Kobalczyk]

Chris,
Actually the flood sensor is manufactured by Everspring not Fibaro. HABmin shows UNKNOWN for manufacturer id, device id, and device type.

But speaking of Fibaro I actually have two older modules that weren't recognized from database:
Roller Shutter control ID=102, Type=300, Version 1.2
Switch ID=102, Type=200, Version 1.2

I'd appreciate if you could add them.

[Chris Jackson]

On Monday, 8 December 2014 11:04:34 UTC, Szymon Kobalczyk wrote:

Chris,
Actually the flood sensor is manufactured by Everspring not Fibaro. HABmin shows UNKNOWN for manufacturer id, device id, and device type.

Sorry - I keep thinking about Fibaro... 

Given that manufacturer is showing UNKNOWN, this means that the device hasn't completed its initialisation, so until this happens HABmin won't show anything. Depending on how the device is configured, this will take a few hours. However, if it's not configured to wake, then you'll need to do this manually (if it's anything like the Everspring temp sensors, there's a button on the back by the battery that you press 3 times). You may also need to configure the wakeup class if it's not set...

 

But speaking of Fibaro I actually have two older modules that weren't recognized from database:
Roller Shutter control ID=102, Type=300, Version 1.2
Switch ID=102, Type=200, Version 1.2

I'd appreciate if you could add them.

No probs - I'll put them in tonight.

Chris

 

[Roy Svendsen]

Everspring ST812 Flood Sensor

Manufacturer 60

Device ID 1

Device version b

Device type 3

It's already in the product.xml file, but its not listed with any config file, no information, For me I can only see neighbor status and information under the node in devices in habmin.

Roy

--

You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

--

--
Roy Svendsen

[Chris Jackson]

Are you sure about this information? It looks different to what I see in other places (e.g. pepper1)… Has this come from HABmin, or is HABmin still showing all this as UNKNOWN?  If it’s still unknown, then it means that the device hasn’t initialised properly yet, and openhab hasn’t got all the information it needs to be able to present the information to you. In this case, you will only get neighbour status and information - not all the configuration type stuff…

However, as you also point out, there’s no config file for this device. Do you have a manual that has configuration? If so, can yo find it online? In the pepper1 database, it shows 2 versions - one has no configuration, the other has 1 parameter and some associations… If we can work out what’s the right one, I can add this easily.

Chris

[Roy Svendsen]

Hi Chris,

We are 2 people who are struggling with this, mine is already at node status done. 

it looks like this one, http://www.pepper1.net/zwavedb/device/123. even this is stated as US version. 

the other one is named old. 

Roy

[Szymon Kobalczyk]

Hi Chris,

For me the node is still not recognized. Curently reported as dead. Earlier I tried pressing the test three times button as you mentiond but only got the battery level to show. Vera shows this sensor correctly so I wonder if this is because I have openHAB runing via Z-Stick as secondary controller. Roy - is openHAB your main controller?

Here is the manual again: http://www.homeseer.com/pdfs/Everspring/ST812.pdf

Noticed in 3-2 that it mentions about Wakeup Command Class. Perhaps I need to configure it to send updates to Z-Stick.

You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/uOGGVq-mTWU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.

[Chris Jackson]

Roy,

Please can you confirm that the information you gave me is correct as my point is that it's inconsistent with the pepper1 database that you also pointed me at. I think you've transposed some numbers - you've said version 'B', but I suspect that this is really the type? I just want to confirm this before I put it into the database.

Szymon,

You probably need to wake the device up manually. It's quite normal for devices to come configured not to wake up. So, you normally need to press the button on the back 3 times (I don't know this device, but I think this is the same as other Everspring devices). This will wake it up, and get it to complete initialisation if it's close enough to the controller to communicate - you may need to do this a couple of times - especially for the current version of the binding.  Once it completes, and you have the manufacturer etc showing, then you may need to initialise the wakeup command class - when you do this, HABmin will automatically set the node to the controller so that further updates are sent to the controller, but you need to get it initialised first.

Cheers

Chris

[Roy Svendsen]

Chris, do you want the nodexx.xml file from openhab to see the infromation it sends out or is there other thing you want?

Roy

--

You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

--

--
Roy Svendsen

[Chris Jackson]

Hi Roy,

If you send the XML, then this would be perfect.

Cheers

Chris

[Roy Svendsen]

Added is the XML file generated when included the Flood sensor.

Roy

[Chris Jackson]

Thanks - I’ll update this tonight.

Chris

<node19.xml>

[Roy Svendsen]

Thanks Chris, 

I just downloaded the last snapshot from github and ST812 responded as it should.

When wet Openhab report

on Basic  99 

on sensor_alarm , alarm_type 5 report 255

 

In short both basic and sensor alarm can be used and working. :)

Roy

[Kirk Junker]

Hi Roy. Would you mind posting your item configuration for the ST812? I have one as well and am using the zwave 1.7 snapshot from 2 weeks ago. I get battery updates from the ST812, but no alarm notification in my tests. I've tried with endpoints and without and there's nothing in the zwave log to indicate a message was even received from that node. I suspect I have a bad sensor, but want to give it a go based on your item configuration (and or any tricks/tips you might have).

-Kirk

[Kirk Junker]

In case anyone else struggles with the configuration for the ST812, the solution is to make sure you specify respond_to_basic=true in your binding configuration.