May have fixed my sleep issue with a router firmware update

Answers

• 9 Comments sorted by Votes Date Added
• William Winter

  November 2012 Vote Up1Vote Down

  Okay, I take it back. I still get the issue of the Twine not being able to update a status after a period of inactivity. This happens after a few hours and I even had to go through the setup this last time to get it showing on the dashboard again.
• Jarrod Krug

  November 2012 Vote Up1Vote Down

  My connection problem went away as soon as I connected twine to a power source. It has been plugged in all day and is active in the dashboard.... I went through two sets of batteries testing the charge. I also put Twine on a static IP
• Chris Arndt

  November 2012 Vote Up1Vote Down

  @Jarrod, out of curiosity, where do you assign an IP? Is it a router option, or something on the Twine configure I missed?
• Jarrod Krug

  November 2012 Vote Up1Vote Down

  http://help.supermechanical.com/kb/using-twine/static-ip-for-twine
• Thomas Costick

  December 2012 edited December 2012 Vote Up1Vote Down

  Static IP seems advisable where Twine's connectivity is unreliable. I suspect timing issues when using dynamic IP addressing.
• David Albert

  December 2012 Vote Up1Vote Down

  Even with static IP, I am getting very erratic connections. I'll get them for a few minutes or hours more or less on schedule (every 45, 90, or 135 seconds) and then it will miss a few hours.
• John Kestner

  December 2012 Vote Up0Vote Down

  David's problem seems to be that he has a network extended across two routers. Twine can get confused when two routers share a network name. We're investigating this one, but if possible, I'd advice creating a guest network on one of the routers (or a new network on another router) for Twine.
  
  Generally we've found that Cisco/Linksys routers work very well. The E1200 is our favorite. http://www.amazon.com/gp/product/B004T9RR6I
• Gerry Mueller

  December 2012 Vote Up-1Vote Down

  I can't think of any logical reason why a router firmware version should have any influence on a Twine's firmware programming's sleep parameters. Stranger things have happened, but this is probably not one of them.