Is there an echo in here? ![]()
Thanks so much for the detailed tip!
We’ll find a way to integrate this information into the mower maintenance section of the Wiki.
We’ll confirm internally regarding the official torque specs and see if we can include part numbers and reference charts in the upcoming Wiki updates. Thanks again for flagging!
Is there an echo echo echo in here? ![]()
Thanks Marco, much appreciated!
This is great! Very useful and I can find what I’m looking for easily.
The wiki and forum have saved the expense of at least one return…
I had made up my mind to place my order, but wanted to verify that it could tow my spreader, de-thatcher, aerator, and leveling roller. I was deeply disappointed to find out that although this ability is promoted, the software support is on indefinite hold. If I had discovered this after receiving the product, I would have been seriously frustrated and would have returned it.
I totally understand that your developer resources are limited, and stability of core functionality is the too priority. This is a situation where offering an API for modular add-ins would allow you to leverage the energy of your user base to expand and enhance the functionality of your product.
You’ve got the only extensible yard robot on the market right now, and if you were open to others developing accessories and attachments, the appeal of your product would be significantly enhanced. Traditional manufacturers have tried to make “closed product systems” for decades with limited success. I know you want to sell your own leaf blowers and string trimmers because there is good margin in it. The benefit of letting other people innovate on your platform is that you will still be able to sell your products as “premium” versions, but let third parties open the markets for you and experience the pitfalls.
I’m an engineer. I know a dozen add-ons I would build to use with my robot if it supported some simple interoperability features. Yours would be a great option if you choose to go that route.
The velocity accelerator on top should be changed out. Please call it the gopher-nater

Edited: This appears to be happening on support.yarbo.com, not wiki. My apologies for the confusion.
Looks like the custom domain auth fix has reverted back. Now when I try to log into the KB, I’m prompted to log into the development auth0.com site again.
Oh, so I might as well say “Hi” and send my first comment then ![]()
Hi and welcome!

