[BETA] Edge Drivers for Homeseer Devices

Is anyone working on an edge driver for the HSM200 multisensor? This is both an RGB nightlight and a motion/temperature/lux sensor. Plug-in, not battery. It’s a re-branded ezmultipli device, and has always been sort of out there on its own, but it’s useful and quite a few community members have it.


It’s a pretty straightforward device when looked at component by component. (It has a second association group, but I don’t think anybody using smartthings uses it, it just turns on up to four devices when motion is detected. And the user settable parameters are for the cool down period, and again, I don’t think most people using smartthings care.)

But it’s the combination of a controllable RGB light, and collecting information from the three sensors that tends to make it a unique project.

It’s worked well for years with a stock driver but a couple of people have reported that it did transition, but they ended up only with light control, not with the motion sensor data. :thinking:

Anyway, it’s a Homeseer sensor still being manufactured and sold, which is why I’m asking in this thread, since I think this is where a lot of people would look for it.


1 Like

I can if someone in the US can loan me one to develop/test with.

FYI, it looks like the EZMultiPI is incorporated into the SmartThingsCommunity drivers.

From what I can tell the HSM200 was introduced (incorrectly) in the past, and removed in September of last year.

I have created the following pull request to add the HomeSeer fingerprint to the existing EZMultiPli definition


Can you tell from the GitHub listing if the stock driver is handling the motion, lux, and temperature sensors, as well as the RGB light? At one point, there was an issue where the stock driver treated it only as a lightbulb, and you didn’t get any of the sensor information, but I don’t know if that’s still true.


Yes, I validated that all of the functionality is included in the EZMultPli

name: motion-switch-color-illuminance-temperature
- id: main
  - id: motionSensor
    version: 1
  - id: switch
    version: 1
  - id: colorControl
    version: 1
  - id: illuminanceMeasurement
    version: 1
        - key: "illuminance.value"
          range: [0, 32000]
  - id: temperatureMeasurement
    version: 1
        - key: "temperature.value"
          range: [-20, 100]
  - id: refresh
    version: 1
1 Like

Definitely interested. Was just boxing up the FLS100 G2 to send back. How do we use it? Is it in the Smartthings App?

PM me if you’re interested.

This is a pretty big feature release (for me that is), as the latest release now includes the ability to “set” the LED color via automation.

I have validated the following functionality:

  • On/Off/Dim Locally
  • On/Off/Dim via App (still see the out-of-sync issue in the app)
  • Multi-Tap to control other devices (up/down/double/toggle 2x up, toggle 2x down)
  • Smart Lighting and Routine triggers
  • Use settings to set the LEDs to all of the capable colors
  • Use toggle 2x up to turn on a subset of the status LEDs (via Smart Lighting) this uses the default color from settings. If settings is set to “Off” default the LED to “White”
  • Use toggle 2x down to turn off a different subset of status LEDs (with overlap) (via Smart Lighting)
  • Turn on LED when door opens and off when closes (using Smart Lighting)
  • When switch is turned on, turn on LED, and overwrite the default color setting with one picked via colorControl. The code will let you pick anything from the color palette, but then will select the closest of the 7 vendor supported colors.
smartthings edge:drivers:install -C c408fa0b-438f-4d00-bf36-efe7343c66b7 5f2d5dca-fcd9-4895-805a-6e976dd349d1

PS - I will likely pivot to the FC200 to get it up and running. Please let me know if there are any issues here, or on GitHub

1 Like

@jshessen Still got this issue

@sylvain – I as well

I created tracking issue just so I don’t lose it. I have been focused on getting the core functionality into the driver. The actual app presentation layer is completely outside of the driver, but I suspect that there may be some type of chatter or event emit that could be missing to force the app to recognize the changes in state.

1 Like

Sorry this is my first go at trying to integrate SmartThings into my current setup. I have the HSM200 and when adding to the SmartThings app it adds as a light. When I log in online I can change it to the “HomeSeer Multisensor”. It still does not have the correct functionality.

It looks like they discontinued device handling, which seemed pretty straightforward.

I might be completely wrong on the verbiage for this. Is there an edge driver that I can authorize for this to function as it should?

1 Like

@DrDraake – no need to be sorry, most of us are here to help where we can.

Unfortunately, the situation with the HSM200 is a bit in flux. From what I can see the EZMultiPli is essentially the same device, and has been developed and already included directly in the SmartThingsCommunity/SmartThingsEdgeDrivers channel.

I have issued a “pull” request to add the HSM200 to the device definition, but this pull request has yet to be reviewed..

As a stop gap, I will work on adding temporarily pulling the code over into my device channel today/tomorrow to offer this functionality until it is properly incorporated into the main channel.


@jshessen I appreciate everything you are doing to enable these drivers!
Your work is much appreciated. Thanks so much

1 Like


I don’t have a an HSM200 to test with, but I have incorported the changes that were included in the pull request to the main channel into the channel documented in this thread. To keep things generic, the driver is referenced as “HomeSeer Z-Wave Sensors”. Feel free to give it a go and provide any testing feedback (may require some logs if things don’t work).

smartthings edge:drivers:install -C c408fa0b-438f-4d00-bf36-efe7343c66b7 f8c65d66-292d-4f61-947e-b3025067b076
1 Like

Doesn’t enroll properly, no zwave device id or hub ID, see below.
Could be problem with hub memory full. Still way under max devices.

Edge devices do not populate those fields in the IDE. The most you get is the name, label, and a device type of “placeholder”.

Re-enforcing @csstup here is a screenshot of one of my devices as well.

The key item to look at is to view the Driver details in the mobile app:

  1. Select a Device
  2. Click on the “menu” (three dots upper right of the Android app)
  3. If you see “Driver” then you are using and Edge device. The details will show you which driver you are using.

1 Like

The IDE is part of the old architecture and will be going away once the transition to the new architecture is complete.

Once a device has been assigned to an edge driver, any edge driver, the information in the IDE may be incomplete or inaccurate or old. Just ignore it.

Instead, there are now three places to look for the information you used to get from the IDE.

  1. as @csstup suggested, just start with the device details in the smartthings app.

  2. if you need still more information, try


Which is a new official feature.

  1. and if you need even more details, you can use the CLI or a community-created webpage called API browser plus

SmartThings API Browser+ ... Now Available to All

But lots of things are going to look weird in the IDE now. They aren’t bothering to update it since it’s going to be eliminated anyway.

You can find additional information in the following community FAQ:

Life after the IDE: Questions and Answers

It works. But need way to organize routines…. Folders would be good, or ability to add all scene control routines to one routine.

@jshessen, Thank you for developing the driver.

@jshessen I did a bit of testing and here are my results.
The good news

  1. I was able remove my HSM200 and successfully re-add it to Smartthings

  2. the correct driver was selected after adding it

  3. I am able to see temperature, lux, motion and color settings as expected

  4. lux and temperature values report correctly

The bad news

  1. turning the sensor on or off from the app results in this message “network or server error occurred. Try again later”.
    Also does not turn on from routine.
    See screenshot below for more details

  2. setting any color from the app or routine does not show the color on the sensor. This is the main feature that I use this device for so I hope this can be corrected

  3. Motion sensor timeout value is no longer available under the sensor Settings menu. After motion is detected, it takes 10 minutes to clear! This makes its use as a motion sensor very limited. It would be great if you can re-add the ability (under the sensor Settings) to set a value (in seconds) to clear motion detection. As an example, my other motions sensors clear detection after 15 seconds of no activity which is perfect for me

Other than those issues, everything else seems to work fine.
Thanks you so much and I appreciate your help to correct the issues I noted above