can-utils VS shairport-sync

CAN is just glorified ethernet. https://github.com/linux-can/can-utils

I use a USB2CAN and the Linux SocketCAN can-utils.

Use the "SocketCAN Driver for Linux" from their support page and then you can use any of the CAN-Utils programs: https://github.com/linux-can/can-utils

For testing I found the CANtact more than adequate. Worked very well with Linux which has the SocketCAN system that basically lets you treat the CAN bus as a network socket. Great tooling exists in can-utils to help you do quick tests, debug a CAN network, and the sniffer is a great help for reverse engineering.

The Linux-CAN package appears to have some J1939/ISOBUS tools as part of can-utils.

SocketCAN, NMEA 2000, can-utils

I'm using slcand (to create a "normal" CAN device from SLCAN), candump and cansniffer from the can-utils package on Linux. It is available as a package in Ubuntu, probably also on other distributions. https://github.com/linux-can/can-utils

It's worth noting that shairport-sync exists. Perhaps it could be made easy by knitting some functions together?

You want SnapCast. You'd run snapserver on your Linux box and snapclient on your Pi's. Snapserver has support for Airplay (via shairport-sync) and Spotify (via librespot). I recommend using MPD for your music library, as I don't think PlexAmp can output audio in a way that's useful for snapserver.

I use shairport-sync for airplay (https://github.com/mikebrady/shairport-sync), complete instructions via: https://blog.adena.dev/blog/apple-airplay-on-raspberry-pi-in-7-easy-steps

If you’re interested, you might be able to get Airplay 1 & 2 support by running shairport-sync on your pi.

The plan is to run shairport-sync on the Omega 2 and have audio output to a 2x50w class d amplifier board.

To replace it, I've purchased in-ceiling speakers and a Control 4 Amp (C4-16AMP3-B) which I can control via the network. I plan on using shareport-sync for AirPlay and librespot for spotify as the sources to play music. 90% of the use for my whole home audio is for music.

ShairPort-Sync allows my Mac to listen for a AirPlay with multiple instances available, each pointing to different settings as per this GitHub Issue, which would allow me in theory to run multiple AirPort plugs and output each to an Alexa. Rarely would I ever need to have them playing all at once, and at this point I don't really care about maintaining pure audio quality or latency. I just need to be able to get out of my office and move to the kitchen, then back to my office without needing to spend a ridiculous amount of time trying to move what I was listening to on my iPad into my Echo Show

The benefit of the Pi is the open source software, in particular I use https://github.com/mikebrady/shairport-sync in order to turn it into an AirPlay 2 receiver, which I can stream to using my phone or laptop. It's my main way of sending audio to my hifi setup.

The only option I know of would be to use multiple raspberry pi’s running Shairport-Sync. I’ve been using the airplay 2 version for about a year and it works great. You might be able to build a server and run multiple instances of shairport with multiple audio cards. https://github.com/mikebrady/shairport-sync

So, after looking around, I realised that just like the Nest Hub 2nd gen, the Nest Audio also has a (sort of) exposed debug USB port. And these devices are (originally) running Linux. Since the Nest Hub 2nd gen has been jailbroken, I'm hoping that I can do the same on the Nest Audio, with a singular purpose: to inject a ShairPlay service, which would run parallel to the Chromecast services, which would allow me to use them as native AirPlay2 speakers.