Well after a quick check of the pi-hole it looks like Roku changed something for the awful and started chatting a whole bunch on my network.  I love pi-hole's dashboard. It gives me some good stats to look at every now and again. Usually there is nothing out of the ordinary going on, just the usual blocked domains.  I checked it after reading a post about Roku's update causing some funkiness on another users network.  Sure enough, I looked at mine and low and behold there it was staring right at me.

Here are some screenshots.  The usual suspects, google, microsoft, and amazon, but hey hey WTF Roku?

Also, here is Roku's terms, so this is to be expected.  I just never thought they would be hammering out that much data.

B. Information We Collect as You Use the Roku Services

1. Apps, Browser and Device Information

When you use the Roku Services, we may receive information about the apps, browser and devices you use to access our services, such as device types and models, unique identifiers (including, for Roku Devices, the Advertising Identifier associated with that device), IP address, operating system type and version, browser type and language, Wi-Fi network name and connection data, and information about other devices connected to the same network. For Roku Devices, we may also collect the name of the retailer to whom your Roku Device was shipped, various quality measures, error logs and software version numbers

While replacing the device with a Chromecast is just trading one spy for another, I think that Roku over stepped their bounds a bit and are now officially banned from the house.  

I'll have to finish that project to get my Kodi setup dialed it a bit more.  I need to figure out a good bluetooth remote and get some plugins installed.  The thing I really use the most is the casting features from Chromecasts or Roku type devices. I have yet to find a good way to do that on a Kodi/RaspberryPi setup.  That will be a post for another time...

Have fun.


By the way, here's how to clear the the pi-hole logs, just ssh in and run the following:

cd /etc/pihole
sudo service pihole-FTL stop
sudo mv pihole-FTL.db pihole-FTL.db.old
sudo service pihole-FTL start