For all of them?
Also the zwave github repo shows the correct channels:
<channel id="scene_number" typeId="scene_number"> <label>Scene Number</label> <properties> <property name="binding:*:DecimalType">COMMAND_CLASS_SCENE_ACTIVATION</property> </properties>
I have no idea what is going on …
Sorry, for all of what? I have two Fibaro Dimmer 2 in total. Just wanted to point out that all my ZWave devices seem to be working, except for SCENE_ACTIVATION in the one Dimmer 2 (have not set that up in the other Dimmer 2).
I recommend to do that for testing.
Downgrading your configuration is explicitly no supported if you used your old configuration backup or files…
I did not use my backup with the restore method. I actually set up all things by discovery or “by hand” and then used my old items / rules files to set everything up. Why would that cause a problem?
I tried it with my second Fibaro Dimmer 2, and it looks like it’s not working with that one either. When triple pressing the button, I get:
2019-10-19 09:16:19.387 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 20 00 49 84 06 1A 04 11 01 5E 20 86 72 26 5A 59 85 73 98 7A 56 70 31 32 8E 60 75 71 27 22 EF 2B AF 2019-10-19 09:16:19.407 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationUpdate, type=Request, dest=6, callback=132, payload=84 06 1A 04 11 01 5E 20 86 72 26 5A 59 85 73 98 7A 56 70 31 32 8E 60 75 71 27 22 EF 2B 2019-10-19 09:16:19.415 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationUpdate, type=Request, dest=6, callback=132, payload=84 06 1A 04 11 01 5E 20 86 72 26 5A 59 85 73 98 7A 56 70 31 32 8E 60 75 71 27 22 EF 2B 2019-10-19 09:16:19.418 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null 2019-10-19 09:16:19.420 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 0 2019-10-19 09:16:19.423 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: null 2019-10-19 09:16:19.430 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=ApplicationUpdate, type=Request, dest=6, callback=132, payload=84 06 1A 04 11 01 5E 20 86 72 26 5A 59 85 73 98 7A 56 70 31 32 8E 60 75 71 27 22 EF 2B 2019-10-19 09:16:19.434 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 6: Application update request. Node information received. Transaction null 2019-10-19 09:16:19.437 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 6: resetResendCount initComplete=true isDead=false 2019-10-19 09:16:19.443 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 6: Application update - no transaction. 2019-10-19 09:16:19.446 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty 2019-10-19 09:16:19.449 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
Somehow it worked with ZWave 2.5, but not with 2.4. What can I do?
Do the 2.5 versions of the binding work with openHAB 2.4?
I will check with my FGD this evening …
Is the current development version of the ZWave binding backward compatible, so can I install it on openHAB 2.4?
Quick update: I installed the latest ZWave 2.5.0 snapshot version, and it’s still not working. Really I have no clue why. It worked with openHAB 2.5.0 M1 with ZWave 2.5. I did not change anything to the devices configuration.
How did you install it? There is a manual install script for updating that also checks & adds new dependencies. More than just the zwave addon is needed.
Hm, I installed it by just putting the newest snapshot jar in the addons folder. I had to install a couple of dependencies myself (org.apache.servicemix.bundles.xstream and another one which I don’t remember, and then the installation of the snapshot version worked without problems. My devices seem to be working fine, just triple press / scene activation still doesn’t.
The manual steps are in the README here.
Okay, I checked this out today:
Triple clicking is only available on S2, as I only have S1 connected I can’t test, sorry.
Make sure you have Group 3 set to your controller and scenes are activated.
That’s fine. That is how we did it the last couple of years and should still be working fine.
What does “Group 3 set to your controller” mean?
I activated scenes in the FGD itself (parameter 28). Is there some other place to activate it? Also, I did have only S1 connected (don’t have a dual switch). BUT, it’s (or at least it was) actually enough to connect S1 to S2 and triple click on the one switch will trigger the scene activation.
That can be set by the user? I thought that on Z-Wave Plus devices only the Group 1 Lifeline was set to the controller. Am I mistaken? Chris could not think of any exceptions but perhaps this is one.
It was late yesterday and I picked the wrong device (Dimmer 1 instead of Dimmer 2).
No, for the Dimmer 2 you don’t need to set the association group to your controller, since a couple of month this is done by the binding.
For non Zwave plus devices you need to set the correct association group to the controller. This was the main culprit in support questions in this forum, so Chris decided to make it more user friendly and implemented an automated setting for the plus devices.
Do you guys have any hint on what I could do to try and fix it? There seems to be some kind of message when I triple press…
Is there a chance that factory resetting the ZWave devices and including/setting them up fresh might help?
I got it to work. I did have to set the association groups (I did that in HABmin). Somehow, all groups were empty. I guess when installing openHAB from scratch and not resetting the ZWave controller or something that stuff gets lost?
Is it enough to set the groups as seen in the screenshot below? Or do other groups have to be set as well (for everything to work correctly)?