Add start stop channel for Aeotec swipe #1135

cdjackson · 2019-02-16T09:26:51Z

This adds a new switch_startstop channel and makes it available for the ZW130 swipe commands.
Closes #598
Signed-off-by: Chris Jackson [email protected]

Signed-off-by: Chris Jackson <[email protected]>

dastrix80 · 2019-02-16T12:22:40Z

Thanks Chris !

cdjackson · 2019-02-16T12:29:13Z

Let me know how it works in real life (ie with rules etc). I’ve only given it a basic test here since I’m not using the ZW130 in anger...

…

On 16 Feb 2019, at 12:22, dastrix80 ***@***.***> wrote: Thanks Chris ! — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#1135 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA_kQ4EL_q4tYEaNSWUK4kE_wyJOCXDVks5vN_gQgaJpZM4a-5D0>.

dastrix80 · 2019-02-16T12:46:31Z

Shall do soon as i work out where the jar file is :) i have 4 of these so they will get a good workout

mhilbush · 2019-02-18T01:07:41Z

I couldn't get the Wallmote Quad to emit anything until I set config parameter 3 (Button slide) to Enable AND config parameter 4 (Notification report) to Central scene and report. In my testing, just setting parameter 3 alone was not sufficient.

With both those parameters set, the device would emit a CONFIGURATION_REPORT for parameters 9 and 10.

I might have this backwards, but

if value9 < value10
    // Swipe UP
else if value9 > value10
    // Swipe DOWN

This HA post seems to say the same thing.

If this is the way it's supposed to work, it seems pretty odd to me.

@cdjackson Does this match was you were told by Aeotec?

dastrix80 · 2019-02-18T01:32:36Z

Interesting. Ill turn the Central Scene & Report back on and do some testing.

mhilbush · 2019-02-18T01:39:41Z

BTW, I'm guessing those values returned in the configuration report are the location of my finger on the sensor when I start and stop the swipe.

I find this whole thing rather confusing. The Wallmote Quad has 4 "zones", but there's nothing in these configuration reports that would indicate what "zone" is being swiped (other than a way to possibly derive that from the values).

I'm very curious to know what Aeotec says about this functionality.

dastrix80 · 2019-02-18T01:51:23Z

switch_startstop1
switch_startstop2
switch_startstop3
switch_startstop4

Each 3,5,7,9 values for the Association Groups gets set to LifeLine for MultiLevel.

I would then imagine you get different numerical values on each swipe for each zone?

mhilbush · 2019-02-18T01:53:28Z

Possibly. I didn't try setting any of those associations. I can try that tomorrow.

dastrix80 · 2019-02-18T01:57:11Z

Yep, set all those associations. Chris mentioned this to me via email. I'll test this in a few hours and see how I go with report being added to parameter 4 and report back.

PS: do you have linked channels for your new string item? I do not.

cdjackson · 2019-02-18T09:01:07Z

Yes, the configuration parameters report the location and direction. I don't plan to try and support that (it's very non-standard!) so I would suggest to disable the config reports. You MUST have the other associations set though.

dastrix80 · 2019-02-18T10:14:58Z

Hi Chris

Ive done this and the string item reports NULL. I also see no linked channels to this new string item. Nor the channel visible in Habmin

Cheers

cdjackson · 2019-02-18T10:36:50Z

I don’t understand. If there are no channels, then there can’t be any items. Are you using the latest binding? Did you delete the thing and add it back again so it updates the definition?

…

Sent from my iPhone

On 18 Feb 2019, at 10:14, dastrix80 ***@***.***> wrote: Hi Chris Ive done this and the string item reports NULL. I also see no linked channels to this new string item. Nor the channel visible in Habmin Cheers — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

dastrix80 · 2019-02-18T19:42:53Z

Hi Chris, no i didnt delete it. You never mentioned I had to. I have done that now and I can see the channels.

cdjackson · 2019-02-18T19:43:48Z

Sorry - this is always required when the thing type is updated as ESH doesn’t perform any update of definitions.

…

On 18 Feb 2019, at 19:42, dastrix80 ***@***.***> wrote: Hi Chris, no i didnt delete it. You never mentioned I had to. I have done that now and I can see the channels. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1135 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA_kQ2iIfWuIxPsWS4dJ8Vd9Y77hNJbdks5vOwI-gaJpZM4a-5D0>.

dastrix80 · 2019-02-18T19:52:59Z

No dramas :) I still don't get values populated into the string item despite them being linked now. But the debug does show the Parameter 9 & 10 values

cdjackson · 2019-02-18T19:55:04Z

Can you provide the log - just of what is received here. If you’re not receiving the multilevel-sensor START/STOP commands, then the associations aren’t configured. We don’t want the parameters being reported as they are not used.

