ZWave binding updates

chris · January 20, 2019, 1:12pm

Amongst other things. The format is processed against a number of different options to try and resolve strings, or string arrays (ie arrays that are passed in as strings rather than lists which is meant to be handled in ESH). However the other thing is that it also explicitly forces associations for the ZWave+ lifeline, or controller groups - ie it will not allow users to remove these associations.

shorty707 · January 20, 2019, 1:14pm

Hey
I added a temperature channel for the qubino din dimmers.
a deprecated tag was automatically added. never seen this before.
something I made wrong there?
cheers

chris · January 20, 2019, 1:14pm

This might be a bug in the database - I’ll have a look. Thanks for reporting.

rjduraocosta · January 20, 2019, 2:41pm

Hello to all,

Thank you very much for analysing my issues. The channel that is not even beeing updated and I use in my rules is the Sensor Power channel.
Concerning the update procedure I am following the steps to update openHAB for my system that is windows and for the binding I am following all the steps above in the first post of this thread so that I do not miss anything. I used PaperUI to configure the things, but also tried Habmin with the same results and pending messages when saving the parameters.

The log that I provided was from a fresh install of openHAB, where I just installed the zwave binding and added all the zwave things (in PaperUI), controller and fgr-222 modules.

Another issue that I found is that when I fresh install, or upgrade to 2.4 and I add the things, fgr-222 modules, there are some parameters that do not have the same values as they have when I am at 2.3.0. I always have to change them to the value that they where, it seems like that the confuguration stored inthe modules does not get well read by the binding (I don’t know if I am explaining this well) This does not happen on all modulesand I have seen this behaviour on PaperUI and Habmin:

Example 2.3.0 values :

image.png1074×637 47.1 KB
Example 2.4.0 values:

image.png1061×623 46.5 KB

Thanks again for you support and time for helping me on this.

chris · January 20, 2019, 2:43pm

Just to be clear, you are deleting all things and adding them back each time you swap between 2.3 and 2.4?

As suggested above, I would recommend that you use the 2.5 snapshot binding.

Tobi77 · January 20, 2019, 3:28pm

Someone using those famous Z-Wave Devolo MT2650 valves? I can’t transfer setpoint values…

mhilbush · January 20, 2019, 3:53pm

Here’s my take on what’s happening. I’m using node 7 as an example. If you think I have this wrong, please let me know what I might be misunderstanding.

For some reason, the device is not responding to the command to get Config Parameter 1. This is introducing a fair bit of delay in initializing node 7. The device also is not responding to the command to get config parameter 2, which is introducing even more delay in initializing node 7.

fgr222-1

At this point, the binding hasn’t read all the config parameters from the device (specifically, it has not read config parameter 13 from the device). Then you used Paper UI to make a config change, which sent updates for ALL the config parameters. However, at this point config parameter 13 in the binding is the default value of 1.

fgr222-2

The binding finally gave up trying to get config parameter 1. It then SETs config parameter 13 to the default, as you directed it to do when you used Paper UI to update the config. This is why, IMO, you should not use Paper UI to administer zwave devices!!!

I have no idea why the device is not responding to the GET for config parameters 1 and 2. Perhaps they are not supported by this version of the device firmware?

rjduraocosta · January 20, 2019, 3:54pm

I am doing exactly that. Deleting and adding all the things back each time I swap between 2.3 and 2.4.

Can you please point me out to where I can download the 2.5 snapshot binding? Are there any versions envolved? Sorry but I am new to these tests, I alway used stable releases and upgraded.

Thanks again for the support.

rjduraocosta · January 20, 2019, 3:57pm

Thanks for your reply. It makes perfect sence. Maybe I should look for an upgrade on the firmware?
All my devices firmware have the following firmware version:

mhilbush · January 20, 2019, 3:58pm

You could try updating the binding as described here. I’m not exactly sure if this will work on a release version, as I only use snapshot releases.

rjduraocosta · January 20, 2019, 5:43pm

Thanks for point me out for the link.

Another thing, I have been analysing diferences between binding configurations for the FGR-222 devices between 2.3.0 and 2.4.0 and the parameters 1 and 2 where not present in 2.3.0 just in 2.4.0. From what I have seen in manuals and the Fibaro website and the device database, my device supports those parameters. Jut to be sure if these parameters exist on the devices, Is there any other way to look at them? Another software to analyse the network other then PaperUi / Habmin?

Thanks.

mhilbush · January 20, 2019, 5:56pm

Good catch. Those two parameters were added in October in this change.

