Switch state doesnt turn on for a ZWave Dimmer when the Dimmer is turned on

rossko57 · December 4, 2019, 11:27pm

@chris , that’s fine with me.

dastrix80 · December 4, 2019, 11:28pm

restoring the switch_binary channel I dont think will make a difference as in my working example, there are no items bound to it.

Maybe it will, I don’t know. But visually, it’s the only difference I can see between binding versions, despite Chris saying the binding has not changed.

chris · December 4, 2019, 11:33pm

If there is a bug, then shouldn’t we try and fix it? What the binding is doing is (as far as I understand) the correct implementation. A device should not provide both a switch channel and a dimmer channel - only a dimmer is required.

Sorry - it seems I now need to prove that I’m telling the truth?

So this is as I said earlier -:

This is clearly well before October when you said it was working.

dastrix80 · December 4, 2019, 11:37pm

Chris, if you have the means with a Aeotec Nano dimmer, test it using the binding I provided and 2.4.0.

That’s the only way I suspect, unless someone else can support my claims/issue

chris · December 4, 2019, 11:39pm

From the documentation -:

This states that the update of the channel information from the binding is delegated to the FRAMEWORK. ie what this means is that the binding updates channels, and the link from channels to items is handled by the openhab core. Not the binding.

Please see -:

rossko57 · December 4, 2019, 11:40pm

