Potentially. Looks like certificate based issues, and/or version of library issues. Probably need to downgrade current pybotvac to previous version that was working in 3.10.
Seems exception with urllib3.exceptions.SubjectAltNameWarning, which appears to have not existed in urllib for some time..
If do, in terminal window (not Indigo scripting window)
Should show previous python 3.10 version of pybotvac that you had running.
& then install this version the python 3.11 via pip3.11. Because it is already installed and a later version you can either uninstall and reinstall specifying the same version. Or force-install
On further looking at this, I believe it is because of urllib3 change between these 2 python versions of Indigo, and because the pybotvac library hasn’t been updated to support the urllib3 changes.
Would skip my last post.
(There still may be a pybotvac version issue = but doesn’t seem the main issue)
I think the best way to fix this in the 2023.2 landscape would be to add a requirements.txt file to the plugin.
Total contents of requirements.txt
pybotvac
urllib3==1.26.16
It goes in the Server Plugin folder of the pluginBundle, Contents, Server Plugin folder (same directory as plugin.py file)
&
Will need API info.plist changed to ServerAPIVersion
3.4
All this is getting a bit tricky understandably. Ideally hopefully plugin author can update the plugin - and hopefully this helps a bit
I’m afraid fixing the obvious library based issues is where my help probably ends. Seems like that has happened based on this communication that has occurred.
Seems like it connects to the robot, but that is the limit? Might relate to the certificate issues which seem to abound in the library pulls - although they are all a year or so old. But really could be anything!
It is a cloud connection though - so could possibility see if can login and figure out/work with your account details. Probably not that great an idea because I’m sure you don’t want your vacuum starting at 2am in the morning…. So unless super-keen probably wouldn’t recommend?
(I just deleted a paragraph talking about how good the latest AI iroombas are (cost aside) despite being round, betting Neato in all reviews that I could find… but then realised was probably unneeded and rubbing salt in wound! Sorry - just done it again!)
Thank you very much for your extended explanation.
It is indeed strange that a connection is made with the robot, but then it stops.
Not every update is progress, so sometimes you lose things in life...
With Indigo 2021.1, this plugin worked perfectly last week, so I can't imagine it would be certificates (or problems at the Neato site).
(and the cloud login apparently also works, otherwise no information about the robot will appear in the log)
The vacuum cleaner still works fine and we are extremely satisfied with the D-shape of the Neato.
Round doesn't fit in a corner
I have created an Neato account and will see if can replicate some of the issues
No promises as obviously a bit hard without a device connected to said account ….
Actually it all is working well, minus missing a robot to actually control...
Seems to connect.
The error msg invalid UI that you report is common and means nothing it would seem.
So would double check Neato devices - selection etc.
Then post/email a full debug log and can have a further look.
I saw that Neato stopped making the best vacuum robot. https://neatorobotics.com
That's too bad.
So we'll have to be careful with ours, they're still doing great.
I checked whether I could enable a more extensive log in the plugin, but the debug information shown is the maximum.
There is a menu in the Plugin; "Update Neato Account"
when I do that then I saw in the log:
Made a new Indigo Neato Device, called Neato Botvac upstairs
The strange thing is that with an action from an Action Group, the log says:
Neato Botvac "new device" start house cleaning
Neato Botvac "new device" request status
Neato Botvac Debug "new device" available commands: {'start': True, 'stop': False, 'pause': False, 'resume': False, 'goToBase': False}
Neato Botvac Debug "new device" status update complete
I wonder why it says "new device"
Never saw that.
But there seems to be a connection because the battery status is ok and there is custom state info.
Attachments
Screenshot 2024-02-05 at 15.14.46.png (496.47 KiB) Viewed 1705 times
McJohn wrote:
I wonder why it says "new device"
Never saw that.
That's caused by the plugin developer not updating the internal device representation after you rename the device. When the device is first initialized, it has the default name Indigo gives it when it's created. You changing the name happens after that, and sometimes a developer won't refresh the device info properly.
I should know, I'm guilty of the same thing in some of my plugins. I've fixed it in most, but not all.
Hello everyone. As you probably noticed, I'm not around much these days. I haven't completely stopped maintaining my plugins, but I'm really not staying on top of it either (and don't expect to ).
Sorry about the errors on upgrade. When I first stopped bundling the pybotvac library with the plugin, I thought it would be helpful to throw an error on import telling users they had to install the library themselves. Bad idea in hindsight as it masked other sorts of import issues.
@GennNZ, is it possible to turn your edits into a pull request?
Also happy to accept any volunteer co-maintainers.
