Scene number not updated after zwave message received

dominicdesu · September 16, 2016, 5:23pm

Hi,

I have the following item defined:

Number  WallcLeftUp     {channel="zwave:device:a367f17a:node10:scene_number" }

When I press the button on my zwave device, I can see information in the log, but the item is not updated:

2016-09-16 19:17:40.999 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0A 00 04 00 0A 04 2B 01 0B FF 21
2016-09-16 19:17:41.007 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-09-16 19:17:41.010 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 04 00 0A 04 2B 01 0B FF 21
2016-09-16 19:17:41.013 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0A 00 04 00 0A 04 2B 01 0B FF 21
2016-09-16 19:17:41.015 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0A 04 2B 01 0B FF
2016-09-16 19:17:41.017 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 10: Application Command Request (ALIVE:DONE)
2016-09-16 19:17:41.018 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Starting initialisation from DONE
2016-09-16 19:17:41.019 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@10fe19c already registered
2016-09-16 19:17:41.020 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 10: Incoming command class SCENE_ACTIVATION
2016-09-16 19:17:41.021 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - Received Scene Activation for Node ID = 10
2016-09-16 19:17:41.022 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - Scene Activation Set
2016-09-16 19:17:41.023 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - Scene activation node from node 10: Scene 11, Time 255
2016-09-16 19:17:41.024 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2016-09-16 19:17:41.026 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2016-09-16 19:17:41.026 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = SCENE_ACTIVATION, value = 11
2016-09-16 19:17:41.030 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=10, callback=25, payload=0A 02 84 08
2016-09-16 19:17:41.033 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0A 04 2B 01 0B FF
2016-09-16 19:17:41.035 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=25, expected=SendData, cancelled=false      MISMATCH

What am I missing?

Thanks,
Dominic

chris · September 16, 2016, 5:30pm

Can you tell us what the device is please ;).

dominicdesu · September 16, 2016, 5:33pm

Oh, yes. It is a WALLC-S Wall Controller

dominicdesu · September 16, 2016, 5:35pm

In OH, it was working with items like this:

Switch  WallcLeftDown            { zwave="10:0:command=SCENE_ACTIVATION,scene=12,state=1" }

But if I understand it correctly, I now need a Number item which receives the scene number instead of a switch for every scene?

chris · September 16, 2016, 5:37pm

The device is sending the SCENE_ACTIVATION, but the channel is currently linked to the CENTRAL_SCENE. If there’s an option in the device to change what is sent, then that might be best since CENTRAL_SCENE is recommended, but otherwise we can easily add an extra channel to provide the choice.

Take a look in the manual, and if there’s no option I’ll update the database later tonight…

chris · September 16, 2016, 5:41pm

Actually, I will just add the channel - then you can choose…

dominicdesu · September 16, 2016, 6:07pm

Thanks!
There is also no CENTRAL_SCENE mentioned in the manual, therefore I guess no option to change.

chris · September 16, 2016, 6:17pm

There is in the manual I looked at ;). Its listed in the supported command classes in the manual anyway…

Maybe there are multiple versions…

dominicdesu · September 16, 2016, 6:35pm

Just doubled checked, you are right:
I just changed the “Action on Group” parameter from “Send Scenes” to “Central Scene to Gateway” and now it works!

2016-09-16 20:31:28.613 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 10: Node Status event - Node is ALIVE
2016-09-16 20:31:28.614 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 10: Incoming command class CENTRAL_SCENE
2016-09-16 20:31:28.616 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 10: Received CENTRAL_SCENE command V1
2016-09-16 20:31:28.617 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 10: Received scene 1 at time 0
2016-09-16 20:31:28.618 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2016-09-16 20:31:28.619 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2016-09-16 20:31:28.621 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = CENTRAL_SCENE, value = 1
2016-09-16 20:31:28.623 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating channel state zwave:device:a367f17a:node10:scene_number to 1 [DecimalType]

Thanks again for this incredibly fast support!

dominicdesu · September 16, 2016, 6:52pm

Although now a long-press doesn’t send a seperate scene id for start and end dimming anymore, but instead a lot of scene ids for a normal press. I guess I wait for the SCENE_ACTIVATION command to be added

Schwartsenegger · November 24, 2017, 11:18am

sorry to open an old conversation again but the initial problem is what i encounter too with the Devolo MT2652 switch. but unfortunately in OH2 cannot set / see the parameters that solved the issue for dominic.
So no “Action on Group” is available to change and also not the Central Scene to Gateway option.
Is this something to add for this device.

Schwartsenegger · November 30, 2017, 9:34am

Anybody still out there?
As said my log is like the log provided by @dominicdesu:

