Google home max bugged on 275994

[Windhoos]

Hello there,

Since version 275994 my two paired google home max have had terrible performance. After a reboot/hardware reset, they work for a couple of days but then they become unresponsive to Casting audio or google home voice commands. I also get a error that the speakers cannot be reached.

Please fix this.

[Dan_A]

Hi Windhoos,

I'm sorry that you're having trouble with your Google Home Max ― let's check it out. A few questions: when did you update your Nest devices? What is the exact error message when casting or giving voice commands? Is the behavior up to now? When you say hardware reset, was it the same way as what you see on this guide? If so, it would help a lot if you could do a sequential reboot first. Unplug the power cord of your router followed by your Nest speakers. Plug them back in after 3 minutes tops. Restarting your phone might also help.

Best,

Dan

[Windhoos]

Hi there,

Thanx for the reply!

Yes it was exactly what i did to reset it from this guide using the small button on the back.

This is my exact device info:

Device information
Device name
Max
Home
Home
Placement Woonkamer
Wi-Fi
Look Morty Im a router 24ghz
Forget
Preview program On (waiting for next preview firmware update)
Open source licenses
Technical information
Left speaker:
System firmware version: 275994 Cast firmware: 1.56.275994 MAC address: 20:DF:B9:66:2F:9F Country code: NL IP address: 192.168.2.30
Right speaker:
System firmware version: 275994 Cast firmware: 1.56.275994 Language: English (United States) MAC address: D8:6C:63:54:BE:72 Country code: NL IP address: 192.168.2.29

[Dan_A]

Hey there,

Thank you for the information and we appreciate your patience. How about if we try each Google Home Max but this time around, set them apart since you mentioned that they're on a speaker pair. Unpair them and set them close to your router. Monitor if the behavior persists.

Keep us posted.

Thanks,

Dan

[Windhoos]

Hi there,

Actually the speakers are 5 meters from my router. There is a range extender between them as well.

[Windhoos]

I also removed all the additonal wifi acces points but no luck.

The weird thing is only my right speaker of the group disconnects, and that's the speaker closest to the router.

When it disconnect I also can't see the speaker pair anymore when i cast.

Rebooting always fixes the issue for a couple of days.

[Dan_A]

Hi Windhoos,

Apologies for the delayed response. If you have access to your router GUI page or router settings through their website and do the following:

• Channel interference (channel congestion from too many devices, optimal channels for 2.4GHz is 1,6, or 11)
• UPnP should be enabled.
• AP Isolation disabled.
• Make sure a VPN or Proxy Server is not configured on the network.
• Confirm distance between the router, setup device and Google Home are optimal.
• MAC Filtering should not be enabled on the router.
• Preferred DNS settings: 8.8.8.8 for the primary and 8.8.4.4 for the secondary.

If in case you're not able to gain access, please contact your ISP or router's manufacturer for assistance. Also, for confirmation, what Nest speakers are on the speaker pair and which are not? If possible, remove them as speaker pair and test them out individually.

Looking forward to your response.

Best,

Dan

[Windhoos]

Okay i wil try that.........

[Princesss]

Hi Windhoos,

Thanks! I'll keep this thread open for few more days until you try the steps. Keep us posted!

Best,

Princess

[Dan_A]

Hey there,

I wanted to follow up and see if you still need help. Please let me know if you are still having any concerns or questions from here, as I would be happy to take a closer look and assist you further.

Regards,

Dan

[Windhoos]

Hello there, i think it's fixed. The problem was with an access point that it did not understand that both google devices had the exact same name on the network. It was fixed when i renamed one of the devices.

[Windhoos]

This is also weird because all other google devices on my network have a name with an unique identifier except for the google home max which just called itself 'google home max'.

[Dan_A]

Hi Windhoos,

I'm glad that you're able to work this out. It would be best to have the name set as Google Home Max. As they say, simple is better.

As we got our resolution here, I'm going to mark this one as resolved and will be closing this thread after 24 hours. Please feel free to open up a new thread if you have other questions or concerns.

Kind regards,

Dan

[Windhoos]

well no if you read what happened was that my access point got confused because i had 2 products with the hostname 'google-home-max' apparently a different mac and ip address was not sufficient. I now have one 'google-home-max' and a 'google-home-max2', that solved the problem. I guss the speakers have problems with bonjour ?

[Dan_A]

Hey there Windhoos,

Thank you for providing the solution in the Community. That might explain why this concern is happening. Having 2 different names got us the solution and from there, the one access point that got confused is now accepting 2 names you created. Hats off to you! It looks like we can consider this one complete, so I will lock the thread in 24 hours unless I can help out with anything else. 

Best,

Dan

[Jake]

Hey there,

I wanted to check in and see if you managed to see Dan's post. Please let me know if you have any questions from here. I would be happy to assist, and make sure you are good to go.

Best regards,
Jake

[Windhoos]

Thank you! I just repled.