Thread and Matter support would be ideal in my mind as that would support most all of the main smart platforms and Yarbo wouldn’t need to alienate groups of customers by choosing one or two.
4 Likes
Any update on this?
2 Likes
Any update on this? Providing API access the DIY communities/programmers/third party software developers would boost the sale of the product, if they know they can work with it. Do you wanna sell units or keep the api locked ? Currently cant recommend yarbo because of this. Others have it: Husqvarna Developer Portal and their product will grow faster because of it.
5 Likes
@jon1 Hi there, thanks for your interest in API access. We understand many of you are eager for this. While no clear timeline is set yet, I’ll be sure to pass your strong interest along to the relevant team.
5 Likes
Even mammotion has access for home assistant
4 Likes
And terramow
1 Like
Why can’t we access MQTT? It doesn’t change anything for you because it’s local and doesn’t consume any more power.
4 Likes
I’m sorry, but we don’t have any plans for that at the moment.
they really don’t have any intentions of opening up the API for anything we are stuck with cloud based app only access they won’t even allow it to work on a desktop to edit maps to straighten out lines
3 Likes
More reasons, too busy. It honestly comes across like you guys really just don’t care. For months it’s “on the list” but that’s as far as it ever goes.
There’s already a developed Control4 (still in beta from the dev before public release) driver. Works great, few bugs.
so why not just open it up, and stop saying it’s on the list because it clearly isn’t based on that it’s been said with no updates
4 Likes
Who is the dev. I would love to test I am control4 dealer
1 Like
Yes, because I developed it, Hi Mammotion Home Assistant dev here, I’m starting to look into yarbo, but I do not own one, if the Yarbo guys are interested, I’d be keen to work on this.
9 Likes
Welcome to the community @Mikey0000 I’d be keen for you working on it too. I could kick in a cycle or two myself.
3 Likes
Same! The dreame ha integration might also be a good roadmap.
2 Likes
I bought Yarbo precisely for the integration they promised and because the machine seemed incredibly well-designed and easily modular. But I’m realizing I’m entering a proprietary and completely closed environment, and that the day the company goes under, I won’t be able to do anything with the machine because it will be completely closed and unavailable locally. ;-( We’re not asking for anything! Just the ability to connect locally to the machine, even if it’s through a web interface or something else.
For me, opening the doors would show that you’re working on it and that you’re actually developing the machine, but you already know all that!
3 Likes
I think the biggest current limiter for having an open API is the platform’s maturity or lack thereof.
Basically, you need the code in a stable state before you can reliably allow external access. If stuff is changing all the time and nothing’s documented yet, the task of allowing API access and supporting it would be much greater.
I know they have some serious SmartHome type plans in the mix. As long as things done get pushed out, 2026 should yield some fun stuff for us all. My fingers are crossed.
5 Likes
why not just open mqtt on local ??? just that ! and open rtsp;// on local too 
with that i can receive many alert ! for help me
the yarbo alert for any problems is not working on ios ;-( is poor è-(
nice day at every body
2 Likes