Announcement

Collapse
No announcement yet.

Sonos Speak issues on steropairs

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Sonos Speak issues on steropairs

    Dirk,

    I have several issues with linkgroup speak actions. I have 2 stereo pair in my home

    But every time i start to speak it announces on one of the speakers of the steropair but next to that i also get these errors after the speak action;
    jul-11 18:56:03 Sonos Error ERROR in PlayURI for zoneplayer = Serre with UPNP Error = Read only tag / Transport is locked / Access denied. URI=x-rincon-queue:RINCON_7828CAE41B3801400#0 and isObjectID = False, MetaData=, Error =MyUPnPService.InvokeAction for ServiceID = http://192.168.1.168:1400/xml/AVTransport1.xml while sending Action = SetAVTransportURI for URI = http://192.168.1.168:1400/MediaRende...nsport/Control and Request = 0 x-rincon-queue:RINCON_7828CAE41B3801400#0 UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 1023 with error = The remote server returned an error: (500) Internal Server Error.
    jul-11 18:56:02 Sonos Error ERROR in PlayURI for zoneplayer = Woonkamer with UPNP Error = Read only tag / Transport is locked / Access denied. URI=x-rincon-queue:RINCON_7828CAE365CA01400#0 and isObjectID = False, MetaData=, Error =MyUPnPService.InvokeAction for ServiceID = http://192.168.1.169:1400/xml/AVTransport1.xml while sending Action = SetAVTransportURI for URI = http://192.168.1.169:1400/MediaRende...nsport/Control and Request = 0 x-rincon-queue:RINCON_7828CAE365CA01400#0 UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 1023 with error = The remote server returned an error: (500) Internal Server Error.
    jul-11 18:56:00 Event Event Trigger "sonostest test spreek"

    linkgroup example;

    Click image for larger version

Name:	linkgroups.png
Views:	65
Size:	169.3 KB
ID:	1315142

    in this case woonkamer is woonkamer_LF
    and Serre is Serre_LF

    When i try to add woonkamer _RF and Serre_RF I get these again;
    jul-11 19:08:02 Sonos Error ERROR in PlayURI for zoneplayer = Serre with UPNP Error = Read only tag / Transport is locked / Access denied. URI=x-rincon-queue:RINCON_7828CAE41B3801400#0 and isObjectID = False, MetaData=, Error =MyUPnPService.InvokeAction for ServiceID = http://192.168.1.168:1400/xml/AVTransport1.xml while sending Action = SetAVTransportURI for URI = http://192.168.1.168:1400/MediaRende...nsport/Control and Request = 0 x-rincon-queue:RINCON_7828CAE41B3801400#0 UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 1023 with error = The remote server returned an error: (500) Internal Server Error.
    jul-11 19:08:02 Sonos Error ERROR in PlayURI for zoneplayer = Woonkamer with UPNP Error = Read only tag / Transport is locked / Access denied. URI=x-rincon-queue:RINCON_7828CAE365CA01400#0 and isObjectID = False, MetaData=, Error =MyUPnPService.InvokeAction for ServiceID = http://192.168.1.169:1400/xml/AVTransport1.xml while sending Action = SetAVTransportURI for URI = http://192.168.1.169:1400/MediaRende...nsport/Control and Request = 0 x-rincon-queue:RINCON_7828CAE365CA01400#0 UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 1023 with error = The remote server returned an error: (500) Internal Server Error.
    jul-11 19:07:59 Event Event Trigger "sonostest test spreek"

    I also tried only selecting woonkamer _RF and Serre_RF as destination but same result


    controlling all players via the hs3 devices is no issue. No groups are paired however for example the 2 "woonkamer" speakers in the sterogroup stae this:

    Serre_RF:

    Stopped

    Paired to Serre

    HomeSeer Announcement

    Dirk Corsus

    SonosController

    Serre (SERRE_LF)

    Stopped

    Linked to Serre_RF

    HomeSeer Announcement

    Dirk Corsus

    SonosController


    I tried also installing the plugin in a clean VM with HS3, exactly the same result. Any thoughts? First of all i want to get rid of these errors (OCD ) and i would prefer the sterogroups to play the announcement left and right.


    regards,

    bart


    Attached Files
    Regards Bart
    ------------------------------------------
    Win7 64Bit on Intel NUCI7 with SSD
    HSPRO 3.
    Devices; 1370 Events; 691

    Jon00 Scripts, JowHue, HSTouch, Plugwise, Z-wave, Ultranetatmo, Ultracam, PHlocation, BLUSBUIRT, MeiHarmony, Buienradar, MEiUnifi Pushover 3P, Random, Nest HSPhone and Blueiris

    Visonic Powermax Alarm System (HS3) Interface: http://www.domoticaforum.eu/viewtopic.php?f=68&t=11129

  • #2
    Originally posted by bartbakels View Post
    Dirk,

    I have several issues with linkgroup speak actions. I have 2 stereo pair in my home

    But every time i start to speak it announces on one of the speakers of the steropair but next to that i also get these errors after the speak action;
    jul-11 18:56:03 Sonos Error ERROR in PlayURI for zoneplayer = Serre with UPNP Error = Read only tag / Transport is locked / Access denied. URI=x-rincon-queue:RINCON_7828CAE41B3801400#0 and isObjectID = False, MetaData=, Error =MyUPnPService.InvokeAction for ServiceID = http://192.168.1.168:1400/xml/AVTransport1.xml while sending Action = SetAVTransportURI for URI = http://192.168.1.168:1400/MediaRende...nsport/Control and Request = 0 x-rincon-queue:RINCON_7828CAE41B3801400#0 UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 1023 with error = The remote server returned an error: (500) Internal Server Error.
    jul-11 18:56:02 Sonos Error ERROR in PlayURI for zoneplayer = Woonkamer with UPNP Error = Read only tag / Transport is locked / Access denied. URI=x-rincon-queue:RINCON_7828CAE365CA01400#0 and isObjectID = False, MetaData=, Error =MyUPnPService.InvokeAction for ServiceID = http://192.168.1.169:1400/xml/AVTransport1.xml while sending Action = SetAVTransportURI for URI = http://192.168.1.169:1400/MediaRende...nsport/Control and Request = 0 x-rincon-queue:RINCON_7828CAE365CA01400#0 UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 1023 with error = The remote server returned an error: (500) Internal Server Error.
    jul-11 18:56:00 Event Event Trigger "sonostest test spreek"

    linkgroup example;

    Click image for larger version

