New Google Home device tracker Component - Introduced in HA 0.83

Mariusthvdb · June 14, 2019, 5:55am

trying this component for the first time, I’ve made a small package:

googlehome:
  devices:
    - host: 192.168.1.134 #woonkamer
      track_devices: false
      track_alarms: true
    - host: 192.168.1.23 #hall
      track_devices: true
      device_types: 1
      track_alarms: false

what am I supposed to find after a restart? I can’t see any new sensors, nor device_trackers with the ip addresses. Please forgive me if this has been asked before, couldn’t find a true pointer really.

thanks for having a look

baz_12312 · July 1, 2019, 7:23pm

Has this stopped working on the minis? My hub seems ok, but now when I go to http://google_homes_ip:8008/setup/bluetooth/scan_results on the mini or home I get a 403 and HA doesn’t track anything with them

and my logfile is full of this:


2019-07-01 20:32:36 ERROR (MainThread) [googledevices] ClientError contacting http://192.168.1.35:8008/setup/bluetooth/scan_results - 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-07-01 20:32:36 ERROR (MainThread) [googledevices] ClientError contacting http://192.168.1.36:8008/setup/bluetooth/scan_results - 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-07-01 20:32:36 ERROR (MainThread) [googledevices] ClientError contacting http://192.168.1.37:8008/setup/bluetooth/scan_results - 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-07-01 20:32:47 ERROR (MainThread) [googledevices] ClientError contacting http://192.168.1.37:8008/setup/bluetooth/scan_results - 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-07-01 20:32:47 ERROR (MainThread) [googledevices] ClientError contacting http://192.168.1.36:8008/setup/bluetooth/scan_results - 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-07-01 20:32:47 ERROR (MainThread) [googledevices] ClientError contacting http://192.168.1.35:8008/setup/bluetooth/scan_results - 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-07-01 20:32:58 ERROR (MainThread) [googledevices] ClientError contacting http://192.168.1.37:8008/setup/bluetooth/scan_results - 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-07-01 20:32:58 ERROR (MainThread) [googledevices] ClientError contacting http://192.168.1.36:8008/setup/bluetooth/scan_results - 0, message='Attempt to decode JSON with unexpected mimetype: '
2019-07-01 20:32:58 ERROR (MainThread) [googledevices] ClientError contacting http://192.168.1.35:8008/setup/bluetooth/scan_results - 0, message='Attempt to decode JSON with unexpected mimetype: '

davefrooney · July 1, 2019, 8:59pm

The new firmware update from google has broken the tracking and alarms. This may not be fixable

jerobins · July 1, 2019, 10:43pm

Google is spending more time turning off features than fixing features. Frustrating.

ludeeus · July 2, 2019, 6:30am

The features of the Google home are still there, they just added more security to them.

DavidFW1960 · July 2, 2019, 6:31am

But the unofficial API is gone now?

ludeeus · July 2, 2019, 6:32am

No, it’s still there, they just added a security layer.
The Google home app still uses it

DavidFW1960 · July 2, 2019, 6:38am

So are you going to be able to update the component with the new security requirement?

ludeeus · July 2, 2019, 6:44am

I have no idea (yet)

Alesoft73 · July 9, 2019, 12:55pm

The google home continuous to work tracking.
If have resolve the problem with disconnect and riconnet plug . Until 3 times…

firstof9 · July 10, 2019, 3:19pm

Seems like part of their steps towards “local first then cloud” for home controls.

Tyfoon · July 10, 2019, 9:26pm

Thanks but not sure what you mean. You mean unplugging the device from main power?

iantrich · July 11, 2019, 4:17am

I think you’re right: https://developers.google.com/actions/smarthome/concepts/local, but mine looks to be working again. Perhaps they released it a little bit early and have since rolled it back?

firstof9 · July 11, 2019, 11:32am

Wouldn’t be the first time lol

Alesoft73 · August 6, 2019, 9:41am

Plug and unplug the main power…

gurbina93 · August 7, 2019, 12:25pm

Not working for me… getting 403 on my Google Home Minis and a Google Nest Hub when trying to scan devices. No amount of restarts resolves it.

Anyway I don’t think I am missing much, just the alarms and indoor positioning which wasn’t very reliable. I am still waiting for Ariela client to implement indoor positioning.

If anything Google Home was filling up my known devices in matter of days.

Thib5 · August 9, 2019, 4:06am

So it’s dead ? I just finished my 3d plan and I wanted to integrate room location in it … Well ok thank you

Tyfoon · August 12, 2019, 11:46am

I also can’t get it to work anymore. I have below in my log 4945 times (and this is just 2 days).

I was actually very happy with this integration as it worked really well with my two LTE trackers (as addition to the phone tracker). I guess this does not work anymore on ANY Google Home device?

Any alternative available?

Error I get:

ClientError contacting http://192.168.1.190:8008/setup/bluetooth/scan_results - 0, message='Attempt to decode JSON with unexpected mimetype: '

Thib5 · August 12, 2019, 3:35pm

Google keep their api but change the port and put it in https … i ask around and it does not seam to have a solution to fix the complement … right now i’m looking into mysensors … i already go down this way for sensors and did not like it BUT if i don’t have any other solution i will check it

Tyfoon · August 12, 2019, 6:39pm

I had an old unused Google home lying around and plugged that on in. And that one still works. Wonder how long.