Google Homes not showing up in docker

Configuration
1

I have, so far, successfully moved my HA from RPi to Docker running on Mac Mini.

However, none of my 12 Google Home mini devices are showing up.

They self discovered on the RPI.

What may I not have copied across correctly or is there a way to manually add them?

2

Try to enter with a console into the homeassistant container and ping the GH mini IP to see if they are reachable

3

Good idea!

I’ll need to find out how to do that.

Is it just ping 192.x.x.x.x?

4

if you’re running Hassio, just add the SSH & Web Terminal addon and you will have a web terminal to use.
Yes, ping ip_address

5

I’m not running HassIO.

I got into it with Portainer.

Yes, I can ping them.

6

This is what I see for all of them:

No state available for media_player.kitchen_speaker
{
“entity”: “media_player.kitchen_speaker”,
“type”: “media-control”
}

Where is the entity ‘media_player’ configured? I think that’s what I’m missing.

7

I’ve copied over core.device_registry and core.entity_registry files from the Rpi to the docker HA and they now show up in the Entity Registry but still show as ‘unavailable’, as above.

8

it should be defined in configuration,yaml as

cast:
  media_player:
    - host: xxx.xxx.xxx.xxx
    - host: xxx.xxx.xxx.xxx
9

do you have the set network_mode as host as mentioned in the documentation. i believe thats required for successful discovery

or you can use the cast integration instead of defining in configuration.yaml

10

When I tried to add the Cast integration it said no cast devices found on the network.

Container network is set to Bridge. My MQTT devices are communicating with it fine on the same network.

You’re on the right lines though, I think. It seems to be a network config issue somewhere. I just don’t yet have the experience to find it.

11

pretty sure for HA to work correctly you need to set the network to use host

12

if using portainer you can edit/duplicate the container and also change the network mode

13

When I attempt to join the host network it gives me an error.

In all other respects, webhooks, mqtt etc. it’s communicating fine with bridge though.

I can’t see where to duplicate the container in Portainer.

14

if you click on the container near the top u have stop start restart

2019-03-13%2021_48_15-Portainer
2019-03-13%2021_48_15-Portainer769×80 5.73 KB

15

Thanks! I just found it. Deploying now with Host as the network.

16

That was a struggle.

Turns out that host network is not available on docker for Mac.

17

So, if I can ping the Google Homes from the container, publish and subscribe to MQTT broker and devices, run webhook automations from outside the network, what is it about Google Homes that is stopping them being added?

18

ahhh, thats a bugger.

19

A bugger, yes, but that doesn’t explain why I can’t access the Google Homes.

20

Adding them like this they do show up in the front tend and also in cast integration! Progress.

However, I can make them ‘chirp’ when turning on and off from the front end but they don’t speak the entered text. They do from the RPi, however.