Gladys Assistant 4.32: Sonos integration is available! đŸŽ”

News
21

I’m looking into this and I’m really struggling


I opened all the ports indicated on the SONOS site: Configurez votre pare-feu pour fonctionner avec Sonos | Sonos

That didn’t work. I found this post on the Home Assistant forum: Sonos - which ports do I need to open for auto-discovery? - #9 by jjlawren - Configuration - Home Assistant Community

So, I opened a UDP port range: 32768-60999

It works but the range seems huge to me.

I’m still looking (if you have any suggestions, I’m all ears).

22

You should monitor your network on the Sonos test IP addresses to see which ports are used (which also amounts to reading the blocking logs)

You could maybe create a specific rule that

1 Like
23

on Windows download

and scan your network, it should show your Sonos devices and the ports open on them

on Linux

and the same but in the command line

1 Like
24

I don’t know since when, but the link to the Sonos documentation doesn’t work, it redirects to :https://gladysassistant.com/fr/docs/undefined/sonos

Instead of redirecting to :

25

Yes, apparently this has been fixed!! Available in the next version

1 Like
26

Hello,

I integrated SONOS and set up the speaker last December. Since then, apart from a few successful tests, I haven’t been able to get my speaker to speak during regular use. I test from time to time, starting from scratch several times, deleting the integration and the scene, but nothing works.

Is anyone else experiencing the same issue?

27

Hi @Jluc :slight_smile: I’ll let others reply if they also have problems — I’m curious to know whether you’re the only one experiencing this issue!

On my side, I looked a bit into the Sonos library and found 2 possible improvements:

  • There is a timeout for playing the voice announcement part, which is currently 10 seconds. If your network is a bit slow, or the TTS API takes more than 10 seconds to respond, that could explain the issue. I’ll increase it to 20 seconds.
  • If that doesn’t improve the issue, it seems possible in the library we use for the Sonos part to pass an environment variable to enable logs and better understand what’s failing on their side:

Screenshot 2024-05-27 at 14.40.50
Screenshot 2024-05-27 at 14.40.501604×1142 122 KB

Source: Getting started - Sonos

Is restarting your Gladys container with the environment variable something within your skills? (If not, tell me and we’ll find another solution)

In the meantime, I’ve already made a PR for the first point to add a bit more logs on the Gladys side:

28

Unfortunately, I have no skills and I’d rather not tinker and break everything :slight_smile:

1 Like
29

I understand!

We’ll first look at the PR to increase the timeout and we’ll see afterwards if we need more logs :slight_smile:

I’ll keep you posted as soon as it goes into production.

30

Hello :slight_smile:

The audio feature in Gladys seems to be well progressed by this integration, but have you thought about all those who don’t use SONOS hardware?

Wouldn’t it be possible to separate the integration/use of sound in a scene from the playback method, in order to more broadly target everything currently available on the market (Amazon Echo, Google Home

2 Likes
31

Hi @jean_bruder :slight_smile: It’s already the case!

As always in Gladys, the core is separated from the integrations that bridge a Gladys device and the