Hi,

 

I was wondering if it was possible to read the internal temp that is art of an ELK/RCS setup. I can see the internal temp in the ISY config and adjust set points from the isy actions, but cannot seem to read the temp as a variable that i can put in a text message or notification.

 

Thanks,

Steve

I was wondering if it was possible to read the internal temp that is art of an ELK/RCS setup. I can see the internal temp in the ISY config and adjust set points from the isy actions, but cannot seem to read the temp as a variable that i can put in a text message or notification.

Hi Steve,

 

Are you referring to the temperatures available on Elk keypads, zones, and thermostats? If so, they are available as shown in the wiki:

 

http://www.universal-devices.com/mwiki/ ... _Variables

Chris,

Thanks! That seems like it should have done the trick, but I am getting blank values when trying to grab the temp with the following (trying to get indoor/outdoor temp to display):

 

${elk.tstat.1.ST}/${mod.weather.temp.current}

Hi daxiang28,

 

Do you get a completely blank message?

 

With kind regards,

Michel

Hi daxiang28,

 

Do you get a completely blank message?

 

With kind regards,

Michel

 

 

Yes, completely blank.

Michael,

 

Is this a bug that I should submit a ticket for?

 

Thanks,

Steve

I have several notifications that are very similar to yours that are working.

 

For example I am sending the outside temp (weatherbug) to Elk keypads for display.

 

I don't want to insult you by suggesting something so obvious, but you did hit the "save" key in your setup... right?

I have several notifications that are very similar to yours that are working.

 

For example I am sending the outside temp (weatherbug) to Elk keypads for display.

 

I don't want to insult you by suggesting something so obvious, but you did hit the "save" key in your setup... right?

 

I have the weatherbug temp coming through to the keypads fine. It's the internal temp via Elk and RCS thermostat that is returning blank via the variable

 

In:${elk.tstat.1.ST} Out:${mod.weather.temp.current}

 

And yep, I'm constantly saving before testing my programs.

 

Steve

Hi Steve,

 

When you go to the Thermostats tab under Elk, do you see the temperature values for your thermostats? If so, are you sure the ID you are specifying in your variable is correct?

Hi Steve,

 

When you go to the Thermostats tab under Elk, do you see the temperature values for your thermostats? If so, are you sure the ID you are specifying in your variable is correct?

 

I do see the thermostat with correct temperature values. The ID for the RCS thermostat is 1. I tried other variations of 0 and 2 just in case the index started at 0 or something funky with no luck. I also tried other variables like "tstat.1.name" and it was blank as well.

 

Steve

I have several notifications that are very similar to yours that are working.

 

For example I am sending the outside temp (weatherbug) to Elk keypads for display.

 

I don't want to insult you by suggesting something so obvious, but you did hit the "save" key in your setup... right?

 

I have the weatherbug temp coming through to the keypads fine. It's the internal temp via Elk and RCS thermostat that is returning blank via the variable

 

In:${elk.tstat.1.ST} Out:${mod.weather.temp.current}

 

And yep, I'm constantly saving before testing my programs.

 

Steve

 

I don't have the Elk thermometer or any type of thermostat connected, but I was able to successfully text and email the keypad temp. Not sure if this info is of any use to you.

I don't have the Elk thermometer or any type of thermostat connected, but I was able to successfully text and email the keypad temp. Not sure if this info is of any use to you.

 

I'm running the KP2s, so no keypad temp for me unfortunately.

Bump. Has anybody had any success using the Elk temp variables?

Hello daxiang28,

 

My recommendation is to upgrade to 3.3.1 ... even though we have tested this multiple times and it always works, it would be best to work based on the same reference.

 

3.2.6 did have a bug where some variables would've been blanked out; this said, this bug was not ELK related.

 

With kind regards,

Michel

My recommendation is to upgrade to 3.3.1 ... even though we have tested this multiple times and it always works, it would be best to work based on the same reference.

 

Michael, Awesome!! That did the trick.

 

Steve

Excellent and thanks so very much for the update.

 

With kind regards,

Michel