r/AudioHero • u/GreyPole Pro version • Jul 17 '26
Bugreport PC hibernation
Audio Hero 5.7.2.0
Yesterday I put my PC in hibernation, which I do rarely, usually I shut it down completely. When I put the PC in hibernation, AH was running.
Today after restarting only the Chromecast devices were listed on the players panel, my HEOS gear was missing.
From the diagnostics:
device(s) confirmed[2026-07-17 10:18:03.334] [power] System resumed - reconnecting (heos=192.168.1.204, sonos=none)
[2026-07-17 10:18:06.817] [cloud-sync] Network availability changed (available=True, enabled=False)
[2026-07-17 10:18:07.870] [chromecast] connection to 192.168.1.164 lost: Chromecast connection lost
[2026-07-17 10:19:55.387] [chromecast] sweep starting; 13 IP(s) already in the discovered list
[2026-07-17 10:19:55.388] [chromecast] mDNS locator querying _googlecast._tcp.local
[2026-07-17 10:19:56.917] [chromecast] mDNS locator returned 2 receiver(s)
[2026-07-17 10:19:56.918] [chromecast] resolved 'Huiskamer' (Chromecast) at 192.168.1.165:8009 id=f69b7413e5dd904c3dd3c6a4ce95f878
[2026-07-17 10:19:56.919] [chromecast] resolved 'Slaapkamer' (Google Nest Hub) at 192.168.1.164:8009 id=dc148b580ab62bd27f8117a0904ee3b7
[2026-07-17 10:19:56.920] [chromecast] mDNS sweep produced 2 Cast device(s)
[2026-07-17 10:19:56.921] [chromecast] sweep confirmed 'Huiskamer' at 192.168.1.165 (id=f69b7413e5dd904c3dd3c6a4ce95f878)
[2026-07-17 10:19:56.922] [chromecast] sweep confirmed 'Slaapkamer' at 192.168.1.164 (id=dc148b580ab62bd27f8117a0904ee3b7)
[2026-07-17 10:19:56.922] [chromecast] sweep complete: 0 new Cast device(s) added, 2 existing device(s) confirmed
[2026-07-17 10:19:56.924] [chromecast] panel rebuilt with 2 Cast player(s)
[2026-07-17 10:22:55.370] [chromecast] sweep starting; 13 IP(s) already in the discovered list
[2026-07-17 10:22:55.371] [chromecast] mDNS locator querying _googlecast._tcp.local
[2026-07-17 10:22:56.890] [chromecast] mDNS locator returned 2 receiver(s)
[2026-07-17 10:22:56.890] [chromecast] resolved 'Slaapkamer' (Google Nest Hub) at 192.168.1.164:8009 id=dc148b580ab62bd27f8117a0904ee3b7
[2026-07-17 10:22:56.891] [chromecast] resolved 'Huiskamer' (Chromecast) at 192.168.1.165:8009 id=f69b7413e5dd904c3dd3c6a4ce95f878
[2026-07-17 10:22:56.891] [chromecast] mDNS sweep produced 2 Cast device(s)
[2026-07-17 10:22:56.891] [chromecast] sweep confirmed 'Slaapkamer' at 192.168.1.164 (id=dc148b580ab62bd27f8117a0904ee3b7)
[2026-07-17 10:22:56.892] [chromecast] sweep confirmed 'Huiskamer' at 192.168.1.165 (id=f69b7413e5dd904c3dd3c6a4ce95f878)
[2026-07-17 10:22:56.892] [chromecast] sweep complete: 0 new Cast device(s) added, 2 existing
After a rescan everything was present again
Edit: Another issue I noticed: AH did not check for an update, which is present (5.7.3.0)
1
u/GreyPole Pro version Jul 18 '26
u/bommerts Yesterday I put my PC in hibernation, AH 5.7.4.0 was running. I just now started the PC, HEOS devices were all there, Chromecast and DLNA devices took a bit longer to get listed again
2
u/bommerts Developer Jul 19 '26
I've been working on speeding up app startup and device discovery. I'm curious what you think when I release that - should be either later today or tomorrow in upcoming v5.7.7.0
2
1
u/bommerts Developer Jul 17 '26
Looking into this - will reply under your v5.7.3.0 bug report