bpwwer

That line of code that's throwing the error hasn't changed. What did change was that it moved inside a loop so that it will keep trying to connect instead of timing out after 10 seconds. I'll take a look at that section and try to determine what's going one to make it fail now.

I'm far from an expert on how the Roombas work. Basically, if you're going to use the plug-in, don't use the app and if you're going to use the app, don't use the plug-in. And when I say don't use the app, I mean you should not have it running, not even in the background. I don't know what happens if the app is connected and you press the button on the roomba. Pressing the button on the roomba, puts it in a mode where it will send it's password to whatever makes a connection to it. Once something has that password, it can connect directly to the roomba without having to get the password again. So when the plug-in gets the password, it saves it along with the IP address of the roomba so that from that point on, it simply connects to the roomba when it starts.

So what changed between your two posts above? The first looks like it connected to the roomba and got something while waiting for the password. However, it doesn't appear to be valid password data. That line of code where it failed, has been in the plug-in since the beginning so I don't think it's suddenly wrong. It just looks like the roomba sent something it can't handle. The second isn't even connecting and the roomba is refusing to connect. Looks like I need to quit trying to connect if I get anything other than a timeout error. I'll add that to the code. But I don't think the plug-in can do anything to make the roomba accept the connection request, that's controlled by the roomba itself. The roomba can only have one connection at a time. If you connect with the app, the plug-in will be unable to connect and if the plug-in is connected, the app won't be able to connect.

Ok, I found what I missed when updating to the new getPassword code. It should now wait for you to press the button on the Roomba. Version 2.0.17 with this fix has been submitted to the store.

set the plug-in log level to debug, restart, download the log and attach here. I'll take a look.

I do see one problem in the log now. Looks like you only have 10 seconds to press the button on the Roomba before the plug-in gives up looking for the password. This one section of the code that had major changes to work with the latest Roomba library code.

Thanks. It did show a couple of the messages I added, but still doesn't seem to want to initialize the Roomba. Version 2.0.16 makes a slight change and I'm curios what happens. My working theory is that when it sends the notice, it interrupts the initialization so that it never finishes. If that's the case, I'm not at all sure how to fix it.

@Lore Thanks. I don't see the log message that I added to help debug this so something strange is going on. I made some change that may help, but I'm not sure. Try the new version and then capture the log again.

@Lore I don't have any PM's from you so I'm guessing it didn't go through. Maybe I don't have space for a large log file anymore. I'll clean up my PM's just in case.

@EricBarish Thanks for the details. It does give me a better idea of where to look for the issue. This file is not available (so the forum says). So I still don't have a full debug log showing the issue.

Seems to be working for me. I also do see the dependency error in my install.log after installing it on a system with IoX 6.0. But it doesn't seem to cause any issues. As mentioned above, Server error 500 is coming from the Emporia server, it's not something the plug-in can do anything about.

Neither Benoit or I was able to reproduce this, ST-Inventory was working for both of us. The error looks like it could be caused by the checkbox not being checked. I know at least once, I checked the box, but forgot to save it causing a very similar error.

One thing I just thought of, for ST-Inventory to work, you do have to check the checkbox on the config tab to allow the plug-in to access the IoX/ISY. and make sure you hit the save button after checking the check box.

Re-reviewing this, it does look like the sonos-http-api may not be running. Or may not have been running when the plug-in started. Have you tried simply stopping and then starting the plug-in? When I installed it, the first time it tried to start I got errors like what you posted, but after restarting it, it seemed to work fine. Of course I have no Sonos devices so it doesn't actually discover anything, but it did create the control node and didn't have any errors in the log.

I did find an issue with the dimmer and also with the rgb bulbs. Those have been corrected in version 1.0.9, which I have submitted to the non-production store. See if this version behaves a bit better when setting levels. I still need to investigate why it seems to stop getting updates from the devices after a day or two.