BKreger Posted July 3 Share Posted July 3 I installed the Roku trail in PG3 and I am having discovery issues. I am getting the following errors. Based on other posts I have already enabled the remote app control. 2024-07-03 08:12:51.135 MainThread udi_interface ERROR roku:discover: Discovery failed for http://192.168.0.13:8060/: 'user-device-location' 2024-07-03 08:12:51.425 MainThread udi_interface ERROR roku:discover: Discovery failed for http://192.168.0.14:8060/: encoding without a string argument Link to comment
bpwwer Posted July 3 Share Posted July 3 It's not getting the data it expects from the devices. If you enable debug log level, it will show more info on what it is getting from the devices. Link to comment
BKreger Posted July 5 Author Share Posted July 5 It states user-device-location. I can see where it states 'LOCATION': 'http://192.168.0.13:8060/' but I'm not sure if that is what it is referring to. Here is the discovery portion with debug: --------------------------------------------- 2024-07-05 08:09:07.897 MainThread udi_interface DEBUG roku:discover: Processing http://192.168.0.13:8060/ 2024-07-05 08:09:07.897 MainThread udi_interface DEBUG roku:discover: roku_dev = {'WAKEUP': 'MAC=b8:3e:59:03:c1:f5;Timeout=10', 'device-group.roku.com': '86726741FD3B4DF4D742', 'LOCATION': 'http://192.168.0.13:8060/', 'Server': 'Roku UPnP/1.0 Roku/9.1.0', 'Ext': '', 'USN': 'uuid:roku:ecp:13G2DV061196', 'ST': 'roku:ecp', 'Cache-Control': 'max-age=3600'} 2024-07-05 08:09:07.996 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2024-07-05 08:09:07.996 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2024-07-05 08:09:07.996 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2024-07-05 08:09:08.330 MainThread udi_interface ERROR roku:discover: Discovery failed for http://192.168.0.13:8060/: 'user-device-location' 2024-07-05 08:09:08.330 MainThread udi_interface INFO roku:discover: Discovery finished Link to comment
BKreger Posted July 5 Author Share Posted July 5 I should mention, I was using the same Roku device on the PG2 version and did not have any issue. Link to comment
bpwwer Posted July 5 Share Posted July 5 The device data for your Roku doesn't have the field 'user-device-location' in it, which it should. I pushed a new version, 2.0.6, that adds a debug message which displays the device data so we can look at what your device is returning. Link to comment
BKreger Posted July 9 Author Share Posted July 9 Thanks!! I'm travelling this week but will load the new version and post the debug logs this weekend. Link to comment
BKreger Posted July 17 Author Share Posted July 17 Well, I loaded up the new version and was going to capture the log file but I inadvertently held the button down on the Roku for to long while plugging it back in and it factory reset the device. The good news is after going through the Roku setup the auto discover worked perfectly and it is working now. If anyone encounters this issue I would suggest a factory reset. It really only takes a few minutes to select your language and re-enter the Wifi info. Way faster than the hour or two I spent trying to troubleshoot. Also, it was clearly a Roku problem and not the PG3 app. Thanks for all your help! 1 Link to comment
Recommended Posts