[RELEASE] Neato (Connect) V1.2.6c (Botvac Connected Series)

Is there a way to abort a currently running Neato based on precense sensor arrival without complicated WebCore coding?

Say the house is in away mode and the scheduled vacuuming commences, then someone unexpectedly arrives home - I’d like the Neato to stop the current routine and scurry off. Optimally, when the house is unoccupied again the Neato would commence where it left off.

The issue is that when Neato returns to base, it resets so it can’t carry on where it left off. The behaviour that is possible to code in a future release is pausing the Neato’s once you arrive and resuming when you leave. This means you might have a Neato left in the middle of the floor until you leave the house again which might not be ideal. Another option is just to initialise a clean immediately if it was interrupted which would mean it would cover ground twice but that might not be a huge deal. The only issue I can see is if you pop out regularly for 30 minutes and the Neato gets stuck in a loop as it never finishes a cleaning cycle. If this would be a handy feature I can add it as a future update to the app.

Pausing a running cleaning cycle should work. The odds of the Neato getting turned off to stuble on just makes life a little more challenging :slight_smile:

It’s actually the vaccuuming noise more than anything I’d like to mitigate by having this option, so your suggestion with a temporary pause and resume when the house is empty again sounds like a viable plan.

Please let me know if you need any help forming/testing this option in the future!

@Alyc100

Alex any chance of you adding the new Neato D7??? Is that showing in the Neato Developer API yet?? I am curious because I want one when it comes out. Looks very cool…

Device Handler V1.6 “should” support D7. As I do not have the luxury of owning one I’ve had to make some assumptions in the code. If anyone out there receives one let me know if Maps and FindMe works as well as the obvious start, stop and scheduling.

New device handler v1.7 now supports D7 eco/turbo cleaning profiles and now extra care navigation modes for D3/D5/D7 Botvacs.

V1.6…shortest lifespan for a device handler version yet.

1 Like

My Neato D5 lost connection to my wifi and I had to add it again in the Neato app. This has resulted in a device named null in the app, which is not possible to remove. Last time it happend I had to reinstall the app.

Try and go into the neato(connect) smart app and click the reauthenticate link at the bottom. Then go into the device selection menu and see if that works.

Unfortunately it´s still there. When I choose my Botvac I have two devices, my Botvac and null.

Alex, this smart app is brilliant!
I do have one requested change though please.

At present, I’ve set the smart schedule to clean every 1 day between the hours of 9am and 9pm, but the timer starts 24 hours after the last clean was done. So assuming the botvac started at 11am, the next day the scheduler won’t kick in unless I’m out of the house after 11am, rather than 9am.

What I’d like is for the scheduler to reset each day, so that every day between the hours of 9am - 9pm, if I go out, the botvac will start a cleaning cycle. Is that possible?

1 Like

I’ve been working on something. Try the latest build of the SmartApp 1.2.1 BETA. There is a new option within the SmartSchedule configuration that allows a day to be measured from midnight. Let me know if it works as it’s difficult to test.

It should start changing behaviour after a clean as the time markers need to be overwritten once this option has been selected.

Thanks Alex, installed the beta version, clicked reset schedule and it now says 17 hours till activating. I’ll report back how it functions tomorrow.

Just one more request if this is possible, I know I could build it in WebCoRE but it would be nice to sit inside the app.

Could you also add the option to turn On a switch/button when the Vac starts cleaning and then turn off again when done?

I’ve got some Homeboy cameras linked to ST via a virtual switch (controlled via Stringify) that I need to deactivate when the cleaning starts and then reactive when it’s done.

Also…

Where can I donate you some money to buy you a few beers to show my appreciation of your work on this app (and the Hive one too)

Edit - ignore, I found your link. Enjoy those beers on me :slight_smile:

Alex, the SHM implementation doesn’t seem to work correctly. It changes to Armed/Stay when the BotVac starts cleaning, but once finished, it doesn’t change back to Armed/Away. Is it working correctly for you?

Hello,

I am getting an error adding my botvac. Any ideas?

