Homeseer HSM200 Z wave multisensor has limited functionality

I purchased a Homeseer HSM200 line voltage multi sensor. I am running a brand new Zooz z wave hub. The pir function and the temperature sensor both work, they report to the hub and will start automation’s.

One of the reasons that I purchased the sensor was I read the RGB lamp has its own sensor input called color controller. You can program triggers to activate the RGB light with different colors depending on what scene was triggered. I can not get the RGB lamps to work. I tried with scenes and code no luck. Zooz tech support( which has been very disappointing) said you cant control the RGB led’s. They suggested a Home seer product was the culprit. The product is a registered Z wave device, so I believe it will work.

any suggestions on how to get the Homeseer HSM200 z wave multi sensor to work on my Zooz hub would be helpful.

Thanks

RVF Hiker

Hello. Researching that sensor a bit I found this:
The Homeseer site for that sensor says it may require the Homeseer hub for full functionality: specifically:

“ Non-HomeSeer Compatibility

Most non-HomeSeer hubs will recognize HSM200 as a BINARY sensor with ON (for motion) and OFF (for no motion) status. Temperature and Luminance reports may or may not be detected. If the hub does not support the Z-Wave COLOR CONTROL command class, it won’t be able to change the RGB LED indicator. Be sure to check with your non-HomeSeer hub manufacturer for more information about compatibility.”

Which hub do you have? Are you using a Zooz Z-Box or are you using the Zooz 800 dongle with another system? (Wasn’t sure what you meant exactly by ‘Zooz zwave hub’)

If I can get one of those sensors I’m happy to test in my lab. Of course the Zooz folks can chime in here as well, as they likely already know the real answer.

Edit: I found one and it will be here tomorrow - I’ll let you know what I discover!

Good Morning. Just a quick update. I did receive the HSM200 yesterday and was able to add it to the z-box without issue. I can control the light and its colors directly but it has some peculiarities. Also controlling via a block script is not working properly for setting color but I think I see the issue and may be able to resolve. Give me a few days to work on this and I’ll post what I find. May even turn this into a video for ease of explanation.

In short this device seems to be meant only for Homeseer. It seems that Homeseer did some things trying to lock it to their hub, like encrypting the firmware update so it can only be performed from a Homeseer hub! Not a friendly device, imho.

So when you have a chance, please let us know exactly which hub you are using (z-box vs something else with a Zooz dongle , etc). Also please post what firmware version your HSM200 is currently on.

Thank you.

I’m not sure if this is an abandoned post, but I did do some extensive testing with the HSM200 recently. In short, it appears that a template needs to be added to the Z-Box for full functionality. Specifically to get the LED to be programmable via block and/or LUA scenes.

You could open a ticket with the Zooz team to request a Z-Box device template for the HomeSeer HSM200 multi-sensor, specifically to expose the LED / Color Control functionality to automations.

On the Z-Box I’ve observed:

  • The HSM200 includes successfully and reports sensors correctly
  • The Preview tab UI can change the LED color (“Set Color As” / favorites)
  • However, LED control is not available via:
    • Block Scenes
    • Lua
    • REST API
  • Calls to the Color Controller device return not implemented (code -3)
  • Only the Multilevel Switch endpoint responds to basic turnOn/turnOff

If you have the patience :grinning_face:, you can see my review of the HSM200 on my channel at: https://youtu.be/yTUz2Qxftz8

There you will see it had some challenges in other platforms like Home Assistant as well. IMHO, this device is happiest in Homeseer.

May you test this lua code to change color?

red = 0
blue = 255 
red = 0
blue = 255 
green = 0
white = 0 
var_value = 100  ---%
color_id = 101   --change id of color controller



-- try this 
api.post("/devices/groupAction/setColorComponentsAndBrightness", json.decode("{\"args\":[{\"brightness\":"..var_value..",\"colorComponents\":{\"blue\":"..blue..",\"green\":"..green..",\"red\":"..red..",\"warmWhite\":"..white.."}}],\"filters\":[{\"filter\":\"id\",\"value\":[\""..color_id.."\"]}]}"))



Hello,

Thank you for your reply!
I just tested and it did not work, unfortunately… no entries that I could see in the log either. I did change the color_id to the value of the color controller (304).



Hmm, Wonder why it wont work :thinking:
if you go into the swagger and devices and fill in your device id. Do you find somthing like color or colorcomponents in the device json?

Here’s the resultant json for the device:
I’m not an expert here… but I’d like to be! lol. Appreciate any insight.

{
  "id": 304,
  "name": "52.0 Color Controller",
  "roomID": 220,
  "view": [
    {
      "assetsPath": "",
      "name": "com.fibaro.colorController",
      "translatesPath": "/assets/i18n/com.fibaro.colorController",
      "type": "ts"
    }
  ],
  "type": "com.fibaro.colorController",
  "baseType": "com.fibaro.multilevelSwitch",
  "enabled": true,
  "visible": true,
  "isPlugin": false,
  "parentId": 300,
  "viewXml": false,
  "hasUIView": true,
  "configXml": false,
  "interfaces": [
    "autoTurnOff",
    "light",
    "notification",
    "parameters",
    "zwave"
  ],
  "properties": {
    "parameters": [],
    "pollingTimeSec": 0,
    "zwaveCompany": "HomeSeer Technologies",
    "zwaveInfo": "3,6,1",
    "zwaveVersion": "2.7",
    "autoOffDefaultTime": 900,
    "autoOffTimestamp": 0,
    "categories": [
      "lights"
    ],
    "color": "255,0,0,0",
    "colorComponents": {
      "blue": 0,
      "green": 0,
      "red": 255
    },
    "configured": true,
    "dead": false,
    "deadReason": "",
    "deviceControlType": 51,
    "deviceIcon": 582,
    "deviceRole": "Rgb",
    "endPointId": 0,
    "icon": {},
    "isLight": true,
    "log": "",
    "logTemp": "",
    "manufacturer": "HomeSeer Technologies",
    "markAsDead": true,
    "model": "",
    "nodeId": 52,
    "parameterProvider": "zwave",
    "parametersTemplate": "0",
    "productInfo": "0,12,0,4,0,1,2,7",
    "saveLogs": true,
    "serialNumber": "",
    "setColorComponentsAndBrightnessNativeSupport": false,
    "state": false,
    "supportedDeviceRoles": [
      "Rgb"
    ],
    "supportedNotifications": {
      "7": {
        "eventValues": {},
        "key": "blockScenes.notification.properties.7",
        "stateValues": {
          "motion-sensor-status": {
            "key": "blockScenes.notification.properties.motion-sensor-status",
            "values": {
              "0": {
                "key": "blockScenes.notification.properties.7.0",
                "saveToPanel": true
              },
              "7": {
                "key": "blockScenes.notification.properties.7.7",
                "saveToPanel": true
              }
            }
          }
        }
      }
    },
    "useTemplate": true,
    "userDescription": "",
    "value": 0
  },
  "actions": {
    "reconfigure": 0,
    "setAutoOff": 0,
    "setColor": 1,
    "setColorComponents": 1,
    "setColorComponentsAndBrightness": 1,
    "setValue": 1,
    "startColorEnhancement": 1,
    "startColorFade": 1,
    "stopColorChange": 1,
    "toggle": 0,
    "turnOff": 0,
    "turnOn": 0
  },
  "hiddenActions": {},
  "created": 1769857465,
  "modified": 1769857465,
  "sortOrder": 24
}