UE65F9000 with SEK-3500 not showing in log about homebridge-samsungtv-control2 HOT 6 OPEN

Can you test if the tv can be discovered with this command:

npx homebridge-samsungtv-control discover

from homebridge-samsungtv-control2.

Thanks for the quick reply.

It has been "Searching for devices" for over 3 minutes...
Don't know how long it usually takes but guess this is not really what you wanted to hear😂

from homebridge-samsungtv-control2.

Finally a result...

Searching for devices...
Got error while trying to check device with usn: "uuid:5bf091cc-4955-4398-aeb4-44a27fa888c4". GotError: connect ETIMEDOUT 10.123.176.1:9197
at onError (/usr/lib/node_modules/homebridge-samsungtv-control/node_modules/got/dist/source/request-as-event-emitter.js:140:29)
at handleRequest (/usr/lib/node_modules/homebridge-samsungtv-control/node_modules/got/dist/source/request-as-event-emitter.js:173:17)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16) {
name: 'RequestError',
code: 'ETIMEDOUT'
}
😞 No Samsung TV found. Remember to turn on your Samsung TV's and check if they are connected to the same network before starting the discovery.

from homebridge-samsungtv-control2.

Hm strange. No 3 minutes is not particularly the expected time it should take 😉. For me it takes about 6s.

It seems like the timeout appears when the discovery method tries to check the device description via upnp. Maybe there is some extra setting in the tv menu that disables other devices from fetching the device description via upnp...

from homebridge-samsungtv-control2.

I think your plugin gets the wrong device type authorisation from the TV.
The myTifi app works and gets a "SLEEPsense" service authorisation in "Multimedia Device Manager" but Homebridge gets "Play Mobile Content on TV".
So I think the pairing gets a screen mirroring auth or so instead of a remote control auth.
In M-Search the xml files are accessible that hold the appropriate device description.

The 192.168.0.35 is the wired IP.
The 2x 10.123.17x.1 are for Wifi direct? Not pingable though...

SSDP reply message from 10.123.176.1:9197
XML file is located at http://10.123.176.1:9197/dmr
Device is running SHP, UPnP/1.0, Samsung UPnP SDK/1.0

SSDP reply message from 10.123.175.1:9197
XML file is located at http://10.123.175.1:9197/dmr
Device is running SHP, UPnP/1.0, Samsung UPnP SDK/1.0

SSDP reply message from 10.123.175.1:7679
XML file is located at http://10.123.175.1:7679/MainTVServer2/
Device is running SHP, UPnP/1.0, Samsung UPnP SDK/1.0

SSDP reply message from 192.168.0.35:9197
XML file is located at http://192.168.0.35:9197/dmr
Device is running SHP, UPnP/1.0, Samsung UPnP SDK/1.0

SSDP reply message from 192.168.0.35:7679
XML file is located at http://192.168.0.35:7679/MainTVServer2/
Device is running SHP, UPnP/1.0, Samsung UPnP SDK/1.0

SSDP reply message from 10.123.175.1:7676
XML file is located at http://10.123.175.1:7676/rcr/
Device is running SHP, UPnP/1.0, Samsung UPnP SDK/1.0

SSDP reply message from 192.168.0.35:7676
XML file is located at http://192.168.0.35:7676/rcr/
Device is running SHP, UPnP/1.0, Samsung UPnP SDK/1.0

SSDP reply message from 192.168.0.35:7678
XML file is located at http://192.168.0.35:7678/nservice/
Device is running SHP, UPnP/1.0, Samsung UPnP SDK/1.0

from homebridge-samsungtv-control2.

If you are interested, I made TCP dumps from the authorisation between the myTifi app and the TV and your plugin and the TV .
Sadly this is beyond my comprehension but maybe it could be useful to you?

from homebridge-samsungtv-control2.