Aeotec doorbell question

[RogerO]

Hello,

I have a Aeotec doorbell with a barking dog file on it. In reactor I have a activity like this:
luup.call_action('urn:micasaverde-com:serviceId:ZWaveNetwork1','SendData',{Node='77',Data='112 4 6 1 8'},1)

How do I get this to work in MSR?
There is a SendData action for the doorbell with Node and Data as inputs. Tried a few combinations but not getting ot to play. Anyone have one of these?

[tunnus]

Just use entity action - runlua?

[toggledbits]

There is an entity called "Zwave" associated with your hub (it will have ID device_1, so if your Vera is configured using the default ID Vera, the canonical ID of the entity is vera>device_1. This is the ZWave device parent on Vera, the mother of all ZWave devices (did you know that all of your ZWave devices on Vera are actually child devices of this device #1?)

You need to use the SendData on that entity. This is exactly the same thing you are doing on Vera. Notice the device number in your call_action() call, at the end... it's 1.

[RogerO]

@toggledbits Thanks for the reply, you have completely lost me. In my set reaction I have an Entity Action pointing at the doorbell and the senddata drop down. That action has a box for Node and data. I assume the Node is 77 and the data is 112 4 6 1 8. Where does the 1 come into play and does the value in Node and Data have to be wrapped in any other punctuation?

[toggledbits]

Look at your Vera/Luup action. You are not sending that to the Aeotec door bell, you are sending it to device #1, which is the ZWave network controller, telling it what node and what data to send. You are not sending data directly to the node; you are sending it to the ZWave controller telling it to send it to the node.

You have to do the same thing in MSR: the action you run is on the ZWave network entity (device_1)

[RogerO]

Thanks for the additional details. That worked.