What should I set in the value field of the event when I select the “Brightness reached” or “Temperature reached” event types? Is is an absolute value (i.e. “0”, “10” or “72”) or is it something like “<10” or “>72”? I tried both and it didn’t seem to work either way. I’m using a HSM100 multi-sensor to read the temperature and brightness levels.
We were told that complex expressions would be release in version 1.0.565 for the HSM100. http://forum.micasaverde.com/index.php?topic=683.0
Like you I tried for hours to make the light sensor trigger a scene using both a value and an expression (< or >) with no results. 
I see there is another release out now but there is no mention of a fix for this. The 3 in 1 is now a 1 in 3.
Any progress on this?
It would be nice to be able to use the multi sensor for what it is. Think of the possibilities… averaging of temperature between rooms… supplement to z-wave thermostats sensors with data from the HSM 100…
Just wondering,
- D
I have this working, see the thread here >[url=http://forum.micasaverde.com/index.php?topic=790.0]http://forum.micasaverde.com/index.php?topic=790.0[/url]
I’m not seeing any specifics in that topic. Can you please provide more details?
I know that I can associate other zwave devices with the HSM100 and let the HSM100 control them, however I think that something like this would be made easier (at least for the non coder / newbie / cautious person like me) if it was programmed through a GUI similar to Vera’s.
Instead of having to associate the HSM100 to directly control a zwave outlet or fader, why not let Vera take information that it already receives via polling and use it to manipulate the other zwave devices? Or take for example a complex command that takes into consideration time instead of a second factor reported by the HSM100.
If illumination = <30 and time = later than sunset (or any other value… static or dynamic), and motion is detected, then set room lights to 50% and do whatever (leave it, turn it off in 5, etc.).
I have a few rooms that catch sunlight after sunset. If it is cloudy though, the room is significantly darker. Things that I would want to take into account when setting up automation are:
Time, Motion, illumination levels
The idea is that complex commands using various data (not just from the HSM100) and using Vera to control that, opens many more options in smarthome automation more so than simply associating the HSM100 to another zwave device.
Sure there are downfalls to that, if Vera is offline for any reason, the automation fails… but I would like the option of being able to make that decision for myself.
Doc–I think you hit the nail on the head with your post. Another example could be "If (front door sensor is triggered) AND (foyer motion detecter detects motion) THEN (turn on downstairs house lights and send text message to…).
I don’t have any sensors yet, but it seems that the capability to integrate complex information is precisely what defines the benefit of these systems anyway. For example, if I simply want to turn on a local light when motion is detected, there are plenty of commercial light switches/sensors and even screw-in detectors for outdoor locations. The presence of a computer (in this case, Vera) allows creative applications that are otherwise impossible and justify the cost. It’s precisely those applications that, IMHO, will result in “Wow” reactions that will lead non-techies to adopt these technologies (and part with their $ for them).
This is precisely the type of programming that the ISY99 from Universal Devices allowed me to do with Insteon… I am hoping that Vera allows this type of programming in the future. It would allow you to link multiple condiitons with AND/OR condition statements and provide a THEN and ELSE action if the statement was true or false. I think the Vera programmers should really take a look at how this was implemented in that device and make it somewhat similar. The programming was very powerful and very easy to understand and implement once you got the hang of it.
This type of programming was also nicely done in Indigo for the Mac (an X-10/Insteon control platform). You could also assign “groups” of switches or other devices of similar type and then control them with one command (as opposed to separately). Any event could either separately or in conjunction with other events trigger scenes and/or actions in one or more nodes or groups.
I hope this is coming our way via Vera.
MCV’s consistent response to this request (conditionals, nesting, etc.) is to wait for them to release their LUA interface. This is supposed to be done “soon”, but the lack of it seriously restricts the usefulness of the device. Events or grouping all all “flat” now and will remain that way.
I use Vera for a remote observing and control of the heating systems at a cabin. It’s easy to set up a “I’m at the cabin” and “I’m away” but can’t do any other events, like “I’m at the cabin and it’s 10PM so set the temp to 65”. No conditionals means no real control.
I really want this capability and soon.
Randy S.
Well said, Randy.
While I am asking for more… I’d like to see associated advanced zWave settings too specific to each device.
Example… The HSM100 Sensor can be “Programmed” to “behave” a certain way.
See: http://www.homeseer.com/wiki/index.php/HomeSeer_HSM100
under “Configure the HSM100”
There are 6 configuration items:
- Off Delay - this is the amount of time from the last time motion was detected until the lights are turned off. Recommended Values: 5 for Hallways where people are actively moving thru the space ans you want the lights to turn off as soon as they have left. 20 (default) is good for most rooms such as a home office, den or kitchen. 30-60 minutes for rooms where people might be sitting still (IE: reading) for a while and it might be difficult to detect motion. The key to a high WAF is to set this value high enough so the lights don’t turn off while you’re sitting in the room.
- Led Enable - leave this at the default
- Sensitivity - leave this at the default of 200 unless you want it to not detect your pets, then set it to a lower value (100).
- Wakeup Interval - The HSM100 will report in every N minutes even if it hasn’t detected motion. This is important for HVAC or Light readings. Note that the lower you set this value, the shorter the battery life. Typically leave this at the default of 60 minutes for 1 year of battery life.
- Device Activation State - This is the DIM level sent to lights that are controlled directly by the HSM100. Requires that the HSM100 be associated with the light.
- Sleep State - Leave this in the default “sleep” state for battery powered operation.
When I go to configure these settings in Vera, I now get to guess about a number of things. What do I need data value wise? default, 1/2/4 hex or decimal value? I have yet to get the thing programmed the way I want it to work.
Why not just put this in plain english, since simplicity is supposed to be a main selling point of Vera.
In fact, I wonder if setting any of these really apply since Vera controls the “off” time of the controlled device (for setting #1 above) once the device is turned on.
I WILL become a code monkey trying to figure out how to make this thing do what I want it to, or I will make Vera a second controller and invest in something that supports more complex commands (shortly).
FitPC has caught my eye… running something like Homeseer… with a solid state hard drive. Just add a zWave dongle and viola.
I’ll wait for 1 year for this LUA stuff. I hope the work on the LUA explains the lack of Software updates. I hope the hype is worth it.
Windows based home automation? Right, until it gives you the famous BSOD, or simply decides to reboot when you least expect it… Been there, done that, still have ThinkEssentials and HomeZIX shortcuts on my desktop…
However newer fit-pc2.com could do a nice media director for LinuxMCE, and potentially for Vera.
