No DFS events in the logs.
I was able to catch it in the act. The speakers went dead and looking at the log, the channel changed to get better reception less than 30 seconds before. The log shows the speakers dissociate while every other device doesnt even bat an eye. Some report dissociation and then less than 2 seconds later reassociate. I bought this:
https://www.tp-link.com/us/home-networking/wifi-router/tl-wr902ac/
And set it up in client mode as a simple wireless bridge. The speakers have an RJ45 on them for hardwired connections. I factory reset the speakers and told them not to connect to my wireless network. They connected via this TP Link device smooth as butter and have been happily listening to music for days with not a single drop out with a few channel changes. To me, this pretty conclusively points the finger at the speaker's wireless implementation. That they hit an unrecoverable crashed state (they must be power cycled to come back online) is an indicator that the driver or whatever governs their operation is not familiar with the circumstance where a channel changes. Computers need to know what to expect or they dont work right. That all sound about right to you guys?
Networking geek since high school where I got half of a CCNA. Played Marathon II and Infinity over localtalk.
Made many a network over the years, now de facto admin of a retreat center with some of this fine Meraki hardware.
Fortune 100 Tech veteran/refugee.