Yes. Had to change how secret keys are stored for each device in the device handler and that meant also changing the add new device code in the smart app.
Sorry, what do you mean by 1 and 2? Delete the app from my phone, do step 3, then do step 4?
It will not let me turn on personal maps, i have the 5 series.
No need to delete the Neato Smart App. Just delete your Botvacs from ‘Things’. To do this, you’re best removing any references to those Botvacs from other apps such as ActionTiles or WebCore first.
Then after you’ve definitely removed the Botvacs, update the SmartApp and Device Handler with the latest version.
Works for me again now after updating to the new SmartApp and device handler version, thank you!
Works again for me. Thanks so much.
It will not allow me to turn on Personal Maps. I deleted the app and handler and reinstalled. What am i missing? I have the Connected D5
Sorry to be a pain.
anyone have any tips on how to get things working again. I am having a really hard time. Both my Neatos show offline and I cannot for the life of me get them deleted from Smartthings. I updated all the smart and handler code but I still cant get it to work. Any ideas ? I also was going to to just delete the whole neato smart app and start over but again I cannot delete it I keep getting an error. So bummed things were working so well before.
Have you completed the steps in the following post:
I have a D7 and I updated its firmware to the recent 4.5 release recently.
I also updated the smart app and device handler as recommended here.
They all work fine.
However, after this update, I noticed that the app on my Android phone does not show the robots current state when it is cleaning.
It always shows as “ready to clean” even if it is already cleaning.
Besides, while cleaning it does not show “pause”, “stop” or “dock” buttons as it thinks it is not cleaning. Is this a bug of the firmware?
Does anyone else with a D7 have this problem ?
EDIT: nevermind, this is solved after a power cycle.
I had same issue today, also had to power cycle to resolve…
I’ll look into it tomorrow. Probably some code that’s using the secret key to lookup status