jec6613 Posted February 9 Share Posted February 9 Discovery on initial startup isn't working, and I've tested on both an eisy and a polisy, both with PG3x, seeing the same log entries. Anybody run into anything similar? 2024-02-09 08:24:17,704 Thread-1 udi_interface INFO roomba-poly:start: Roomba node server starting 2024-02-09 08:24:17,772 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2024-02-09 08:24:17,774 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:60:46_24 - MID: 2 Result: 0 2024-02-09 08:24:17,818 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2024-02-09 08:24:17,893 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': '<h3>Roomba robots are auto discovered</h3>\n\n<p>If no robots are configured when starting, the node server will start the discovery process.\nThis will look for Roomba devices on the network. For each device found, you will then have\nto manually put the Roomba in to a mode that allows the node server to query the authentication\ninformation from the device. You will be prompted via a notice when this is required.</p>\n\n<p>The discovered Roomba deivces are then saved so that future starts can skip the discovery process.</p>\n\n<p>If you need to re-discover devices, use the "Discover" button in the UI to start the discovery\nprocess. This will clear any exising devices and start from an empty list.</p>\n'} 2024-02-09 08:24:17,933 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2024-02-09 08:24:18,014 Thread-3 udi_interface INFO roomba-poly:handleRobotData: Loading saved robots {'robots': {}} 2024-02-09 08:24:18,018 Thread-3 udi_interface INFO roomba-poly:handleRobotData: We have restored the saved robot list 2024-02-09 08:24:18,021 Thread-3 udi_interface INFO roomba-poly:handleRobotData: Finished with handleRobotData 2024-02-09 08:24:18,054 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2024-02-09 08:24:18,125 Thread-5 udi_interface INFO roomba-poly:handleConfigDone: No saved robots... 2024-02-09 08:24:18,126 Thread-5 udi_interface INFO roomba-poly:discover: Attempting to discover Roombas 2024-02-09 08:24:18,129 Thread-5 udi_interface INFO roomba-poly:_get_response: Comparing irobotmcs with irobotmcs 2024-02-09 08:24:25,142 Thread-5 udi_interface ERROR roomba-poly:_get_response: Socket timeout while waiting for response 2024-02-09 08:24:26,207 Thread-5 udi_interface INFO roomba-poly:_get_response: Comparing irobotmcs with irobotmcs 2024-02-09 08:24:33,227 Thread-5 udi_interface ERROR roomba-poly:_get_response: Socket timeout while waiting for response 2024-02-09 08:24:34,244 Thread-5 udi_interface INFO roomba-poly:_get_response: Comparing irobotmcs with irobotmcs 2024-02-09 08:24:41,258 Thread-5 udi_interface ERROR roomba-poly:_get_response: Socket timeout while waiting for response 2024-02-09 08:24:42,265 Thread-5 udi_interface INFO roomba-poly:_get_response: Comparing irobotmcs with irobotmcs 2024-02-09 08:24:49,269 Thread-5 udi_interface ERROR roomba-poly:_get_response: Socket timeout while waiting for response 2024-02-09 08:24:50,273 Thread-5 udi_interface INFO roomba-poly:_get_response: Comparing irobotmcs with irobotmcs 2024-02-09 08:24:57,355 Thread-5 udi_interface ERROR roomba-poly:_get_response: Socket timeout while waiting for response 2024-02-09 08:24:58,371 Thread-5 udi_interface ERROR roomba-poly:discover: Failed to discover any Roomba robots 2024-02-09 08:24:58,372 Thread-5 udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot. 2024-02-09 08:24:58,373 Thread-5 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2024-02-09 08:24:58,456 Thread-6 udi_interface INFO roomba-poly:handleRobotData: Loading saved robots {'robots': {}} 2024-02-09 08:24:58,458 Thread-6 udi_interface INFO roomba-poly:handleRobotData: We have restored the saved robot list 2024-02-09 08:24:58,461 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2024-02-09 08:24:58,461 Thread-6 udi_interface INFO roomba-poly:handleRobotData: Finished with handleRobotData 2024-02-09 08:24:58,541 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2024-02-09 08:25:02,878 Thread-1 udi_interface INFO roomba-poly:addNodes: addNodes: Discovery fround 0 robots! Quote Link to comment
Solution bpwwer Posted February 9 Solution Share Posted February 9 The plug-in is not getting a response from the robot. Are you sure it's in the charging station and you're able to connect/control from the app? Quote Link to comment
jec6613 Posted February 9 Author Share Posted February 9 Yes, they all are - i3, s9, and four m6's. Quote Link to comment
jec6613 Posted February 9 Author Share Posted February 9 Update: there was a connectivity issue where a firewall rule was eating ICMP packets - put an allow rule in and things started working, thanks for putting me on the right track! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.