more G-Labs products

Author Topic: r503; z-wave parameters not correct  (Read 3908 times)

December 03, 2015, 10:46:47 PM
Reply #15

Gene

  • *****
  • Information
  • Administrator
  • Posts: 1472
  • Tangible is the future!
    • Yet Another Programmer
which of these is wrong ?

December 04, 2015, 10:48:44 AM
Reply #16

pim555

  • ****
  • Information
  • Sr. Member
  • Posts: 143
Hi Gene,

In the visualization, tamper alarm is shown (see attached). This is not correct as this sensor does not have a tamper alarm. Not sure which value you pick up to display as tamper alarm?

Cheers
Pim.

December 04, 2015, 11:20:24 AM
Reply #17

Gene

  • *****
  • Information
  • Administrator
  • Posts: 1472
  • Tangible is the future!
    • Yet Another Programmer
the tamper field is probably coming from previous release bug. You can remove it by clicking the button on the right, in the configure->groups module list.

g.

December 04, 2015, 01:11:29 PM
Reply #18

pim555

  • ****
  • Information
  • Sr. Member
  • Posts: 143
Cool, wasn't aware that historically introduced parameters are kept. Is that on purpose?

I would assume that you can query a device for its capabilities and based on that populate the parameter list.

Cheers
Pim

January 07, 2016, 08:46:54 PM
Reply #19

kevin1

  • *****
  • Information
  • Hero Member
  • Posts: 330
Sorry if I am bringing off topic to this discussion, but I am seeing tamper alarms on my door and motion sensors (they do have this capability but I'm seeing tamper when they have not been opened up).  I have erased the values using the config-group but they return after some time.  Is the decoding of this data from node part of pepper database, or is it done in other HG code?