…

On 18 Feb 2019, at 19:53, dastrix80 ***@***.***> wrote: No dramas :) I still don't get values populated into the string item despite them being linked now. But the debug does show the Parameter 9 & 10 values — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1135 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA_kQxKHWtZVY-H9osKXSB-XuRRGWy2aks5vOwScgaJpZM4a-5D0>.

dastrix80 · 2019-02-18T19:59:27Z

Hi Chris

I had the report set in para 4, have changed that now and the log shows the info correctly

19-Feb-2019 06:58:26.684 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: resetResendCount initComplete=true isDead=false
19-Feb-2019 06:58:26.684 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
19-Feb-2019 06:58:26.684 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: COMMAND_CLASS_MULTI_CHANNEL corrupted payload 60 0D 02 01 26 05
19-Feb-2019 06:58:36.843 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 20: Message payload = 00 14 0A 60 0D 02 01 26 04 38 00 FF 00
19-Feb-2019 06:58:36.844 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 20: Application Command Request (ALIVE:DONE)
19-Feb-2019 06:58:36.845 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: resetResendCount initComplete=true isDead=false
19-Feb-2019 06:58:36.845 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
19-Feb-2019 06:58:36.845 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: Incoming command class COMMAND_CLASS_SWITCH_MULTILEVEL, endpoint 2
19-Feb-2019 06:58:36.845 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: SECURITY not supported
19-Feb-2019 06:58:36.845 [DEBUG] [e.internal.protocol.commandclass.ZWaveCommandClass] - NODE 20: Received COMMAND_CLASS_SWITCH_MULTILEVEL V0 SWITCH_MULTILEVEL_START_LEVEL_CHANGE
19-Feb-2019 06:58:36.846 [DEBUG] [col.commandclass.ZWaveMultiLevelSwitchCommandClass] - NODE 20: Switch Multi Level start level change, direction = INCREASE
19-Feb-2019 06:58:36.846 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 20: Got an event from Z-Wave network: ZWaveStartStopEvent
19-Feb-2019 06:58:36.846 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 20: Got a value event from Z-Wave network, endpoint = 2, command class = COMMAND_CLASS_SWITCH_MULTILEVEL, value = INCREASE
19-Feb-2019 06:58:36.846 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 20: Commands processed 1.
19-Feb-2019 06:58:36.847 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 20: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@76b91d53.
19-Feb-2019 06:58:37.133 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 20: Message payload = 00 14 06 60 0D 02 01 26 05
19-Feb-2019 06:58:37.135 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 20: Application Command Request (ALIVE:DONE)
19-Feb-2019 06:58:37.135 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: resetResendCount initComplete=true isDead=false
19-Feb-2019 06:58:37.135 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
19-Feb-2019 06:58:37.135 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: COMMAND_CLASS_MULTI_CHANNEL corrupted payload 60 0D 02 01 26 05
19-Feb-2019 06:58:57.113 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 20: Message payload = 00 14 0A 60 0D 02 01 26 04 78 00 FF 00
19-Feb-2019 06:58:57.114 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 20: Application Command Request (ALIVE:DONE)
19-Feb-2019 06:58:57.115 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: resetResendCount initComplete=true isDead=false
19-Feb-2019 06:58:57.115 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
19-Feb-2019 06:58:57.115 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: Incoming command class COMMAND_CLASS_SWITCH_MULTILEVEL, endpoint 2
19-Feb-2019 06:58:57.115 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: SECURITY not supported
19-Feb-2019 06:58:57.116 [DEBUG] [e.internal.protocol.commandclass.ZWaveCommandClass] - NODE 20: Received COMMAND_CLASS_SWITCH_MULTILEVEL V0 SWITCH_MULTILEVEL_START_LEVEL_CHANGE
19-Feb-2019 06:58:57.116 [DEBUG] [col.commandclass.ZWaveMultiLevelSwitchCommandClass] - NODE 20: Switch Multi Level start level change, direction = DECREASE
19-Feb-2019 06:58:57.116 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 20: Got an event from Z-Wave network: ZWaveStartStopEvent
19-Feb-2019 06:58:57.117 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 20: Got a value event from Z-Wave network, endpoint = 2, command class = COMMAND_CLASS_SWITCH_MULTILEVEL, value = DECREASE
19-Feb-2019 06:58:57.117 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 20: Commands processed 1.
19-Feb-2019 06:58:57.117 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 20: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@4d343c6d.
19-Feb-2019 06:58:57.355 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 20: Message payload = 00 14 06 60 0D 02 01 26 05
19-Feb-2019 06:58:57.357 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 20: Application Command Request (ALIVE:DONE)
19-Feb-2019 06:58:57.357 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: resetResendCount initComplete=true isDead=false
19-Feb-2019 06:58:57.357 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
19-Feb-2019 06:58:57.358 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 20: COMMAND_CLASS_MULTI_CHANNEL corrupted payload 60 0D 02 01 26 05

