smarty Super User
Joined: May 21 2006 Location: United States
Online Status: Offline Posts: 728
|
Posted: March 06 2007 at 20:08 | IP Logged
|
|
|
Dave,
I followed your instructions and put in the "[DATA] - 60" in the Raw to Calulated formula field. I also changed the "I/O" column type from "Elk Input" to "Input" since this temperature probe connects to zone 16 (which is a multi-state type input).
While this now DOES give me a number (which I am pretty sure was not there before), this number reads as 74, when all the rest of my temp sensors read 79 or 80.
As an interesting note, my Xlobby M1 plug-in also reads this temperature from zone 16. It tells me it sees 79 degrees.
Hope this helps....
********************************************************
Dave said...
Steve,
Yay! Someone testing the Elk functionality! Glad to hear that the multi-state's and the digital outputs are working properly.
Concerning the temperature sensor...I didnt have any temperature sensors to check with so I had to program this blind. The Elk seems to support 3 different types of temperatures...Thermostats, Keypads, and Temp sensors (which I assume is connected to an Elk multi-state input).
If it's a temperature probe connected to a multi-state input, then you should be able to declare a standard "Input" in the Analog I/O screen (don't use Elk multi-state). The value to use in the formula though, Im not quite sure. If it follows the standard temperature protocol outlined in the documentation, then you should be able to use "[DATA] - 60" without the double quotes for the "Raw to Calculated" formula to obtain the temperature in degrees farenheight.
If this works, let me know. After reading back over the docs while researching this for you, I think the light bulb may have just gone off for me and I can implement some quick changes for the next version.
Thanks,
Dave.
__________________ Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech
|