Communication errors when adding second Google Home device

Setup, Configuration and Use Beginners
1

Hello,

I have an existing working setup where I used a Google Home Mini to make a sound when someone rings the door. Now I just bought a Google Nest Mini so I could play a sound also upstairs but this second device gives me communication errors. Can’t figure out why since the setup seems identical. I run OHv3 in a docker container.

When I try to play a test sound in the console it works only on my original device not the added one. If I change the audio sinc to the new Nest device I hear nothing, if I change it to the Google Home everything works. No error or anything in logs.

openhab> openhab:audio sinks
Google Home Mini Femke (chromecast:chromecast:7d925395a85b3208012668aae6130db0)
Google Nest Mini Living (chromecast:chromecast:297e9538146f65ff0daa52b0f87accc0)
System Speaker (enhancedjavasound)
Web Audio (webaudio)

When I try a test rule that is supposed to trigger both devices I get an error in the logs:

rule "Dinner Time!" // Only works with Google Home not Nest
when
  Item DinnerTime changed from OFF to ON
then
  playSound("chromecast:chromecast:297e9538146f65ff0daa52b0f87accc0","doorbell2.mp3")
  playSound("chromecast:chromecast:7d925395a85b3208012668aae6130db0","doorbell2.mp3")
end

Logs:

2021-05-01 14:56:31.715 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'DinnerTime' changed from OFF to ON
2021-05-01 14:56:36.916 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:7d925395a85b3208012668aae6130db0' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Interrupted while waiting for response
2021-05-01 14:56:40.554 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'chromecast:chromecast:7d925395a85b3208012668aae6130db0' changed from OFFLINE (COMMUNICATION_ERROR): Interrupted while waiting for response to ONLINE

Any suggestions?

2

You might want to check if the new Mini has access for downloading the sound files from openHAB. When you play a sound, openHAB sends a URL to the Mini to play. If it then cannot connect to the URL it will remain silent. :no_mouth:

Maybe it is in another subnet or blocked by a proxy or firewall? If you use Docker you’ve probably also configured a callbackUrl. That is the URL prefix used in URLs sent to the Mini to download audio files from.

3

Hi Wouter, thanks for the response. The mp3 however sits locally in the sounds folder and the callbackUrl is set at the binding so applies for both devices, I don’t think that’s it, both devices rely upon the same binding. They’re sitting next to each other on the same subnet also. Very strange.

4

Okay the issue got resolved today for me, turns out it was a broken Google Home Mini speaker. The replacement is working fine.