apostolakisl Posted May 5, 2022 Posted May 5, 2022 4 hours ago, wmcneil said: Was the roomba started from the roomba server, or from the node server? It started from its own schedule. It runs at 1am every night. Not sure where the initiating event for a scheduled cleaning comes from, I would bet that is saved on the roomba itself, but it might come from the cloud in which case it would functionally be the same as starting it from the phone app.
Athlon Posted May 5, 2022 Posted May 5, 2022 29 minutes ago, apostolakisl said: It started from its own schedule. It runs at 1am every night. Not sure where the initiating event for a scheduled cleaning comes from, I would bet that is saved on the roomba itself, but it might come from the cloud in which case it would functionally be the same as starting it from the phone app. I've been watching this thread - I have a Roomba Mop & Vacuum. Is your 'schedule' in your ISY or in your iRobot app?
apostolakisl Posted May 5, 2022 Posted May 5, 2022 4 minutes ago, Athlon said: I've been watching this thread - I have a Roomba Mop & Vacuum. Is your 'schedule' in your ISY or in your iRobot app? Its own built in schedule. As I mentioned, I don;t know how they work that, it could be on the cloud or it could saved directly to the unit. I suppose I could shut my internet off at 1am when it is scheduled to run and see if it runs.
wmcneil Posted May 5, 2022 Author Posted May 5, 2022 5 minutes ago, apostolakisl said: Its own built in schedule. As I mentioned, I don;t know how they work that, it could be on the cloud or it could saved directly to the unit. I suppose I could shut my internet off at 1am when it is scheduled to run and see if it runs. I have also seen that a run that is initiated by a schedule event on the roomba app results in AC sometimes staying in communication with the rooma, and other times appears locked out from communication with roomba. It seems possible/likely that when the AC appears locked out, it is because the one local connection that roomba supports is in use by the roomba app. Continuing this speculation, it may be that sometimes the scheduled run happens without any interaction with the local roomba app (i.e. the roomba cloud server is in play), and other times the roomba app is involved (I have no idea what factors might cause these two different behaviors). When the roomba app is consuming the one local connection, the theory is that the node server is unable to communicate with roomba.
Athlon Posted May 5, 2022 Posted May 5, 2022 23 minutes ago, apostolakisl said: Its own built in schedule. Who put it in there? I'm sure it didn't start vacuuming at 1am everyday when you first set it up. The reason I'm asking is if you used the app to create that schedule, then perhaps the iRobot cloud is grabbing control form your ISY once in a while.
apostolakisl Posted May 5, 2022 Posted May 5, 2022 19 minutes ago, Athlon said: Who put it in there? I'm sure it didn't start vacuuming at 1am everyday when you first set it up. The reason I'm asking is if you used the app to create that schedule, then perhaps the iRobot cloud is grabbing control form your ISY once in a while. Of course I set it up. 35 minutes ago, wmcneil said: I have also seen that a run that is initiated by a schedule event on the roomba app results in AC sometimes staying in communication with the rooma, and other times appears locked out from communication with roomba. It seems possible/likely that when the AC appears locked out, it is because the one local connection that roomba supports is in use by the roomba app. Continuing this speculation, it may be that sometimes the scheduled run happens without any interaction with the local roomba app (i.e. the roomba cloud server is in play), and other times the roomba app is involved (I have no idea what factors might cause these two different behaviors). When the roomba app is consuming the one local connection, the theory is that the node server is unable to communicate with roomba. PG3 node lost connection to ISY, not to Roomba. The log still showed data flowing in from Roomba. The AC was getting no updates, so the values stayed as they were. After an AC restart, the fields were left unpopulated. Other PG3 nodes were still connected to ISY.
Athlon Posted May 5, 2022 Posted May 5, 2022 (edited) Perhaps I misspoke. When I said iRobot's cloud grabbed control from your ISY - I meant the PG3 Node Server. Assuming your schedule was created using your iRobot app, that's perhaps why the Node server is losing it's connection. I'm wondering if you were to delete all programs in the iRobot app and recreate them in your ISY if the issue you and wmcneil are having would go away. By the way, I have no programs in my iRobot app and never have. I also never lose Node server connection with either of my robots. Edited May 5, 2022 by Athlon
bpwwer Posted May 5, 2022 Posted May 5, 2022 9 hours ago, apostolakisl said: I do not know why the NS would lose its link to ISY. I haven't made any changes to ISY or any NS's since the last reboot. You can also check the PG3 log as it will show everything being sent to the ISY. If the connection was lost for some reason you should see errors in the PG3 for each attempt to contact the ISY.
wmcneil Posted May 5, 2022 Author Posted May 5, 2022 17 minutes ago, apostolakisl said: Of course I set it up. PG3 node lost connection to ISY, not to Roomba. The log still showed data flowing in from Roomba. The AC was getting no updates, so the values stayed as they were. After an AC restart, the fields were left unpopulated. Other PG3 nodes were still connected to ISY. I also observed that when the AC was behaving as if frozen, that the node server was logging what appear to be updates from roomba. @bpwwer, can you comment here, if the node server is logging updates from roomba, that argues against the one-local-server slot being taken, do you agree?
bpwwer Posted May 5, 2022 Posted May 5, 2022 The connection to the Roomba is handled in a separate thread by the roomba library code developed as part of the Roomba980-Python project. That code waits for updates from the Roomba and stores them. The node server polls that stored data at the poll interval. Thus the node server can look like it is updating frequently when in reality, it is just getting whatever stale data was last received from the Roomba. Also note that if the data is not changing, the node server won't pass it on to the ISY. It only sends data that has actually changed to the ISY.
apostolakisl Posted May 6, 2022 Posted May 6, 2022 Roomba triggered today from a program in ISY. It also triggered last night from a native Roomba schedule. I haven't manually triggered it, though I have opened the app and connected.
wmcneil Posted May 20, 2022 Author Posted May 20, 2022 I have disabled schedules from the Roomba phone app for both my phone and my wife's phone. After several days of testing, I have found that I can connect reliably to the Roombas from ISY only if I first reboot the PG3 node server. So it seems likely that the Roomba phone app is connecting locally to the Roombas periodically even when no schedules are enabled in the Roomba app. For the purposes of testing, I guess I can try uninstalling the phone app from both our phones.
wmcneil Posted May 25, 2022 Author Posted May 25, 2022 I've uninstalled the Roomba app from both my phone and my wife's phone (so there is no Roomba phone app installed anywhere). I am still seeing the Roombas not stay connected to the node server. I can connect reliably to the Roombas from ISY only if I first reboot the PG3 node server.
Recommended Posts