OH2 Z-Wave refactoring and testing... and SECURITY

Just for information, I solved my problem with my Aeon Labs Smart Energy Switch (DSC06). To get a feedback in openHAB from an action to the local switch button, it is necessary to change the value of the parameter 80 (automatic notifications). It is set by default to “Nothing”. I switched it to “Basic CC Report” and now it works well as I expected.

1 Like

Ok I come back to my problem to setup the ST814 using Paper UI.
As a reminder, I am trying to set the parameter 6 “Auto report time” to 60. After monitoring the REST call in Firefox, I can confirm that that the call is done with config_6_2 set to 0 rather than 60 entered into the field !

So it looks like a bug either in Paper UI or the way the parameter is defined by the binding:

      <parameter name="config_6_2" type="integer" groupName="configuration"
                 min="0" max="1439">
        <label>6: Auto report time</label>
        <description><![CDATA[
Sets the time interval when a sensor report is sent<br /><h1>Overview</h1><p>0 = Disable</p> <p>1 min - 1439 min = Auto report periodically</p>
        ]]></description>
        <default>0</default>
        <options>
          <option value="0">Disable</option>
        </options>
        <limitToOptions>false</limitToOptions>
</parameter>

Could it be a problem relative to options + limitToOptions set to false ?

@mhilbush : did you already set this parameter using Paper UI ?

PS: I will now try using HABmin.

Running for 3 hrs now, I haven’t seen any.
Thanks.

1 Like

Sorry to step in here…
I have a ST814 as well. My problem with it is, that after a coupple of months running, it reports battery level 0. But the device itself does not indicate there is lack of battery. Have you had the same experience?

Well, it might be a bug related to this, but if so, it’s in PaperUI. The definition looks fine - we are saying that there is an option 0, but you are not limited to this, and you can set any value from 0 to 1439.

I think the definition is ok and my guess is there’s a PaperUI bug. What happens if you set the value to 1500 - PaperUI shouldn’t allow you to click the save button which would tell me that it’s correctly defining the parameter in the UI, but then possibly some checks at the end are somehow selecting the options again. (but that’s a guess).

I want to offer a tip to help others if they are trying to include a lock and it is failing to include securely. I know that every guide says to bring the lock close to the zwave controller when doing the secure inclusion. I tried uncusscessfully to include a Kwikset 914TRL lock about 20 times that was placed 12" away from the z-stick in my raspberry pi. I tried everything: fresh batteries, locked, unlocked, high power, network wide, low power, standing on one foot while turning in a circle. :wink:
The solution was to hold the lock as close as physically possible to the zstick while doing the secure inclusion. Holding the lock right up against the zstick worked for me the first time.
I hope this can save some frustration for someone.

I use HABmin to make config changes to my zwave devices. If you use HABmin it should properly set the autoreport time to 60.

Yes, with HABmin it works. But not with Paper UI. Apparently the bug is known and issue already declared.

I have now added a Fibaro FGMS 001 and I encounter 2 difficulties:

  1. Battery level is not updated
  2. Sensor luminance is either 0 or 1

Here is how are defined my channels:

Number BatterieDetecteur2Salon "Batterie détecteur salon Fibaro [%d %%]" <battery> (GBatterie) { channel="zwave:fibaro_fgms001_00_000:controller:node8:battery-level" }

Number LuminositeSalon "Luminosité salon [%d lux]" <none> (SalleSejour) { channel="zwave:fibaro_fgms001_00_000:controller:node8:sensor_luminance" }

What is the unit of the luminance ? With my Vera, it was a value in lux.

Here’s how I have my channels defined.

Number Living_Luminance        "Living Luminance [%.0f]"     <light>       (gFF_Living,gSensor,gLuminance)     { channel="zwave:device:zstick:node37:sensor_luminance" }
Number Living_BatteryLevel     "Living Battery [%.0f %%]"    <battery>     (gBattery)                          { channel="zwave:device:zstick:node37:battery-level" }

Should be lux. These are typical values I see.

