It's possible to have the Twine send its temp on a regular basis to a simple web "service" that collects them and stores them in a database. I've done this and am hosting in a free environment. I can get the data out, whenever I want and in different formats.
+1 for scheduled sensor state transmission. It would also be nice to have "update on change" which would trigger on any change above some absolute value. (i.e. "Update if change in temperature is greater than 1 degree." Or update if orientation changes.)
I'd prefer to rely on my own "conditional rule processor" and loggers rather than what is on SuperMechanical's servers.
Kit, I'm guessing he's using a script to pull the temperature off the web interface, since it gets updated there. (Twine's current temp, orientation, voltage.) Sounds like lots of people are requesting a straight-up scheduler or time-based conditions (count me in), and they say it's on the to-do list.
And also, a full log of all rules which were triggered along with a timestamp. Right now, SMS alerts don't come through ... and nor are emails. It would be useful to check when rules were triggered in order to diagnose SMS/email relay problems
+1 on logging based on time and a sensor variable. And +10 to the person who writes out idiot-proof directions for those of us who have never ventured into logging before.
Yes. I'd like to profile the temperature in my attic, for instance, so I can know if it would be safe to install some equipment up there. An alert when the temp is out of bounds could do that, but not tell me as much as I really need to know, while a log of the data over time (CSV?) would be quite helpful.
I too have gone the web service route and have a simple line graph on my website that I can refer to for the last 10 reads. I have all previous reads sent over the HTTP request saved in the database.
I agree with logging. I don't really know if my Twine is working. One rule could be to send an email if nothing happens with Twine for X minutes, hours, days, months.
Answers
I'd prefer to rely on my own "conditional rule processor" and loggers rather than what is on SuperMechanical's servers.
And also, a full log of all rules which were triggered along with a timestamp. Right now, SMS alerts don't come through ... and nor are emails. It would be useful to check when rules were triggered in order to diagnose SMS/email relay problems
Logging on https://twine.supermechanical.com/ would be nice.
logging on http://cosm.com would be even nicer!