Scene number not updated after zwave message received

[dominicdesu (Dominic Lerbs)]

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 (Dominic Lerbs)]

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 (Robert Schwarts)]

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 (Robert Schwarts)]

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 (Robert Schwarts)]

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 (Robert Schwarts)]

I guess this thread is dead…

[chris (Chris Jackson)]

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

@Schwartsenegger

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.

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?

@Schwartsenegger

As said my log is like the log provided by @dominicdesu:

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 (Robert Schwarts)]

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 (Robert Schwarts)]

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 (Chris Jackson)]

@Schwartsenegger

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

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

@Schwartsenegger

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.

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 (Robert Schwarts)]

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 (Chris Jackson)]

@Schwartsenegger

I can but please tell me how .

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…

@Schwartsenegger

I have sent them now by mail to you

Got it and uploaded it to the site.

@Schwartsenegger

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

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

[Schwartsenegger (Robert Schwarts)]

Ok, i will have a look.
Have to leave home now for an appointment but will try to check when i’m back.
I will let you know when I have registered.
Many thx for your support!
Robert

[Schwartsenegger (Robert Schwarts)]

i’m registered…

[chris (Chris Jackson)]

Thanks - I’ve updated your access… Any issues, just let me know…

[Schwartsenegger (Robert Schwarts)]

checked the MT2652 against the POPE009303 (Wall-C):
Association = both identical
Configuration = both identical except 1 parameter:
DEVOLO:

POP009303:

Command classes = a bit different (i highlight the diffs):
DEVOLO:

POP009303:

Only one line is marked on the POP009303 as this one is missing on the MT2652.
On the MT2652 i marked the versions when they differ and complete lines when they are missing on the POP009303.

All other settings on the product details lists are 1:1

What do you want me to do?
Update the MT2652 on the database site when needed and ‘assume’ the POP009303 is correct?
e.g. the Library types are different on the device list but the same when looking at the product details. I don’t know the impact of this parameter

Please let me know…

[chris (Chris Jackson)]

@Schwartsenegger

checked the MT2652 against the POPE009303 (Wall-C):

I’m not sure the POPE is relevant - we just need to get the MT2652 database entry consistent with the product definition on the zwave products site.

@Schwartsenegger

What do you want me to do?

Update the MT2652 on the database site when needed and ‘assume’ the POP009303 is correct?

To me, the best thing to do is to check the database entry on the OH database against the database entry for the MT2652 in the zwave products site. This is what’s important, and as I mentioned earlier, it shows that there are options missing for parameters 11 to 14 (unless I am mistaken?). Getting these options into the MT2652 entry will likely be the solution to your problem.

Don’t worry about command class versions - this isn’t relevant (although always nice if it’s correct, but the binding will use data directly from the device for this).

[Schwartsenegger (Robert Schwarts)]

adjusting the database site now.
I have 2 parameters which are in the file but not in the documentation (product details).
As i don’t know who added them (and why) i don’t want to delete them straight away…what is the best thing for me to do? (parameters 20 and 24)

i have updated the Endpoints too (to my best knowledge)…what do the different columns mean?

Maybe you can have a look to see if they look ok to you now?
I added the command class SCENE_ACTIVATION although it was not mentioned…remove it if you think this is not needed…

So all parameters are updated now. Let me know if i can do anything else…

[chris (Chris Jackson)]

Thanks. I’m tempted to remove these parameters as they can cause initialisation issues if they are wrong.

The different columns mean -:

• Basic - the class is linked to the basic class, so if a basic message is received, it’s treated as it if had come from this class
• NIF - the device reports it supports this in what’s called the Node Information Frame
• Sec - the class can work in secure mode
• Unsec - the class can work in unsecure mode

I’ll try and take a look over this later tonight.

Thanks

[Schwartsenegger (Robert Schwarts)]

Hi @chris,
I downloaded the latest SNAPSHOT and used it. Settings look ok now
I can see the 5 association groups now, which is ok, but it has problems in saving the associations. Sometimes it saves (and updates the node) correctly, but most of the time it is not updating anything. it just remains as is.
e.g.: i want to have my lifeline only to be the controller but i have now node13 and controller as association for the lifeline. Deleting the node13 is not possible so far. After each refresh it is back again.
Group D was empty. I added the controller and some nodes and after a couple of retries it saved them.

for the 4 groups i can now select the “Central scene to Gateway” which now gives me some figures on my scene_number channel. So it receives an update now. Very good!
It also gives me different numbers when i hold the button, which is also perfect.
Only thing is that they show as 1.0, 1.1, 1.2, 3.0, 3.1, 3.2, etc… instead of the 11, 12, 13, etc… but does not sound as a huge problem.
no time to continue right now but will do that asap.

Many thanks for your help so far and speak to soon.
HNY!!