No ^^ Not yet
The parts are good though ^^
Is it possible to store the text in a variable so that Sonos can play it directly ??
Not right now, but that could be a nice evolution ![]()
However, in terms of cost, on setups like yours itâs quite expensive to really send everything on each request
So basically, for the AI to be able to have the information about your whole home, I have to send the AI all the values from your sensors, and that creates a huge chunk of data on your side!
If I keep the same limit as currently (1000 requests / month / account), that exceeds the budget
Do you think we could send only certain devices?
QuestionâŠ
Wouldnât it be interesting to select a request type within the scenes.
In the case of sensor retrieval, send an initial request with the appropriate context that returns only the categories/types to take into account and then send them back to it
Because indeed, sending the entirety of the sensors with every message⊠I understand that becomes costly ^^ it necessarily has to be done in several steps.
Maybe another feature later for the sensors, right?
Thatâs the approach thatâs already being used right now if you request a temperature.
Here, the idea was really to give the AI the full view of your home to allow the AI to answer very complex questions like:
« The alarm went off at my house â do you see anything strange at my place? »
The idea was really to allow the AI to answer open-ended questions, not just to respond to requests (we already know how to do that)
Still, it might be a bit premature, especially since we can see the AI hallucinates quite a bit, so itâs not very conclusive for a fairly high cost.
I think Iâm going to remove this option for now
@Terdious I rebuilt a Docker build without sending the devices!
Available here:
gladysassistant/gladys:ask-ai-in-scene
Do you see anything else that would be essential for this first release?
Great !!
-
Implementing switches in the same way as lights would be great
-
being able to make Sonos speak the response, but like you said that can come later ^^
I think the current implementation is a good thing !! Itâs just that weâre almost frustrated at not having more. But one thing at a time, and your usual approach of building small pieces step by step is, I think, a very good thing.
I, who wasnât convinced at all at the start, am now pushing the thinking in that direction in my personal project. In the end it moves much faster and itâs a comfort for coding/ review
A big thank you to you for that
^^
Thanks for your feedback!
Regarding switches, I just looked and itâs a topic in its own right, so itâs outside the scope of this development. We can go into detail in another thread
I invite you to create it if youâre interested!
Making the Sonos speak isnât that complicated but I think we can keep that for a later time. Iâd welcome a feature request as well to gauge interest!
I think weâll deploy this first development as is to get more feedback, thanks again for all your testing ![]()
This feature is available in Gladys Assistant 4.48:
Iâm closing this thread to free up the votes!
Requests created!