dastrix80 · 2019-02-18T20:00:43Z

Still no values in the string item

cdjackson · 2019-02-19T07:32:39Z

So to be clear, you have an item linked to the switch_startstop channel? The log looks ok in that the data is being processed, and the event is being passed to the thing handler. After this it will only be processed if the channel is linked to an item that has this channel type. If that is the case, then I will add some more debug to see what is happening.

…

On 18 Feb 2019, at 20:00, dastrix80 ***@***.***> wrote: Still no values in the string item — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1135 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA_kQ_WJNhnsmrIurZOo35DZIOAjxqaTks5vOwZsgaJpZM4a-5D0>.

dastrix80 · 2019-02-19T08:55:34Z

Correct.

See my attached items, I believe I've done this correctly.

/*ZWave Aeotec WallMote Bedroom  */
Number BedRoom1_AeoButton_Scene      "Aeotec WallMote #3 Button"                               { channel="zwave:device:a1562d1c:node20:scene_number" }
Number BedRoom1_AeoButton_Battery    "Aeotec WallMote #3 Battery"          (gBatteries)        { channel="zwave:device:a1562d1c:node20:battery-level" }
String BedRoom1_AeoButton_Slide1      "Aeotec WallMote #3 Button"                               { channel="zwave:device:a1562d1c:node20:switch_startstop1" }

cdjackson added the enhancement label Feb 16, 2019

cdjackson added this to the 2.5 milestone Feb 16, 2019

cdjackson force-pushed the move_stop_channel branch from bc9ca37 to 1177c52 Compare February 16, 2019 10:11

Add start stop channel

df8eff7

Signed-off-by: Chris Jackson <[email protected]>

cdjackson force-pushed the move_stop_channel branch from 1177c52 to df8eff7 Compare February 16, 2019 10:55

cdjackson merged commit a74a413 into openhab:master Feb 16, 2019

cdjackson deleted the move_stop_channel branch February 16, 2019 12:15

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add start stop channel for Aeotec swipe #1135

Add start stop channel for Aeotec swipe #1135

cdjackson commented Feb 16, 2019

dastrix80 commented Feb 16, 2019

cdjackson commented Feb 16, 2019 via email

dastrix80 commented Feb 16, 2019 •

edited

Loading

mhilbush commented Feb 18, 2019

dastrix80 commented Feb 18, 2019

mhilbush commented Feb 18, 2019 •

edited

Loading

dastrix80 commented Feb 18, 2019

mhilbush commented Feb 18, 2019

dastrix80 commented Feb 18, 2019 •

edited

Loading

cdjackson commented Feb 18, 2019

dastrix80 commented Feb 18, 2019

cdjackson commented Feb 18, 2019 via email

dastrix80 commented Feb 18, 2019

cdjackson commented Feb 18, 2019 via email

dastrix80 commented Feb 18, 2019

cdjackson commented Feb 18, 2019 via email

dastrix80 commented Feb 18, 2019

dastrix80 commented Feb 18, 2019

cdjackson commented Feb 19, 2019 via email

dastrix80 commented Feb 19, 2019

Add start stop channel for Aeotec swipe #1135

Add start stop channel for Aeotec swipe #1135

Conversation

cdjackson commented Feb 16, 2019

dastrix80 commented Feb 16, 2019

cdjackson commented Feb 16, 2019 via email

dastrix80 commented Feb 16, 2019 • edited Loading

mhilbush commented Feb 18, 2019

dastrix80 commented Feb 18, 2019

mhilbush commented Feb 18, 2019 • edited Loading

dastrix80 commented Feb 18, 2019

mhilbush commented Feb 18, 2019

dastrix80 commented Feb 18, 2019 • edited Loading

cdjackson commented Feb 18, 2019

dastrix80 commented Feb 18, 2019

cdjackson commented Feb 18, 2019 via email

dastrix80 commented Feb 18, 2019

cdjackson commented Feb 18, 2019 via email

dastrix80 commented Feb 18, 2019

cdjackson commented Feb 18, 2019 via email

dastrix80 commented Feb 18, 2019

dastrix80 commented Feb 18, 2019

cdjackson commented Feb 19, 2019 via email

dastrix80 commented Feb 19, 2019

dastrix80 commented Feb 16, 2019 •

edited

Loading

mhilbush commented Feb 18, 2019 •

edited

Loading

dastrix80 commented Feb 18, 2019 •

edited

Loading