I’m just going to add my support for this. I would suggest, of course, that the API runs through the RTK. There would be no need for any other connectivity scheme hopefully.
Anyway, another vote for API that connects to HA / every other home automation system out there. Thanks. BTW, Mower Pro is %103.72 better than the orginal. I did the math myself ;>)
Just ordered my Yarbo and first thing I came to look for was ways to kick off snow blower tasks via Home Assistant. I hope this is actually coming.
You keep saying this with each post. “it’s on the list but x, y and Z are being worked on. So how long do people need to ask before it actually happens? Or it is just more excuses. Because honestly thats what it looks like. Tons of form posts you have replied to, over MONTHS with some new reason why it’s not being worked on but don’t worry it’s on the list!
Just say you won’t do it so people don’t have to keep waiting on something that won’t happen. This is as bad as Samsung.
@Dragon-IT Hi there, thank you for sharing your thoughts so honestly — we do understand where the frustration comes from.
For every feature that we believe would genuinely benefit users, we pass it to our product team and add it to our internal feature-request list. These suggestions from the Yarbo community are incredibly valuable, and they play a big role in shaping how the product evolves.
That said, because of priority planning and limited development resources, we’re not able to implement every request as quickly as the community (and we) would like. We know this can be disappointing at times, and we truly understand how it may feel when a feature takes longer than expected.
Regarding API access specifically — yes, this has been discussed for a long time, and we’re very aware of how much interest there is in this feature. It’s something many users have been asking for. However, we want to be transparent: we still don’t have a clear timeline for when API access will be available.
Please know that your voice is heard and valued, even if not everything can be delivered right away. We really appreciate your patience and your passion for making Yarbo better.
Just like every other voice is heard but
-no time line
-we’re “heard”
-planning for a long time
-you’ve know about people who want it
See you guys keep recycling the same reasons just formatting the words different so it comes across like you might care, but actually probably won’t do it because you don’t make money off it.
When it comes down to it companies really only focus on what makes money and since an API doesn’t make the money it’s less of a concern for them to implement.
But also when something is requested enough times and a company is recycling replies, saying its being talked about, no time line, and been months, it becomes less trusting its actually going to happen.
I’ve been running an HA system for close to 30 years. I’d love to see this functionality but they have many other higher priority issues to address. At the moment the API should be, and is, a low priority. They’re probably losing potential sales because of this but I understand why this isn’t a priority.
As far as I have seen they have always said it is something they want and plan to do but there is no timeline.
Completely agree and I feel like it’s probably a significant effort and code rewrite to undertake. No one wants it more than Ken K, Co-Founder. I’m sure it will come at some point. But resources are limited and this is definitely something that should be in the back log compared to other more pressing issues.
My point stands lol
It’s also unwise and inefficient to create a public API until their codebase is stable.
Right now, they’re still refining and solidifying the codebase, which would (likely) mean any API would also require frequent revision.
I’m 100% good with them devoting their limited resources to solving the problems and creating a stable platform before they start working on ‘stretch goal’ type items.
yeah I need the feature to open my gate so the yarbo does not rip its antennas off trying to go under it
Where should start a pool on when HA is implemented.
I’ll be so happy when we get a public API. But I don’t expect to see one any time soon.
I agree with Yarbo’s approach - Resolve basic stability and functionality issues first.
I am so interested in the Yarbo, however reading this thread gives me some concerns about purchasing.
1st, there is no integration with my smart home application, I use Smartthings from Samsung and everything in my house is controlled through SmartThings; garage doors, vacuums, lights, outlets, coffeemakers, etc. everything is mostly run by automatic routines/scenes. Having a device like Yarbo for mowing the lawn, or snowblowing would be absolutely perfect. Being able to run based on a routine that looks at the weather, and then decides whether or not to trigger the Yarbo to snowblow. Or being able to look at the forecast and hold the Yarbo lawn mower because it rained, or triggering it for the afternoon once the dew burns off from the grass. Not being able to integrate is definitely a showstopper.
2nd, reading this thread and seeing how there have been no definitive timelines, or release dates tells me that the company doesn’t value the customers. I work for a software vendor, and we score items that come in and decide where to interject on the roadmap, seeing that this has been talked about for so long, with still no commitment is very telling.
I am sure there are many others waiting in the wings for this to happen. Integrations are the way of the world. For this to not have been thought of is a bit concerning.
Hello Jordan. Welcome to the forum!
I don’t think the lack of an API timeline suggests that Yarbo doesn’t value its customers. Here’s why…
My honest thought is that they have a small development team, and their current focus is on improving basic system functionality and stability. As a Yarbo owner, that tells me that the company’s focus is more on improving the overall user experience versus developing a new feature they can promote on their web site to generate sales.
I think a lot of current owners (as well as potential owners) would greatly appreciate an exposed API, but I think it’s understood that they need to prioritize their efforts.
Yarbo is a cool product. And it’s growing and maturing with every firmware release. If you’re the kind of person who likes being on the cutting edge of technology, this is the right robot for you.
Thank you, I understand where you are coming from, however, even with stabilization issues, they can still roadmap it out, or give a tentative timeline.
I really am eager to try the product and give valuable feedback, I just don’t think it’s ready, especially at the current price point.
You should try to find a Yarbo owner that is local to you so you can get an in person demo. I think that’s probably a good first step in terms of getting to learn more about the robot and its pros/cons.
Of course Yarbo isn’t perfect. But very few 1.0 products are. It’s an entirely new product category, and I’d say the company is learning and adapting at a reasonable pace.
Thankfully the hardware is (mostly) really solid. And on the software side, like I said, they continue to iterate and mature with every release.
@rgloverii nailed it on the head.
If you are looking to toss your mower, shovel, and weed wiper?
“Not so fast my friend”
-Lee Corso.
I just came in around September. The community is out here doing the Lord’s Work. Haha
@bryan.wheeler @ken.w.gregory @rgloverii have been my Yarbo Sherpas.
I’m in Northern MI (lower peninsula) if you want to ever see this thing in action.
Come in with expectations of helping build the product you want. It’s still early enough. We are absolutely bombarding them with ideas and tweeks. They are definitely listening.
Where can I get me one of them there weed wipers? 
Somewhere out there behind the ol barn.
It’s a SHOP…. the mortgage company doesn’t do farm loans. 