Jump to content

Z-Wave light sensor


k5map

Recommended Posts

Just now, Scottmichaelj said:

Like a Aeotec MultiSensor6 with light lux? Might do a quick search and see if anything comes up.

I've been looking at that sensor but it appears there are 2 versions of the Aeotec... a Plus and non-Plus model.  Would appreciate hearing from anyone who has that sensor connected to their ISY.

Link to comment
Share on other sites

11 minutes ago, kissfan said:

I have two of these running.

https://www.monoprice.com/product?c_id=122&cp_id=12212&cs_id=1091804&p_id=15902

Questions?


Sent from my iPad using Tapatalk

1) Are you running v4.x of firmware on your ISY?

2) Does that sensor have the option of being powered or battery only?

3) How often can you poll it for light level?

Link to comment
Share on other sites

I've been looking at that sensor but it appears there are 2 versions of the Aeotec... a Plus and non-Plus model.  Would appreciate hearing from anyone who has that sensor connected to their ISY.

 I am not seeing two models. It’s just a single model, a plus and works on battery and powered via USB outlet. AFAICT many people are using it with their ISY on v4 and v5 of ISY FW with ZWave. I don’t have ZWave on my ISY, I use an RTI Remote ZWave control. Aeotec is a good company and they make solid products. 

https://aeotec.com/z-wave-sensor

 

Edit: you can poll the light level however you want. I have mine at 300ms - but the “polling” time will also reduce battery life if you go that route.

 

Here is the support documentation for the settings.

 

https://aeotec.freshdesk.com/support/solutions/articles/6000088070-gen5-6

Link to comment
Share on other sites

I have several Aeon Multisensor 6 sensors.

 

In my case, the ISY they are connected to is my production one (4.6.2) and they are all powered from the USB port and were included ‘securely’. In my case, I don’t poll. I have them set to report on change of values.

 

The only issues I’ve had are when someone knocks out the power brick supplying the usb power. Otherwise, I’m getting regular reports of lux, UV, Rh, temp and motion events. In my case, whenever any report comes in I fire a network event that posts the data to my ELK logging stack - so I can graph he data. I am even using one (in conjunction with my Weatherflow and thermostat data) to control an HVAC booster fan with good success.

 

Slowly, they are replacing CAO tags in my house.

 

Link to comment
Share on other sites

1) Are you running v4.x of firmware on your ISY?
2) Does that sensor have the option of being powered or battery only?
3) How often can you poll it for light level?


1-5.x
2-No, battery only
3-it sends to ISY, haven’t seen a poll option


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites

I don’t poll. I have them set to report on change of values.
 


How do you get them to poll? I am running mine on battery and they seem to drain pretty quickly. How can I set mine up to just send when the light lux is low? I changed parameter 300 to 3mins.
Link to comment
Share on other sites

Mine are on power, but it’s all described in the main tech guide...

You probably want to consider 40 set to 1 (to enable selective reporting), set the reporting thresholds with 41 thru 45.

Parameter 111 controls interval sending - on power it’s configurable to the second - on battery the smallest interval is an hour.

I don’t see a parameter 300 in the manual - it goes up to 255... It’s a two byte hex number, so I don’t think there is even a parameter 300...

Link to comment
Share on other sites

The latest 1.10 firmware is needed to get good reporting on battery. I set 40 to 1 and 41 to 5, and this is from
Chris @ Aeotec:

Hmm, on battery power, threshold reports are very slow. My suggestion are these right afterwards:


101 - 4 byte - 0
102 - 4 byte - 0
103 - 4 byte - 0
111 - 4 byte - 240
112 - 4 byte - 240
113 - 4 byte - 240

The threshold checks are based off parameter 111-113 for checking, so these are my suggested settings with threshold reports mainly.

This is because timed checks for thresholds (param 40-43) are based on Parameter 111-113 set times when on battery power.

But on USB power, parameter 40-43 ignore all set timings and will check every 10 seconds.

These are the 2 distinct differences between USB power and battery power over the threshold reports.


Sent from my Pixel 2 XL using Tapatalk

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...