I’ve spent countless hours reading up and experimenting with the HSM100 3-in-1 sensor. After much pain and frustration with the manuals and forum entries for the HSM100, I’ve decided to update the Wiki page to capture what I’ve learned. Hopefully it will save some poor soul the same trouble.
[url=http://wiki.mios.com/index.php/ExpressControls3in1]http://wiki.mios.com/index.php/ExpressControls3in1[/url]
The previous wiki page was well out of date, somewhat inaccurate and referred to Vera 1 throughout.
I would appreciate it if those with experience with the device could [glow=yellow,2,300]review the wiki page[/glow] and discuss it to make sure it’s accurate. I’m not sure what the Micasaverde policy is about random people updating the wiki, but I think it can only be a good thing considering how poor the general documentation around the Vera ecosystem seems to be. 
Thanxs for the updated walk thru, great overview. some comments:
[list]
[li]]Why do you need to put the unit in test prior to setting the On Time?
[list][li]Configure the On Time to 5 minutes how (which tab) and what value
[/li][li]Did not indicate that when settingup a scene, that you have to go to the Commands Tab and set up the light(s) to do something?
[ul][li]A walk thru for setting up light level in conjunction with motion would be nice with explianation as what actually happening. Part of the problem for many is that setting up a single scene is relatively easy to understand it when you have multple scenes that are interacting is were it becomes a little difficult to grasp. Might add a simple state diagram or similar.
[/li][/ul]
to help
Thanks @solipsia, the instructions on the wiki worked perfectly.
A good piece of work solipsia. As one who has spent many painful hours endeavouring to make my sensors work it has sadly come too late for me but will doubtless be invaluable to the many now struggling and those yet to come to this challenge.
A couple of comments.
My understanding is that the exclude/include cycle is only required when setting the “Always Awake” parameter. Once this has been successfully set future changes to the Device Options are adopted directly - at least this has been my experience.
In your Polling Frequency section you make a reference to the unit never waking up. I can see what you are trying to say but this will be confusing for some as the unit actually never goes to sleep. Perhaps a change to the English here?
I have now converted all my sensors to AC power and set then to “Always Awake” and “Always Fire”. I have built all the necessary logic including the polling in Lua. In consequence I get temperature reports in my HVAC application once every minute. This may be seen as an extreme step by some and not everyone will be prepared to get in so deep. However, for anyone with a large or complex application I can say that it is well worth it especially as we now have a stable firmware. I’ve now reached the point where I am no longer continually playing with the system. The holy grail for most of us I would say.
As to the principle of users contributing to the Wiki. I for one think that this should be encouraged but that MCV should perhaps vet for accuracy from time to time.
Thanks for all the feedback. I’ve incorporated the changes into the wiki manual.
@Terencec: Excellent, thanks. I didn’t know that about inclusion and exclusion and I’ve added it to the page. I’ve also reworded the Polling Frequency paragraph.
@Michael_N_Blackwell: I’ve created a flowchart for how the Scenes and Events work (at least, as much as I think I understand how they work). Since it’s not just limited to the 3-in-1, I’ve added it to the Scenes Wiki Page:
[url=http://wiki.micasaverde.com/index.php/Luup_Scenes_Events]http://wiki.micasaverde.com/index.php/Luup_Scenes_Events[/url]
Everyone, please feel free to update the wiki pages with what you’ve learned directly!
Nice work @solipsia.
I was going to update the wiki, but decided to post my suggestions here in case there is any disagreement from other users.
-
The comment about associating with only one device may be incorrect. I have one of my sensors associated with three devices (a wall dimmer and two lamp modules) and it works fine.
-
In the section “Wake Up Interval” I would add the following after the sentence “To set the Wake Up Interval, click on the spanner (wrench) icon for the “3-in-1 sensor” device, click on Setting and set Wakeup Interval to the desired interval.” [font=Verdana]Reducing the wake up interval reduces battery life.[/font]
-
Settings and parameters should only be configured in the parent device. Changing settings in the child devices causes Vera to report an error which will persist in the message tab of the UI.
-
For the sake of completeness a list of the available parameters and instructions about where to find them (under the “Device Options” tab) and a mention that the “Data Size” is “one byte dec” might be helpful.
-
Would it be helpful to mention that these take longer to configure than other devices? At first I thought my “include” had failed because I didn’t see all four devices in the UI immediately. Then I started fiddling and excluding and trying again…
Thanks for your work on the wiki!
This has been VERY helpful. Thank You for posting this. I am interested in the Temperature function for the HSM100. Once I read your file and incorporated the suggestions, I finally had a change in temperature recorded. Now I’m trying to increase the frequency of the temperature reporting and i’m not having too much luck. I changed the WAKE up interval time (in seconds, as you said) and lowered it to 1 or 2 minutes. I stand by patiently and watch to see if the sensor is updated, but it doesn’t.
Any tips?
The Vera 3 (UI5) has been reported to have problems with the Temp and light sensors. I don’t know whether this has been fixed. It probably also depends on what firmware you are running.
That’s correct, this is a regression in the recent UI5 betas and these two child devices are not working in the most recent UI5 beta. They are a high priority bug on MCV’s list, so I am hopeful that this will be solved in the next version.
The recent issues aside, the wake up interval for the HSM100 is configured in 6 minute increments.
Thanks for your efforts, the wiki needs lots of work,
- the default wakeup interval on mine (and per my manual) is 1 hour (perhaps this was updated since I bought mine?)
- would mention the default “on time” as 20 min
Thanks again, great work!
Hi, just to let you know about a new parameters, i dont know if it available on all revision of hsm100 but it working on mine
Just add new device option 7
7 TempAdj
TempAdj is a twos-complement number that is used to adjust
the temperature reading to make it more accurate. The value
programmed is in tenths of degree Fahrenheit. The
temperature reading can be adjusted up to +12.7F to -12.8F. A
value of 1 will adjust the temperature reading by +0.1F. A value
of -1 will adjust the temperature by -0.1F. A value of 123 will
adjust the temperature by +12.3F.
TempAdj is NOT changed when Excluded (reset) from the ZWave
network.
Range
-127 -
+128
Sorry for my english