Hi @David_Pakhnyuk welcome to the community! Sending email/sms/Pushbullet/Pushover notification is supported, but not the dynamic device attribute at this moment. This is one of the use cases of the Variable feature that we have in our list.
Do you need the temperature reading in details or do you care if the temperature reaches some thresholds like 75 and 80? See below for the workaround to get notifications when temp reaches 75 and different sms content when the temp is above 80.
Picking up this topic again. I’m looking to collect all my battery levels as variables and then send me a weekly report showing the battery levels. I can easily collect them as variables, but how do I include the variables in an email or notification communication?
I would like to see this as well, with the ability to select a group of sensors and notify which sensor activated the trigger, and what the readings are. This would reduce repeating the same program for each trigger over and over.
@James has been actively working on the concept of ‘context variables’ along with the ability to include variables into notification content.
In the above example, I have several different potential variables which could trigger the rule and there are different IF conditions within the rule based on which variable triggers things. What’s shown in the screenshot above is using the ‘event’ context to to get the ID of the variable that triggered things and the value of the variable that triggered things.
In the following video clip, I briefly show how you can select a context variable (or a regular variable) and include it into the notification content. Just a reminder that this is a working demo from an internal development build at the moment, but hopefully it gives you an idea of what we’re working on.