It seems ytm is not supported in the app, but I'm not sure if that's a problem for my use case or not. If Google home "casts" requests then I think it'll work for me.
I sent them a message asking
Do WiiM Pro devices show up as speakers/streamable devices in apps (for casting) or can Google Home see them. Can they be assigned as the default speaker of a google home device?
I've got 11 CCAs in operation right now... That would be a pricey swap. Might be worth buying one and playing around. Also need to see if it supports yt music
My whole house audio runs off a product Google no longer makes unfortunately (Chromecast audios).
There's, no like-for-like new version, and no good replacement that I've found. Thankfully, this was a fixable problem and they fixed it vs. Just EOLing them.
I'm in the same boat. I'd say that my current setup is still not back to 'normal' since the issue with the certificates on the second gen devices.
I was able to cast to a CCA yesterday for a few hours after rebooting it again.
I have, over the years gone all in with the CCAs which is great when it works but sucks being tied to google. I have 11 active running CCAs connected to two separate 12 channel amps that have wired speakers throughout my house.
I use Google Mini's in those locations with their default speaker set to the CCA feeding that room's speakers. I also have groups "Basement" "Upstairs" "outside" etc that allow me to group them into larger zones. This is all very awesome when it works, but like we found out last week falls apart when there's a problem on that house of cards.
We can via apps directly manually 'cast' from YTM or Spotify or whatever (podcast app) or just ask the mini in the room to play music or play music on 'group speaker name'.
I got here from 'Casatunes' which when I was using it, was a PCIE card you installed in a windows machine and then installed their software (that ran on IIS) and it created a web service where the PCIE card (a soundblaster) had 6 3.5mm jacks (6 zones) as output, and then the software allowed you to assign 4 different inputs. Biggest issue I had with it, is as I moved from Sirius XM to streaming the service I opted to go with wasn't supported. Eventually I migrated to the CCA approach.
I'd love a way to setup 11 Pi's (although not at today's prices) with some open source protocol that replaced googles casting. The problem then would be getting some local speaker (google mini) to interact with it, or even your phone (spotify/ytm to 'cast' to that open protocol). Whatever the long term solution it would need to be easy to use or nobody but me will use it.
spin up a second pihole docker and upgrade them separately so they can failover to the other one while upgrading. I do not have an issue with 20min lose of DNS after updating my pi.hole docker, but I did spin up a second one when I wanted to try unbound+pi.hole and just kept them both up/running.
The stress was quite high today for sure as well as a 41 sleep score and I've been at 5 body battery half the day :(
Sorry, been sick as hell today. I have just always been happy with the features and capabilities.
I like that there's no subscription to your data too.
I'm game and here to contribute where I can :)
Fenix 8 51mm amoled, following a long line of Garmin watches back to around 2013 when I switched from polar stuff over to a 910xt.
I wouldn't notice
I pay what I consider a pretty affordable price for this ($65/yr), and support HA dev community. It also allows auto-syncing devices to my Google Assistants. No affiliation but an easy way to get something more and give a little back.
Everything about these two spacecraft is just amazing. It's going to be quite a sad day when they transmit their last byte of data to our little planet. Reading about all the things we've done to keep talking to them. The redundancies that they're running on etc... Fascinating stuff
The thumbnail totally looks like the back of someone with long hairs head. I assumed it was a picture of someone taking a picture of a whale. :)