2018-08-19 14:44:36.557 [vent.ItemStateChangedEvent] - Living_Luminance changed from 39 to 70
2018-08-19 15:14:26.112 [vent.ItemStateChangedEvent] - Living_Luminance changed from 70 to 76
2018-08-19 15:44:07.234 [vent.ItemStateChangedEvent] - Living_Luminance changed from 76 to 85
2018-08-19 15:44:15.137 [vent.ItemStateChangedEvent] - Living_Luminance changed from 85 to 88
2018-08-19 16:14:05.194 [vent.ItemStateChangedEvent] - Living_Luminance changed from 88 to 52
2018-08-19 16:43:56.004 [vent.ItemStateChangedEvent] - Living_Luminance changed from 52 to 59
2018-08-19 17:13:46.609 [vent.ItemStateChangedEvent] - Living_Luminance changed from 59 to 28
2018-08-19 17:43:37.379 [vent.ItemStateChangedEvent] - Living_Luminance changed from 28 to 26
2018-08-19 18:13:28.645 [vent.ItemStateChangedEvent] - Living_Luminance changed from 26 to 16
2018-08-19 18:43:19.857 [vent.ItemStateChangedEvent] - Living_Luminance changed from 16 to 5
2018-08-19 19:13:12.776 [vent.ItemStateChangedEvent] - Living_Luminance changed from 5 to 1
2018-08-19 19:42:53.774 [vent.ItemStateChangedEvent] - Living_Luminance changed from 1 to 0
2018-08-20 06:39:24.730 [vent.ItemStateChangedEvent] - Living_Luminance changed from 0 to 1
2018-08-20 07:09:16.434 [vent.ItemStateChangedEvent] - Living_Luminance changed from 1 to 3
2018-08-20 07:38:58.467 [vent.ItemStateChangedEvent] - Living_Luminance changed from 3 to 8
2018-08-20 08:08:58.790 [vent.ItemStateChangedEvent] - Living_Luminance changed from 8 to 5
2018-08-20 08:38:49.581 [vent.ItemStateChangedEvent] - Living_Luminance changed from 5 to 10
2018-08-20 09:08:38.366 [vent.ItemStateChangedEvent] - Living_Luminance changed from 10 to 15
2018-08-20 09:38:27.537 [vent.ItemStateChangedEvent] - Living_Luminance changed from 15 to 45
2018-08-20 10:08:19.623 [vent.ItemStateChangedEvent] - Living_Luminance changed from 45 to 30
2018-08-20 10:38:11.839 [vent.ItemStateChangedEvent] - Living_Luminance changed from 30 to 17
2018-08-20 11:08:04.040 [vent.ItemStateChangedEvent] - Living_Luminance changed from 17 to 88
2018-08-20 11:37:44.882 [vent.ItemStateChangedEvent] - Living_Luminance changed from 88 to 67
2018-08-20 12:07:45.422 [vent.ItemStateChangedEvent] - Living_Luminance changed from 67 to 46
2018-08-20 12:37:36.916 [vent.ItemStateChangedEvent] - Living_Luminance changed from 46 to 94
2018-08-20 13:07:28.585 [vent.ItemStateChangedEvent] - Living_Luminance changed from 94 to 113
2018-08-20 13:37:09.782 [vent.ItemStateChangedEvent] - Living_Luminance changed from 113 to 33
2018-08-20 13:37:19.564 [vent.ItemStateChangedEvent] - Living_Luminance changed from 33 to 32
2018-08-20 14:07:11.617 [vent.ItemStateChangedEvent] - Living_Luminance changed from 32 to 27
2018-08-20 14:37:01.934 [vent.ItemStateChangedEvent] - Living_Luminance changed from 27 to 22
2018-08-20 15:06:51.845 [vent.ItemStateChangedEvent] - Living_Luminance changed from 22 to 52
2018-08-20 15:36:42.087 [vent.ItemStateChangedEvent] - Living_Luminance changed from 52 to 22

@mhilbush: what’s the version of your FGMS001 ? Mine is 2.7.
I tried to change the pattern for the luminance item to match yours. But the value was not yet updated since my restart.

@chris : are you sing QuantityType for the luminance ?

No - there are only 2 units possible (if “units” is the right term). The sensor can either report in percent, or in lux - currently the binding passes the value directly through to the system.

I can easily add QuantityType, and that’s fine if it’s lux, but if it’s percent, I’m not sure it can be converted as it’s not a “unit”. I guess I could return QuantityType if the sensor is returning lux, and a normal DecimalType, or something unitless if it’s not.

I’m open to suggestions though…

I finally got a battery level. Temperature is retrieved too.

For the luminance, how can I know if the value is in percent or in lux ? Why is my value so small ? The biggest value I was able to get is 2 !

Not so easily I guess - what does the debug log show? I think it should show the scale - 0 is percent, 1 is lux.

Either way though, 2 is a low value so maybe there’s something else wrong…

Both of mine are running firmware v3.2.

I don’t see anywhere to set the unit for luminance. Mine only seem to report in lux.

I hope this isn’t a stupid suggestion, but why not just put it under a lamp and see if it shows a value above 100?

Wouldn’t it be somewhat confusing to measure luminance in percent? What would 100% luminance actually mean? :thinking:

I guess it would mean 100% of the highest value that the sensor is able to read… The light sensor I’m using (Aeon DSB05) measures up to 1000 lux, so I guess I could as well divide the reading by 10 and call it percent. But I have to admit lux makes more sense :sunglasses:

I’ve been using various FGMS for ages, and they have only ever been delivering values in lux. Manual also say lux. @lolodomo you possibly need to reset your device.

Finally, my value increased this morning until 106. So that is a value in lux.

2018-08-21 01:24:17.035 [vent.ItemStateChangedEvent] - Luminosite2Salon changed from NULL to 2
2018-08-21 08:11:45.170 [vent.ItemStateChangedEvent] - Luminosite2Salon changed from 2 to 45
2018-08-21 08:36:13.886 [vent.ItemStateChangedEvent] - Luminosite2Salon changed from 45 to 73
2018-08-21 08:36:33.563 [vent.ItemStateChangedEvent] - Luminosite2Salon changed from 73 to 74
2018-08-21 08:37:17.351 [vent.ItemStateChangedEvent] - Luminosite2Salon changed from 74 to 75
2018-08-21 08:38:05.503 [vent.ItemStateChangedEvent] - Luminosite2Salon changed from 75 to 76
2018-08-21 08:39:02.418 [vent.ItemStateChangedEvent] - Luminosite2Salon changed from 76 to 77
2018-08-21 09:15:34.159 [vent.ItemStateChangedEvent] - Luminosite2Salon changed from 77 to 106

So the binding is very probably working as expected.
What I don’t understand is why I got 4 increases of 1 lux in 4 minutes while my parameter 40 Illumination Report Theshold is set to 25. My understanding of this setting is that I should get a new value only when there is at least 25 lux between 2 measures.

It is strange that yesterday during evening the luminance was not increased when I switched lights on and off.