Name:	linkgroups.png
Views:	65
Size:	169.3 KB
ID:	1315142

    in this case woonkamer is woonkamer_LF
    and Serre is Serre_LF

    When i try to add woonkamer _RF and Serre_RF I get these again;
    jul-11 19:08:02 Sonos Error ERROR in PlayURI for zoneplayer = Serre with UPNP Error = Read only tag / Transport is locked / Access denied. URI=x-rincon-queue:RINCON_7828CAE41B3801400#0 and isObjectID = False, MetaData=, Error =MyUPnPService.InvokeAction for ServiceID = http://192.168.1.168:1400/xml/AVTransport1.xml while sending Action = SetAVTransportURI for URI = http://192.168.1.168:1400/MediaRende...nsport/Control and Request = 0 x-rincon-queue:RINCON_7828CAE41B3801400#0 UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 1023 with error = The remote server returned an error: (500) Internal Server Error.
    jul-11 19:08:02 Sonos Error ERROR in PlayURI for zoneplayer = Woonkamer with UPNP Error = Read only tag / Transport is locked / Access denied. URI=x-rincon-queue:RINCON_7828CAE365CA01400#0 and isObjectID = False, MetaData=, Error =MyUPnPService.InvokeAction for ServiceID = http://192.168.1.169:1400/xml/AVTransport1.xml while sending Action = SetAVTransportURI for URI = http://192.168.1.169:1400/MediaRende...nsport/Control and Request = 0 x-rincon-queue:RINCON_7828CAE365CA01400#0 UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 1023 with error = The remote server returned an error: (500) Internal Server Error.
    jul-11 19:07:59 Event Event Trigger "sonostest test spreek"

    I also tried only selecting woonkamer _RF and Serre_RF as destination but same result


    controlling all players via the hs3 devices is no issue. No groups are paired however for example the 2 "woonkamer" speakers in the sterogroup stae this:

    Serre_RF:

    Stopped

    Paired to Serre

    HomeSeer Announcement

    Dirk Corsus

    SonosController

    Serre (SERRE_LF)

    Stopped

    Linked to Serre_RF

    HomeSeer Announcement

    Dirk Corsus

    SonosController


    I tried also installing the plugin in a clean VM with HS3, exactly the same result. Any thoughts? First of all i want to get rid of these errors (OCD ) and i would prefer the sterogroups to play the announcement left and right.


    regards,

    bart

    can you post the full debug log? Thanks, Dirk

    Comment


    • #3
      which version of the Sonos PI are you running?

      Comment


      • #4
        The one in the beta section, i will post the debug log tomorrow
        Regards Bart
        ------------------------------------------
        Win7 64Bit on Intel NUCI7 with SSD
        HSPRO 3.
        Devices; 1370 Events; 691

        Jon00 Scripts, JowHue, HSTouch, Plugwise, Z-wave, Ultranetatmo, Ultracam, PHlocation, BLUSBUIRT, MeiHarmony, Buienradar, MEiUnifi Pushover 3P, Random, Nest HSPhone and Blueiris

        Visonic Powermax Alarm System (HS3) Interface: http://www.domoticaforum.eu/viewtopic.php?f=68&t=11129

        Comment


        • #5
          Originally posted by bartbakels View Post
          The one in the beta section, i will post the debug log tomorrow
          OK.
          To recapture the issues:
          1/ you have some errors but not sure they do anything wrong
          2/ the announcement only comes out of one of the 2 speakers of a stereo pair.

          If you installed the PI in a fresh VM, did you install totally fresh or you restored a DB? Can you post a screenshot of the player table.

          Correct?

          Comment


          • #6
            I installed a fresh hs3 and sonos controller. No db restore, just an empty install. Screenshot will also follow tomorrow.

            bart
            Regards Bart
            ------------------------------------------
            Win7 64Bit on Intel NUCI7 with SSD
            HSPRO 3.
            Devices; 1370 Events; 691

            Jon00 Scripts, JowHue, HSTouch, Plugwise, Z-wave, Ultranetatmo, Ultracam, PHlocation, BLUSBUIRT, MeiHarmony, Buienradar, MEiUnifi Pushover 3P, Random, Nest HSPhone and Blueiris

            Visonic Powermax Alarm System (HS3) Interface: http://www.domoticaforum.eu/viewtopic.php?f=68&t=11129

            Comment


            • #7
              dirk

              hereby my player table;
              Click image for larger version  Name:	playertable.png Views:	0 Size:	297.0 KB ID:	1315238

              i tried logging to file, but that is not working, or i cant find the file? nothing in log/data or bin. current log settings are;

              Click image for larger version  Name:	logsettings.png Views:	0 Size:	31.1 KB ID:	1315239

              Dirk,

              I also tried creating a linkgroup serre with only a source player Serre_RF an no destination, which outputs the announcement at both Serre speaker (RF and LF) but still have there errors;
              jul-12 13:52:22 Sonos Error ERROR in PlayURI for zoneplayer = Serre with UPNP Error = Read only tag / Transport is locked / Access denied. URI=x-rincon-queue:RINCON_7828CAE41B3801400#0 and isObjectID = False, MetaData=, Error =MyUPnPService.InvokeAction for ServiceID = http://192.168.1.168:1400/xml/AVTransport1.xml while sending Action = SetAVTransportURI for URI = http://192.168.1.168:1400/MediaRende...nsport/Control and Request = 0 x-rincon-queue:RINCON_7828CAE41B3801400#0 UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 1023 with error = The remote server returned an error: (500) Internal Server Error.
              When i do announcements to a non stereopair speaker i dont have these issue (eg badkamer)

              bart
              Regards Bart
              ------------------------------------------
              Win7 64Bit on Intel NUCI7 with SSD
              HSPRO 3.
              Devices; 1370 Events; 691

              Jon00 Scripts, JowHue, HSTouch, Plugwise, Z-wave, Ultranetatmo, Ultracam, PHlocation, BLUSBUIRT, MeiHarmony, Buienradar, MEiUnifi Pushover 3P, Random, Nest HSPhone and Blueiris

              Visonic Powermax Alarm System (HS3) Interface: http://www.domoticaforum.eu/viewtopic.php?f=68&t=11129

              Comment


              • #8
                Originally posted by bartbakels View Post
                dirk

                hereby my player table;
                Click image for larger version Name:	playertable.png Views:	0 Size:	297.0 KB ID:	1315238

                i tried logging to file, but that is not working, or i cant find the file? nothing in log/data or bin. current log settings are;

                Click image for larger version Name:	logsettings.png Views:	0 Size:	31.1 KB ID:	1315239

                Dirk,

                I also tried creating a linkgroup serre with only a source player Serre_RF an no destination, which outputs the announcement at both Serre speaker (RF and LF) but still have there errors;
                jul-12 13:52:22 Sonos Error ERROR in PlayURI for zoneplayer = Serre with UPNP Error = Read only tag / Transport is locked / Access denied. URI=x-rincon-queue:RINCON_7828CAE41B3801400#0 and isObjectID = False, MetaData=, Error =MyUPnPService.InvokeAction for ServiceID = http://192.168.1.168:1400/xml/AVTransport1.xml while sending Action = SetAVTransportURI for URI = http://192.168.1.168:1400/MediaRende...nsport/Control and Request = 0 x-rincon-queue:RINCON_7828CAE41B3801400#0 UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 1023 with error = The remote server returned an error: (500) Internal Server Error.
                When i do announcements to a non stereopair speaker i dont have these issue (eg badkamer)

                bart
                What kind are the S18 players (serre, badkamer, woonkamer ....)? This is a new player that I haven't seen before, are they a new S1 version? So that's the problem and I need to add this to the code. In fact, Sonos seems to come out now every year with new player, I'm going to have to think about the changes, see if I can make them more generic to avoid having to re-issue the PI every few months because Sonos delivered yet another player.

                As to the debugging, don't set superdebug only debug and don't set UPNP logging to verbose, leave it to errors only. If you log to disk, you need to use the "log to disk flag" as a toggle, so when you turn it on, the log file is opened and the previous log file is overwritten. It needs to be turned off to close the log file. Once done you can find the log file in the <hs root>\html\Sonos\Logs

                Comment


                • #9
                  Okay i will create the logging for you, the s18 are the sonos ones (i guess v2)

                  edit: debug log will be send private
                  Regards Bart
                  ------------------------------------------
                  Win7 64Bit on Intel NUCI7 with SSD
                  HSPRO 3.
                  Devices; 1370 Events; 691

                  Jon00 Scripts, JowHue, HSTouch, Plugwise, Z-wave, Ultranetatmo, Ultracam, PHlocation, BLUSBUIRT, MeiHarmony, Buienradar, MEiUnifi Pushover 3P, Random, Nest HSPhone and Blueiris

                  Visonic Powermax Alarm System (HS3) Interface: http://www.domoticaforum.eu/viewtopic.php?f=68&t=11129

                  Comment


                  • #10
                    At this point, no need for log, the code doesn't know this is a pairable player, so doesn't do the right things. Guess this never worked, right?

                    Comment


                    • #11
                      tbh, not sure, i think i have these new sonos ones now for 4 weeks, i think it works for none (stereo Paired) Ones. because i first used 2 standalone sonos ONEs
                      Regards Bart
                      ------------------------------------------
                      Win7 64Bit on Intel NUCI7 with SSD
                      HSPRO 3.
                      Devices; 1370 Events; 691

                      Jon00 Scripts, JowHue, HSTouch, Plugwise, Z-wave, Ultranetatmo, Ultracam, PHlocation, BLUSBUIRT, MeiHarmony, Buienradar, MEiUnifi Pushover 3P, Random, Nest HSPhone and Blueiris

                      Visonic Powermax Alarm System (HS3) Interface: http://www.domoticaforum.eu/viewtopic.php?f=68&t=11129

                      Comment


                      • #12
                        Bart, I was looking at my code again (written many years ago) and it appears that I already structured the code to NOT be dependent on player types, I check player types but not for announcements.
                        When I look at the log file you sent me, your event calls linkgroup "serre" but you have no destination player set, that's NOK, there must be one and it can be the same as the source if you only use one player.
                        When I look at the event "woonkamer", it looks to work as is should but there is an error when the player is restored, and that error is benign. It is a command sent to a slave player, need to look at my code why I don't prevent that but that should be OK.
                        Do check you balance settings to make sure it isn't your setting that you make believe that it only plays from one side of the stereo pair.
                        I tried a bunch of scenari here and I don't see any issues with stereo pairs. I did find an issue when the slave player is chose for the SOURCE player. That will be fixed in next release.
                        I'm also revisiting the whole renaming business to make sure there isn't an issue with that, but at this point, if you select the master player as source and you select the master player as destination, you should get a stereo announcement.


                        Comment


                        • #13
                          Originally posted by dcorsus View Post
                          Bart, I was looking at my code again (written many years ago) and it appears that I already structured the code to NOT be dependent on player types, I check player types but not for announcements.
                          When I look at the log file you sent me, your event calls linkgroup "serre" but you have no destination player set, that's NOK, there must be one and it can be the same as the source if you only use one player.
                          When I look at the event "woonkamer", it looks to work as is should but there is an error when the player is restored, and that error is benign. It is a command sent to a slave player, need to look at my code why I don't prevent that but that should be OK.
                          Do check you balance settings to make sure it isn't your setting that you make believe that it only plays from one side of the stereo pair.
                          I tried a bunch of scenari here and I don't see any issues with stereo pairs. I did find an issue when the slave player is chose for the SOURCE player. That will be fixed in next release.
                          I'm also revisiting the whole renaming business to make sure there isn't an issue with that, but at this point, if you select the master player as source and you select the master player as destination, you should get a stereo announcement.

                          that correct in that scenario, but i get the same errors when i select for example woonkamerconnect as source and serre or woonkamer as destination. Does the error generated cause an timout for several seconds, becaue i also tried sending speech to 2 linkgroups, however the second linkgroup only starts after several seconds to play the announcements. I checked th balance which is in the center. and indeed i still suspect something with the naming, as you see in the logs.


                          Next to that i have another scenario, which is not outputting any announcement in one of my steropairs

                          Linkgroup:

                          Master:
                          Woonkamer (or woonkamerconnect)

                          Destination:
                          Woonkamer
                          Woonkamer_RF
                          Serre
                          Serre_RF

                          Woonkamer is working (both speakers of steropair) but serre is not at all and i get these in the log which are a little bit different arent they;

                          Code:
                          ERROR in PlayURI for zoneplayer = Serre with UPNP Error = Read only tag / Transport is locked / Access denied. URI=x-rincon:RINCON_7828CAE365CA01400 and isObjectID = False, MetaData=http://192.168.1.190:80/images/Sonos/Announcement.jpgHomeSeer Announcementobject.item.audioItem.musicTrackDirk CorsusSonosControllerDirk Corsus, Error =MyUPnPService.InvokeAction for ServiceID = http://192.168.1.168:1400/xml/AVTransport1.xml while sending Action = SetAVTransportURI for URI = http://192.168.1.168:1400/MediaRenderer/AVTransport/Control and Request = 0 x-rincon:RINCON_7828CAE365CA01400 <DIDL-Lite xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:upnp="urn:schemas-upnp-org:metadata-1-0/upnp/" xmlns:r="urn:schemas-rinconnetworks-com:metadata-1-0/" xmlns="urn:schemas-upnp-org:metadata-1-0/DIDL-Lite/"><item id="-1" parentID="-1" restricted="true"><upnp:albumArtURI>http://192.168.1.190:80/images/Sonos/Announcement.jpg</upnp:albumArtURI><dc:title>HomeSeer Announcement</dc:title><upnp:class>object.item.audioItem.musicTrack</upnp:class><dc:creator>Dirk Corsus</dc:creator><upnp:album>SonosController</upnp:album><r:albumArtist>Dirk Corsus</r:albumArtist></item></DIDL-Lite> UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 501 with error = The remote server returned an error: (500) Internal Server Error.
                          I i now try

                          Master:
                          erre
                          Destination:

                          Serre
                          Serre_RF

                          It just plays the announcement without issues except the mentioned errors;

                          Code:
                           
                          jul-13 11:26:03 Sonos Error ERROR in PlayURI for zoneplayer = Serre with UPNP Error = Read only tag / Transport is locked / Access denied. URI=x-rincon-queue:RINCON_7828CAE41B3801400#0 and isObjectID = False, MetaData=, Error =MyUPnPService.InvokeAction for ServiceID = http://192.168.1.168:1400/xml/AVTransport1.xml while sending Action = SetAVTransportURI for URI = http://192.168.1.168:1400/MediaRenderer/AVTransport/Control and Request = 0 x-rincon-queue:RINCON_7828CAE41B3801400#0 UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 1023 with error = The remote server returned an error: (500) Internal Server Error.
                          jul-13 11:25:59 Sonos Error ERROR in PlayURI for zoneplayer = Serre with UPNP Error = Read only tag / Transport is locked / Access denied. URI=x-rincon-queue:RINCON_7828CAE41B3801400#0 and isObjectID = False, MetaData=, Error =MyUPnPService.InvokeAction for ServiceID = http://192.168.1.168:1400/xml/AVTransport1.xml while sending Action = SetAVTransportURI for URI = http://192.168.1.168:1400/MediaRenderer/AVTransport/Control and Request = 0 x-rincon-queue:RINCON_7828CAE41B3801400#0 UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 1023 with error = The remote server returned an error: (500) Internal Server Error.

                          I checked the speakers were not paired to other rooms etc.


                          Bart
                          Regards Bart
                          ------------------------------------------
                          Win7 64Bit on Intel NUCI7 with SSD
                          HSPRO 3.
                          Devices; 1370 Events; 691

                          Jon00 Scripts, JowHue, HSTouch, Plugwise, Z-wave, Ultranetatmo, Ultracam, PHlocation, BLUSBUIRT, MeiHarmony, Buienradar, MEiUnifi Pushover 3P, Random, Nest HSPhone and Blueiris

                          Visonic Powermax Alarm System (HS3) Interface: http://www.domoticaforum.eu/viewtopic.php?f=68&t=11129

                          Comment


                          • #14
                            Bart,

                            I just posted version 33 in the beta section of the updater, I did find an issue with naming and figuring out what player is what, not sure why it doesn't work anymore, I do suspect a change over time in Sonos SW. As far as I can tell, this doesn't seem to cause issues on my setup but better to have all players identified properly.

                            Just to be clear on a bunch of things and optimize our time spend reporting;

                            1/ the error or PlayURI has nothing to do with which source player is used, it is caused because a command is sent to a slave player ANYWHERE in the linkgroup. Ignore the error for now, it isn't causing an issue.
                            2/ Don't use players that have an extension _RF or _RR or whatever ANYWHERE in the linkgroup, they are all slaves, unless they are marked wrong (which we suspect somewhat). If you picked the master, the slaves will participate.
                            3/ Only one announcement can be handled at a time, if you tickle multiple announcements at the same time, they will be queued and acted upon, one after the other.

                            Try and let me know. Post of a single error don't help me, I need to see the whole flow. NO Superdebug, NO verbose logging, just the debug flag in case you need it. There is a chance (or hope to see it) you have warnings the first time you startup the new version so make sure the DEBUG flag is ON before you update so we can look at that warning if we need to. If the players were given the wrong extension, the warnings should show us the PI renaming them.

                            Dirk

                            Comment


                            • #15
                              Originally posted by dcorsus View Post
                              Bart,

                              I just posted version 33 in the beta section of the updater, I did find an issue with naming and figuring out what player is what, not sure why it doesn't work anymore, I do suspect a change over time in Sonos SW. As far as I can tell, this doesn't seem to cause issues on my setup but better to have all players identified properly.

                              Just to be clear on a bunch of things and optimize our time spend reporting;

                              1/ the error or PlayURI has nothing to do with which source player is used, it is caused because a command is sent to a slave player ANYWHERE in the linkgroup. Ignore the error for now, it isn't causing an issue.
                              2/ Don't use players that have an extension _RF or _RR or whatever ANYWHERE in the linkgroup, they are all slaves, unless they are marked wrong (which we suspect somewhat). If you picked the master, the slaves will participate.
                              3/ Only one announcement can be handled at a time, if you tickle multiple announcements at the same time, they will be queued and acted upon, one after the other.

                              Try and let me know. Post of a single error don't help me, I need to see the whole flow. NO Superdebug, NO verbose logging, just the debug flag in case you need it. There is a chance (or hope to see it) you have warnings the first time you startup the new version so make sure the DEBUG flag is ON before you update so we can look at that warning if we need to. If the players were given the wrong extension, the warnings should show us the PI renaming them.

                              Dirk
                              dirk i tried the new version is send you the debug from upgrading starting and playing an announcement on TEST LINK GROUP;

                              master: Woonkamer
                              Destination: Serre

                              NO announcement is being heard....

                              the only way now is to have this config to output an announcement

                              Master : woonkamer connect;

                              destination:

                              woonkamer and/or woonkamer_RF

                              but then i only hear the left speaker announce


                              So it seems i cannot select one of the steropairs speakers as source(anymore)
                              Regards Bart
                              ------------------------------------------
                              Win7 64Bit on Intel NUCI7 with SSD
                              HSPRO 3.
                              Devices; 1370 Events; 691

                              Jon00 Scripts, JowHue, HSTouch, Plugwise, Z-wave, Ultranetatmo, Ultracam, PHlocation, BLUSBUIRT, MeiHarmony, Buienradar, MEiUnifi Pushover 3P, Random, Nest HSPhone and Blueiris

                              Visonic Powermax Alarm System (HS3) Interface: http://www.domoticaforum.eu/viewtopic.php?f=68&t=11129

                              Comment

                              Working...
                              X