I was just curious if anyone has Airgroup working with their Google Home Mini specifically Have a TAC Case open concerning the Google Home Mini not showing up as an AirGroup Server (ArubaOS 6.5.3.3 and 6.5.4.0).

The Google Home works perfectly, but not the Google Home Mini - reviewing the mDNS packets between the Google Home and Google Home Mini - they look identicial.

If I disable Drop Broadcast and Unknown Multicast and disable Airgroup - the devices can discover each-other.

One of the attributes I noticed in the user-debug logs called origin has helped narrow down the problem: 1.

Non-Working Google Home Mini - origin2 Developer informed me when an mDNS packet is received from a client termintating to the controller - is flagged as origin1 - if an mDNS packet is received from another controller on the same VLAN - such as with when doing AirGroup Clustering its flagged as origin2.

In our case - the controller is discarding the record instead of classifying it as an AirGroup server.

We did enable AirGroup clustering just in case to check for any changes.

No change. So for whatever reason that DeveloperTAC is unsure yet, the controller is classifying the mDNS response of this specific Google Home Mini - (manufacturerd a month earlier than the working one - with a MAC Address ending in C) - as originating from outside the controller.

It is because in header format, we attach a pattern 0xde to detect if its from different controller or not.

Since the MAC address of this mini contains 0xde it looks like the header is getting corrupted with this pattern 0xde and hence we are seeing this problem.

Whats bizarre - on a hunch - went and bought another Google Home Mini (same firmwaresoftwareetc - only difference is a month in the manufacturing date).

That would point to a defective device - however, mDNS works just fine on a home network - as well as on an SSID with multicast enabled and AirGroup DISABLED.

What myself and TAC saw in the debug logs for mDNS was periodic cases where the mDNS responses were being discarded.

My knowledge of mDNSSSDP is still low - although Ive been the only one crazydetermined enough to understand these devices to the point that Im jokingly the new multicast administrator.

Google Home For The Bluetooth And Use

My theory is if I were to forgo the Bluetooth and use just Wi-Fi Direct - I should get the same end-success I had with Android.

Google Home For The Update The Network

I still need to do more testing Note - If the Google Home loses its network connection (IoT SSID) stops broadcasting - The Google Home will begin broadcasting its own SSID again (Google-Home-Name) to update the network config.

Google Home For The Mac