ControlThink Forums

1) does your sdk (v1.2) support the HSM100 multi-sensor (motion, temp, light, battery)?  If so, how? Can you give code examples?

2) when will version 2 be out?

 Thanks

leggatt,

If it's a motion sensor, you'll probably pick up the motion events via the ZWaveDevice.LevelChanged event.  I don't know about the other features, although we can certainly work on integrating support if our customers request it.  We try to support all Z-Wave devices the best we can.

I don't have any dates to announce on future versions, but suffice it to say that we're working along those lines...

Chris

Hi Chris

Has there been any update on support of the HSM100? It may be more suited to a future release but the ability to build the following two functions would be great:

1) Transition a light's state from OFF to ON over a set period of time. (i.e. multiple dimmer changes over time)

2) Turn lights on in a room by level of illumination rather than time. Even sunset / sunrise tracking with an offset isn't always enough. Basically.. IF it's between 3pm and 11pm AND light level is dark THEN turn on the lights in the lounge.

Thanks again

 I would also like to see support for this device added to the SDK.  It is a great device that opens up a lot of possibilities in automation.

I plan to put a HSM100 in just about every room in my new home.

It has 4 sensors/outputs:

Motion

Temp

Light level

Battery Level

Support for this would be huge for me.

 Full ThinkEssentials support for this is in my wish list too.

Any updates on the support of this multisensor?

Can anyone provide feedback as to how well they work?

I have 1 HSM100,  my experience is the faster you set them to send out updates the faster the battery's die.  I had 1 set to send out regular updates (Temp, light level, batt level ) every 6 minutes and it lasted only a couple of months.  I replaced the batteries with fresh Energizer's and still only a couple of months.   So I am either going to have to greatly increase the regular updates, or maybe try lithium batteries.

 It just didn't seem logical to me to expect temp / light readings every 30 minutes or so.

JMHO

StevenE

Well... if you're sending out data every 6 minutes, that's 240 transmissions per day or 14,400 transmissions in 60 days!  It definitely does add up.  If 14,400 transmissions is the limit for your batteries, and my math is correct, you can extend the life of those batteries to a full year by setting your transmission interval to 36.5 minutes (or something close to that).  I could be wrong, of course... but you won't know that for a year (give or take). 

 Mark

Changing the time to over 30 minutes just makes the temp and light readings almost useless in my opinion.

I had wanted to trigger some events depending on those readings, that is why I set it to 6 minutes and I thought that was too long.   With 30+ minutes in between updates I will have to rethink my configuration.

 StevenE

The EZMotion (aka HSM100) uses 1000X more power when it's transmitting that when it is "sleeping". Thus, the more often it is transmitting, the shorter the battery life. 30 min updates should give 1 yr battery life.

You can remove the batteries and power it with a +5V wall-wart power supply from radio-shack. If you can configure it properly, it'll never go to sleep and will be part of the mesh-network routing.

Details can be found on: http://www.expresscontrols.com/zwaveproducts.htm#EZMotion