Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 3.0.0-Alpha.1 not detecting TCL 55C807 during setup #118

Open
isupremedyou opened this issue Aug 12, 2019 · 9 comments
Open

Version 3.0.0-Alpha.1 not detecting TCL 55C807 during setup #118

isupremedyou opened this issue Aug 12, 2019 · 9 comments
Labels

Comments

@isupremedyou
Copy link

I am using Version 3.0.0-Alpha.1
My Roku TV is the TCL 55C807

Whenever I run the homebridge-roku-config, it gets a timeout error saying no Roku devices are found in 10 seconds.

I have confirmed that my homebridge server is running on the same network as the TV. I tried extending the timeout up to 60 seconds and that did not help either.

Is there anything I am missing?

@isupremedyou isupremedyou changed the title Version 3.0.0-Alpha.1 not detecting TCL Version 3.0.0-Alpha.1 not detecting TCL 55C807 during setup Aug 12, 2019
@isupremedyou
Copy link
Author

isupremedyou commented Aug 13, 2019

The error that prints out is:

Error: Could not find any Roku devices after 10 seconds
    at RokuFinder.<anonymous> (/usr/local/lib/node_modules/homebridge-roku/node_modules/roku-client/dist/discover.js:95:20)
    at RokuFinder.emit (events.js:198:13)
    at Timeout.done (/usr/local/lib/node_modules/homebridge-roku/node_modules/roku-client/dist/discover.js:61:19)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

@fullmetaljester
Copy link

Having this same issue with a TCL 65R615

@isupremedyou
Copy link
Author

isupremedyou commented Jan 25, 2020

@fullmetaljester I ended up having to hardcode the values in the homebridge config.json file, let me know if you need any help with that

@fullmetaljester
Copy link

i suspected that might be the case. I'm actually doing it in HOOBS too but the process is the same just via the GUI.

@hetkin
Copy link

hetkin commented Feb 22, 2020

I'm having the same problem with a TCL Roku TV. Can anyone share their config?

@bschlenk bschlenk added the bug label Jun 1, 2020
@isupremedyou
Copy link
Author

@hetkin do you have Google WiFi? I ask because today I switched over to using Eero for my WiFi and I was able to get the plugin to detect my TV.

@bschlenk
Copy link
Owner

I’m not sure what causes this. I switched to ATT fiber recently, and for a couple of days I was unable to auto discover my TV. But I tried again a few days later and it worked. I initially suspected that my router blocked UPnP, but I didn’t change any config for it to start working. You could check if your router is blocking UPnP.

Otherwise, I’ve been working on a more user friendly homebridge-roku-config command that’ll be interactive, and if it fails to find any devices then it’ll ask for the Roku IP before continuing. I’m not sure when I’ll have time to finish working on it though.

@mushbuddygoose
Copy link

mushbuddygoose commented Oct 20, 2020

@isupremedyou @fullmetaljester I ended up having to hardcode the values in the homebridge config.json file, let me know if you need any help with that

Could you share your config. I cant get my tcl to work either and not sure what i need in the config

@Jacksonbm1
Copy link

Anyone have any luck on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants