Had this not happened sledgehammers would have been going through speakers.

I would still prefer they rolled back to the old app, or made it as an optional re-release.

The actual Sonos integration still works (IIRC) with most of my speakers, in that I can use them as targets in automations involving audio (sees them on network and integrates directly).

The AirSonos add-in makes the Gen1 devices show up on your network as AirPlay targets. IME, AirSonos can be a little buggy since you're going through a bridge but not enough to really matter. It's functional value far exceeds the frustration (90% of the time it works 100% of the time).

With all this, you might be stuck with the old room names set when you had access to the Sonos native app. I think AirSonos lets me mask those names, but every now and then I have to remember that, oh yeah, the Play3 labeled Kitchen is actually now actually bedroomxyz. But again, it works for all intents and purposes. I can airplay from sonos, audible, etc to my gen1 sonos equipment, and that's waaaay better than tossing them into a chinese river (recycling) or a local landfill.

The EEVBlog video about the "Fronos" project (https://www.youtube.com/watch?v=IeIk-4ItQ70) involved embedding a new amp with bluetooth into the Play:5 chasis, and there are certainly amps these days you could consider that have built-in airplay. Something for the project queue. For me, using the above with Home Assistant keeps this project at the bottom of the queue, though it's probably the "right" solution long term.