I ran into the same thing. Once I understood how it worked though, it made sense. It was just not obvious and the UI4 dialogs and terminology didn't help things. I think the keys to quickly understanding the HSM100 3-in-1's are these concepts:
Motion1] The motion sensor has two basic states Tripped and Not-Tripped - you can tell in UI4 which state it is in by the person icon, if it is a standing person then it is in "Not-tripped" and if it is a running person then it is in "Tripped" state. In iVera on iPhone it's a little different: The word Tripped is the indicator, and if it is all grey then it is "Not-Tripped" and if it is red colored then it is "Tripped"
2] When it is tripped it will generate an event, and when it switches back to not-tripped it also generates an event - both of which you can set scenes for to turn on and then off lights etc in reaction to these events
3] You can set the amount of "still" time with no motion detected that it takes the sensor to switch from Tripped back to Not-Tripped. It defaults to 20min so the sensor will generate a not-tripped event after it detects 20min of stillness/no-motion. You can change this in the 3-in-1 device (not the motion device) settings under Device Options, Variable 2 (on time) in minutes.
4] While the sensor is in the "Tripped" state, it will not continue to fire off motion events (unless you custom configure it to do so continually)
5] The sensor has a special "test" mode (hitting the zwave button once) that lasts for 10min
6] You (or Vera) can communicate with the sensor directly to configure user parameters etc -
only- while it is in test mode
7] The "motion" LED
only lights up in response to constant motion while it is in the "Test" mode (for 10min) after which it only lights briefly when Tripped is fired off
8] When configuring an event for the motion sensor in UI4, the event parameter "Tripped?" is where you designate whether you are acting upon the Tripped state event or the Not-Tripped (aka idle or still) state from the sensor. In my opinion this should be called "State=" and the value options should be "Motion" and "Still"
also the manual that comes with the homeseer branded version of HSM100 isn't very thorough. The express controls manual is much better and more complete
http://www.expresscontrols.com/pdf/EZMotionOwnerManual.pdfLight Level and Temp1] To conserve battery these will not generate events when they change
2] They will report back their values to Vera periodically based on the sensor's wakeup variable value (in seconds). It defaults to 1800 (every 30min) but you can change to shorter or longer values - just remember that the more often it sends updates to Vera the more battery it will use.
3] You may create scenes to react to the Light and Temp value changes, just remember that the scenes will be able to check and react to the values as only often as what the wakeup value is configured for.