I have a chromecast 2 powered up and ready to cast all the time - eventhough i don't use it that often.
I noticed suspicious data usage of ~150MB per day on my router. I dont have per device or website traffic logging on my router but suspected the chromecast as that was the most recent addition to my network. I googled a bit and found quite a few related hits. It seems to be downloading HD background wallpapers even when your TV is off and the chromecast is in "idle".
Two solutions suggested so far:
1. Only power up the chromecast when you want to use it / power it from your TV's USB port (if it can give enough power - google recommends using the external psu to avoid other problems)
2. Setup the chromecast to only "stream" background images from a google+ account with only one low res photo on the account
5GB in useless photos that you dont even look at (since when you are actually using the device you are casting an app!). Wasteful even if you are on uncapped.
Anyone else spotted the problem? Or perhaps with the ability to record better logs? I would love to just block the wallpaper ip on my router but it looks like the same ip used for general CC comms (https on ajax.googleapis.com... maybe...)
I'm going to try solution #2 soon and see if it helps.
I noticed suspicious data usage of ~150MB per day on my router. I dont have per device or website traffic logging on my router but suspected the chromecast as that was the most recent addition to my network. I googled a bit and found quite a few related hits. It seems to be downloading HD background wallpapers even when your TV is off and the chromecast is in "idle".
Two solutions suggested so far:
1. Only power up the chromecast when you want to use it / power it from your TV's USB port (if it can give enough power - google recommends using the external psu to avoid other problems)
2. Setup the chromecast to only "stream" background images from a google+ account with only one low res photo on the account
5GB in useless photos that you dont even look at (since when you are actually using the device you are casting an app!). Wasteful even if you are on uncapped.
Anyone else spotted the problem? Or perhaps with the ability to record better logs? I would love to just block the wallpaper ip on my router but it looks like the same ip used for general CC comms (https on ajax.googleapis.com... maybe...)
I'm going to try solution #2 soon and see if it helps.