Hacking a Neato Robotics BotVac Connected
-
Hmm it almost sounds like the Botvac could go for a firmware update, unfortunately it looks like Neato's post launch product support is severely lacking
@Jonathan8301
Funny thing is, before the connected was launched, I remember being able to find an API document and programming info for interfacing with the lower models...NOW, I can't so much as even find any page that contains a link to anything resembling an update file or api documentation... -
@RawLiquid So you are looking for this -> https://www.neatorobotics.com/resources/programmersmanual_20140305.pdf
Or something else?
- Tomas
-
@RawLiquid So you are looking for this -> https://www.neatorobotics.com/resources/programmersmanual_20140305.pdf
Or something else?
@korttoma actually, I already had that very document, and that is the one I was referring to. I might suggest keeping mentions of the exact url fairly low, It's likely an oversight that it's available still and if so, likely to be removed if they notice it. maybe use bitly to reference it instead...
I don't know what exactly changed within the company to cause such a drastic shift, but it's obvious that something changed.... -
Hello hackers!
Let me introduce myself, I am Roberto Ostinelli, Neato Robotics' Director of Cloud Services.I'm impressed with the work that you've put into integrating with our robots! Great job!
Given the interest we've seen on this and other forums, we've listened and have just released the Neato Developer Network, which might hopefully be of interest for some of you here.
You can become a developer with just your Neato account from here:
https://developers.neatorobotics.comYou will find official documentation and SDKs for JavaScript, iOS and Android (for now, we plan on expanding to other languages too!).
Simply put, as a developer you can create your own OAuth apps that interacts with Neato robots.A demo of what you can achieve with the JavaScript SDK can be seen here (just login with your Neato account when requested):
https://developers.neatorobotics.com/demo/sdk-jsPlease note that all of this is in Beta, we're a small team but are doing our best!
Cheers,
r. -
Thanks for finally acknowledging the fact that some people want to integrate their robotic vacuum cleaner with the rest of their smart home functionality.
Is your Neato Developer Network investment only targeting the new Neato Connected series and future versions or is there a communication module in the pipeline for older models like my Neato botvac 85?
- Tomas
-
Thanks for finally acknowledging the fact that some people want to integrate their robotic vacuum cleaner with the rest of their smart home functionality.
Is your Neato Developer Network investment only targeting the new Neato Connected series and future versions or is there a communication module in the pipeline for older models like my Neato botvac 85?
-
Welcome @roberto,
Thanks for making the Neato more hacker friendly. I'm sure it will boost your sales. The HA/DIY crowd and the early adopters buying robotic vacuum cleaners is coinciding.
-
This is good news. Thank you Neato.
Is it possible to send commands with just an https url? These URL's I can implement in LUA scripts for my Domotica.
-
This is good news. Thank you Neato.
Is it possible to send commands with just an https url? These URL's I can implement in LUA scripts for my Domotica.
@Michael-van-der-Heijden Yes, everything is just standard http requests. Just head to the API section of the docs to learn more. You can see implementation examples in the existing SDK, that may help you out too!
-
@Michael-van-der-Heijden Yes, everything is just standard http requests. Just head to the API section of the docs to learn more. You can see implementation examples in the existing SDK, that may help you out too!
@roberto Awesome to see you make the API public and official even though it seems that you're just making the endpoints "official" and pretty much identical to the API resulted from reverse engineering efforts. Any chance you (as in Neato) would consider allowing us to switch to our backend server, essentially replacing your cometa.io server (cometa.neatocloud.com)? And on a sidenote, to get access to the developers portal and API through your site, you have to accept to your new terms, yet you've made the libraries public on github. :)
-
@roberto - Thanks for making the API public! @kangguru and others - thanks for reverse engineering it!
@roberto - Any chance of making the local LAN, direct-to-robot API official and documenting it? Some people prefer the lower latency and non-cloud dependency of local LAN control.
P.S. I started an OpenHAB thread about developing a OpenHAB binding for the Neato Connected series.
-
@Michael-van-der-Heijden Yes, everything is just standard http requests. Just head to the API section of the docs to learn more. You can see implementation examples in the existing SDK, that may help you out too!
-
@roberto Thanks for the documentation! Are there any plans to integrate with IFTTT? That would make it much easier for people to use with other smarthome things such as SmartThings, Echo, and Google Home.
Looks like Smartthings is underway and Neato are engaged. I have not tested yet.
https://community.smartthings.com/t/neato-botvac-connected/24607/24
-
@roberto - Thanks for making the API public! @kangguru and others - thanks for reverse engineering it!
@roberto - Any chance of making the local LAN, direct-to-robot API official and documenting it? Some people prefer the lower latency and non-cloud dependency of local LAN control.
P.S. I started an OpenHAB thread about developing a OpenHAB binding for the Neato Connected series.
@Ubiquitous said:
Any chance you (as in Neato) would consider allowing us to switch to our backend server, essentially replacing your cometa.io server (cometa.neatocloud.com)?
We took your suggestion, but there are so many implications that i doubt this will get prioritized.
FYI, we do not use the cometa.io server, the official endpoint is https://nucleo.neatocloud.com:4443/ and the one you pointed out is for retro-compatibility only.@Stormwind said:
@roberto - Any chance of making the local LAN, direct-to-robot API official and documenting it? Some people prefer the lower latency and non-cloud dependency of local LAN control.
Suggestion noted. Note that direct-to-robot have limited functionalities.
@Seth-Daniel said:
@roberto Are there any plans to integrate with IFTTT? That would make it much easier for people to use with other smarthome things such as SmartThings, Echo, and Google Home.
A SmartThings integration exists, so does the Alexa one. IFTTT and Google Home are on the list of integrations that we are considering.
@Basic said:
I see there is limitations to the scheduling in the software. I want to run the robot two times a day (set the schedule remotely). Any ideas on how to do that? :)
This is an internal robot implementation. You can use the API to start your robot anytime you want, and build your own schedule system. :)
-
Greetings hackers!
Some of you may have seen that the latest 2.2 release for Botvac Connected includes the new maps functionality. Basically, you can now see the cleaning maps of your home in the Neato applications.We thought you might interested in accessing this functionality too, hence we've just released the new SDKs and API documentation which include this functionality. This main addition can be seen here:
https://developers.neatorobotics.com/api/beehiveHappy hacking! ^^_
Cheers,
r. -
@Ubiquitous said:
Any chance you (as in Neato) would consider allowing us to switch to our backend server, essentially replacing your cometa.io server (cometa.neatocloud.com)?
We took your suggestion, but there are so many implications that i doubt this will get prioritized.
FYI, we do not use the cometa.io server, the official endpoint is https://nucleo.neatocloud.com:4443/ and the one you pointed out is for retro-compatibility only.@Stormwind said:
@roberto - Any chance of making the local LAN, direct-to-robot API official and documenting it? Some people prefer the lower latency and non-cloud dependency of local LAN control.
Suggestion noted. Note that direct-to-robot have limited functionalities.
@Seth-Daniel said:
@roberto Are there any plans to integrate with IFTTT? That would make it much easier for people to use with other smarthome things such as SmartThings, Echo, and Google Home.
A SmartThings integration exists, so does the Alexa one. IFTTT and Google Home are on the list of integrations that we are considering.
@Basic said:
I see there is limitations to the scheduling in the software. I want to run the robot two times a day (set the schedule remotely). Any ideas on how to do that? :)
This is an internal robot implementation. You can use the API to start your robot anytime you want, and build your own schedule system. :)
@roberto Are there any plans to integrate with IFTTT? That would make it much easier for people to use with other smarthome things such as SmartThings, Echo, and Google Home.
A SmartThings integration exists, so does the Alexa one. IFTTT and Google Home are on the list of integrations that we are considering.
Hope it's not only considered but done. SmartThings isn't available everywhere, IFTTT is.
Will Alexa be able to control the D5 in the future?
-
@roberto Now that the GDPR is in effect in Europe, will you prioritise local network control? It seems to me (privacy expert) that it will be hard to defend only having cloud-based control now that 'privacy by design' is mandatory?
