Roomba Plugin - Discontinued

[FlyingDiver]

Try v.0.06 which I just posted. I increased the timeout on the requests call.

[avanti]

The folder says .0.6, but when I install it Indigo says it is 0.5 and won't overwrite the old one.

[FlyingDiver]

Fixed. Try again.

[avanti]

I edited the plist and got it to load. No change (assuming I didn't screw anything up).

Code: Select all

        getRoombaPassword called
   Roomba Error                    Unable to get Roomba Password.  Ensure Roomba IP address is correct.
   Roomba Debug                    getRoombaPassword called
   Roomba Error                    Unable to get Roomba Password.  Ensure Roomba IP address is correct.
   Roomba Debug                    validateDeviceConfigUi called
   Roomba Debug                    validateDeviceConfigUi: RequestException: [Errno 1] _ssl.c:499: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
   Roomba Debug                    getRoombaPassword called
   Roomba Error                   

Note the "unknown protocol"

Out of time tonight. I will load your updated 0.6 tomorrow. Thanks for the prompt attention.

[FlyingDiver]

What's your Robot Software version number? Mine is v1.6.6.

[avanti]

I'm 1.6.6 as well.

I tried the procedure found here:
https://community.smartthings.com/t/roo ... g/44860/24

It does not work, either, so I guess this has nothing to do with the plugin. This is very strange. Must have something to do with my network, but I can't imagine what. Indigo speaks nicely to my alarm panel, and the iPhone app works with the Roomba. Running out of ideas. Not sure what to try next. Should I be able to SSH to that port?

[FlyingDiver]

No, not ssh. The Roomba is listening for HTTPS on port 443 (standard https port).

The first error you posted said it was timing out. The latest version increased the timeout, so I think that's fixed. The second is a protocol error. It looks like you cut off the rest of the log entries. What's after that last "Roomba Error"?

[avanti]

Ok, so this is getting odd.

I, was able to retrieve the password using the smartthings Javascript thing, using the command
npm run get password 192.168.0.17
This is slightly different from what I tried the first time. Don't understand that stuff well enough to be useful, but at least I have an existence proof that I can communicate with the robot. It appears to be reliable.

As for Indigo, I am getting mysterious results:
--I have been running an Indigo server on an old Macbook Pro in the basement, with the interface running upstairs on a modern Macbook Pro. I have tried getting the password both on the server and on the client machine. Both fail identically, as I have described.
--Just as a test, I ran an Indigo instance upstairs in single-process mode.
--Using this, I was finally able to get the plugin to accept the IP address. However, it took several tries. I did NOT press GET PASSWORD.
--Once I had the IP set, I did press GET PASSWORD. It worked!
--BUT, I then pressed SAVE, and got the "error validating fields..." error, and it did not save.
--I tired SAVE once more, and it worked this time.

So, I now know my password (two different ways). I also have it saved, but on the wrong server. I still cannot get any of this to work on the basement server. I now realize that it is possible to save the URL without querying the password. If I enter the URL and press SAVE, I get the error:

validateDeviceConfigUi called
Roomba Debug validateDeviceConfigUi: RequestException: [Errno 1] _ssl.c:499: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

It does not matter whether I am logged into the server machine or the client machine.
It DOES matter whether I am running on the upstairs machine running in single-process mode: It SOMETIMES works if I am, but it NEVER works on the downstairs machine running a separate server.

I am now fairly convinced that my problem has nothing to do with fetching the password, but rather with saving the URL. Maybe some kind of race condition?

Does the SAVE button cause the URL to be validated with the robot, or is it just a property save?

I am no Indigo expert, but I do know Python. If there is some stand-alone test you might suggest, I am all ears.

Thanks again for the persistence.

P.S. -- I just checked: On the machine that works, I am running OS X 10.10.5. However, the server machine is running 10.7.5. I guess this may have something to do with it. I can update the downstairs machine, but I will wait to hear from you before I do so.

[FlyingDiver]

Getting the password is optional in that dialog, but the plugin won't be able to do anything else until you do get the password.

The IP address is validated in that dialog, but attempting a request to the Roomba. If that request fails, then the IP address is considered to be bad. It may not be, but the only way for the plugin to verify it is to do the request to that URL.

My guess is that the machine running 10.7.5 has a version of Python (or the requests module) that doesn't support SSL connections and that's why it's failing. On that machine, do:

Code: Select all

python --version
pip show requests

And compare those to the system that works. You might be able to just update the requests module to a more recent version.

[JaceJenkins]

Whats the best way to test to see if he Roomba completed a cycle on its own, without being stopped by a user? Testing to see if its at the dock doesn't differentiate whether it was sent there by cancelling the job or because it actually finished a full cycle.

[FlyingDiver]

Check the deviceStatus state. I think it has different strings depending on where it is in the cleaning cycle. Or maybe the Cycle state.

[GlennNZ]

Problems with Firmware 2.0.0-34

Unfortunately the plugin stopped working with my Roomba. Failed to connect on port 443.
No easy fix.
Port scan the Roomba and only port 8883 is open.

On firmware v2.0.0-34

Seems like there has been major iroomba changes with this firmware so that port 443 no longer works and Roomba changed to mqtt protocol.

See here:
https://github.com/koalazak/dorita980/issues/10

Any one else seeing?

Glenn

[FlyingDiver]

Sigh.

Well, I've subscribed to that thread, and when he figures out the new protocol I'll update the plugin. Assuming I can figure out how to do the mqtt protocol, that is.