Adam Ant Posted December 1, 2022 Share Posted December 1, 2022 (edited) 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 December 10, 2022 by Adam Ant Link to comment
bpwwer Posted December 1, 2022 Share Posted December 1, 2022 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). Link to comment
Adam Ant Posted December 1, 2022 Author Share Posted December 1, 2022 (edited) 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 December 10, 2022 by Adam Ant Link to comment
bpwwer Posted December 2, 2022 Share Posted December 2, 2022 Well, that change didn't do what I wanted, I'll have to make another version. Link to comment
Adam Ant Posted December 2, 2022 Author Share Posted December 2, 2022 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 Link to comment
bpwwer Posted December 2, 2022 Share Posted December 2, 2022 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. Link to comment
Adam Ant Posted December 2, 2022 Author Share Posted December 2, 2022 (edited) 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 December 10, 2022 by Adam Ant Link to comment
Solution bpwwer Posted December 3, 2022 Solution Share Posted December 3, 2022 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. Link to comment
Adam Ant Posted December 3, 2022 Author Share Posted December 3, 2022 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! Link to comment
Adam Ant Posted December 3, 2022 Author Share Posted December 3, 2022 That fixed the issue! Will I need to stay on the beta moving forward? Link to comment
bpwwer Posted December 3, 2022 Share Posted December 3, 2022 No, I'll clean up the change and push it to the production store. Link to comment
Adam Ant Posted December 3, 2022 Author Share Posted December 3, 2022 thanks again! have a great weekend! Link to comment
Recommended Posts