johnstonf Posted January 4, 2017 Share Posted January 4, 2017 RE: Substitution Variables Anybody know how to actually put CURRENT TEMPERATURE into an email? I see Heat and Cool SETPOINT, Humidity, ETC, but not the current TEMPERATURE... I don't want the agony of moving to v5 yet, i'll wait for more maturity on it... (looking to do it with v4.5.4) (SORRY For the reformatting of a NICE table below... lol... see attachment screenshot) Variable Example Description sys.node.<address>.name sys.node.11 22 AA 1.name Name of the device node sys.node.<address>.addr sys.node.#.addr Address of the device node sys.node.<address>.<valueName>.ST sys.node.11 22 AA 1.ST The formatted specified value sys.node.<address>.<valueName>.raw sys.node.11 22 AA 1.ST.raw The unformated specified value sys.node.<address>.<valueName>.OL sys.node.11 22 AA 1.OL On Level sys.node.<address>.<valueName>.RR sys.node.11 22 AA 1.RR Ramp Rate sys.node.<address>.<valueName>.ERR sys.node.11 22 AA 1.ERR Error sys.node.<address>.<valueName>.CLISPH sys.node.11 22 AA 1.CLISPH Heat Setpoint sys.node.<address>.<valueName>.CLISPC sys.node.11 22 AA 1.CLISPC Cool Setpoint sys.node.<address>.<valueName>.CLIFS sys.node.11 22 AA 1.CLIFS Fan State sys.node.<address>.<valueName>.CLIMD sys.node.11 22 AA 1.CLIMD Thermostat Mode sys.node.<address>.<valueName>.CLIHUM sys.node.11 22 AA 1.CLIHUM Humidity sys.node.<address>.<valueName>.CLIHCS sys.node.11 22 AA 1.CLIHCS Heat/Cool State sys.node.<address>.<valueName>.UOM sys.node.11 22 AA 1.UOM Unit sys.node.<address>.<valueName>.CV sys.node.11 22 AA 1.CV Current Voltage sys.node.<address>.<valueName>.CC sys.node.11 22 AA 1.CC Current Current sys.node.<address>.<valueName>.PPW sys.node.11 22 AA 1.PPW Polarized Power Used sys.node.<address>.<valueName>.TPW sys.node.11 22 AA 1.TPW Total Energy Used sys.node.<address>.<valueName>.PF sys.node.11 22 AA 1.PF Power Factor Link to comment
larryllix Posted January 4, 2017 Share Posted January 4, 2017 I don't recall using any variable suffix to report temperature right out of the 2441ZTH units. EDIT: Just looking inside my notifications and I used... Util:${sys.node.20 48 B3 1.ST}C, RH:${sys.node.20 48 B3 1.CLIHUM} Link to comment
johnstonf Posted January 4, 2017 Author Share Posted January 4, 2017 THANKS Larry! Works Great! Where in the world is this all documented? Fred Link to comment
larryllix Posted January 4, 2017 Share Posted January 4, 2017 The only thing I have ever seen is the one page in the wiki regarding variable substitution. Admin Console|Help has links to the wiki now. Link to comment
stusviews Posted January 4, 2017 Share Posted January 4, 2017 THANKS Larry! Works Great! Where in the world is this all documented? Fred http://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables Link to comment
johnstonf Posted January 5, 2017 Author Share Posted January 5, 2017 Funny, that's the screen i took the screenshot from. I looked 10 times at it, and skipped by it! What a HORRIBLE description! How about "formatted temperature value" Instead of "The formatted specified value" /Fred Link to comment
stusviews Posted January 5, 2017 Share Posted January 5, 2017 Because the specified value is not restricted to temperature. Link to comment
johnstonf Posted January 5, 2017 Author Share Posted January 5, 2017 ok, but maybe an '(eg temp)' added to end to cover 90% usage maybe Link to comment
stusviews Posted January 5, 2017 Share Posted January 5, 2017 I see 15 possible usages, the specified value can be for any one of those. Link to comment
johnstonf Posted January 5, 2017 Author Share Posted January 5, 2017 ok, i guess that's why footnotes were invented, lol Link to comment
larryllix Posted January 5, 2017 Share Posted January 5, 2017 You have to think like the developers. A thermostat only sends temperature, right? That was the probably the first and only parameter. Oppps.... It sends more parameters. we better get some more suffixes working.. Link to comment
johnstonf Posted January 5, 2017 Author Share Posted January 5, 2017 Correct!And developers need to think like normal end-users too... (happy end-users = more sales = more success) (hard for them to do sometimes, being bitheads) Link to comment
larryllix Posted January 5, 2017 Share Posted January 5, 2017 Correct! And developers need to think like normal end-users too... (happy end-users = more sales = more success) (hard for them to do sometimes, being bitheads) Code monkeys. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.