tavicu / homebridge-samsung-tizen

Homebridge plugin for Samsung TV's with Tizen OS
MIT License
638 stars 86 forks source link

Pairing is failing #600

Closed Yarrlm closed 1 year ago

Yarrlm commented 1 year ago

I have installed the plugin the TV appears to be compatible. I have 2 TVs. One is older with the older menu style.

When i run the http://TV_IP:8001/api/v2/, i get responses back on both. I have manually added to HomeKit. HomeKit can see it because when the TV is ON the home kit button is lit up. When TV is OFF the Home kit button is not lit up. I was getting an E/1 error in the screen but that has not come back in some time. I never got the "Allow" pop up message. I have uninstalled and reinstalled several times. I have also tried the UUiD change command that was recommended.

The DeBug is from the "Newer" TV with the newer style of menus that was listed in the other troubleshooting

1/2/2023, 12:18:05 PM] [SamsungTizen] Initializing SamsungTizen platform... [1/2/2023, 12:18:05 PM] [SamsungTizen] Initializing child bridge 0E:84:D9:3D:A3:81 [1/2/2023, 12:18:17 PM] [homebridge-samsung-tizen] Launched child bridge with PID 32747 [1/2/2023, 12:18:17 PM] Registering platform 'homebridge-samsung-tizen.SamsungTizen' [1/2/2023, 12:18:17 PM] [homebridge-samsung-tizen] Loaded homebridge-samsung-tizen v5.2.4 child bridge successfully [1/2/2023, 12:18:17 PM] Loaded 0 cached accessories from cachedAccessories.0E84D93DA381. [1/2/2023, 12:18:17 PM] Publishing bridge accessory (name: homebridge-samsung-tizen, publishInfo: { username: '0E:84:D9:3D:A3:81', port: 46987, pincode: '*-*-', category: 2, bind: [ 'bond0', [length]: 1 ], mdns: undefined, addIdentifyingMaterial: true, advertiser: 'bonjour-hap' }). [1/2/2023, 12:18:17 PM] Homebridge v1.6.0 (HAP v0.11.0) (homebridge-samsung-tizen) is running on port 46987. [1/2/2023, 12:18:17 PM] [Living Room TV] [DEBUG] { frametv: false, tokenauth: true, powerstate: true } [1/2/2023, 12:18:17 PM] Publishing external accessory (name: Living Room TV, publishInfo: { username: '9C:2C:EA:4D:1E:1C', pincode: '*-*-', category: 31, port: undefined, bind: [ 'bond0', [length]: 1 ], mdns: undefined, addIdentifyingMaterial: true, advertiser: 'bonjour-hap' }). [1/2/2023, 12:18:17 PM] Living Room TV 2030 is running on port 35912. [1/2/2023, 12:18:17 PM] Please add [Living Room TV 2030] manually in Home app. Setup Code: 511-94-576 1/2/2023, 12:18:27 PM] [Living Room TV] [DEBUG] { event: 'ms.channel.timeOut' } [1/2/2023, 12:18:30 PM] [Living Room TV] [DEBUG] Failed to open socket {"event":"ms.channel.timeOut"} [1/2/2023, 12:18:31 PM] [Living Room TV] [DEBUG] { event: 'ms.channel.timeOut' } [1/2/2023, 12:18:34 PM] [Living Room TV] [DEBUG] Failed to open socket {"event":"ms.channel.timeOut"} [1/2/2023, 12:18:35 PM] [Living Room TV] [DEBUG] { event: 'ms.channel.timeOut' } [1/2/2023, 12:18:38 PM] [Living Room TV] [DEBUG] Failed to open socket {"event":"ms.channel.timeOut"} [1/2/2023, 12:18:38 PM] [Living Room TV] Failed to pair! Make sure TV is online and you click "Allow" on the popup [1/2/2023, 12:18:38 PM] [Living Room TV] [DEBUG] PairFailedError: Failed to pair! Make sure TV is online and you click "Allow" on the popup at WebSocketSecure.pair (/volume1/homebridge/node_modules/homebridge-samsung-tizen/lib/methods/wss.js:38:19)

tavicu commented 1 year ago

As you can see in the logs the homebridge server can't reach the TV. The IP can be wrong, the devices may be in different subnets, maybe something on your network block the request