Neato BotVac Connected binding?

Hi Patrik,

when binding configuration is changed, old NeatoHander is not shutdown correctly. As you see from the log, after configuration change there are two handlers running simultonously.

2017-04-29 20:52:13.761 [INFO ] [b.binding.neato.handler.NeatoHandler] - Will get STATE for Robot Robo
2017-04-29 20:52:13.774 [INFO ] [b.binding.neato.handler.NeatoHandler] - Will get STATE for Robot Robo
2017-04-29 20:52:14.057 [INFO ] [b.binding.neato.handler.NeatoHandler] - Successfully got and parsed new state for Robo
2017-04-29 20:52:14.251 [INFO ] [b.binding.neato.handler.NeatoHandler] - Successfully got and parsed new state for Robo

When Neato binding is fully uninstalled, NeatoHandler(s) still continues polling.

Reason for this is that you haven’t implemented dispose method. Dispose method is called by the openHAB framework automatically, before initialisation method is recalled.

Another issue is related to logging. Binding pollutes logs by “Will get STATE for Robot …” and “Successfully got and parsed new state for …” staff as logging is done in INFO level. You should change log level to DEBUG for those.

I’m getting the same “flapping” as @Alex_Bum and I also see the messages @pauli_anttila mentions.

Hope you can find some time to fix the binding.
Since it looks very promising!

Hi,

I am looking for neato-sv.map, but I can’t find it. Where can I download?

Thanks

Try this:

ui_alert_busy_charging=Busy Charging
ui_error_navigation_noprogress=Navigation Issue
ui_alert_recovering_location=Recovering Location
ui_error_brush_overload=Brush Overload
ui_error_dust_bin_full=Dust Bin Full
ui_error_dust_bin_emptied=Dust Bin Emptied
ui_error_brush_stuck=Brush Stuck

// Curent state of the vacuum cleaner
INVALID=Invalid
IDLE=Idle
BUSY=Busy
PAUSED=Paused
ERROR=Error

ON=Yes
OFF=No

// Current action of the vacuum cleaner
HOUSE CLEANING=Cleaning House
SPOT CLEANING=Spot Cleaning
MANUAL CLEANING=Manual Cleaning
DOCKING=Docking
USER MENU ACTIVE=User Menu Active
SUSPENDED CLEANING=Suspended Cleaning
UPDATING=Updating
COPYING LOGS=Copying Logs
RECOVERING LOCATION=Recovering Location
IEC TEST=Iec Test

// Current or last cleaning mode
CLEAN-MODE-ECO=Eco
CLEAN-MODE-TURBO=Turbo

// Modifier of current or last cleaning
CLEAN-MODIFIER-NORMAL=Normal
CLEAN-MODIFIER-DOUBLE=Double

// Current or Last category of the cleaning
CLEAN-CATEGORY-HOUSE=House Cleaning
CLEAN-CATEGORY-SPOT=Spot Cleaning
CLEAN-CATEGORY-MANUAL=Manual Cleaning

Thanks for the mapping file, i will do a translation to german …

I read, that Florian did some modification for the Kobold VR200 from the german vendor Vorwerk. The latest jar file on GitHub is unfortunately not yet generated with the new code. I have no experience in building openhab runtime modules. I tried it, but without success … Has anyone done that, and can make the jar file available?

Hi

I made it! However the binding works well with the Kobold VR200. If someone is interested, give me a feedback.

1 Like

Hi there from a newby to this.

I have a Kobold, and have been watching this thread on the sidelines for a while. I have just made the jump from Opehab1 to Openhab2, and decided to try this binding.

I am not a coder, so not too sure what is done to make a new .jar, but expected to see a new file on this link:

without success (most recent is 3 months old) - where do I go to get the file to test it here?

Thanks
Alan

Please excuse my bad English! I am also not a Java programmer, but I have some experience in software development. Scripting is ok, but it’s enough.
Send me your email address, then I can send you the jar file.

1 Like

Can you send me the jar, too?

… I sent you am pm …

Great Job.
Is your binding working with the D3 connected as well? I can only find something about the connected versions, but the d3 seems to be pretty new!?

Hi Bernd,

can you please send me your jar file too?
Is it possible to host the file and the code on GitHub?

Thank you very much

Any plans to implement appartment map functionality like in the Roomba binding (see below)?

Should not be that hard it’s now part of the API. Neato also has a MUCH better map, but I am not a developer. :frowning:

Anyone up for taking over this binding? It looks like Patrick has not been able to work on it. There are a number of things you can do with the API that would be nice to expose to openHAB.

findMe – Issue the findMe action on the robot.

getGeneralInfo – More information like: “timeToEmpty” and “timeToFullCharge”

startCleaning – Would be nice to set eco or normal.

getLocalStats – Lot more info: “totalCleanedArea”, “totalCleaningTime”, “averageCleanedArea” and “averageCleaningTime”

maps – Really would like to see the maps in openHAB.

Any takers? Happy to buy anyone a Neato for the work!

1 Like

That’s a very generous offer, Nathan.
Unfortunately that is beyond my capabilities :wink:

It’s really hard to find reliable information about the differences od D3 / D5 or the BotVac Connected.
It seems only the latter one provides the map.

However, is this limited by the App by checking, if it’s a D3 / D5 or Connected or is this also restricted by the API?
Does anyone have a clue?

I would like to have the map and I am unsure about D5 vs. Connected.
(the other option would be a Roomba 960… :wink:

Hi @sipvoip,

how do you know that map of Neato is better than the of the Roomba?
The screenshots I have seen look pretty similar.

… I sent you a PN

Friend has the 960, the maps for his house were a lot worse then mine, but since they both were not the same house it may not be a 100% fair comparison.