JSP0511 Posted April 16, 2016 Posted April 16, 2016 Hey peoples, I'd simply like to add the current humidity level of my thermostat to my email/text notification. I am using this for a music room that has my guitars in it and I regulate the humidity in the room. The humidifier can only run for so long before needing water so I'd like to use the warning to let me know when the levels are getting close to my threshold. I would also like to include the humidity level in the message. Thanks for your help! Jerry
jerlands Posted April 16, 2016 Posted April 16, 2016 You should be able to do this by adding getting the node address for humidity and adding that to a substitution variable included in the notification. example from wiki: sys.node.<address>.<valueName>.CLIHUM sys.node.11 22 AA 1.CLIHUM Jon...
JSP0511 Posted April 16, 2016 Author Posted April 16, 2016 You should be able to do this by adding getting the node address for humidity and adding that to a substitution variable included in the notification. example from wiki: sys.node.<address>.<valueName>.CLIHUM sys.node.11 22 AA 1.CLIHUM Jon... This doesn't seem to be working. I have two thermostats. On my home t stat I use ${sys.node.22 17 8E 1.ST} to get an alert about temp and it works. I never created a variable or anything. Just simply put that into the HTML message and it works (I think that's all I did, regardless, I don't have any variables set up). When I use sys.node.1f 70 64 1.CLIHUM or ${sys.node.1f 70 64 1.CLIHUM}, the text comes in as MSG:sys.node.1f 70 64 1.CLIHUM Thoughts?
jerlands Posted April 16, 2016 Posted April 16, 2016 (edited) I don't have an Insteon thermostat but you need to use the correct node number for humidity ${sys.node.1f 70 64 1.CLIHUM} look at the device and you'll see it. It won't be the same as for temperature. Jon... Edited April 17, 2016 by jerlands
rabbit1543 Posted April 19, 2016 Posted April 19, 2016 (edited) I think I ran into similar issue. I am using pushover for notifications and had errors whenever I added humidity. In my case I think it is due to % symbol. Try using ${1f 70 64 1.clihum.raw} I added a percent sign by apending %25 to the end. ${1f 70 64 1.clihum.raw}%25 Sent from my SM-G920V using Tapatalk Edited April 19, 2016 by rabbit1543
Techman Posted April 19, 2016 Posted April 19, 2016 You should be able to do this by adding getting the node address for humidity and adding that to a substitution variable included in the notification. example from wiki: sys.node.<address>.<valueName>.CLIHUM sys.node.11 22 AA 1.CLIHUM Jon... Have you had any luck adding humidity to your notifications? The humidity node for an Insteon thermostat doesn't show up in the ISY so it may not be a workable option.
JSP0511 Posted April 19, 2016 Author Posted April 19, 2016 Have you had any luck adding humidity to your notifications? The humidity node for an Insteon thermostat doesn't show up in the ISY so it may not be a workable option. No not yet. The main thermostat works if I use the code. It'll send temp or humidity. Whichever I put in. The new thermostat does not work. Not sure why. I'll try the percent this week.
Techman Posted April 19, 2016 Posted April 19, 2016 No not yet. The main thermostat works if I use the code. It'll send temp or humidity. Whichever I put in. The new thermostat does not work. Not sure why. I'll try the percent this week. What thermostats are you using? What's the line of code that works?
JSP0511 Posted April 19, 2016 Author Posted April 19, 2016 What thermostats are you using? What's the line of code that works? The code that works for my main therm is ${sys.node.22 17 8E 1.ST} I am using the insteon therms. He one that the code works for is wired. The other is wireless (battery). Not sure if that matters
MWareman Posted April 19, 2016 Posted April 19, 2016 (edited) When I use sys.node.1f 70 64 1.CLIHUM or ${sys.node.1f 70 64 1.CLIHUM}, the text comes in as MSG:sys.node.1f 70 64 1.CLIHUM Thoughts? This sounds like the symptom caused by having the 'Encode URL' option checked on network resources with substitution... Not sure why this would happen on email notifications.... Edited April 19, 2016 by MWareman
JSP0511 Posted April 19, 2016 Author Posted April 19, 2016 This sounds like the symptom caused by having the 'Encode URL' option checked on network resources with substitution... That could cause it to work for one and not the other?
Techman Posted April 19, 2016 Posted April 19, 2016 The code that works for my main therm is ${sys.node.22 17 8E 1.ST} I am using the insteon therms. He one that the code works for is wired. The other is wireless (battery). Not sure if that matters That's the code I've been using for the Insteon wireless thermostat but it only displays temperature.
JSP0511 Posted April 19, 2016 Author Posted April 19, 2016 That's the code I've been using for the Insteon wireless thermostat but it only displays temperature. The humidity definitely worked when I applied it to the main therm. I've had the main for a few years now. The wireless I recently added to the network.
MWareman Posted April 19, 2016 Posted April 19, 2016 That could cause it to work for one and not the other?Are they network resources - or email notifications? I'm not sure why it would happen at all in email notifications - other than trying to reference a node that isn't there. You could try accessing the problem node thru the rest API and ensure its providing a .CLIHUM value.
JSP0511 Posted April 19, 2016 Author Posted April 19, 2016 Are they network resources - or email notifications? I'm not sure why it would happen at all in email notifications - other than trying to reference a node that isn't there. You could try accessing the problem node thru the rest API and ensure its providing a .CLIHUM value. Text messages
MWareman Posted April 19, 2016 Posted April 19, 2016 ISY cannot send text messages. It's either an email notification (being delivered via your SMS provider gateway) or a network resource (calling a providers API like Twilio). I suspect its an email - and the only reason I can think of that the substitution would fail is if the device simply does not provide the node. Can you access the device via the REST API and see if the device even provides a CLIHUM node? I believe I explained how to do this on the Wiki page when I was building the tables...
JSP0511 Posted April 19, 2016 Author Posted April 19, 2016 ISY cannot send text messages. It's either an email notification (being delivered via your SMS provider gateway) or a network resource (calling a providers API like Twilio). I suspect its an email - and the only reason I can think of that the substitution would fail is if the device simply does not provide the node. Can you access the device via the REST API and see if the device even provides a CLIHUM node? I believe I explained how to do this on the Wiki page when I was building the tables... I'll give it a shot.
Techman Posted April 19, 2016 Posted April 19, 2016 I'll give it a shot. I just ran a email notification test and it works on the wireless thermostat ${sys.node.xx xx xx 1.CLIHUM} It's frustrating that the humidity option isn't documented.
JSP0511 Posted April 19, 2016 Author Posted April 19, 2016 I just ran a email notification test and it works on the wireless thermostat ${sys.node.xx xx xx 1.CLIHUM} It's frustrating that the humidity option isn't documented. thats what I've used. I'll try again. Not home at the moment.
MWareman Posted April 20, 2016 Posted April 20, 2016 It's frustrating that the humidity option isn't documented. Have you not seen this page http://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables Where I see this: (Full disclosure - I put that table there.... )
Techman Posted April 20, 2016 Posted April 20, 2016 Have you not seen this page http://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables Where I see this: Thank you. I don't recall those options being there the last time I looked, which was quite a while ago. . The page indicates it was updated in March. Either I missed it or it was added.
MWareman Posted April 20, 2016 Posted April 20, 2016 That was about the time that I significantly expanded and reworded the page to add details of network rule substitution and adding details of the device nodes.... It also shows the URL to call to get a specific devices nodes - so you can confirm what nodes are provided by any given device. I suspect that this particular device isn't providing humidity data - causing the substitution to fail.
Recommended Posts