Announcement

Collapse
No announcement yet.

MediaController plugin beta testing Forum

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

    Originally posted by Bernold View Post
    That's strange. The debug flag was actually still on when I just started HS. I did notice it takes quite a while for the plugin to initialize. So this time I made sure I waited long enough for initialization to finish and I toggled the debug flag off/on, just to be sure.

    Another thing I notice is that the plugin does not finish initializing after this (>15 min).

    Edit: The plugin only reaches the connected status after I delete the remote device and restart HS. If you're missing the last entries again I may have to do this before turning off log-to-disk next time.
    Which version of the PI are you using? I start to realize that all the code for the newer versions I'm looking at here probably never made it out.

    Could you post your .ini file.
    Can you also post these URL in a browser and post the result

    http://192.168.1.194:7678/nservice/
    http://192.168.1.194:7676/rcr/
    http://192.168.1.194:9197/dmr

    I cold post a newer version but I doubt it will work. Maybe if you can give me the info, you should delete the remote for now.

    Dirk

    Comment


      Originally posted by dcorsus View Post
      Which version of the PI are you using? I start to realize that all the code for the newer versions I'm looking at here probably never made it out.

      Could you post your .ini file.
      Can you also post these URL in a browser and post the result

      http://192.168.1.194:7678/nservice/
      http://192.168.1.194:7676/rcr/
      http://192.168.1.194:9197/dmr

      I cold post a newer version but I doubt it will work. Maybe if you can give me the info, you should delete the remote for now.

      Dirk
      That makes sense according to the changelog in your first post. Currently I'm using version 3.0.0.28. Is there a recent beta version I could test? Or maybe I could test https://forums.homeseer.com/showpost...4&postcount=33, which was reported to work on a K series (though I'm not sure if modifications to the ini file have to be made)?

      I have zipped and attached the ini file.

      http://192.168.1.194:7678/nservice/:

      <?xml version="1.0"?>
      <root xmlns="urn:schemas-upnp-org:device-1-0" xmlns:sec="http://www.sec.co.kr/dlna" xmlns:dlna="urn:schemas-dlna-org:device-1-0">
      <specVersion>
      <major>1</major>
      <minor>0</minor>
      </specVersion>
      <device>
      <deviceType>urn:dial-multiscreen-org:device:dialreceiver:1</deviceType>
      <friendlyName>[TV] Samsung 7 Series (55)</friendlyName>
      <manufacturer>Samsung Electronics</manufacturer>
      <manufacturerURL>http://www.samsung.com/sec</manufacturerURL>
      <modelDescription>Samsung DTV RCR</modelDescription>
      <modelName>UE55MU7070</modelName>
      <modelNumber>1.0</modelNumber>
      <modelURL>http://www.samsung.com/sec</modelURL>
      <serialNumber>20090804RCR</serialNumber>
      <UDN>uuid:4d947893-8732-4553-b323-9bf57d5a56b0</UDN>
      <sec:deviceID>NSNSC5ZTTO2RS</sec:deviceID>
      <sec:ProductCap>Resolution:1920X1080,Tizen,Y2017</sec:ProductCap>
      <serviceList>
      <service>
      <serviceType>urn:dial-multiscreen-org:service:dial:1</serviceType>
      <serviceId>urn:dial-multiscreen-org:serviceId:dial</serviceId>
      <controlURL>/RCR/control/dial</controlURL>
      <eventSubURL>/RCR/event/dial</eventSubURL>
      <SCPDURL>dial.xml</SCPDURL>
      </service>
      </serviceList>
      <sec:Capabilities>
      <sec:Capability name="samsung:multiscreen:1" port="8001" location="/ms/1.0/"/>
      </sec:Capabilities>
      </device>
      </root>



      http://192.168.1.194:7676/rcr/:
      <?xml version="1.0"?>
      <root xmlns="urn:schemas-upnp-org:device-1-0" xmlns:sec="http://www.sec.co.kr/dlna" xmlns:dlna="urn:schemas-dlna-org:device-1-0">
      <specVersion>
      <major>1</major>
      <minor>0</minor>
      </specVersion>
      <device>
      <deviceType>urn:samsung.com:device:RemoteControlReceiver:1 </deviceType>
      <friendlyName>[TV] Samsung 7 Series (55)</friendlyName>
      <manufacturer>Samsung Electronics</manufacturer>
      <manufacturerURL>http://www.samsung.com/sec</manufacturerURL>
      <modelDescription>Samsung DTV RCR</modelDescription>
      <modelName>UE55MU7070</modelName>
      <modelNumber>1.0</modelNumber>
      <modelURL>http://www.samsung.com/sec</modelURL>
      <serialNumber>20090804RCR</serialNumber>
      <UDN>uuid:c9a47c05-5e9c-4cd4-9003-e48f6f0ff8b5</UDN>
      <sec:deviceID>SHCHC5ZTTO2RS</sec:deviceID>
      <sec:ProductCap>Resolution:1920X1080,Tizen,Y2017</sec:ProductCap>
      <serviceList>
      <service>
      <serviceType>urn:samsung.com:service:MultiScreenService:1</serviceType>
      <serviceId>urn:samsung.com:serviceId:MultiScreenService</serviceId>
      <controlURL>/RCR/control/MultiScreenService</controlURL>
      <eventSubURL>/RCR/event/MultiScreenService</eventSubURL>
      <SCPDURL>MultiScreenService.xml</SCPDURL>
      </service>
      </serviceList>
      <sec:Capabilities>
      <sec:Capability name="samsung:multiscreen:1" port="8001" location="/ms/1.0/"/>
      </sec:Capabilities>
      </device>
      </root>

      http://192.168.1.194:9197/dmr:

      <?xml version="1.0"?>
      <root xmlns="urn:schemas-upnp-org:device-1-0" xmlnsnpx="http://schemas.microsoft.com/windows/pnpx/2005/11" xmlns:df="http://schemas.microsoft.com/windows/2008/09/devicefoundation" xmlns:sec="http://www.sec.co.kr/dlna">
      <specVersion>
      <major>1</major>
      <minor>0</minor>
      </specVersion>
      <device>
      <deviceType>urn:schemas-upnp-org:device:MediaRenderer:1</deviceType>
      <pnpx:X_compatibleId>MS_DigitalMediaDeviceClass_DMR_V001</pnpx:X_compatibleId>
      <df:X_deviceCategory>Display.TV.LCD Multimedia.DMR</df:X_deviceCategory>
      <dlna:X_DLNADOC xmlns:dlna="urn:schemas-dlna-org:device-1-0">DMR-1.50</dlna:X_DLNADOC>
      <friendlyName>[TV] Samsung 7 Series (55)</friendlyName>
      <manufacturer>Samsung Electronics</manufacturer>
      <manufacturerURL>http://www.samsung.com/sec</manufacturerURL>
      <modelDescription>Samsung TV DMR</modelDescription>
      <modelName>UE55MU7070</modelName>
      <modelNumber>AllShare1.0</modelNumber>
      <modelURL>http://www.samsung.com/sec</modelURL>
      <serialNumber>0DF83HGK100043W</serialNumber>
      <UDN>uuid:bea26aae-730a-4864-ad47-d2b50a34c109</UDN>
      <iconList>
      <icon>
      <mimetype>image/jpeg</mimetype>
      <width>48</width>
      <height>48</height>
      <depth>24</depth>
      <url>/icon_SML.jpg</url>
      </icon>
      <icon>
      <mimetype>image/jpeg</mimetype>
      <width>120</width>
      <height>120</height>
      <depth>24</depth>
      <url>/icon_LRG.jpg</url>
      </icon>
      <icon>
      <mimetype>image/png</mimetype>
      <width>48</width>
      <height>48</height>
      <depth>24</depth>
      <url>/icon_SML.png</url>
      </icon>
      <icon>
      <mimetype>image/png</mimetype>
      <width>120</width>
      <height>120</height>
      <depth>24</depth>
      <url>/icon_LRG.png</url>
      </icon>
      </iconList>
      <serviceList>
      <service>
      <serviceType>urn:schemas-upnp-org:service:RenderingControl:1</serviceType>
      <serviceId>urn:upnp-org:serviceId:RenderingControl</serviceId>
      <controlURL>/upnp/control/RenderingControl1</controlURL>
      <eventSubURL>/upnp/event/RenderingControl1</eventSubURL>
      <SCPDURL>/RenderingControl_1.xml</SCPDURL>
      </service>
      <service>
      <serviceType>urn:schemas-upnp-org:service:ConnectionManager:1</serviceType>
      <serviceId>urn:upnp-org:serviceId:ConnectionManager</serviceId>
      <controlURL>/upnp/control/ConnectionManager1</controlURL>
      <eventSubURL>/upnp/event/ConnectionManager1</eventSubURL>
      <SCPDURL>/ConnectionManager_1.xml</SCPDURL>
      </service>
      <service>
      <serviceType>urn:schemas-upnp-org:service:AVTransport:1</serviceType>
      <serviceId>urn:upnp-org:serviceId:AVTransport</serviceId>
      <controlURL>/upnp/control/AVTransport1</controlURL>
      <eventSubURL>/upnp/event/AVTransport1</eventSubURL>
      <SCPDURL>/AVTransport_1.xml</SCPDURL>
      </service>
      <service>
      <serviceType>urn:schemas-rvualliance-org:service:StreamSplicing:1</serviceType>
      <serviceId>urn:upnp-org:serviceId:StreamSplicing</serviceId>
      <controlURL>/upnp/control/StreamSplicing1</controlURL>
      <eventSubURL>/upnp/event/StreamSplicing1</eventSubURL>
      <SCPDURL>/StreamSplicing_1.xml</SCPDURL>
      </service>
      </serviceList>
      <sec:ProductCap>Tizen,Y2017,WebURIPlayable,NavigateInPause,S creenMirroringP2PMAC=9e:8c:6e:4b:28:96,UHD_SCREEN,SerialNumb er=0DF83HGK100043W,vdProductType=TV,OCF=1</sec:ProductCap>
      <pnpx:X_hardwareId>VEN_0105&amp;DEV_VD0001</pnpx:X_hardwareId>
      </device>
      </root>
      Attached Files
      Last edited by Bernold; April 2, 2018, 01:18 PM. Reason: Fixed the xml formatting
      Plugins I developed for HS4: Somfy Local, MiLight (LimitlessLED), Updates, Volvo (VoC), OpenTherm Gateway (OTGW)
      Running HS4 Pro on Windows 10 Pro on a Synology VM, with Node-RED running as a container.

      Comment


        Originally posted by Bernold View Post
        That makes sense according to the changelog in your first post. Currently I'm using version 3.0.0.28. Is there a recent beta version I could test? Or maybe I could test https://forums.homeseer.com/showpost...4&postcount=33, which was reported to work on a K series (though I'm not sure if modifications to the ini file have to be made)?
        Ah excellent, now I recall. I did the changes for a specific user but never released it completely. You could download the zip file in https://forums.homeseer.com/showpost...4&postcount=33
        , stop hs3, overwrite the Mediacontroller.exe with the one from the zip in the HS3 homedirectory but perhaps before you do that make sure you delete the remote control device using the PI config page!

        I looked at the attached info and all is looking good. If you want to help test, keep the debug flag on and post full logs, preferable when the PI starts and (re)discovers the devices OR when you add them OR when you click on buttons to issue commands.

        Perhaps best that we move this conversation to its own thread and call it say "Samsung TV Y2016 and newer remote control"

        Cheers,

        Dirk

        Comment


          I'm seeing a lot of errors in my log - any suggestions as to the cause;


          May-24 17:30:30 MC Error Error in DoRediscover with error = Object reference not set to an instance of an object.

          Comment


            Originally posted by IanIreland View Post
            I'm seeing a lot of errors in my log - any suggestions as to the cause;


            May-24 17:30:30 MC Error Error in DoRediscover with error = Object reference not set to an instance of an object.

            Did you delete any devices from the device management page?

            Comment


              Hello

              i have installed the last beta 3.0.0.52

              i get this error:

              févr.-05 09:29:04 MC SamsungAuthenticateUsePIN for device - [TV]F9000 received authentication data for ClientAck with content = {"auth_data":"{"auth_type":"SPC","request_id":"0","ClientAck Msg":"01040000000000000000142425F966FCB4AC382914A19730B1501B 7D239D9A0000000000","session_id":"2"}"}
              févr.-05 09:29:04 MC SendWebRequest called for Device = [TV]F9000 with Method = POST and RequestURL = http://192.168.50.30:8080/ws/pairing...iaControllerPI
              févr.-05 09:29:04 MC SamsungAuthenticateUsePIN for device - [TV]F9000 is sending ServerAckMsg with content = {"auth_Data":{"auth_type":"SPC","request_id":"0","ServerAckM sg":"01030000000000000000143BB5D36CA243BBF3E83F010D6A692B352 1414F1B0000000000"}}
              févr.-05 09:29:04 MC generateServerAcknowledge for UPnPDevice = [TV]F9000 generated returnString = 01030000000000000000143BB5D36CA243BBF3E83F010D6A692B3521414F 1B0000000000
              févr.-05 09:29:04 MC Error Error in ParseClientHello for UPnPDevice = [TV]F9000 with clientHello = 010100000000000000009E00000006363534333231695D0622D20EE80563 45D9E237530CBB8834900FA7FB882314F9F6881101E0F1FF01542E945658 3B7CED745AFCE398352E9A6E51DCCBF4C5020F15B48CA8542C8EBE681608 4BE2B7793F4571FFE03919B6657852743E7DE6947AB82A4CE2212C693EB6 7E7855C3D68472DC499B78FDA4F0DBBA20823BAFA405ADD6061B305C4E27 543AB71D01E18D51368684709E6AB1067DE79F0000000000, dataHash = 904F0EDB9179C3312A0496CDEDFDB85742122F7C, aesKey = A7E33171AE5445DB807E813BE5C56937 and Error = Impossible de charger la DLL 'MediaControllerCrypto.dll': Le module spécifié est introuvable. (Exception de HRESULT : 0x8007007E)
              févr.-05 09:29:04 MC ParseClientHello for UPnPDevice = [TV]F9000 Pin OK!!!
              févr.-05 09:29:04 MC SamsungAuthenticateUsePIN for device - [TV]F9000 Pin = 6820
              févr.-05 09:29:04 MC SendWebRequest called for Device = [TV]F9000 with Method = POST and RequestURL = http://192.168.50.30:8080/ws/pairing...iaControllerPI
              févr.-05 09:29:04 MC SamsungAuthenticateUsePIN for device - [TV]F9000 Sending GeneratorServerHello with payload = {"auth_Data":{"auth_type":"SPC","GeneratorServerHello":"0102 00000000000000008A000000063635343332316D1BD29FAC0029D437AC06 04E2C555A28D512320246A99A68FA4ECE50982C91F70611920FBE079598C ECE0A7A87E36901BEF32E84B1AAAE238108BEB3A0950CCDB5F5EF3ACE238 9B55DB5068805DCEE108B0C27CB46F371B73A1C9A040FC344BC5BC1C3844 C96F82FD5777685EEDCBE11F984525EC5E75D35298BDF03E4B598E000000 0000"}}
              févr.-05 09:29:04 MC GenerateServerHello for UPnPDevice = [TV]F9000 generated ServerHello = 010200000000000000008A000000063635343332316D1BD29FAC0029D437 AC0604E2C555A28D512320246A99A68FA4ECE50982C91F70611920FBE079 598CECE0A7A87E36901BEF32E84B1AAAE238108BEB3A0950CCDB5F5EF3AC E2389B55DB5068805DCEE108B0C27CB46F371B73A1C9A040FC344BC5BC1C 3844C96F82FD5777685EEDCBE11F984525EC5E75D35298BDF03E4B598E00 00000000
              févr.-05 09:29:04 MC GenerateServerHello called for UPnPDevice = [TV]F9000 with UserID = 654321 and PIN = 6820
              févr.-05 09:29:04 MC SamsungAuthenticateUsePIN called for device - [TV]F9000 with PIN = 6820
              févr.-05 09:29:04 MC TreatSetIOExSamsung called for UPnPDevice = [TV]F9000 and buttonvalue = 40
              févr.-05 09:29:04 MC TreatSetIOExRemoteControl called for UPnPDevice = [TV]F9000 and buttonvalue = 40
              jean-francois.

              Comment


                Originally posted by jfla View Post
                Hello

                i have installed the last beta 3.0.0.52

                jean-francois.
                Can you find this dll (MediaControllerCrypto.dll) in the hs root directory?
                What OS and version are you running this on?
                I'll double check the install file but at first glance it all look ok.
                Dirk

                Comment


                  Hello, Dirk

                  Yes The dllis in HS3 directory

                  Click image for larger version  Name:	Screen Shot 02-05-19 at 08.40 PM.JPG Views:	1 Size:	189.6 KB ID:	1282612
                  My system:
                  Current Date/Time: 05/02/2019 20:37:33
                  HomeSeer Version: HS3 Pro Edition 3.0.0.478
                  Operating System: Microsoft Windows 10 Famille - Work Station
                  System Uptime: 1 Day 16 Hours 36 Minutes 6 Seconds
                  IP Address: 192.168.50.55
                  Number of Devices: 628
                  Number of Events: 185
                  Available Threads: 800
                  HSTouch Enabled: True
                  Event Threads: 0
                  Event Trigger Eval Queue: 0
                  Event Trigger Priority Eval Queue: 0
                  Device Exec Queue: 0
                  HSTouch Event Queue: 0
                  Email Send Queue: 0
                  Anti Virus Installed: Avast Antivirus Windows Defender
                  The HS3 directory is exclude from AVAST.

                  Worked correctly with V3.0.0.50 with SPCApi.dll

                  Jean-Francois

                  Comment


                    Originally posted by jfla View Post
                    Hello, Dirk

                    Yes The dllis in HS3 directory

                    Click image for larger version Name:	Screen Shot 02-05-19 at 08.40 PM.JPG Views:	1 Size:	189.6 KB ID:	1282612
                    My system:


                    The HS3 directory is exclude from AVAST.

                    Worked correctly with V3.0.0.50 with SPCApi.dll

                    Jean-Francois
                    Anything special about your setup? Do you autostart HS perhaps? You could as a test copy MediaControllerCrypto.dll into <hs root>\html\MediaController\bin and see if that makes a difference. I tried it all this morning on a Windows and Linux machine and didn't have a problem, so not sure where to start. If you check the properties of the DLL, go to "security" tab, does it show permission to execute?

                    Comment


                      Hi, Dirk

                      I tested the path <hs root>\html\MediaController\bin, no change

                      Security properties:
                      Click image for larger version

