Use Periodic Schedule as trigger for the rule. Create a local variable in the rule, and stick the temperature in with Sensor Value for your sensor. Then Send Notification with %variable-name% in the message, using the local variable you created.
Thanks that worked. Never used local variables before but will now!
Should I add a delay to make sure the local variable has been set? In my rule, I placed a 30-second delay, and the I have message sent to my phone. I figured the local variable might need some time to set?
Going to let this be a "wakeup greeting" via Sonos.
So to get "EVERY" day in the Periodic Schedule you used n=1 right ?
EDIT:
(Nevermind, the n=1 is obvious)
What isn't so obvious is best practice naming conventions for variables. I just created "Temp - Greenhouse" then went in to use this in the %variable-name% and went oooooh those capital letters and spaces and the dash are NOT a good idea. While RM might handle it I can't be guaranteed to remember it exactly. Obviously I got carried away with the flexibility, in the ole days that woulda been tempgreenhouse. I see I can't edit this, gotta delete. Best undo the use of it in the %variable-name% message first I assume.
Should be OK. There are some disallowed special characters that Hub Variables and Local Variables both announce and prohibit. But otherwise, names are pretty flexible. There is a bug associated special characters in variable names in the context of Custom Attribute and Sensor Value (this rule), but that is squashed in the upcoming hot fix release.
Thanks BUT...
if I get sloppy and don't get the caps or the space-space exactly as created I'm gonna be in trouble right?
EDIT:
I'm not gonna lie, there's a whole-nuther-level of "quick satisfaction" in putting together a helpful little automation/announcement with these tools compared to cranking through to the successful compilation of a FORTRAN program that analyzes a pile of data.
@jim273 I've just tried this on mine to see how it's done and get you a screen shot. String won't work. You want Decimal then set the initial value to any decimal value (as your rule will change it to match the value from your ecowitt the first time the rule triggers). When I set string, then set my action as set variable, choosing my temperature sensor - there was no option to pick "temperature" as it is a decimal value not a string. Here's the action:
No problem - I learned something myself to be honest. I'm might set one for 10AM and further modify it so that if it's >20 degrees announce on Sonos "The temperature is xx degrees outside" then follow it with a sample of Bill Withers "and I know it's gonna be, a lovely daaaaaaaaaaaaaaaaaaaaaaaaaaaay" !