bottleneck
Choose style:

Author Topic: Error code on Multi Sensor  (Read 9605 times)

0 Members and 1 Guest are viewing this topic.

Offline itzfry

  • Newbie
  • *
  • Posts: 9
  • Thanks: 0
  • Registered : 01/03/2015
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Error code on Multi Sensor
« on: June 04, 2016, 08:46:34 am »
I know this isn't on the supported list but the functionality for motion, temp, and humidity work.  The LUX (which is what I want to use it for) does not.  Any idea of the error codes and if there is a work around to get this to work on the almond - perhaps using another device type, etc?

Error code after adding device:  user.info sysinit: WRITE ERR: ep 01 clus 0019 attr 0006 not supported^M

Model:  http://www.amazon.com/Aeon-Labs-Aeotec-Z-Wave-Multi-Sensor/dp/B00S68NUSW

Thanks in advance!

Offline Ashok

  • Securifi Staff
  • *
  • Posts: 2770
  • Thanks: 3
  • Registered : 25/07/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Error code on Multi Sensor
« Reply #1 on: June 04, 2016, 09:26:28 am »
@ itzfry,

May be through changing the parameters, we may be able to do something on this, try to send the log files.

Offline itzfry

  • Newbie
  • *
  • Posts: 9
  • Thanks: 0
  • Registered : 01/03/2015
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Error code on Multi Sensor
« Reply #2 on: June 05, 2016, 09:37:05 am »
Thanks.  I kept at it and got the device to add - all values are now reporting.  Partially, I may have been inpatient as it seems either a) the device only tests LUM % every x amount of minutes or b) the Almond is only processing it correctly with a delay. 

Before sending the logs, perhaps you could help with 2 questions:

A)  the device is ranging LUM % based on 0-200%.  Is this normal for devices?  Seems the rules engine maxs at 100%. I assume an issue.
B)  Regarding rules on sensors, how does the logic work - when something is above or below?  For things like temp and lum, it doesn't make sense for a single value but more of a range or > or < values..

I assume the answer of atleast the first question, will still require me to send logs but wanted to ask before doing so.

Thanks Secruifi Team!

Offline fillibar

  • Backer
  • *
  • Posts: 2060
  • Thanks: 4
  • Registered : 02/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Error code on Multi Sensor
« Reply #3 on: June 05, 2016, 11:22:33 am »
Is there a chance the value is going to 254? That would be an 8 bit value (pretty common).

As for the way it works... At this time it is only an exact value. This is a limitation of the current software, although there was mention lately about maybe the next version (or some upcoming one) will have >< support.
Almond 3 mesh handling the home.

Offline itzfry

  • Newbie
  • *
  • Posts: 9
  • Thanks: 0
  • Registered : 01/03/2015
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Error code on Multi Sensor
« Reply #4 on: June 05, 2016, 01:04:44 pm »
Thanks, perhaps - I will need to crank up directly light further to find out.  The problem is the rules only allow 0-100%, so there is the underlining issue.

If there is no range, I think there is no value in this sensor on the almond network.  Hitting an exact % of light will be extremely tough.  Same situation for temperature, humidity, etc too. 

Anyone else have any advice here?

 

Page created in 0.042 seconds with 18 queries.