But what you would expect (like with this example of the Battery state) is the update statement:

10:33:15.477 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:a7598433:node12:battery-level to 72 [DecimalType]

Why is this not happening for the SCENE_ACTIVATION?

Schwartsenegger · December 1, 2017, 9:21am

Hi @chris ,
This is my node12 .XML (association part) which does not look good to me.

  <associationGroups>
    <entry>
      <int>1</int>
      <associationGroup>
        <index>1</index>
        <name>Life line</name>
        <profile1>0x0</profile1>
        <profile2>0x0</profile2>
        <commands>
          <commandClass>BATTERY</commandClass>
          <commandClass>DEVICE_RESET_LOCALLY</commandClass>
        </commands>
        <associations>
          <associationMember>
            <node>1</node>
            <endpoint>0</endpoint>
          </associationMember>
        </associations>
      </associationGroup>
    </entry>
    <entry>
      <int>2</int>
      <associationGroup>
        <index>2</index>
        <name>Group A</name>
        <profile1>0x0</profile1>
        <profile2>0x0</profile2>
        <commands>
          <commandClass>BASIC</commandClass>
        </commands>
        <associations>
          <associationMember>
            <node>1</node>
            <endpoint>0</endpoint>
          </associationMember>
        </associations>
      </associationGroup>
    </entry>
    <entry>
      <int>3</int>
      <associationGroup>
        <index>3</index>
        <name>Group B</name>
        <profile1>0x0</profile1>
        <profile2>0x0</profile2>
        <commands>
          <commandClass>BASIC</commandClass>
        </commands>
        <associations>
          <associationMember>
            <node>14</node>
            <endpoint>0</endpoint>
          </associationMember>
          <associationMember>
            <node>1</node>
            <endpoint>0</endpoint>
          </associationMember>
        </associations>
      </associationGroup>
    </entry>
    <entry>
      <int>4</int>
      <associationGroup>
        <index>4</index>
        <name>Group C</name>
        <profile1>0x0</profile1>
        <profile2>0x0</profile2>
        <commands>
          <commandClass>BASIC</commandClass>
        </commands>
        <associations>
          <associationMember>
            <node>13</node>
            <endpoint>0</endpoint>
          </associationMember>
          <associationMember>
            <node>14</node>
            <endpoint>0</endpoint>
          </associationMember>
          <associationMember>
            <node>1</node>
            <endpoint>0</endpoint>
          </associationMember>
        </associations>
      </associationGroup>
    </entry>
    <entry>
      <int>5</int>
      <associationGroup>
        <index>5</index>
        <name>Group D</name>
        <profile1>0x0</profile1>
        <profile2>0x0</profile2>
        <commands>
          <commandClass>BASIC</commandClass>
        </commands>
        <associations/>
      </associationGroup>
    </entry>
  </associationGroups>

This is my openhab Things screen for the MT2652:

You can see index 1 in the xml is the life line, but shows as what should be group A.
Easier to see is that group C (index 4) should be group D.
Or am i wrong here…?
I think the Devolo is exactly the same as the Z-Wave.me switch and i think the settings can be the same from what i read on the internet…
What do you think?

Schwartsenegger · December 29, 2017, 9:39am

I guess this thread is dead…

chris · December 29, 2017, 10:05am

Sorry - I missed this as I’ve been away for a while…

I don’t understand what you mean. The XML is downloaded directly from the device, so it’s unlikely that things are swapped around if that’s what you are getting at?

Please provide the actual log - not an image that is truncated on the right side where the log data is. Please also advise what version you are running.

Schwartsenegger · December 29, 2017, 10:52am

Hi Chris,
Happy to see that you are back.
My device is a Devolo MT2652 Scene switch:
version of the z-wave binding is (since this morning): org.openhab.binding.zwave-2.3.0-SNAPSHOT.jar

Recent log:

