It would be great if Yarbo could enable some kind of (local) API Access.
I would like to be able to access both the data from Yarbo, and be able to send it commands. Ideally using Home Assistant. Similar to what I can do, for example, with my Roborock vacuums (where I can see maps, see information such as runtimes, etc. And also tell it to go do a job).
It would be great to both monitor the Yarbo with something other than the app (including diagnostics like GPS signal strength), and be able to interact with it via. my home automation system.
Here is an example of the card in Home Assistant I have for one of my Roborock vacuums (which is possible because of the API access):
Thank you for sharing your suggestion! We understand how valuable local API access for Yarbo would be, especially for integration with Home Assistant. However, we’re sorry to inform you that, at this stage, we are not going to enable API access. Currently, our focus is on ongoing product improvements, but we’ve taken note of your request and will consider this feature when we have more development resources available.
Since it’s mowing season, our main focus right now is on improving the lawn mower and working on the upcoming trimmer product. All of our resources are currently dedicated to these areas. As for the HA integration and API access, it’s still on our request list, but we don’t have the spare resources to develop it at this moment. However, it is part of our future plans.
We truly appreciate your understanding and support as we work on these key priorities. Thanks for your patience!
@Yarbo-Forum - In a recent tech session within the last two weeks I’d say, there was an answer the opposite of this, including mention of Alexa, Home Assistant, Google Home, Homekit, etc. It sounded like Yarbo decided to go ahead with this and development had started.
Unfortunately I do not recall which session or who mentioned it. It may have been the Trimmer livestream? The last tech session with Suppoert and Dev? Honestly I don’t remember.
So somewhere there is inconsistent messaging.
I agree that this would be nice to have, but I can see there being other priorities at the moment.
Yes, we have indeed decided to develop this in the future, and we are still in the very early stages of the process. Thank you for your understanding, as we currently have other priorities. Unfortunately, this feature will not be available in the short term, but we truly appreciate your patience and support.
You forget, I think the HA community has a lot of volunteer resources to integrate your robots into HA! Wouldn’t it be interesting to be able to free your mqtt so that we can put a second one like that HA could read the data? It seems to me that it’s personal data, right? So why can’t we have access to it locally? The more you trust the community, the more advertising you’ll get and the more your robot will evolve and sell very quickly Have a good day and thank you very much for your support to the whole team
I run Home assistant and would Like a Local API to the Mower Software as well, with my Mammotion mower I have that ability and monitoring and control from my HA has gotten my mower out of some jams while I was away from home
Yes, absolutely, that’s what I have too, and I’ll even say better, it’s that with the Dreame X50 and certainly the X40 you can also see the cards, change lots of settings and see the cameras!!!
There are lots of us who want an HA integration. There are also a lot of unfinished features I personally would like first. Time will tell if it gets legs again.
Co-Founder Ken K has stated numerous times that he wants this feature as he is a big Home Assistant user himself. I promise you this integration will come but it won’t be until they nail down some of the root issues they have been working very hard on solving.
It would be so much fun if we could be an informant of what is happening and of things that we could do or not! But really! It would be fun! Tesla and for example Homeseer Zwave… we open their code and see where they are! The Walker is open! This machine is sure to have a lot of potential but I think it needs help! And it’s a shame that we can’t receive the betas of everything just to give our opinions on the ground
Indeed I think API is really a benefit. I am also a huge home assistant user. Off loading tasks could help in so many ways. I am thinking even ai object detection. Just scheduling would be a huge help! I trust my HA and all of its inputs more than a slimmed down mower capability. Sharing resources, that’s what it’s all about
I’am late on this but being able to call the API if only to start/stop a work plan and maybe if we are lucky some area setting would already be huge. We could then program our own shedulers
Effectively start a work plan, recharge at some time, continue when dew should be gone.
A generic status would be nice. (Working, paused, charging)
I am always of the belief that starting simple and building on it would be best. I think too many times developers are trying to build in all the bells and whistles.
As a start, how about providing a login with read only access to the MQTT topics. This would be a great starting point and at least allow some monitoring outside of the App. The user/password could be autoconfigured based on the unit serial #.
and not taking into account customer requests may mean losing customers and having to integrate them later and therefore wasting time because we could have planned for it in advance! but yes, at the same time, you’re right! Planning costs nothing!
Have a good day and thank you very much for your support to the whole team