Containerised deployment icw Notify

[Superbert25]

Hi,
I experience the following issue: When I send a notify to a Sonos device, the device stops playing, changes the volume to the notification volume, plays the notification url, returns the volume to the previous level. The previous source is however not resumed playing.

What I have tried to resolve the issue:

• Use the latest Beta
• Set experimental to true
• Use notifytwo
• Use different sources for playing music (tunein radio, apple music)

I observed various behaviors, but was by no means able to automatically resume the playing. The source sticks per default to the notification URL.

Maybe not relevant, but I'm migrating away from my current automation solution FHEM. Within FHEM there's a Sonos module that has a separate command called playURLtemp which can be used for notifications (this one works flawless). I have to admit that FHEM is not running in a container, I don't know if it works flawless from inside a container.

Any suggestions to resolve this issue are welcome!

PS: Thanks for all the effort that has been invested into this application.

[svrooij]

Just don't use the "faulty" notifytwo method..... See svrooij/node-sonos-ts#119

This was an (in my opinion) failed experiment. The regular notify method (when runnning in experimental mode) will use the native implementation to start notifications. Which is explained in details here.

If this answers your question, be sure to mark it as answered

[Superbert25]

Very sorry for bothering you, but I found out that I induced an error in my MQTT topic during trouble shooting. Now after correcting that error, using your latest beta, setting experimental=true, it works like a charm! Thanks a lot for your support and creating this application.

[svrooij]

You're welcome!!

Spread the word about this cool way to control your soeakers