Name:	Screen Shot 02-05-19 at 10.39 PM.JPG
Views:	348
Size:	61.9 KB
ID:	1282648
                      Same for three users.

                      Jean francois.

                      Comment


                        Originally posted by jfla View Post
                        Hi, Dirk

                        I tested the path <hs root>\html\MediaController\bin, no change

                        Security properties:
                        Click image for larger version

Name:	Screen Shot 02-05-19 at 10.39 PM.JPG
Views:	348
Size:	61.9 KB
ID:	1282648
                        Same for three users.

                        Jean francois.
                        Do you start HS manually or through script or perhaps as a service? If you do, did you specify a "work folder" that is perhaps different from the <HS root> folder?

                        Comment


                          Originally posted by dcorsus View Post

                          Do you start HS manually or through script or perhaps as a service? If you do, did you specify a "work folder" that is perhaps different from the <HS root> folder?
                          jfla Do you have errors in your log file when you start HS? Which .NET versions are installed? Not sure it makes a difference but the error clearly states it can't find the dll whereas it is clearly in the root directory so anything I can think off is perhaps another misbehaving .config file or error somewhere during start-up. Did you restart HS? Maybe it requires an HS restart .....

                          Comment


                            Hello, Dcorsus

                            I make a new install of HS3 on an another PC under WIN10 Family.

                            This new install is in the standard folder C:\Program Files (x86)\HomeSeer HS3. i restored my HS3 folder from the main PC

                            I started MediaController and i don't have any error with (MediaControllerCrypto.dll).....

                            mars-03 17:35:44

                            MC
                            SamsungAuthenticateUsePIN called for device - [TV]F9000 with PIN = 7659
                            mars-03 17:35:44

                            MC
                            SendWebRequest called for Device = [TV]F9000 with Method = GET and RequestURL = http://192.168.50.30:8080/ws/pairing...ollerPI&type=1
                            mars-03 17:35:49

                            MC
                            GenerateServerHello called for UPnPDevice = [TV]F9000 with UserID = 654321 and PIN = 7659
                            mars-03 17:35:49

                            MC
                            GenerateServerHello for UPnPDevice = [TV]F9000 generated ServerHello = 010200000000000000008A000000063635343332310806BEA48C5A8F70BC FA67A31E45A34BEB42F63F0F5D7669BE4DE25BC6DF0D79020EB56CFD5ABE F9BF5B6709CE7957E50324D0E82EF9EBFA86780A32B285713DE30ECCFBAE 2FE14ABC6FD5025F7BE1767C0D9D5F8CD47B84598819C81675C47F9D4F8D BD0482ECF443EC69DC2574109D9AB449159606213CB7210170E0EB5D2B00 00000000
                            mars-03 17:35:49

                            MC
                            SamsungAuthenticateUsePIN for device - [TV]F9000 Sending GeneratorServerHello with payload = {"auth_Data":{"auth_type":"SPC","GeneratorServerHello":"0102 00000000000000008A000000063635343332310806BEA48C5A8F70BCFA67 A31E45A34BEB42F63F0F5D7669BE4DE25BC6DF0D79020EB56CFD5ABEF9BF 5B6709CE7957E50324D0E82EF9EBFA86780A32B285713DE30ECCFBAE2FE1 4ABC6FD5025F7BE1767C0D9D5F8CD47B84598819C81675C47F9D4F8DBD04 82ECF443EC69DC2574109D9AB449159606213CB7210170E0EB5D2B000000 0000"}}
                            mars-03 17:35:49

                            MC
                            SendWebRequest called for Device = [TV]F9000 with Method = POST and RequestURL = http://192.168.50.30:8080/ws/pairing...iaControllerPI
                            mars-03 17:35:49

                            MC
                            SamsungAuthenticateUsePIN for device - [TV]F9000 Pin = 7659
                            mars-03 17:35:49

                            MC
                            ParseClientHello for UPnPDevice = [TV]F9000 Pin OK!!!
                            mars-03 17:35:49

                            MC
                            ParseClientHello for UPnPDevice = [TV]F9000 ctx: EA28A3163429260737C617E9EAEEBB4A
                            mars-03 17:35:49

                            MC
                            generateServerAcknowledge for UPnPDevice = [TV]F9000 generated returnString = 0103000000000000000014B2D62851186CCE4B64F8219962752C9EE578CD 860000000000
                            mars-03 17:35:49

                            MC
                            SamsungAuthenticateUsePIN for device - [TV]F9000 is sending ServerAckMsg with content = {"auth_Data":{"auth_type":"SPC","request_id":"2","ServerAckM sg":"0103000000000000000014B2D62851186CCE4B64F8219962752C9EE 578CD860000000000"}}
                            mars-03 17:35:49

                            MC
                            SendWebRequest called for Device = [TV]F9000 with Method = POST and RequestURL = http://192.168.50.30:8080/ws/pairing...iaControllerPI
                            mars-03 17:35:49

                            MC
                            SamsungAuthenticateUsePIN for device - [TV]F9000 received authentication data for ClientAck with content = {"auth_data":"{"auth_type":"SPC","request_id":"2","ClientAck Msg":"0104000000000000000014A67C080A45EBA9423576078AC97F24F2 449E40D80000000000","session_id":"4"}"}
                            mars-03 17:35:49

                            MC
                            SamsungAuthenticateUsePIN for device - [TV]F9000 ClientAckMsg = 0104000000000000000014A67C080A45EBA9423576078AC97F24F2449E40 D80000000000
                            mars-03 17:35:49

                            MC
                            SamsungAuthenticateUsePIN for device - [TV]F9000 SessionID = 4
                            mars-03 17:35:49

                            MC
                            SamsungAuthenticateUsePIN for device - [TV]F9000 SessionKey =
                            On the main PC , HS3 is installed in C:\Homeseer HS3

                            And i get the error with MediacontrollerCrypto.dll:

                            Homesser Installed in folder c:\Homesser HS3

                            mars-03 17:32:44

                            MC
                            SamsungAuthenticateUsePIN called for device - [TV]F9000 with PIN = 7659
                            mars-03 17:32:44

                            MC
                            SendWebRequest called for Device = [TV]F9000 with Method = GET and RequestURL = http://192.168.50.30:8080/ws/pairing...ollerPI&type=1
                            mars-03 17:32:44

                            MC
                            GenerateServerHello called for UPnPDevice = [TV]F9000 with UserID = 654321 and PIN = 7659
                            mars-03 17:32:44

                            MC
                            GenerateServerHello for UPnPDevice = [TV]F9000 generated ServerHello = 010200000000000000008A000000063635343332310806BEA48C5A8F70BC FA67A31E45A34BEB42F63F0F5D7669BE4DE25BC6DF0D79020EB56CFD5ABE F9BF5B6709CE7957E50324D0E82EF9EBFA86780A32B285713DE30ECCFBAE 2FE14ABC6FD5025F7BE1767C0D9D5F8CD47B84598819C81675C47F9D4F8D BD0482ECF443EC69DC2574109D9AB449159606213CB7210170E0EB5D2B00 00000000
                            mars-03 17:32:44

                            MC
                            SamsungAuthenticateUsePIN for device - [TV]F9000 Sending GeneratorServerHello with payload = {"auth_Data":{"auth_type":"SPC","GeneratorServerHello":"0102 00000000000000008A000000063635343332310806BEA48C5A8F70BCFA67 A31E45A34BEB42F63F0F5D7669BE4DE25BC6DF0D79020EB56CFD5ABEF9BF 5B6709CE7957E50324D0E82EF9EBFA86780A32B285713DE30ECCFBAE2FE1 4ABC6FD5025F7BE1767C0D9D5F8CD47B84598819C81675C47F9D4F8DBD04 82ECF443EC69DC2574109D9AB449159606213CB7210170E0EB5D2B000000 0000"}}
                            mars-03 17:32:44

                            MC
                            SendWebRequest called for Device = [TV]F9000 with Method = POST and RequestURL = http://192.168.50.30:8080/ws/pairing...iaControllerPI
                            mars-03 17:32:44

                            MC
                            SamsungAuthenticateUsePIN for device - [TV]F9000 Pin = 7659
                            mars-03 17:32:44

                            MC
                            ParseClientHello for UPnPDevice = [TV]F9000 Pin OK!!!
                            mars-03 17:32:44

                            MC Error
                            Error in ParseClientHello for UPnPDevice = [TV]F9000 with clientHello = 010100000000000000009E00000006363534333231695D0622D20EE80563 45D9E237530CBB8834900FA7FB882314F9F6881101E0F1FF01542E945658 3B7CED745AFCE398352E9A6E51DCCBF4C5020F15B48CA8542C8EBE681608 4BE2B7793F4571FFE03919B6657852743E7DE6947AB82A4CE2212C693EB6 7E7855C3D68472DC499B78FDA4F0DBBA20823BAFA405ADD6061B305C4E27 543AB71D01E18D51368684709E6AB1067DE79F0000000000, dataHash = 904F0EDB9179C3312A0496CDEDFDB85742122F7C, aesKey = A7E33171AE5445DB807E813BE5C56937 and Error = Impossible de charger la DLL 'MediaControllerCrypto.dll': Le module spécifié est introuvable. (Exception de HRESULT : 0x8007007E)
                            mars-03 17:32:44

                            MC
                            generateServerAcknowledge for UPnPDevice = [TV]F9000 generated returnString = 010300000000000000001486C0DDE7516B7A16457A49B686828581C90495 460000000000
                            mars-03 17:32:44

                            MC
                            SamsungAuthenticateUsePIN for device - [TV]F9000 is sending ServerAckMsg with content = {"auth_Data":{"auth_type":"SPC","request_id":"2","ServerAckM sg":"010300000000000000001486C0DDE7516B7A16457A49B686828581C 90495460000000000"}}
                            Jean-Francois.


                            Comment


                              Originally posted by jfla View Post
                              Hello, Dcorsus

                              I make a new install of HS3 on an another PC under WIN10 Family.

                              This new install is in the standard folder C:\Program Files (x86)\HomeSeer HS3. i restored my HS3 folder from the main PC

                              I started MediaController and i don't have any error with (MediaControllerCrypto.dll).....



                              On the main PC , HS3 is installed in C:\Homeseer HS3

                              And i get the error with MediacontrollerCrypto.dll:



                              Jean-Francois.

                              Hi Jean-Francois, I believe the error must be somewhere in the environment of what you have in your setup.
                              Either allowance to execute something in that directory where HS is, or admin rights or other allowances etc.
                              Allowances tend to be inherited from directories so that's where I would start.

                              On the PC where it doesn't work, where exactly are HS3's executables? Maybe you need to post screenshots of directory structures here to try to get to the bottom of this. In the non working case, how do you start HS? Is it through a shortcut, if so, what are the properties of that shortcut? Most important is whether the work-directory is different from the HS root directory.

                              Comment


                                Trying to get the plugin (v3.0.0.52) to work with TTS to my Logitech Squeezeboxes (HS3 Standard Edition 3.0.0.534 (Windows); web server configured for port 82). No annoucement plays and I see the following error in the log when I run a test:
                                Jun-14 13:13:38 MC Error Error in DoCheckAnnouncementQueue adding a track to the Queue = http://xxx.xxx.xxx.xxx:82/MediaContr..._Kitchen_0.wav
                                Jun-14 13:13:36 MC SpeakIn called for Device = 0, Text = Testing 1 2 3, Wait=False, Host = $MC$Kitchen$:*
                                Jun-14 13:13:36 Event Event Trigger "Testing Speaker test"
                                Jun-14 13:13:36 Event Event Testing Speaker test triggered by the event page 'Run' button.
                                I checked the .wav (and also tried with .mp3) is correctly generated and available. Any ideas as to where to start in getting this fixed and playing?

                                Thanks!

                                Comment

                                Working...
                                X