Able to pair, turn off once, then not able to turn off or use remote again #47
Comments
|
Hm strange... this is probable a library agnostic problem that originates from this library. I am not 100% familiar with the way this library actually controls the tv unfortunately. Maybe I'll try to dive a bit deeper into the library to fix some bugs like these myself when I find some time to do so. |
|
Below is the error printed in the HomeBridge log when I press the Power button on the device from both the Home app and from HomeBridge accessories:
|
|
Same issue here, it was OK for the first time / day, now trowing this error for every button press. |
|
Same Issue. Managed to reconnect by (1) Resetting Samsung TV to factory settings, (2) reinstalling "SamsungTV Control" and going through pairing again. Sadly, the TV Q85T2020 now continuously want me to "Allow Node.js" each and everytime I send a command (and the command isn't implemented). Other wise the programming is really neat and Mr MMENDE deserves credit for the neatest yet seen Homebridge installation + auto config code. 😄 (Very happy to provide Logs if this is helpful. Just message me :) ) |
|
Same here, keeps asking to allow Node.js |
|
looked at this for a bit. At least for devices that use the underlying samsung-tv-control (which I think is any device that is requiring the pin, but 🤷♂️), the token isn't being passed over. Specifically, the initiation of it here const control = new Samsung(cfg)is passing in this config const cfg = getRemoteConfig(config)which is being generated by this function const getRemoteConfig = (config: DeviceConfig) => {
const model = parseSerialNumber(config.modelName)
const { year = 2013 } = model || {}
const supportsLegacy = typeof year === `number` && year < 2014
const port = config.remoteControlPort || supportsLegacy ? 55000 : 8002
return {
mac: config.mac,
ip: config.lastKnownIp,
name: PLATFORM_NAME,
port,
}
}the token that is being added to the configuration file is not being passed in. I manually added this line token: config.token,to my own version locally, and its working now. const getRemoteConfig = (config: DeviceConfig) => {
const model = parseSerialNumber(config.modelName)
const { year = 2013 } = model || {}
const supportsLegacy = typeof year === `number` && year < 2014
const port = config.remoteControlPort || supportsLegacy ? 55000 : 8002
return {
mac: config.mac,
ip: config.lastKnownIp,
name: PLATFORM_NAME,
token: config.token,
port,
}
} |
|
Thanks for the effort @patrickkettner. I just added your changes and published v2.0.3 |
|
Hi Guys, Thanks for the update, I've tested it, was good for a few days, than it started to throwing this again: (node:30540)_ UnhandledPromiseRejectionWarning: Error: Unable to handleEvent |
|
Tried to remove and add again, now it TV cant be added anymore. Mabye its from IOS 15? |
I was able to pair my TV using pair1. I have tried other ways to see if I could avoid what happens, but only pair1 seems to work with my TV.
I pair successfully, add the device in the Home app and am able to control the device using the iOS remote. I am able to see the status of the TV (on or off). I can power off the device once only, then the device never responds to power off again. I can still see the status in Home, cannot use the remote any longer in iOS, I can change the volume and mute/unmute Homebridge but also cannot power the device off.
When I try to power off the device again I get an UnhandledPromiseRejectionWarning in my logs. I apologize as I cannot paste the full text as iOS is not letting me copy it. I can grab them and post them later.
The text was updated successfully, but these errors were encountered: