Jump to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Not finding any Roku devices

Featured Replies

Posted

Hello, i am have recently purchased the Roku Node server.   It installed fine but is not finding any devices.  When using a Roku iphone app it is finding all my roku devices (5 of them) just fine so no network issue etc. They all have normal names (like "living Room") with no special characters so not running into that bug..  I have left the polling numbers at the default values with no luck and tried 5/60 instead with no improvement.        I had used the previous ( free) version and it had been working great a while back.    Attached is the log.  Any ideas? 

 

Edited by Adam Ant

Solved by bpwwer

Go to solution

That error is happening in the roku python library that the node node server is using.  I could make the node server handle the error better, but I'm not sure I can do anything about the library failing.

It is finding a Roku device (or devices) but the data it's getting back when querying the device is not what is expected.

I just created a version with some error checking and additional debug.  It's in the non-production store and is version 2.0.3.  (refresh the store if it still shows version 2.0.2)

You can install this version either by re-installing in the same slot or installing to a new slot and then download and post the node server log here (I don't need the log package).

  • Author
On 12/1/2022 at 11:38 AM, bpwwer said:

That error is happening in the roku python library that the node node server is using.  I could make the node server handle the error better, but I'm not sure I can do anything about the library failing.

It is finding a Roku device (or devices) but the data it's getting back when querying the device is not what is expected.

I just created a version with some error checking and additional debug.  It's in the non-production store and is version 2.0.3.  (refresh the store if it still shows version 2.0.2)

You can install this version either by re-installing in the same slot or installing to a new slot and then download and post the node server log here (I don't need the log package).

Thank you!  Here you go!  I let it run for about 5 min...

 

Edited by Adam Ant

  • Author
17 hours ago, bpwwer said:

Well, that change didn't do what I wanted, I'll have to make another version

I will be on the lookout for it.  Thanks!

Adam

You can try re-installing the beta version.  Use the option to re-install it to the same slot you used before (non-production store -> Roku -> install -> re-install 

This version should at least show what it finds during discovery.

  • Author
On 12/2/2022 at 12:45 PM, bpwwer said:

You can try re-installing the beta version.  Use the option to re-install it to the same slot you used before (non-production store -> Roku -> install -> re-install 

This version should at least show what it finds during discovery.

Not sure why but could not reinstall.    it wanted me to select the node and would not allow me to select the current node.  I just deleted it and reinstalled.   please see log attached.  thanks!

 

Edited by Adam Ant

  • Solution

I think I see the problem.  This is the first "roku" device it finds: http://192.168.1.134:40000 which doesn't look like a roku device at all.  So something else is responding to the roku discovery broadcast.

I just uploaded a new beta that may resolve the issue.  All it really needs to do is skip this non-roku device and continue and it should find the real roku devices.

  • Author
20 minutes ago, bpwwer said:

I think I see the problem.  This is the first "roku" device it finds: http://192.168.1.134:40000 which doesn't look like a roku device at all.  So something else is responding to the roku discovery broadcast.

I just uploaded a new beta that may resolve the issue.  All it really needs to do is skip this non-roku device and continue and it should find the real roku devices.

Wow!  Strange!  That's my Home Assistant unit.   I really appreciate your help!

 

Guest
This topic is now closed to further replies.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.