Google Home Error log "Attempt to decode JSON with unexpected mimetype"

Configuration
1

I have a dozen of these error logs all of a sudden, i think after latest update

2019-06-28 16:35:28 ERROR (MainThread) [googledevices] ClientError contacting http://192.168.1.100:8008/setup/bluetooth/scan_results - 0, message='Attempt to decode JSON with unexpected mimetype: '

and

2019-06-28 16:18:40 ERROR (MainThread) [frontend.js.latest.201906260] http://192.168.1.10:8123/hassio/dashboard:0:0 Uncaught

Anyone with similar issue?

2

Google have pushed an update that is breaking all API endpoints to the google home…
https://github.com/home-assistant/home-assistant/issues/24815

Not yet sure if this is “fixable”, for now disable the googlehome integration.

4 Likes
3

this is sucks. the sole reason why Google Home still running in my home is now gone. another reason why I should not rely on proprietary cloud smart home device for my local system. Regretted I did not block Internet access on this device.

2 Likes