Seems to be when switching the [other temps] / gauges then going back to dashboard the cookie gets left behind (see attachment). In my case this is repeatable across multiple installs of Win 10 running Chrome 64 bit - current version. I can not duplicate this behavior on MAC OS Chrome installs.

This may just be a Chrome bug but it may be a good thing to know anyway- Clearing the cookie fixes the issue every time.

You do not have the required permissions to view the files attached to this post.

I've taken a look, a cookie is created if you change the Apparent temp gauge to something else - this is correct and is the same as the full web site version of the gauges. I cannot get the page to fail to load when the cookie is set and connecting to my local MX instance. My cookie contents are exactly the same as yours - i.e. "dew". Chrome 59.0.3071.115 (Official Build) (64-bit)

The cookie handling code is the same as the full gauges package.

Can you post the dev console output when the page fails to load? Interesting to see what error you are getting...

I just wanted to report back that everything has worked flawlessly for almost a month now. Not a hint of a problem either with the real time display or the PWS website. Thanks to Steve and all those who helped this old man learn some new tricks.