v1.3.18 — Google Home and Nest speakers now show up reliably.
- Fixed: a Google Home / Nest speaker on the same Wi-Fi could stay invisible for an entire session. Discovery asked the network only once at startup, so a speaker whose reply was lost — or that was asleep or booting at launch — never appeared, and pressing Rescan could not help.
- Cast devices are now found three ways: repeated mDNS queries, an SSDP DIAL search, and a direct scan of your local network for Cast devices. The last two work even on routers that block multicast between Wi-Fi bands or between Wi-Fi and Ethernet.
- Rescan now genuinely re-searches every channel and waits for the result instead of returning immediately.
- Fixed: Google Home speaker groups collided with their lead speaker, so only one of the two appeared — and casting to a group played on the lead speaker alone instead of the whole group.
- Speakers that reply without a name are now asked for it directly, instead of showing a raw hex device id.
- Once found, a Google Home behaves exactly like a Nest device for recitation, Adhan and schedules — including synchronised playback alongside this computer's speakers and Bluetooth outputs.
Installed apps (v1.2.0+) pick this up automatically on their next update check.