Replies: 2 comments 2 replies
-
Hi, first of all sorry for my late response. I just wanted to test the experimental version, but I'm not sure if it was correctly activated. Result within the logfile: According to your mail a message within the logfile should appear: Was the activation sent correctly? |
Beta Was this translation helpful? Give feedback.
-
Hi, I'm running it in docker, managed by Portainer. I added the variable, see screenshot: Unfortunately I don't think that the function is activated, log looks like this: ` 2024-05-05T07:18:44.798Z [Information] LogLevel changed to information 2024-05-05T07:18:44.918Z [Information] Found 2 sonos speakers 2024-05-05T07:18:45.526Z [Information] Mqtt connection changed to connected: true ` Any idea what else I could try? |
Beta Was this translation helpful? Give feedback.
-
Sending an audio notification has been possible for years with this app. Since the latest beta you use the notifications using the native Audio Clip endpoint. This used to be cloud only, but someone discovered it to be no longer cloud only.
We are not ready to switch this for everybody, but you can try it out by starting Sonos2Mqtt with the
SONOS2MQTT_EXPERIMENTAL
environment variable set totrue
. This will switch thenotify
and thespeak
command to use the Audio Clip endpoint. You can also use the--experimental
flag if you're still running this app from the command line.Please provide your feedback below.
Beta Was this translation helpful? Give feedback.
All reactions