Every time I post a new build I also post the build notes here. It has been a few times per week, sometimes once or even twice per day. I don't want to spam the group here, so I wanted to ask: Are these posts helpful? I could consolidate into a single post with an ongoing thread, or I could even just post the notes on the web site.
Let me know what you prefer. Thanks.
Critical fix: Device tone & system controls (Big thanks to GreyPole !)
EDIT: Alexa bridge still disabled / unavailable in this release
Feature: Alexa bridge option now available with simplified Amazon device setup
https://bommerts.com/audiohero/docs/#echo
I sort of rushed the Alexa bridge feature out so I am still marking that feature as experimental until I can complete further testing. It does work in my testing, but I had to balance testing time vs. getting the bug fix out. I would love your feedback on this feature. I am sure I will be releasing more updates to the feature and the helper.
I wanted to get this update out right away due to the critical nature of the bug GreyPole found.
New Firewall exceptions needed after new version AudioHero
Hi, I enjoy the rapid development of this app and glad I'm passively noticing all updates and progress. Also kudo's to the developer for detailed changelogs and, now in search of it, the excellent documentation and debug logging. Really a solid development for this product in regard to support and documentation too :)
I noticed lately that starting AudioHero started with a long delay searching for devices and then asked for a Firewall Exception. Disregarding earlier occurrences it just happened again so i wanted to see why this is. Started to look into the excellent documentation and enabled debugging in the log files but also checked the firewall rules.
I think the explanation is that with every update a firewall exception has to be made for this new location of the app. I can't really tell if this was before as I might have turned off the firewall or the app was located in the same folder.
Config: Windows 11, default firewall enabled which pops up to ask for add exception.
I might enable an exclusion based on the appname solely but this is what I think, the default firewall behavior is.
Hi everyone,
To support continued development of the app, the one-time license fee for Audio Hero will be increasing to $20 effective July 10th, 2026. This will help me continue to release updates, features, and fixes.
I may switch to a subscription model some time in the future ($x/mo or /yr), but will always honor those who purchased a one-time license forever without having to subscribe.
Do any of you use smart plugs to control power to your receivers, speakers, or subwoofers?
My office sub is on a Kasa outlet. When I want bass, I power on that plug. But I have to open my phone, open the app, find the plug, then power it on.
I have an idea to incorporate that as an automation and/or switch in Audio Hero.
My question to you all: Do you do the same? What brands of smart plugs do you use? Would this be a useful feature to you?
Audio Hero 5.4.4.0
I clicked the Rescan button on the Players tab to ad da device to the list. It should have added a third Google Cast device to the list, but that did not happen. According to the diagnostics the device was found. The device, 'Slaapkamer TV' has been shown in the list some days ago, but it is not always live. It is powered from the TV it is connected to, so it loses power when I switch of that TV. The other 2 devices are always powered.
[2026-06-24 09:54:36.884] [chromecast] sweep starting; 14 IP(s) already in the discovered list
[2026-06-24 09:54:36.884] [chromecast] mDNS locator querying _googlecast._tcp.local
[2026-06-24 09:54:38.447] [chromecast] mDNS locator returned 3 receiver(s)
[2026-06-24 09:54:38.448] [chromecast] ignoring 'Slaapkamer TV' at 192.168.1.128 - already in the discovered list
[2026-06-24 09:54:38.448] [chromecast] ignoring 'Slaapkamer' at 192.168.1.164 - already in the discovered list
[2026-06-24 09:54:38.449] [chromecast] ignoring 'Huiskamer' at 192.168.1.165 - already in the discovered list
[2026-06-24 09:54:38.449] [chromecast] mDNS sweep produced 0 new Cast device(s)
[2026-06-24 09:54:38.449] [chromecast] sweep complete: 0 new Cast device(s) added
[2026-06-24 09:54:59.802] [chromecast] opening Cast control connection to 192.168.1.165:8009
[2026-06-24 09:54:59.903] [chromecast] Cast control connection to 192.168.1.165 established
[2026-06-24 09:55:00.830] [chromecast] opening Cast control connection to 192.168.1.164:8009
[2026-06-24 09:55:00.856] [chromecast] Cast control connection to 192.168.1.164 established
[2026-06-24 09:57:36.939] [chromecast] sweep starting; 14 IP(s) already in the discovered list
[2026-06-24 09:57:36.940] [chromecast] mDNS locator querying _googlecast._tcp.local
[2026-06-24 09:57:38.506] [chromecast] mDNS locator returned 3 receiver(s)
[2026-06-24 09:57:38.507] [chromecast] ignoring 'Slaapkamer TV' at 192.168.1.128 - already in the discovered list
[2026-06-24 09:57:38.507] [chromecast] ignoring 'Slaapkamer' at 192.168.1.164 - already in the discovered list
[2026-06-24 09:57:38.508] [chromecast] ignoring 'Huiskamer' at 192.168.1.165 - already in the discovered list
[2026-06-24 09:57:38.508] [chromecast] mDNS sweep produced 0 new Cast device(s)
[2026-06-24 09:57:38.509] [chromecast] sweep complete: 0 new Cast device(s) added
Edit: When I turn off Google Cast in settings and then enable it again, all 3 show up on the players tab