Looking for some guidance here for my very simple Speaker Selector setup. I have a Speaker Selector that can turn on/off my in ceiling speaker pairs via a very straight forward REST API. When you query the Speaker Selector with a GET, then you get the following response:
This seems to work just fine. I can setup the toggles in the UI and I can even ask Google Assistant to turn on / off the Dining Room Speakers which is super amazing.
My question is, can this be done in a simpler way with all of the switches in one entity? I can see three separate API calls going to the speaker selector, every 30 seconds - just to get the status. It seems like it should be able to do just one API call, and get all of the switch states. But maybe I’m over-complicating something that already works fine.
Sure! It’s version 3.0 of my speaker select project, which I have evolved to use a custom PCB. However it still needs plenty of refinement, it is working pretty well in my home.
I wanted to put some pictures here, but unfortunately I’m limited because I’m a new user.
There is a web interface, physical button front panel, and IR input if you want to use a remote control. On the old version, I had an API that was working with IFTTT (and Google Assistant), but after IFTTT started going subscription, I stopped using that. However, I realized I could just use a similar API for Home Assistant and get the functionality back!
Oh, BTW, I noticed you are a Kiwi and wanted to say “so am I”!! Except I moved to the states as a child and have only been back once in 2006.