12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: debug getChildDevices(false), children=1
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: debug Created Neato Botvac - Neato with id: OPS22417-508CB120802B|F8B976CE50356ACFE38FE811A287B4AC
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:04 PM: info Adding Neato Botvac device OPS22417-508CB120802B|F8B976CE50356ACFE38FE811A287B4AC: Neato Botvac - Neato
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:04 PM: info Body: [[timezone:null, model:BotVacConnected, linked_at:2017-09-28T15:27:59Z, name:Neato, prefix:null, traits:[], purchased_at:null, secret_key:F8B976CE50356ACFE38FE811A287B4AC, serial:OPS22417-508CB120802B, nucleo_url:https://nucleo.neatocloud.com:4443]]
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:04 PM: debug getChildDevices(false), children=0
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:04 PM: debug [OPS22417-508CB120802B|F8B976CE50356ACFE38FE811A287B4AC]
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:04 PM: info Status: 200
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:04 PM: debug Beginning API GET: https://beehive.neatocloud.com/users/me/robots, [Accept:application/vnd.neato.nucleo.v1, Content-Type:application/*+json, X-Agent:0.11.3-142, Authorization:Bearer 9c4cc0fe28e083fdbac66186fb773f364adefe68710079ed2fbe29ce89dbcb5c]
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:04 PM: debug Executing 'updateDevices’
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:04 PM: debug Executing 'addBotvacs’
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:04 PM: debug Installed with settings: [autoSHM:false, forceClean:false, autoDockDelay:60, autoDock:true, selectedBotvacs:[OPS22417-508CB120802B|F8B976CE50356ACFE38FE811A287B4AC], forceCleanDelay:7]
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: debug Time to force clean: -1 milliseconds
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: debug Executing ‘timeToForceClean’ with device OPS22417-508CB120802B|F8B976CE50356ACFE38FE811A287B4AC
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: debug Time to smart schedule clean: -1 milliseconds
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: debug Executing ‘timeToSmartScheduleClean’ with device OPS22417-508CB120802B|F8B976CE50356ACFE38FE811A287B4AC
67c92ba0-e4d2-4747-a83e-b81167af4a73 5:43:06 PM: debug Neato Botvac - Neato cleaning mode: turbo
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: info Body: [reqId:1, result:ok, cleaning:[modifier:1, category:2, spotHeight:0, spotWidth:0, mode:2], details:[isScheduleEnabled:false, charge:46, isDocked:true, dockHasBeenSeen:false, isCharging:true], error:ui_alert_invalid, availableCommands:[pause:false, stop:false, resume:false, goToBase:false, start:true], action:0, state:1, data:[:], meta:[firmware:2.2.0, modelName:BotVacConnected], availableServices:[schedule:basic-1, houseCleaning:basic-1, maps:basic-1, manualCleaning:basic-1, spotCleaning:basic-1], version:1]
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: info Status: 200
67c92ba0-e4d2-4747-a83e-b81167af4a73 5:43:06 PM: debug Beginning API POST: https://nucleo.neatocloud.com:4443/vendors/neato/robots/OPS22417-508CB120802B/messages, {“reqId”:“1”, “cmd”:“getRobotState”}
67c92ba0-e4d2-4747-a83e-b81167af4a73 5:43:06 PM: debug Executing 'poll’
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: debug Time to force clean: -1 milliseconds
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: debug Executing ‘timeToForceClean’ with device OPS22417-508CB120802B|F8B976CE50356ACFE38FE811A287B4AC
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: debug Time to smart schedule clean: -1 milliseconds
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: debug Executing ‘timeToSmartScheduleClean’ with device OPS22417-508CB120802B|F8B976CE50356ACFE38FE811A287B4AC
67c92ba0-e4d2-4747-a83e-b81167af4a73 5:43:06 PM: debug Neato Botvac - Neato cleaning mode: turbo
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: info Body: [reqId:1, result:ok, cleaning:[modifier:1, category:2, spotHeight:0, spotWidth:0, mode:2], details:[isScheduleEnabled:false, charge:46, isDocked:true, dockHasBeenSeen:false, isCharging:true], error:ui_alert_invalid, availableCommands:[pause:false, stop:false, resume:false, goToBase:false, start:true], action:0, state:1, data:[:], meta:[firmware:2.2.0, modelName:BotVacConnected], availableServices:[schedule:basic-1, houseCleaning:basic-1, maps:basic-1, manualCleaning:basic-1, spotCleaning:basic-1], version:1]
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: info Status: 200
67c92ba0-e4d2-4747-a83e-b81167af4a73 5:43:06 PM: debug Beginning API POST: https://nucleo.neatocloud.com:4443/vendors/neato/robots/OPS22417-508CB120802B/messages, {“reqId”:“1”, “cmd”:“getRobotState”}
67c92ba0-e4d2-4747-a83e-b81167af4a73 5:43:06 PM: debug Executing 'poll’
67c92ba0-e4d2-4747-a83e-b81167af4a73 5:43:06 PM: debug Executing 'refresh’
d25a9c70-cc46-42bd-b8b4-706510cb1f59 5:43:06 PM: debug lowBatteryHandler: Neato Botvac - Neato battery is 46%
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: debug Time to force clean: -1 milliseconds
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: debug Executing ‘timeToForceClean’ with device OPS22417-508CB120802B|F8B976CE50356ACFE38FE811A287B4AC
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: debug Time to smart schedule clean: -1 milliseconds
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: debug Executing ‘timeToSmartScheduleClean’ with device OPS22417-508CB120802B|F8B976CE50356ACFE38FE811A287B4AC
67c92ba0-e4d2-4747-a83e-b81167af4a73 5:43:06 PM: debug Neato Botvac - Neato cleaning mode: turbo
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: info Body: [reqId:1, result:ok, cleaning:[modifier:1, category:2, spotHeight:0, spotWidth:0, mode:2], details:[isScheduleEnabled:false, charge:46, isDocked:true, dockHasBeenSeen:false, isCharging:true], error:ui_alert_invalid, availableCommands:[pause:false, stop:false, resume:false, goToBase:false, start:true], action:0, state:1, data:[:], meta:[firmware:2.2.0, modelName:BotVacConnected], availableServices:[schedule:basic-1, houseCleaning:basic-1, maps:basic-1, manualCleaning:basic-1, spotCleaning:basic-1], version:1]
12d3ebba-8a09-43fc-b6c4-cfc46d15a8b2 5:43:06 PM: info Status: 200
67c92ba0-e4d2-4747-a83e-b81167af4a73 5:43:05 PM: debug Beginning API POST: https://nucleo.neatocloud.com:4443/vendors/neato/robots/OPS22417-508CB120802B/messages, {“reqId”:“1”, “cmd”:“getRobotState”}
67c92ba0-e4d2-4747-a83e-b81167af4a73 5:43:05 PM: debug Executing 'poll’
67c92ba0-e4d2-4747-a83e-b81167af4a73 5:43:04 PM: debug Installed with settings: [:]

Is this only compatible with 2nd gen hub?

FYI I just built a WebCoRE piston that turns on SHM to Armed/Away when Neato switch turns to Off and nobody is home. This works fine, so I have a workable solution, just puzzled why the app doesn’t do it. Has anyone else had this issue?

Will get round to looking into this. I’ll keep you updated.

:sob:

I bought this vacuüm cause of the smartthings integration. It connects But when pushing Done, there comes An error. Have tried several New clean installs but the error keeps on popping up:sweat:

Anybody any thoughts?

Many Thanks already