Fair enough - your earlier version of the same advice for reference (and the warning that switch_binary may be removed

chris · December 4, 2019, 11:41pm

Yes, and isn’t that saying the same thing as I’ve been saying here?

chris · December 4, 2019, 11:47pm

I should also add that I don’t know what version of the device we are talking about here. I don’t know therefore if the device definition in the database has changed. Maybe a new version has been added with a different definition (there are 3 versions of this device in the database I think). Or maybe a channel was removed - I’m just not sure at the moment, so I can’t say that it can be “added back” - it may not have been there and it may just be new definitions for an updated version of the device.

dastrix80 · December 4, 2019, 11:52pm

Working version ZW111 Aeotec Nano Dimmer (this version has worked since binding back in October 2019)

Not working version ZW111 Aeotec Nano Dimmer (this device was not known to ZWave prior to the update done in build #846)

chris · December 5, 2019, 8:17am

I just checked github, and the only change that has been made to this device in the past couple of months was 5 days ago when an additional type/ID was added.

Prior to that, a change was made in early October to change one of the labels -:

Even the original version of this device from September doesn’t have the switch channel included -:

github.com

openhab/org.openhab.binding.zwave/blob/30343d3e37eb5d6b513909dad4fc620c8d4c3fa2/src/main/resources/ESH-INF/thing/aeon/zw111_2_3.xml#L15


      
            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="aeon_zw111_02_003" listed="false">
              <label>ZW111 Nano Dimmer</label>
              <description><![CDATA[
          Nano Dimmer<br /><h1>Overview</h1><p>Aeotec Nano Dimmer is a Z-Wave Smart Dimmer specifically used to enable Z-Wave command and control (on/off/dim) of any wall switches. It can report immediate wattage consumption or kWh energy usage over a period of time. In the event of power failure, non-volatile memory retains all programmed information relating to the unit’s operating status. <br />It can connect to 2 external manual switches to control the load ON/OFF independently. Its surface has a pin socket, which can be used for connecting to the touch panel, so you can also use the touch panel to control the Nano Dimmer. <br />The Nano Dimmer is also a security Z-Wave plus device and supports Over The Air (OTA) feature for the products firmware upgrade.</p> <br /><h2>Inclusion Information</h2><p>Including Nano Dimmer as a non-secure device:</p> <p>If you want your Nano Dimmer as a non-secure device in your Z-Wave network, press the Action Button once on Nano Dimmer when you pair it to your gateway. If inclusion is successful, the green LED will be on for 2 seconds, and then return to a solid indication. If inclusion is unsuccessful, the red LED will be on for 2 seconds and then return to a colourful gradient.</p> <p>Including Nano Dimmer as a secure device:</p> <p>In order to take full advantage of the Nano Dimmer, you will want your Nano Dimmer as a security device that uses encrypted messages to communicate in your Z-wave network. A security enabled controller/ gateway (or Z-Wave Plus controller) is required.</p> <ol><li>Set your Z-Wave Plus controller into pairing mode.</li> <li>Press the Action Button 2 times within 1 second on the Nano Dimmer, the blue LED (secure indication) will blink to indicate the Nano Dimmer is entering into secure pairing mode.</li> <li>If the Nano Dimmer has been successfully added to your Z-Wave network, its RGB LED will be solid. If the pairing was unsuccessful, the red LED will be on for 2 seconds and then remain a colourful gradient, repeat the instructions above from step 1.</li> </ol><br /><h2>Exclusion Information</h2><p>Your Nano Dimmer can be removed from your Z-Wave network at any time. You’ll need to use your Z-Wave network’s main controller. To set your Z-Wave controller/gateway into removal mode, please refer to the respective section within your controller instruction manual.</p> <ol><li>Set your Z-Wave controller into removal mode.</li> <li>Press the Action Button on the Nano Dimmer or toggle the external manual switch 2 times in fast succession.</li> <li>If the Nano Dimmer has been successfully removed from your Z-Wave network, its RGB LED will remain colourful gradient. If the removal was unsuccessful, the RGB LED will still be solid (following the state of the output load), repeat the instructions above from step 1.</li> </ol>
              ]]></description>
              <category>WallSwitch</category>
          
              <!-- CHANNEL DEFINITIONS -->
              <channels>
                <channel id="switch_dimmer" typeId="switch_dimmer">
                  <label>Dimmer</label>
                  <properties>
                    <property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL,COMMAND_CLASS_BASIC</property>
                    <property name="binding:Command:OnOffType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
                  </properties>
                </channel>
                <channel id="scene_number" typeId="scene_number">
                  <label>Scene Number</label>

I don’t know what else I can do here - I’ve spent a lot of time trying to help, and I’m sorry that you don’t accept my answers. I’ve tried to present the documentation and history that shows where the various features you claim the binding should implement are really meant to be implemented, and I appreciate that this is not accepted by you, but I’m now at a bit of a loss as to what else to do. Maybe there was a new version added to the database that your system has swapped to using, but unfortunately I don’t have the time to continue to chase this one at the moment.

dastrix80 · December 5, 2019, 9:04am

Fair enough, well I can’t explain how this is all working just fine then on my system with the Switch item bound to the Dimmer channel.

dastrix80 · December 5, 2019, 9:22am

@Kai Are you able to comment on why a Switch item doesnt work in 2.4.0 Core for a ZWave device? It has a switch_dimmer channel, of which a dimmer itemtype and a switch itemtype is bound too. When the dimmer receives a command, such as 50, the switch item does NOT change to ON.

This is occuring on a 2.4.0 Stable system. It does not occur on another 2.4.0 Stable system I have with the identical Zwave device.

The only difference between the two is the physical hardware and the Zwave binding

Thanks!

rossko57 · December 5, 2019, 11:44am

I wonder if this may have to with your “working” Things being created under a different/older binding version.

sihui · December 5, 2019, 6:28pm

Then we cannot help you.
In my animated gif you can see how it works on a snapshot zwave binding with a Fibaro dimmer, my switch and dimmer items are bound to a switch_dimmer channel:

Switch FibFGD212_1_Sw (gRestore) { channel="zwave:device:uzb:node37:switch_dimmer1", autoupdate="false" }

Dimmer FibFGD212_1_Dim (gRestore) { channel="zwave:device:uzb:node37:switch_dimmer1", autoupdate="false" }

The switch turns on immediately after the dimmer percentage is set greater than zero.

dastrix80 · December 5, 2019, 7:27pm

That makes no sense. why should I have to upgrade to a non stable platform(2.5.0) to get a feature that works on 2.4.0?

dastrix80 · December 5, 2019, 7:27pm

Not following rossko57. What do you mean mate?

sihui · December 5, 2019, 7:38pm

If it works on different platforms with both the stable 2.4 we cannot help you either because you are the only one who is able to find the differences between them.
Check your config, check your parameters (especially parameter 80)

dastrix80 · December 5, 2019, 7:44pm

understood Sihui! Thanks

rossko57 · December 5, 2019, 8:26pm

Based on this, I presumed you had another system with ZW111 already configured and working as you expected. Those devices would necessarily have had their Things created under an older binding version.

It’s not really clear if you actually do have other, older ZW111 or if they are different versions from your new one, or if you have tried the “failing” new one on your older “working” system.

dastrix80 · December 5, 2019, 8:28pm

No mate, all ZW111s are the same.

I havent tried the new binding on the working system. I will do though!