Begining to look like its the website and not the bridge? unless anyone knows different.
Anyone any ideas???
I believe that, strictly speaking, "Bridge frozen" means "there has not been an update to COSM in the last 15 minutes". That could be
- bridge not running - power etc including momentary disconnection or brownouts
- Intranet or internet failure - continuing or intermitent
- Bridge running and network working but not connected to server
- Authorization failure
If rebooting the bridge fixes the problem it is likely to be a,b or c. A UPS for network components and bridge may be useful if problem is a or b. If the problem is c, fixing a and b and/or replacing router may solve the problem. Also pay atention to the quality of the cables - CAT5e for preference.
Problems fixed by re-registering the bridge or needing support are almost certainly authorization problems and there is nothing we can do about it. From observation of the COSM forums, other arduino type devices do not have the same level of extended problems seen by some people owning bridges, they mostly just work. The main difference is that Bridge owners have to contend with an additional complex and perhaps fragile authorization scheme.
This is the way I think authorization works. Some of it from putting a protocol analyser between the bridge and the internet for a very short time. A lot of it is (fanciful) guesswork.
- Bridge to 188.8.131.52 :: "Hello, This is CurrentCost bridge serial no 1234. My data is 0,1,2,3,4,5,6,7,8,9, Over" - 184.108.40.206 is the address of ConnectedEnvironments.com the owner of COSM. You might call it the commercial arm of COSM.
- 220.127.116.11 to bridge :: "OK, dont bother to send it again. Out" - don't suppose this really happens
- ConnEnv to CurrentCost.com :: "Hello, this is ConnEnv. I've had a call from Bridge serial no 1234, Is it OK to forward? Over" - stores the values for response.
- CurrentCost.com reply to ConnEnv :: "Hello ConnEnv, this is CC. Re your Query about Bridge Serial No 1234 - it has a current subscription and can see all 10 channels. It uses Cosm feed 9999. Over"
- ConEnv to CurrentCost.com :: "Thanks, Roger, Wilco, Out"
- ConnEnv to Cosm :: "Hello old mate! Could you PUT 0,1,2,3,4,5,6,7,8,9 to 9999. Over"
- Cosm reply to ConnEnv :: "Done! BTW can't U batch some of these, I'm running ragged with all the freeloaders."
- ConnEnv to Cosm :: "Out" - deletes stored values
Of course some of these conversations may be cached, but there is still a number of failure points. There may be reliable delivery to ConnectedEnvironments but not beyond. I had one situation where my IAM data was missing and was restored when the authorisation was fixed.
Hmm, I wonder when my subscription expires?
To round out the picture, I should say I have been running the bridge for 9 months. I had a week out in March which needed support assistance, but it has worked flawlessly since then. I have a good quality Linksys router (which needs rebooting occasionally, say monthly ) and I do use a UPS (purchased for my server, but the bridge does not draw much; router is too far away).