Has anyone seen this yet? I have no affiliation with this company but it looks promising. I did subscribe (I’d rather buy a perpetual license) but for $35/year it seems cheap if it does what it says it does. We have a lot of rain coming so I won’t be mowing but I think I’ll spend the rainy week making map corrections on the computer.
Let’s just say I know it works very well. And the feature list is still growing.
Good to know, thanks!
With Yarbo’s latest FW update “cleaning up MQTT” servers, it’s no longer local. It’s still super awesome and worth it just to be able to fix all your jittery maps, etc. it also tracks problem spots in your yard and will tell you some metrics around when the Yarbo throws an error code which can be enough for you to diagnose your own issues really quick
Hello - I built Yardstick. Thanks for the kind words, and @Tom.C, thanks for taking a chance on it already. I think we have built something special that everyone has been asking for so I hope you will take a look.
@rcguymike has it right, after Yarbo did this latest firmware update the ability to stay local only and have your robot keep working using this application even if servers went down or your internet went down is now gone. That is the only change since the idea was conceived a little over a month ago. Yardstick now signs in with your Yarbo account and talks to the robot through Yarbo’s official SDK, so that connection is no longer local. We would like a local connection, but the functionality is not impacted at all using the non-MQTT route. What is still local: the app runs on your own computer, and your maps, recordings and history stay there and never leave it. This application came together with the help of many on this forum - more on that in the next post.
I’ll put up a fuller post shortly with the whole feature list so this thread doesn’t have to carry it.
@B-Mod sells it short 
It’s amazing work! This is how the Yarbo app should work!
Not my sandbox, I just gave a praise without spilling any beans.
Very sad that “cleaning up MQTT” was more important to Yarbo than fixing the devastating bugs or adding truly useful features.
Once I tried Yardstick, I wanted to use the Yarbo app as little as possible.
To be fair it was part of the security updates they’ve been making, being able to control the Yarbo unauthenticated on the local network is a pretty big concern. Hopefully in the future they will implement local control properly, but like Mike1 said in his other posts, they need to work on the core software and let the user community work on these quality of life things until they have a good software update/release cadence. There’s a lot left on the vision, travel algorithms, planning mechanisms etc that they need to focus on
Point taken, but they’ve also effectively locked us out of our OWN hardware.
Well they locked down the software… especially with the advancement of AI cyber abilities I’m all for it. It was scary what was possible just a few months ago, it actually made me go out and buy an entire Ubiquiti network setup just so I could isolate all my IOT devices and be able to monitor and lock things down as needed. There are so many zero day vulnerabilities being discovered all the time now.
Yes, I was pretty upset when that local door was closed, but I understand and agree with the rationale. Some malware on your computer could do bad things to your robot on your home network. That could translate to possibly very dangerous situations in real life. I hope in the future they can open this up securely for those of us who prefer local first, cloud optional.
@rcguymike said it better than I would have. Unauthenticated control on the local network was a real gap, and closing it was the right call. I’d still like to see local control come back, done properly.
We think there’s a way to do that securely, and we’re glad to share it with Yarbo whenever it’s useful to them. In the meantime everything runs on the official SDK and every feature works the same. The one thing you give up is riding out a server or internet outage, which is exactly the part I’d like to get back.
Would just securing the MQTT traffic have been an option and much less drastic approach?
In our opinion, for the local side, yes. Would give the best of both worlds.
tried to download…getting a dark screen with code on it….
Can you share a bit more - what version are you trying to download and what is your computer that you are using? Might be best to take this over to our support channel on yardstickhome.com
@mike1 Even though it’s no longer local due to the firmware change it is still amazing and has already saved me so much frustration with dead ends and long runs against my fence. I was able to fix three areas that have been giving me trouble for months. I mapped them initially and all was well, then like a couple weeks later Yarbo started hitting my fence and tried to rip the post out of the ground. With your software I was able to make a few adjustments to the path and, works exactly like I want it. UNREAL! I’m so happy you created this and Yarbo released the SDK for people like you to help the community.
This software has reinvigorated my love for Yarbo and now I’ll map new areas and be able to use Yardstick to make the fine adjustments that I’m sure will be needed. I never mapped these areas before because I knew it would be nearly impossible to get it right the first time and I really didn’t want to map over and over again.
Again, thank you!
I’ve been doing that for free for months. 20 minutes of Claude Code. Charging for this is tacky.
Are you going to share what Claude created?