@mstormi I think you might’ve submitted the change to the FGR-222 database entry to add parameters 1 & 2. Was there a specific version of the device firmware that supported these two parameters? It looks like version 25.25 doesn’t supports these.

rjduraocosta · January 20, 2019, 7:15pm

I had another look at all the manuals and the github page with the adding of parameters 1 and 2 and noticed the following:

Regarding the firmware version, in the Fibaro website looking at the manual from the 25.25 version it states that it supports parameters 1 and 2 but they should have the following values:

Parameter 1 (0 or 2) and Parameter 2 (0 or 1):

Having a look at the github page and the included parameters I noticed the following:

image.png984×488 27.4 KB

github.com

openhab/org.openhab.binding.zwave/blob/5b58e52ffd2a07143d17c01b1c23bd37d9760376/ESH-INF/thing/fibaro/fgr222_24_24.xml

<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:thing="http://eclipse.org/smarthome/schemas/thing-description/v1.0.0"
  xsi:schemaLocation="http://eclipse.org/smarthome/schemas/thing-description/v1.0.0
                      http://eclipse.org/smarthome/schemas/thing-description/v1.0.0">

  <thing-type id="fibaro_fgr222_24_024" listed="false">
    <label>FGR222 Roller Shutter 2</label>
    <description><![CDATA[
Roller Shutter 2<br /><h1>Overview</h1><p>The device allows for controlling motors of roller blinds, awnings, venetian blinds, gates and others, which are single phase AC powered.</p> <br /><h2>Inclusion Information</h2><p>Fibaro Roller Shutter may be included into the Z-Wave network via the B-button or a push button connected to the S1 terminal. In addition, the module may be included in auto inclusion mode, by simply connecting the power supply.</p> <p>Automatic Z-Wave network inclusion:</p> <ol><li>Make sure the power supply is disconnected and a Roller Shutter is located within a direct Z-Wave network’s main controller communication range.</li> <li>Set the main controller into the learn mode (see main controllers operating manual).</li> <li>Connect the power supply to include the Roller Shutter in auto inclusion mode. 4) Fibaro Roller Shutter will be automatically detected and included into the Z-Wave network.</li> </ol><p>To disable the auto inclusion mode, press the B-button briefly, after connecting the module to the power supply.</p> <p>Manual Z-Wave network inclusion: </p> <ol><li>Connect the power supply.</li> <li>Set the main controller into the learn mode (see main controllers operating manual).</li> <li>Triple click the B-button or a push button connected to the S1 terminal.</li> <li>Fibaro Roller Shutter will be detected and included into the Z-Wave network.</li> </ol><br /><h2>Exclusion Information</h2><ol><li>Make sure the module is connected to the power supply.</li> <li>Set the main controller into the learn mode (see main controllers operating manual).</li> <li>Triple click the B-button or a push button connected to the S1 terminal.</li> </ol><br /><h2>Wakeup Information</h2><p>device has mains power, doesn't sleep.</p>
    ]]></description>
    <category>Blinds</category>

    <!-- CHANNEL DEFINITIONS -->
    <channels>
      <channel id="switch_binary" typeId="switch_binary">
        <label>Switch</label>
        <properties>
          <property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY</property>

This file has been truncated. show original

Parameter 2 has selectable options 0 and 2, not 0 and 1 like it is stated in the manual.

Sorry to bother you again with this, but could this also be something that is preventing parameters 1 and 2 to update?

Thanks.

sihui · January 20, 2019, 7:30pm

They do:

mhilbush · January 20, 2019, 7:38pm

But why is the device not responding to the GET on parameters 1 and 2?

sihui · January 20, 2019, 7:38pm

If that is the case (did not take a closer look) you need to update the database:

sihui · January 20, 2019, 7:40pm

See ~~below~~ above, I guess it is just the wrong option parameter

mhilbush · January 20, 2019, 7:40pm

It’s the GET that the device is not responding to. The range of values shouldn’t matter for the GET command; only the SET command should be an issue.

fgr222-1

rjduraocosta · January 20, 2019, 7:51pm

You are right it is the GET, so i do not know where to go from now.
Is the test with the snapshot version a definitive way to go? Another software to analyse the zwave network/devices?

Thanks

mhilbush · January 20, 2019, 7:56pm

I would suggest using the latest snapshot version as @chris suggested. And I would recommend using HABmin to manage the device configs, rather than Paper UI. IMO, these two things should resolve the majority of the issues you’re seeing.

As for parameters 1 & 2, I really don’t know why the device isn’t responding. In my experience, when a device doesn’t respond like that, it usually means the command/parameter is not supported. Maybe @chris has some better insight on this.