hi, further note i can see that onall my sonos’ i can see the value of rccurl is
and when this is used the level field returned is actually blank, currently my sonos’s aren’t in a group, and i’m pretty sure they weren’t when they were created (i’m just gonna test that now as i can see that rccurl is defined at the point of creation from the parent smartapp)
@ule so i have just confirmed, when a Sonos is not in a group and added via the smartapp the rccurl is populated with /MediaRenderer/GroupRenderingControl/Control which when used does not return a level value
but /MediaRenderer/RenderingControl/Control returns a value.
the section of the logs when trying to use the volume slider is as follows, i also tried muting & unmuting
If populating rccurl as “/MediaRenderer/RenderingControl/Control” will solve the issue, why do we need another solution ?
You said it breaks all other standard DLNA mediarenderer device.
You mean , if this is hardcoded, Sonos speaker works but other DLNA mediarenderer devices fail. Is that correct ?
If so, as a workaround we can create a copy of the mediarenderer device and use it specifically for Sonos devices.
if you want to use that until a new version is released that is upto you. There is a more eloquent way of doing this via the discovery section of the smartapp of hardcoding this when a sonos is is discovered but not when a sonos is device is discovered.
I could use some assistance. I have enabled upnp on my router Cisco E3000. I am using a Jongo S3 speaker. I have followed the instructions and created the App and the Device type Handler. I am also using the Smart Alarm app and have enabled custom notifications on the Jongo S3 but the text to speach is not coming through, I can see in the recent events of the Jongo that somethings is trying to fire but nothing comes through. Any Ideas, did I do something wrong?
I am having some issues with my Kodi on a tablet setup (using Network Audio Remote for Android as CP). It was working fine over the last couple of days. As of this morning, any time I open up the Things portion on my ST app and try to open the speaker/renderer, ST app crashes every time. I know ST is having issues galore over the past several weeks and they are in the process of resolving them now. None of my other 30+ things do this when I open up the thing in detail in the app (lights, switches, sensors, etc.). I have uninstalled and reinstalled several times this morning. I have tried using BubbleUPnP and others on my tablet to no avail and they’re not even discovered. Kodi is discovered quickly, as it always has been, and try to re-setup the speaker, but just keeps crashing. The funny this is that I can manually play a song on my tablet and view the list of things on the ST app and it will show my Kodi speaker thing as “playing”. But as soon as I touch it to open up the player it shows a white screen and crashes. Any ideas or should we chalk it up to the ST issues?
On another note, anyone else have a good DLNA software-on-a-tablet setup for music and notifications? Kodi and NAR seem to be okay, but just curious if there was something better. Thanks in advance!
I think I have a clue on what happened.
According to my Ivona usage statistics, I could not use Ivona after 27th (sunday) midnight.
That’s when DST starts in my country (Turkey)
So it might be an issue of signing POST and GET requests with correct date.
What do you think ?
What is the tts.php doing in this transaction ? Does it use an hardcoded timezone / DST setting ?