May have fixed my sleep issue with a router firmware update

William Winter

Just a note to let everyone know that I think I resolved my Twine's sleep issues. I was having issues similar to what others have posted.
I use a Cisco/Linksys E4200 WiFi router. It was running the out-of-the-box firmware from about 1 year (or more) ago, version 1.0.01. I upgraded the firmware to the latest and now the Twine seems to sleep and wake properly.
I hope this info helps someone!
Best, William

William Winter

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

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

@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

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

Thomas Costick

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

David Albert

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

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

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.