Samsung Multipurpose Sensor

Hi there,

I just bought one of the Samsung Multipurpose sensors ( to try out with the gateway.

The other Samsung product I’ve connected so far is the Samsung SmartThings Outlet plug which connected to gateway with no issues for me once I set the plug into pairing mode.

I’ve haven’t had the same easy set up to connect to the Gateway with the Samsung multipurpose sensor.

I’m just posting to see if anyone else has connected it to the gateway yet or has any suggestions how to make this work?


Hi Loraine,

This should get classified as a binary sensor (at least for the door/window sensor part), but I don’t think the Zigbee classifier recognises it yet.

The team is currently in Mountain View and coincidentally @twobraids just drove to Fry’s to buy one of these and @dhylands is working his magic as we speak. Stay tuned!


ahahaha. Awesome, talk about good timing.

I have a such “F-SS-MULT-001” sensor (from ST gateway kit) but no Zigbee adapter to try it, can you suggest any (that also support ZWave preferably) ?

Not yet. I have a few zigbee sensors and so far I’ve had issues with all of them. I will be working on this and will figure out what the issue is.

Dave Hylands

Hi everyone,
I have got a related question to this subject: It’s great that the Samsung/SmartThings Multipurpose Sensor can be added now with the Zigbee add-on. It works well as an open/close and temperature sensor. My question is: is there a way to also get the acceleration data? Thanks!

Currently there isn’t. The multipurpose sensor uses a vendor specific cluster which isn’t documented. Although I did find the device handler code for it here:

so it should be possible to figure something out.

Hi Dave, thanks for that. I might have a go at it. Would making some changes in the zigbee-adapter get me anywhere? It looks like the file, zb-classifier has the different zigbee device properties defined in there. OR could you point me to where/what I could do to get acceleration data?
Thanks again!

The classifier looks at a node and the information that has been collected so far to determine which properties that a device should have.

For zigbee, when the classifier adds properties, this also triggers “binding and reporting intervals” which cause cluster changes to be reported back to the gateway. The classifier also registers parsing/setting functions (which come from the zb-property.js file) for encoding/decoding the data going to/from the device.

Since the accelerometer is manufacturer specific, you’ll probably need to add a check on node.modelId (similar to this one: but inside the appropriate initXxxx function that gets called for the multi-purpose sensor (I don’t recall off the top of my head exactly which routine this is).

1 Like

Hi Dave,
Thanks for that.
I followed most of your suggestion/example using the clusterid ‘fc02’ (according to the smartthings groovy) but I think I am still missing something , particularly at the add property part (I pasted my code below). I am not sure what else I am missing. Any ideas? Thank you!

const accelerationEndpoint =
if (accelerationEndpoint) {
this.addAccelerationProperty(node, accelerationEndpoint);

addAccelerationProperty(node, accelerationEndpoint) {
//multipurpose sensor
const property = this.addProperty(
node, // device
‘acceleration’, // name
{//property description // property description
@type’: ‘Acceleration’,
label: ‘acceleration’,
type: ‘boolean’,
readOnly: true,
PROFILE_ID.ZHA, // profileId
node.ssIasZoneEndpoint, // endpoint
64514, // clusterId
‘’, // attr
‘’, // setAttrFromValue
‘’ // parseValueFromAttr