I followed post and and I implemented exactly what the author did. It's a very easy way for a novice like me to log data. I highly recommend reading the article.
I implemented this as well, but my twine only updates once, then not again until I reload rules (or change the batteries). I've logged a bug about this, but heard nothing (as usual).
Great solution, but requires LOTS of rules if you want to monitor temperature across a househould range (my basement could fluctuate from 50 degrees to 75 degrees across the day, so I would need about 50 separate rules to keep track of all this).
I'm glad that blog post was useful for you guys. Is your Twine reporting temperature changes consistently? Mine isn't, I've opened a bug report with Supermechanical, I wonder if it is just a problem with my Twine.
Mine updates more than once, but it can go long periods of time without triggering a temperature change, even though the temperature is updated on the Twine website.
Tech support responded pretty quickly for me, but with no resolution yet. Perhaps after the holidays.
It would appear I'm seeing a similar thing, my Twine is reporting a drop in temperature to 69 now, but nothing shows up on Thingspeak since 1:49 PM EST when it was 70. Either the rule is not working, or the HTTP request isn't being fired properly...or both?
It seems that there is some sort of bug with the temperature rules. If I use ºC the rule works for "raises" but not for "falls" it seems that instead of using ºC uses ºF all the time. This might explain inconsistent reporting. I would recommend using internally only SI units. I have also used thingspeak to report the position by assigning a number to each possible position. When the position is "back" twine also sends the temperature. The rule is
Christina from Twine has been helping me with my updating problems. She indicated that they have done some work on their side to improve connectivity. Also, she asked me to try a couple things to see if they help. First was to move the Twine closer to my wireless router (everything gets bad wifi reception where I had the Twine sitting). Second was to set the Twine up with a static IP address (http://help.supermechanical.com/kb/using-twine/static-ip-for-twine)
It seems that the combination of these troubleshooting steps has helped quite a bit. It's not perfect, but it is reporting much more consistently than it was in a month or so ago: https://thingspeak.com/channels/3935
Comments
Thanks for the post. I was able to implement this also as described.
Best,
Tom
Tech support responded pretty quickly for me, but with no resolution yet. Perhaps after the holidays.
https://www.thingspeak.com/channels/3999#publicview
Thanks
This might explain inconsistent reporting.
I would recommend using internally only SI units.
I have also used thingspeak to report the position by assigning a number to each possible position. When the position is "back" twine also sends the temperature.
The rule is
WHEN orientation back THEN blink AND GET “a url”
where "a url" is
http://api.thingspeak.com/update?key=***MYKEY***&field2=4&field1=[temperature]
The two channels show at:
https://thingspeak.com/channels/4029
https://www.thingspeak.com/channels/4156#publicview