Climacell and Variables and Elk Display Panel

[Pierre]

I have the ISY994Pro and and Elk M1 Gold with the LCD Display.  I want to display the temperature in the Display.  (I used to be able to with the Old HAM weather Module.) but now I can't find the current temp variable from the Climacell data.  Do I ned to use a variable?  Any direction would be helpfull.

[bpwwer]

3 hours ago, Pierre said:

I have the ISY994Pro and and Elk M1 Gold with the LCD Display.  I want to display the temperature in the Display.  (I used to be able to with the Old HAM weather Module.) but now I can't find the current temp variable from the Climacell data.  Do I ned to use a variable?  Any direction would be helpfull.

All the variable substitutions are listed in the readme at https://github.com/bpaauwe/udi-climacell-poly/blob/master/README.md

[Pierre]

2 hours ago, bpwwer said:

All the variable substitutions are listed in the readme at https://github.com/bpaauwe/udi-climacell-poly/blob/master/README.md

This is very helpful and I know that I am close.  Would you happen to have the proper syntax with an example of the node address etc.

[bpwwer]

All node server nodes start with 'n' followed by 3 digits followed by an '_' followed by something node server specific.  The address is shown below the name in the admin console when displaying the node.   For the Climacell node server it would look something like 'n001_weather'

[Pierre]

9 hours ago, bpwwer said:

All node server nodes start with 'n' followed by 3 digits followed by an '_' followed by something node server specific.  The address is shown below the name in the admin console when displaying the node.   For the Climacell node server it would look something like 'n001_weather'

These are the test that I am trying...

Test 1 ${sys.node.n004_weather.CLITEMP}
Test 2 ${sys.node.n001_forecast.GV0}
Test 3 ${sys.node.n004_weather.CLITEMP}

and this is the results...

Test 1 node[n004_weather]
Test 2 node[n001_forecast]
Test 3 node[n004_weather]

 

Where am I going wrong?

[Pierre]

Found it.  This was the proper syntax.

Test 1 ${sys.node.n002_weather.CLITEMP}
Test 2 ${sys.node.n002_forecast_0.GV0}
Test 3 ${sys.node.n002_weather.CLITEMP}

 

Results...

Test 1 20.75°C
Test 2 26.6°C
Test 3 20.75°C

[JBanaszak]

Found it.  This was the proper syntax.
Test 1 ${sys.node.n002_weather.CLITEMP}
Test 2 ${sys.node.n002_forecast_0.GV0}
Test 3 ${sys.node.n002_weather.CLITEMP}
 
Results...
Test 1 20.75°C
Test 2 26.6°C
Test 3 20.75°C

I have the same keypads. Would you mind sharing an example for the program you use to display temps? Great idea! Thanks, Jim


Sent from my iPhone using Tapatalk

[Pierre]

Sure thing Jim:

Its a 2 step process.  Create a customized email and add this to the subject.

Outside: ${sys.node.n002_weather.CLITEMP}

Now create a program with the following code.

I only update the temp every 10 minutes.

Hope this helps. Pierre...

[apostolakisl]

I have this functioning.  You set a custom notification (Configuration>Emails\Notifications>Customizations).  The subject line is what Elk picks up.  I also have the body section pull the Elk keypad temp.  If you send it as an email or text that will populate as well.  I use weatherbit polyglot node which is located at n008.

Then the program is very easy.

Elk Temp - [ID 008B][Parent 001A][Run At Startup]

If
        From     1:00:00AM
        For      24 hours 
 
Then
        Repeat Every  5 minutes 
           Set Elk Area 'Main House' Display Text on Keypads, Content 'outside temp'
 
Else
        Repeat Every  5 minutes 
           Set Elk Area 'Main House' Display Text on Keypads, Content 'outside temp'
 

You'll see I have it run at startup.  You actually can leave the "if" blank, but if somehow the program stops running it will start again at 1am.  Populating both the "then" and "else" makes it run no matter what.  But it is actually way overkill.  I could just have the "then" clause and a blank "if" and blank "else" and run at startup checked and it would work.

[JBanaszak]

Thank you Pierre and apostolakisl!