Announcement

Collapse
No announcement yet.

MediaController plugin beta testing Forum

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

    Originally posted by Vincenttor View Post
    Homeseer is running on windows 10
    its a i7 16g ram.
    but i tried it to be sure on my laptop to see if it made any difference.

    Thats a i7 6gig of ram.
    Made another movie what happends and with logging turned off.


    it also gives this error in the log part of homeseer.

    mrt-26 22:47:37 Warning Plugin MediaController is not responding but it is still running, not restarting yet.
    mrt-26 22:39:07
    Warning Plugin MediaController is not responding but it is still running, not restarting yet.
    mrt-26 22:30:37
    Warning Plugin MediaController is not responding but it is still running, not restarting yet.
    mrt-26 22:26:31
    Warning File does not exist: C:\Program Files (x86)\HomeSeer HS3\html\api\v2\assets\snagit_win_messaging_enu mrt-26 22:22:07 Warning Plugin MediaController is not responding but it is still running, not restarting yet.
    mrt-26 22:15:00 Log Info The log database is currently 0,24MB in size.
    mrt-26 22:13:37
    Warning Plugin MediaController is not responding but it is still running, not restarting yet.
    mrt-26 22:05:07 Warning Plugin MediaController is not responding but it is still running, not restarting yet.

    mrt-26 22:04:23
    Error Calling SetIOMulti in plugin MediaControllere objectverwijzing is niet op een exemplaar van een object ingesteld.
    mrt-26 21:56:37
    Warning Plugin MediaController is not responding
    but it is still running, not restarting yet.
    mrt-26 21:56:23 Error Calling SetIOMulti in plugin MediaControllere objectverwijzing is niet op een exemplaar van een object ingesteld.
    mrt-26 22:56:07 Warning Plugin MediaController is not responding but it is still running, not restarting yet.
    Strange.....

    Could you (ONLY!!) turn on the debug flag. Do not turn on the UPNP logging except for errors only.
    Now restart HS3 and capture log from HS starting up, the PI starting, you activating the remote (not sure why that has to happen each time), to clicking on some remote keys. Cut/Paste the whole log.

    Dirk

    Comment


      Thanks for the fast reply Dirk,
      here is the log capture

      mrt-27 12:12:14 Device Control Device: MediaController [TV]Samsung LED22 Remote to Vol + (40) by/from: CAPI Control Handler
      mrt-27 12:12:10 Device Control Device: MediaController [TV]Samsung LED22 Remote to Vol + (40) by/from: CAPI Control Handler
      mrt-27 12:12:09 Device Control Device: MediaController [TV]Samsung LED22 Remote to Vol + (40) by/from: CAPI Control Handler
      mrt-27 12:12:07 Device Control Device: MediaController [TV]Samsung LED22 Remote to Vol + (40) by/from: CAPI Control Handler
      mrt-27 12:12:06 Device Control Device: MediaController [TV]Samsung LED22 Remote to Vol - (41) by/from: CAPI Control Handler
      mrt-27 12:12:05 Device Control Device: MediaController [TV]Samsung LED22 Remote to Vol - (41) by/from: CAPI Control Handler
      mrt-27 12:12:03 Device Control Device: MediaController [TV]Samsung LED22 Remote to Vol + (40) by/from: CAPI Control Handler
      mrt-27 12:12:02 Device Control Device: MediaController [TV]Samsung LED22 Remote to Channel + (42) by/from: CAPI Control Handler
      mrt-27 12:12:01 MC Error Error in ConnectCallback calling EndConnect with ipAddress = 192.168.1.24 with Error = Kan geen verbinding maken omdat de doelcomputer de verbinding actief heeft geweigerd 192.168.1.24:55000
      mrt-27 12:11:55 MC ConnectSocket called with ipAddress = 192.168.1.24 and ipPort = 55000
      mrt-27 12:11:55 MC EstablishTCPConnection called for UPnPDevice = [TV]Samsung LED22 and MyRemoteServiceActive = False
      mrt-27 12:11:55 MC TreatSetIOExSamsung called for UPnPDevice = [TV]Samsung LED22 and buttonvalue = 0
      mrt-27 12:11:55 MC TreatSetIOExRemoteControl called for UPnPDevice = [TV]Samsung LED22 and buttonvalue = 0
      mrt-27 12:11:55 MC TreatSetIOEx called for device = [TV]Samsung LED22 with Ref = 5, Index 0, controlFlag = False, ControlString, ControlType = Button, ControlValue = 0, Label = Remote On
      mrt-27 12:11:55 MC SetIOEx called for Ref = 5, Index 0, controlFlag = False, ControlString, ControlType = Button, ControlValue = 0, Label = Remote On
      mrt-27 12:11:55 MC SetIOMulti set value: 0->ref:5
      mrt-27 12:11:55 MC SetIOMulti called
      mrt-27 12:11:55 Device Control Device: MediaController [TV]Samsung LED22 Remote to Remote On (0) by/from: CAPI Control Handler
      mrt-27 12:11:49 MC SetHSMainState called for device - [TV]Samsung LED22 and Current Remote HSRef = 5 and AdminStateActive = True and DeviceStatus = Online
      mrt-27 12:11:49 MC SetHSMainState called for device - [TV]Samsung LED22 and Current HSRef = 4 and AdminStateActive = True and DeviceStatus = Online
      mrt-27 12:11:49 MC SetAdministrativeState called for device - [TV]Samsung LED22 and Active = True
      mrt-27 12:11:49 MC TreatSetIOEx called for device = [TV]Samsung LED22 with Ref = 4, Index 1, controlFlag = False, ControlString, ControlType = Button, ControlValue = 2, Label = Activate
      mrt-27 12:11:49 MC SetIOEx called for Ref = 4, Index 1, controlFlag = False, ControlString, ControlType = Button, ControlValue = 2, Label = Activate
      mrt-27 12:11:49 MC SetIOMulti set value: 2->ref:4
      mrt-27 12:11:49 MC SetIOMulti called
      mrt-27 12:11:49 Device Control Device: MediaController [TV]Samsung LED22 Device to Activate (2) by/from: CAPI Control Handler
      mrt-27 12:11:41 MC GetPagePlugin for PlugInConfig called with pageName = MediaControl and user = default and userRights = 6 and queryString =
      mrt-27 12:11:41 MC hspi.GetPagePlugin called for instance = and pageName = MediaControl and user = default and userRights = 6 and queryString =
      mrt-27 12:11:41 MC Error Error in ConnectCallback calling EndConnect with ipAddress = 192.168.1.24 with Error = Kan geen verbinding maken omdat de doelcomputer de verbinding actief heeft geweigerd 192.168.1.24:55000
      mrt-27 12:11:35 MC ConnectSocket called with ipAddress = 192.168.1.24 and ipPort = 55000
      mrt-27 12:11:35 MC EstablishTCPConnection called for UPnPDevice = [TV]Samsung LED22 and MyRemoteServiceActive = False
      mrt-27 12:11:35 MC CreateHSSamsungRemoteButtons called for UPnPDevice = [TV]Samsung LED22 and Recreate = False
      mrt-27 12:11:35 MC CreateSamsungRemoteIniFileInfo called for UPnPDevice = [TV]Samsung LED22
      mrt-27 12:11:35 MC ExtractAllServices for device = [TV]Samsung LED22 found DeviceManufacturer = Samsung Electronics
      mrt-27 12:11:35 MC ExtractAllServices for device = [TV]Samsung LED22 found additional service with ID = urn:samsung.com:serviceId:MultiScreenService
      mrt-27 12:11:35 MC ExtractAllServices for device = [TV]Samsung LED22 found 1 Services
      mrt-27 12:11:35 MC ProcessServiceDocument called for device = [TV]Samsung LED22 with URL = http://192.168.1.24:7676/smp_7_
      mrt-27 12:11:35 MC DeviceTrigger called for device - [TV]Samsung LED22 with Trigger = Player Online
      mrt-27 12:11:35 MC PlayChangeNotifyCallback called for device - [TV]Samsung LED22 with ChangeType = DeviceStatusChanged and Changevalue = Online
      mrt-27 12:11:35 MC DirectConnect for Device = [TV]Samsung LED22 added Image = for HSRef = 4
      mrt-27 12:11:35 MC DirectConnect for Device = [TV]Samsung LED22 checking for file = C:\Program Files (x86)\HomeSeer HS3/html/images/MediaController/Artwork/PlayerIcon_055d4a81-005a-1000-9803-40163b72896a.png
      mrt-27 12:11:35 MC DirectConnect for Device = [TV]Samsung LED22 found IconURL =
      mrt-27 12:11:35 MC DirectConnect called for [TV]Samsung LED22
      mrt-27 12:11:35 MC CreateUPnPControllers has found UPnpDevice = [TV]Samsung LED22 with on-line status = True and Adminstate = True
      mrt-27 12:11:35 MC ReadDeviceIniSettings called for device - [TV]Samsung LED22
      mrt-27 12:11:35 MC DeviceAPIIndex called for device = [TV]Samsung LED22 with API Index = 1
      mrt-27 12:11:35 MC GetNextFreeDeviceIndex found Index = 1
      mrt-27 12:11:35 MC GetNextFreeDeviceIndex called
      mrt-27 12:11:35 MC PlayerIconURL called for device = [TV]Samsung LED22 and IConURL =
      mrt-27 12:11:35 MC DeviceHSCode Set called for device - [TV]Samsung LED22 with DeviceRef = 4
      mrt-27 12:11:35 MC DeviceServiceType Set called for device - [TV]Samsung LED22 with ServiceType = RCR
      mrt-27 12:11:35 MC DeviceName called for device - with value = [TV]Samsung LED22
      mrt-27 12:11:34 MC InitMusicAPI called for device =
      mrt-27 12:11:34 MC InitIO Called for Instance = 055d4a81-005a-1000-9803-40163b72896a
      mrt-27 12:11:34 MC InitIO for Instance = 055d4a81-005a-1000-9803-40163b72896a found this plugin running on Linux = False
      mrt-27 12:11:34 MC InitIO Called for Instance = 055d4a81-005a-1000-9803-40163b72896a and running on OS = Win32NT
      mrt-27 12:11:34 MC InitIO for Instance = 055d4a81-005a-1000-9803-40163b72896a found HS running on Linux = False
      mrt-27 12:11:34 MC InitIO for Instance = 055d4a81-005a-1000-9803-40163b72896a found CurrentAppPath = C:\Program Files (x86)\HomeSeer HS3
      mrt-27 12:11:34 Info Plugin MediaController with instance 055d4a81-005a-1000-9803-40163b72896a has connected. IP:127.0.0.1:16564
      mrt-27 12:11:34 MC AddInstance called with InstanceName = 055d4a81-005a-1000-9803-40163b72896a
      mrt-27 12:11:34 MC CreateUPnPControllers found 1 devices and ActivateTheZone = True
      mrt-27 12:11:34 MC DetectUPnPDevices found UPnPDeviceName = [TV]Samsung LED22 on line = True
      mrt-27 12:11:34 MC CheckForInterestedServices for device = [TV]Samsung LED22 found Service ID = urn:samsung.com:serviceId:MultiScreenService
      mrt-27 12:11:34 MC CheckForInterestedServices for device = [TV]Samsung LED22 found 1 Services
      mrt-27 12:11:34 MC DetectUPnPDevices found new UPnPDeviceName = [TV]Samsung LED22 and On-line Status= True
      mrt-27 12:11:34 MC CheckForInterestedServices for device = [TV]Samsung LED22 added ServiceType = DMR
      mrt-27 12:11:34 MC CheckForInterestedServices for device = [TV]Samsung LED22 found Service ID = urn:upnp-org:serviceId:AVTransport
      mrt-27 12:11:34 MC CheckForInterestedServices for device = [TV]Samsung LED22 found Service ID = urn:upnp-org:serviceId:ConnectionManager
      mrt-27 12:11:34 MC CheckForInterestedServices for device = [TV]Samsung LED22 found Service ID = urn:upnp-org:serviceId:RenderingControl
      mrt-27 12:11:34 MC CheckForInterestedServices for device = [TV]Samsung LED22 found 3 Services
      mrt-27 12:11:34 MC DetectUPnPDevices found new UPnPDeviceName = [TV]Samsung LED22 and On-line Status= True
      mrt-27 12:11:34 MC CheckForInterestedServices for device = [TV]Samsung LED22 added ServiceType = DIAL
      mrt-27 12:11:34 MC CheckForInterestedServices for device = [TV]Samsung LED22 found Service ID = urn:dial-multiscreen-org:serviceId:dial
      mrt-27 12:11:34 MC CheckForInterestedServices for device = [TV]Samsung LED22 found 1 Services
      mrt-27 12:11:34 MC DetectUPnPDevices added a total of 3 devices
      mrt-27 12:11:34 MC FindUPnPDevice is adding a Samsung Electronics device with UDN = 055d4a81-005a-1000-9803-40163b72896a and Friendly Name = [TV]Samsung LED22 at Location = http://192.168.1.24:7676/smp_7_ and adding it to the array with index = 2
      mrt-27 12:11:34 MC FindUPnPDevice is adding a Samsung Electronics device with UDN = 08583b02-008c-1000-8d84-40163b72896a and Friendly Name = [TV]Samsung LED22 at Location = http://192.168.1.24:7676/smp_15_ and adding it to the array with index = 1
      mrt-27 12:11:34 MC FindUPnPDevice is adding a Samsung Electronics device with UDN = 055d4a82-005a-1000-9803-40163b72896a and Friendly Name = [TV]Samsung LED22 at Location = http://192.168.1.24:7676/smp_25_ and adding it to the array with index = 0
      mrt-27 12:11:34 MC FindUPnPDevice - Discovery succeeded: 11 UPnPDevice(s) found.
      mrt-27 12:11:26 MC Error Error in SetIOEx: Device not found for received event. Event = 2 DeviceRef = 4
      mrt-27 12:11:26 MC SetIOEx called for Ref = 4, Index 1, controlFlag = False, ControlString, ControlType = Button, ControlValue = 2, Label = Activate
      mrt-27 12:11:26 MC SetIOMulti set value: 2->ref:4
      mrt-27 12:11:26 MC SetIOMulti called
      mrt-27 12:11:26 Device Control Device: MediaController [TV]Samsung LED22 Device to Activate (2) by/from: CAPI Control Handler
      mrt-27 12:11:16 TTS Speak ():Welcome to Home-Seer
      mrt-27 12:11:15 Speaker Speaker host added, Name: ASUSI7LAPTOP Instance: Default IP address: 127.0.0.1
      mrt-27 12:11:04 MC MySSDP.StartSSDPDiscovery waiting for an additional 30 seconds while receiving and processing the UPnP Device Info .....
      mrt-27 12:10:59 MC MySSDP.StartSSDPDiscovery waiting for an additional 5 seconds while discovering UPnP Devices. Still 2 Entries awaiting processing .....
      mrt-27 12:10:58 MC GetPagePlugin for PlugInConfig called with pageName = MediaControl and user = default and userRights = 6 and queryString =
      mrt-27 12:10:58 MC hspi.GetPagePlugin called for instance = and pageName = MediaControl and user = default and userRights = 6 and queryString =
      mrt-27 12:10:57 MC Error Error in MyUPnPDevice.ProcessDeviceInfo for device = uuid:SSTV-X141-0000000000000019225651 while loading the device XML with XML = status=ok and error = Gegevens op hoofdniveau zijn ongeldig. Regel 1, positie 1.
      mrt-27 12:10:52 Web Server Web Server authorized local login successful from: 192.168.1.12 User: default
      mrt-27 12:10:50 Info System connected to MyHS Service successfully with license ID 58094.
      mrt-27 12:10:50 Info System connected to MyHS Service, waiting for acknowledge...
      mrt-27 12:10:50 MC MySSDP.StartSSDPDiscovery, waiting for 9 seconds while discovering UPnP Devices .....
      mrt-27 12:10:50 MC ConnectSocket called with mcastAddress = 239.255.255.250 and mcastPort = 1900 and LocalIpAddress = 127.0.0.1 and LocalIPPort = 0
      mrt-27 12:10:50 MC MCastSocket.new was called with MCastAddress = 239.255.255.250 and MCastPort = 1900
      mrt-27 12:10:50 MC ConnectSocket called with mcastAddress = 239.255.255.250 and mcastPort = 1900 and LocalIpAddress = 192.168.1.12 and LocalIPPort = 0
      mrt-27 12:10:50 MC MCastSocket.new was called with MCastAddress = 239.255.255.250 and MCastPort = 1900
      mrt-27 12:10:50 MC FindUPnPDevice: Attempting to locate all connected devices. This may take up to 9 seconds.
      mrt-27 12:10:50 MC DetectUPnPDevices called with Refresh = False
      mrt-27 12:10:50 MC MyTcpListener.Start successfully opened TCP Listening Port with HostAddress = 192.168.1.12 and HostIPPort = 16272
      mrt-27 12:10:50 MC MyTcpListener.Start called with HostAddress = 192.168.1.12
      mrt-27 12:10:50 MC ConnectSocket called with mcastAddress = 239.255.255.250 and mcastPort = 1900 and LocalIpAddress = 192.168.1.12 and LocalIPPort = 1900
      mrt-27 12:10:50 MC MCastSocket.new was called with MCastAddress = 239.255.255.250 and MCastPort = 1900
      mrt-27 12:10:50 MC MySSDP.CreateMulticastListener called for PlugInIPAddress = 192.168.1.12
      mrt-27 12:10:50 MC BuildUPnPHSDeviceInfoList found [TV]Samsung LED22 at Index 0
      mrt-27 12:10:50 MC BuildUPnPHSDeviceInfoList called
      mrt-27 12:10:50 MC InitializeUPnPDevices found MasterHSDeviceRef in the inifile. MasterHSDeviceRef = 3
      mrt-27 12:10:50 MC InitializeUPnPDevices called
      mrt-27 12:10:50 Startup Start up complete.
      mrt-27 12:10:50 MC SendEventForAllZones called. We have 0 devices
      mrt-27 12:10:50 Startup HSSentry is disabled in Setup, sentry will not be started.
      mrt-27 12:10:50 Startup (Startup.vb script) No speaker clients detected, waiting up to 30 seconds for any to connect...
      mrt-27 12:10:50 Startup (Startup.vb script) Scripting is OK and is now running Startup.vb
      mrt-27 12:10:50 Startup Starting Event Scheduler...
      mrt-27 12:10:49 Startup Running the startup script Startup.vb
      mrt-27 12:10:49 Startup Starting Find service...
      mrt-27 12:10:49 Startup Updater services starting...
      mrt-27 12:10:49 Database Opening (Mode=Read/Write) up HomeSeer Energy database C:\Program Files (x86)\HomeSeer HS3\Data\Energy\Energy.hsd
      mrt-27 12:10:49 Speech Listening for remote speaker connections on port 10401
      mrt-27 12:10:49 Startup Initializing Speaker Client Interface
      mrt-27 12:10:49 Startup Start automation engine...
      mrt-27 12:10:49 Startup Creating ASP.NET application host...
      mrt-27 12:10:49 Web Server Web Server started on port 80
      mrt-27 12:10:49 Web Server UPNP Discovery started
      mrt-27 12:10:49 Web Server Local IP address (subnet) is: 192.168.1.12 (255.255.255.0)
      mrt-27 12:10:49 Startup HStouch server started, waiting for clients to connect.
      mrt-27 12:10:49 MC Capabilities called. Capabilities are IO and Music
      mrt-27 12:10:49 HSTouch Server Server started on port 10200
      mrt-27 12:10:49 Plug-In Finished initializing plug-in MediaController
      mrt-27 12:10:49 MC Media Controller Plugin Initialized
      mrt-27 12:10:48 MC ReadIniFile called
      mrt-27 12:10:48 MC InitIO Called for Instance =
      mrt-27 12:10:48 MC InitIO for Instance = found this plugin running on Linux = False
      mrt-27 12:10:48 MC InitIO Called for Instance = and running on OS = Win32NT
      mrt-27 12:10:48 MC InitIO for Instance = found HS running on Linux = False
      mrt-27 12:10:48 MC InitIO for Instance = found CurrentAppPath = C:\Program Files (x86)\HomeSeer HS3
      mrt-27 12:10:48 Info Plugin MediaController has connected. IP:127.0.0.1:16267
      mrt-27 12:10:48 Startup Initializing Plug-Ins
      mrt-27 12:10:48 Plug-In Found plug-in: MQTT, version: 1.5.0.0
      mrt-27 12:10:48 Plug-In Found plug-in: MediaController, version: 3.0.0.28
      mrt-27 12:10:48 Startup Checking for available plug-ins
      mrt-27 12:10:48 Info Remote plug-in API interface started on port 10400
      mrt-27 12:10:48 Startup This version of HomeSeer is registered as a HS3PRO version.
      mrt-27 12:10:48 Startup Creating Speaker Client Interface Object...
      mrt-27 12:10:48 Startup HomeSeer version is: 3.0.0.368
      mrt-27 12:10:48 Load Config Loading TIMERS...
      mrt-27 12:10:48 Load Config Loading COUNTERS...
      mrt-27 12:10:48 Load Config 0 total events loaded.
      mrt-27 12:10:48 Load Config Loading Events...
      mrt-27 12:10:48 Load Config Loading Event Groups...
      mrt-27 12:10:48 Load Config 3 total devices loaded.
      mrt-27 12:10:48 Database Loading Devices...
      mrt-27 12:10:48 Database Opening (Mode=Read Only) up HomeSeer database C:\Program Files (x86)\HomeSeer HS3\Data\HomeSeerData.hsd
      mrt-27 12:10:48 Startup Loading configuration file ...
      mrt-27 12:10:48 Startup Database SAVE process started.
      mrt-27 12:10:48 Startup Local voice recognition class started.
      mrt-27 12:10:48 Startup HSPhone external interface class started.
      mrt-27 12:10:48 Startup Plug-In Interface class started.
      mrt-27 12:10:48 Startup E-Mail RECEIVE class started.
      mrt-27 12:10:48 Startup E-Mail SEND class started.
      mrt-27 12:10:48 Startup Web server class started.
      mrt-27 12:10:48 Startup Application interface class started.
      mrt-27 12:10:48 Startup COM port classes started.
      mrt-27 12:10:48 Startup Creating Class Objects...
      mrt-27 12:10:48 Startup
      mrt-27 12:10:48 Startup ************************************************************ ********************
      mrt-27 12:10:48 Startup HomeSeer version 3.0.0.368 Edition: HS3 Pro Starting Now
      mrt-27 12:10:48 Startup ************************************************************ ********************
      mrt-27 12:10:48 Startup
      mrt-27 12:10:48 Startup Settings Loaded.
      mrt-27 12:11:41 MC Error Error in ConnectCallback calling EndConnect with ipAddress = 192.168.1.24 with Error = Kan geen verbinding maken omdat de doelcomputer de verbinding actief heeft geweigerd 192.168.1.24:55000

      this is being translated because i run a dutch language version of windows.
      It says can not make connection wit host, connection is refused ip: 192..x.x.x.

      Comment


        Originally posted by Vincenttor View Post


        mrt-27 12:11:41 MC Error Error in ConnectCallback calling EndConnect with ipAddress = 192.168.1.24 with Error = Kan geen verbinding maken omdat de doelcomputer de verbinding actief heeft geweigerd 192.168.1.24:55000
        I'm afraid your model doesn't support the IP-Remote function anymore OR the allowance for remote control isn't set on the TV. First time you set this up (read help file) you should acknowledge this on the TV itself. However, newer Samsung TVs don't support this anymore, not sure when (I think post E series).

        Can't tell why the PI appears to hang except that each time you click on a remote button, the PI knows there is no TCP connection to do remote control and tries to establish that. I suspect that there is no response after a while and things are waiting for it to timeout or something else unanticipated in the PI.

        Dirk

        Comment


          Thanks for your time Dirk,
          i have tried to update the software also but that did not help.
          Will go on the IR solution then.

          who knows maybe there will come a solution since by the android app it works pretty good.

          thanks

          Vince

          Comment


            Originally posted by Vincenttor View Post
            Thanks for your time Dirk,
            i have tried to update the software also but that did not help.
            Will go on the IR solution then.

            who knows maybe there will come a solution since by the android app it works pretty good.

            thanks

            Vince
            There is a solution but it is encrypted and not clear whether anyone ever managed to figure out how. I have a newer model Samsung and LG so I'm motivated to figure it out. I did some latest searches and some guy claimed to have made an app that can communicate. I'll look at it some more but in the past it all turned out to be older models. I have same issue with LG TVs, the remote commands are encrypted and I can't find anyone who figured it out and it really seems to be year to year dependent

            Dirk

            Comment


              Originally posted by Vincenttor View Post
              Thanks for your time Dirk,
              i have tried to update the software also but that did not help.
              Will go on the IR solution then.

              who knows maybe there will come a solution since by the android app it works pretty good.

              thanks

              Vince
              There seems to be one knowledgeable guy out there who seems to have figured out the protocol for all TVs EXCEPT H and J (I have JS8500 grrr)

              See this table here:
              https://github.com/Ape/samsungctl/wiki/Supported-Models

              If anyone out there has a K series or newer; I would be interested to know whether this PI work for it, if not take some traces.

              Do you think you can key in following URLs in your browser and copy/paste it here.

              http://192.168.1.24:7676/smp_7
              http://192.168.1.24:7676/smp_15
              http://192.168.1.24:7676/smp_25

              Would be curious to see what an H-series Samsung posts. This guy (https://github.com/timelery/Samsung-RemoteControl) seems to have used an external DLL to make it work for H and J series, I'm going to study that a bit more.

              Dirk

              Comment


                SMP7
                <root><specVersion><major>1</major><minor>0</minor></specVersion><device><deviceType>urn:samsung.com:device:Remot eControlReceiver:1</deviceType><friendlyName>[TV]Samsung LED22</friendlyName><manufacturer>Samsung Electronics</manufacturer><manufacturerURL>http://www.samsung.com/sec</manufacturerURL><modelDescription>Samsung TV RCR</modelDescription><modelName>UE22H5600</modelName><modelNumber>1.0</modelNumber><modelURL>http://www.samsung.com/sec</modelURL><serialNumber>20090804RCR</serialNumber><UDN>uuid:055d4a81-005a-1000-9803-40163b72896a</UDN><sec:deviceID>7XCLEH4SFRFJM</sec:deviceID><sec:ProductCap>Resolution:1920X1080,ImageZoom, ImageRotate,Y2014,ENC</sec:ProductCap><serviceList><service><serviceType>urn:samsun g.com:service:MultiScreenService:1</serviceType><serviceId>urn:samsung.com:serviceId:MultiScreen Service</serviceId><controlURL>/smp_9_</controlURL><eventSubURL>/smp_10_</eventSubURL><SCPDURL>/smp_8_</SCPDURL></service></serviceList><sec:Capabilities><sec:Capability name="samsung:multiscreen:1" port="8001" location="/ms/1.0/"/></sec:Capabilities></device></root>
                SMP15
                <root><specVersion><major>1</major><minor>0</minor></specVersion><device><deviceType>urn:schemas-upnp-org:device:MediaRenderer:1</deviceType><pnpx:X_compatibleId>MS_DigitalMediaDeviceClass_D MR_V001</pnpx:X_compatibleId><df:X_deviceCategory>Display.TV.LCD Multimedia.DMR</df:X_deviceCategory><dlna:X_DLNADOC>DMR-1.50</dlna:X_DLNADOC><friendlyName>[TV]Samsung LED22</friendlyName><manufacturer>Samsung Electronics</manufacturer><manufacturerURL>http://www.samsung.com/sec</manufacturerURL><modelDescription>Samsung TV DMR</modelDescription><modelName>UE22H5600</modelName><modelNumber>AllShare1.0</modelNumber><modelURL>http://www.samsung.com/sec</modelURL><serialNumber>20110517DMR</serialNumber><UDN>uuid:08583b02-008c-1000-8d84-40163b72896a</UDN><sec:deviceID>7XCLEH4SFRFJM</sec:deviceID><iconList><icon><mimetype>image/jpeg</mimetype><width>48</width><height>48</height><depth>24</depth><url>/dmr/icon_SML.jpg</url></icon><icon><mimetype>image/jpeg</mimetype><width>120</width><height>120</height><depth>24</depth><url>/dmr/icon_LRG.jpg</url></icon><icon><mimetype>image/png</mimetype><width>48</width><height>48</height><depth>24</depth><url>/dmr/icon_SML.png</url></icon><icon><mimetype>image/png</mimetype><width>120</width><height>120</height><depth>24</depth><url>/dmr/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>/smp_17_</controlURL><eventSubURL>/smp_18_</eventSubURL><SCPDURL>/smp_16_</SCPDURL></service><service><serviceType>urn:schemas-upnp-org:service:ConnectionManager:1</serviceType><serviceId>urn:upnp-org:serviceId:ConnectionManager</serviceId><controlURL>/smp_20_</controlURL><eventSubURL>/smp_21_</eventSubURL><SCPDURL>/smp_19_</SCPDURL></service><service><serviceType>urn:schemas-upnp-org:service:AVTransport:1</serviceType><serviceId>urn:upnp-org:serviceId:AVTransport</serviceId><controlURL>/smp_23_</controlURL><eventSubURL>/smp_24_</eventSubURL><SCPDURL>/smp_22_</SCPDURL></service></serviceList><sec:ProductCap>Y2014,WebURIPlayable,SeekTRACK_N R,NavigateInPause,ScreenMirroringP2PMAC=ce:b1:1a:0e:4c:5d</sec:ProductCap><pnpx:X_hardwareId>VEN_0105&DEV_VD0001</pnpx:X_hardwareId></device></root>
                SMP22
                <root><specVersion><major>1</major><minor>0</minor></specVersion><device><deviceType>urn:dial-multiscreen-org:device:dialreceiver:1</deviceType><friendlyName>[TV]Samsung LED22</friendlyName><manufacturer>Samsung Electronics</manufacturer><manufacturerURL>http://www.samsung.com/sec</manufacturerURL><modelDescription>Samsung TV NS</modelDescription><modelName>UE22H5600</modelName><modelNumber>1.0</modelNumber><modelURL>http://www.samsung.com/sec</modelURL><serialNumber>20090804RCR</serialNumber><UDN>uuid:055d4a82-005a-1000-9803-40163b72896a</UDN><sec:deviceID>7XCLEH4SFRFJM</sec:deviceID><sec:ProductCap>Resolution:1280X720,Y2014</sec:ProductCap><serviceList><service><serviceType>urn:dial-multiscreen-org:service:dial:1</serviceType><serviceId>urn:dial-multiscreen-org:serviceId:dial</serviceId><controlURL>/smp_27_</controlURL><eventSubURL>/smp_28_</eventSubURL><SCPDURL>/smp_26_</SCPDURL></service></serviceList><sec:Capabilities><sec:Capability name="samsung:multiscreen:1" port="8001" location="/ms/1.0/"/></sec:Capabilities></device></root>

                When using the app on my phone it asks me when it connects to the tv to exchange/enter a pin code.
                Tried to do this manually and been in every menu setting.
                But could not add my computer or find it in the menu.

                Also tried disabling the security part, seems to have some sort of "virus" scan build in the software.
                This did not work either.


                Been thinking of buying another tv that does support it haha.
                but it would be great if this would work since its easier to set the tv to a certain source/channel instead of using IR.


                ( i can give you acces on a computer if you like here and put a webcam pointed on the tv, IR control to turn it on/off/ so you can test some stuff.)

                Comment


                  Originally posted by Vincenttor View Post
                  SMP7


                  SMP15


                  SMP22



                  When using the app on my phone it asks me when it connects to the tv to exchange/enter a pin code.
                  Tried to do this manually and been in every menu setting.
                  But could not add my computer or find it in the menu.

                  Also tried disabling the security part, seems to have some sort of "virus" scan build in the software.
                  This did not work either.


                  Been thinking of buying another tv that does support it haha.
                  but it would be great if this would work since its easier to set the tv to a certain source/channel instead of using IR.


                  ( i can give you acces on a computer if you like here and put a webcam pointed on the tv, IR control to turn it on/off/ so you can test some stuff.)
                  This info is great, will help to identify the year/capabilities of the TV.
                  My TV is same as yours (wrt to capability) so I can test it on mine. I have been busy coding the protocol, not sure it will work but I'm drawing on info of various other authors how they got it to work. Stay tuned for a few more days, you may have to become my first guinea pig.
                  Dirk

                  Comment


                    O thats great
                    thanks Dirk.
                    Can't wait to see it running

                    Comment


                      Originally posted by Vincenttor View Post
                      O thats great
                      thanks Dirk.
                      Can't wait to see it running
                      It will run but will it work

                      Comment


                        Originally posted by dcorsus View Post
                        There seems to be one knowledgeable guy out there who seems to have figured out the protocol for all TVs EXCEPT H and J (I have JS8500 grrr)

                        See this table here:
                        https://github.com/Ape/samsungctl/wiki/Supported-Models

                        If anyone out there has a K series or newer; I would be interested to know whether this PI work for it, if not take some traces.

                        Do you think you can key in following URLs in your browser and copy/paste it here.

                        http://192.168.1.24:7676/smp_7
                        http://192.168.1.24:7676/smp_15
                        http://192.168.1.24:7676/smp_25

                        Would be curious to see what an H-series Samsung posts. This guy (https://github.com/timelery/Samsung-RemoteControl) seems to have used an external DLL to make it work for H and J series, I'm going to study that a bit more.

                        Dirk
                        Hi Dirk,

                        Recently I bought the Samsung UE55MU7070. Unfortunately the plugin does not work yet. Discovering seems to work fine, but then when I try to add the remote function the plugin seems to crash and Homeseer stops reacting until I kill the plugin. A device is added anyway and I can create the remote buttons, but if I try anybutton the plugin seems to crash.

                        I just tried samsungctl, which works (only tried volume up and down). The strange thing is that I didn't first have to allow the remote access for my laptop, as was the case for the Samsung Smart View app from my iPhone.

                        Please let me know how I can help to take some traces.
                        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
                          Hi Dirk,

                          Recently I bought the Samsung UE55MU7070. Unfortunately the plugin does not work yet. Discovering seems to work fine, but then when I try to add the remote function the plugin seems to crash and Homeseer stops reacting until I kill the plugin. A device is added anyway and I can create the remote buttons, but if I try anybutton the plugin seems to crash.

                          I just tried samsungctl, which works (only tried volume up and down). The strange thing is that I didn't first have to allow the remote access for my laptop, as was the case for the Samsung Smart View app from my iPhone.

                          Please let me know how I can help to take some traces.
                          Go to the PI's config page and delete the remote devices. Then turn on the debug flag, perhaps the log to disk flag, restart hs3 and try to add the remote control device. Close log to disk; post log file (html\mediacontroller\logs\medicacontroller.txt

                          Dirk

                          Comment


                            Originally posted by dcorsus View Post
                            Go to the PI's config page and delete the remote devices. Then turn on the debug flag, perhaps the log to disk flag, restart hs3 and try to add the remote control device. Close log to disk; post log file (html\mediacontroller\logs\medicacontroller.txt

                            Dirk
                            Thanks. Please see the attached files. There are a few things that I find strange myself: 1. The MCastAddress is not in my network's subnet. 2. And I see the PI tries to use port 55000, which is denied. I think it should be 8001 (based on https://forums.homeseer.com/showthread.php?t=190489 - a K series TV).

                            Some explanation, so the eventlog might make more sense: For the occasion I have done a clean install of Homeseer on my work laptop. It's running in demo mode. And I had to restart HS to be able to go to the PI's config page again and turn off log to disk, as it did not respond anymore.
                            Attached Files
                            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
                              Thanks. Please see the attached files. There are a few things that I find strange myself: 1. The MCastAddress is not in my network's subnet. 2. And I see the PI tries to use port 55000, which is denied. I think it should be 8001 (based on https://forums.homeseer.com/showthread.php?t=190489 - a K series TV).

                              Some explanation, so the eventlog might make more sense: For the occasion I have done a clean install of Homeseer on my work laptop. It's running in demo mode. And I had to restart HS to be able to go to the PI's config page again and turn off log to disk, as it did not respond anymore.
                              The debug file was taken with the debug flag off. Can you do again with log-to-disk AND debug flag on. So NOT the superdebug flag and NOT the UPNP-logging level.

                              No need to reinstall all, just restart HS and make sure the debug flags were both on before you restarted HS. Remember that the log-to-disk flag MUST be turned off before you upload the log file as turning it off, writes the last log entries to disk.

                              Dirk

                              Comment


                                Originally posted by dcorsus View Post
                                The debug file was taken with the debug flag off. Can you do again with log-to-disk AND debug flag on. So NOT the superdebug flag and NOT the UPNP-logging level.

                                No need to reinstall all, just restart HS and make sure the debug flags were both on before you restarted HS. Remember that the log-to-disk flag MUST be turned off before you upload the log file as turning it off, writes the last log entries to disk.

                                Dirk
                                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.
                                Attached Files
                                Last edited by Bernold; April 2, 2018, 06:20 AM. Reason: Figured out how to get PI connected again
                                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

                                Working...
                                X