11:24:27.560 [DEBUG] [essage.ApplicationCommandMessageClass] - NODE 12: Application Command Request (ALIVE:DONE)
11:24:27.561 [DEBUG] [ialization.ZWaveNodeInitStageAdvancer] - NODE 12: Starting initialisation from DONE
11:24:27.562 [DEBUG] [ave.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@4fbac7c3 already registered
11:24:27.563 [DEBUG] [essage.ApplicationCommandMessageClass] - NODE 12: Incoming command class SCENE_ACTIVATION
11:24:27.564 [DEBUG] [l.commandclass.ZWaveBasicCommandClass] - Received Scene Activation for Node ID = 12
11:24:27.565 [DEBUG] [l.commandclass.ZWaveBasicCommandClass] - Scene Activation Set
11:24:27.566 [DEBUG] [l.commandclass.ZWaveBasicCommandClass] - Scene activation node from node 12: Scene 11, Time 255
11:24:27.566 [DEBUG] [ave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
11:24:27.567 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
11:24:27.568 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint = 0, command class = SCENE_ACTIVATION, value = 11
11:24:27.569 [DEBUG] [l.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=12, callback=107, payload=0C 02 84 08
11:24:27.570 [DEBUG] [l.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0C 04 2B 01 0B FF
11:24:27.571 [DEBUG] [l.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=107, expected=SendData, cancelled=false      MISMATCH
11:24:28.733 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 00 0C 02 84 07 7E
11:24:28.735 [DEBUG] [ave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
11:24:28.736 [DEBUG] [zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 04 00 0C 02 84 07 7E
11:24:28.737 [DEBUG] [ave.internal.protocol.ZWaveController] - Process Message = 01 08 00 04 00 0C 02 84 07 7E
11:24:28.738 [DEBUG] [ave.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0C 02 84 07
11:24:28.739 [DEBUG] [essage.ApplicationCommandMessageClass] - NODE 12: Application Command Request (ALIVE:DONE)

On other models with different branding you solved the issue by updating some files (sorry,i’m new to all this so don’t know how you call ‘the files’)

My device is generating SCENE_ACTIVATION but no updates on the scene_number channel: {channel=“zwave:device:1607ef0959a:node12:scene_number”}

The issue for dominicdesu (above) was solved by adjusting the “Action on Group” parameter to “Central scene to Gateway” but that option is not available for my device:

What you can also see in my previous pictures above is the XML i have and the difference between what i see in my console.
there should be a life line setting for my device (as you can see in the XML) but it is not available in my console. It seems to shift the settings. So life-line becomes group A, etc…
Group C has node 13 and 14 assigned to it in the XML but it is showing in my console as group/index 4.
As a result of this shifting group D is not shown at all in my console.
I hope it is a bit clearer now

Note: Dominicdesu has a WALLC-S Wall Controller which looks (from the outside) 1:1 as my Devolo MT2652.

Many thx in advance for your help!
Robert

Schwartsenegger · December 29, 2017, 10:55am

oh, yes…i’m running OH 2.2 Stable

items:

//############# Devolo Scene Switch ############
Switch	Devolo_Button			    "Devolo - Schakelaar"               <switch>	(gSchakelaars,gBenedenverdieping)	["Schakelaars"]	{channel="zwave:device:1607ef0959a:node12:scene_number"}
Number	Devolo_Switch_Battery	"MT2652 Batterij [%d %%]"           <battery>	(gSchakelaars,gBenedenverdieping)	["Schakelaars"]	{channel="zwave:device:1607ef0959a:node12:battery-level"}
Number	MyRemoteItem			    "MT2652 Scene number [%d]"                    (gSchakelaars,gBenedenverdieping) ["Schakelaars"] {channel="zwave:device:1607ef0959a:node12:scene_number"}

chris · December 29, 2017, 11:08am

The issue is that the database is configured for the CENTRAL_SCENE command class - not SCENE_ACTIVATION that you device is sending.

Understood…

Are you able to upload the user manual to the database site.

Also, please post the full XML here and we’ll take a look. Clearly there is something wrong in the database - the question be to work out if you have a different version, or if the database is just wrong for all versions…

Schwartsenegger · December 29, 2017, 11:31am

Hi @chris,
I can but please tell me how .
I can only leave a comment without attachments…
I have sent them now by mail to you (chris@cd-jackson.com)

Please also note that the manual coming from Devolo is very minimal.

Regards,
Robert

chris · December 29, 2017, 11:43am

There is a section for reference documents - youll only have the upload buttons if you are logged in and have the permision - I couldn’t find your name in the user list, so I’m guessing this might be the issue…

Got it and uploaded it to the site.

Yes - I think the word you’re looking for use “useless”!

Fortunately, there is more on the zwave products site. This indicates that the associations are wrong in the database (as you suspected). I’ve not checked the configuration properly - they looked similar, but can you do a systematic check to see if it’s the same?

Unfortunately… The docs there only list the CENTRAL_SCENE class in the list of supported classes - not the SCENE_ACTIVATION that your device seems to be sending.

I would guess (note - GUESS - docs aren’t so useful) that changing the config of parameters 11 to 14 might fix this.

Ahh— in the zwave products site, it shows extra options for these parameters and one of them is to use central scene - this is likely to be the answer.

So, if you are not registered on the database site, can you please register and I’ll give you access to update the data. Hopefully we should be able to get it going