Hacking a Neato Robotics BotVac Connected
-
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?
-
@roberto Really supportive of the community to join this discussion.
I see there is a desire by the community unmet by what you're able to provide: local LAN controller. The obvious reasons include both the complexity that you might have in various cloud services that would be difficult to setup in a small LAN, the variance in server hardware or software to host the controller, and the IP that might become obvious if you ship a parsed language such as python.
This might actually be mitigated if you're willing to offer a docker image of a controller: supporting (or not-supporting: support yourselves, hackers!) is more consistent if one docker image can run on whatever orchestration we use, and we gain the ability to hit a local resource without uptime and latency and cloud-ness to worry about.
Understanding the subtle-but-continuous increase of cost in cloud services, this allows your uber-elite users that may generate above-average query load to shunt this load to their own resources.
Additionally, you'd seem like even more awesome people for doing this. Very cutting-edge. Define the next level of customer interaction and independence, GDPR privacy issues, etc.
I bet if you made a dummy service -- some go routine or python flask that simply responds with logical bogus values -- the open source community would build the docker image for you. Overnight.
Anyhow, it's a thought.
