Based on the valuable feedback we’ve received from our community since the last major update, we are now rolling out Hotfix Firmware V3.13.7 and App V3.18.4.
The update will be released in batches and is expected to be fully deployed within one week.
What’s included in this hotfix?
General Improvements:
Fixed the issue affecting the automatic light on/off logic during nighttime
Added Lithuanian language support in the app
Fixed a path planning issue where Yarbo could incorrectly route into No-Go Zones (NGZs).
About the security content of this update
This update provides important security fixes and is recommended for all users.
For detailed information about the security content of this update, please visit our Security Center.
How to update
Please make sure your Yarbo is powered on and connected to the internet. The new firmware will be installed automatically once it becomes available for your device.
If you have not received the update after one week, please feel free to contact us at support@yarbo.com.
Extremely disappointing that there is no mention of Security improvements or enhancements.
A week ago co-founder Kenneth Kohlmann said the security vulnerabilities were the most important work for Yarbo, yet a week later a Firmware and App release doesn’t mention Security improvements.
There’s also no solution to the dead-end problem, which I’ve reported involves skidding toward the perimeter walls at the start. You even tested it on my Yarbo and discovered a problem.
@rgloverii I AGREE with you. If something is ready get it out to End Users.
My issue is Kenneth’s/Yarbo’s lack of timely communications. These security gaps are significant. The reason I provided feedback is specifically because Kenneth set (or failed to set) expectations.
#1 was expected to be complete within one week - either it should have been in the release -OR- if it didn’t require new Firmware at least a statement should have been released stating it was done or something like, “we need a couple more days to ensure quality of the update.”
#3 and #4 were is Testing a week ago. Is a week a reasonable amount of time to test? I would think so. If not Kenneth/Yarbo should have managed our expectations by provided an update saying something like “next two weeks”.
Here is the exact text of Kenneth’s statement for reference. Bold is my emphasis.
We are implementing an allowlist-based, user-authorized, and auditable remote diagnostic model. The first phase is expected to be completed within one week. Once implemented, remote diagnostic access will be limited to authorized internal company personnel, may only be used after user authorization has been obtained, and will be gradually brought under audit logging.
We are using OTA updates to advance credential rotation and device-level independent credential mechanisms, gradually replacing the historical shared-password model. In the future, each device will use its own independent credentials to prevent one affected device from impacting the entire fleet.
We are building and testing a robot credential management service so that device passwords are no longer hardcoded in firmware, scripts, or databases. Instead, credentials will be dynamically derived based on device identity. OPS access will also record the visitor, reason for access, work order, and timestamp.
We are hardening other authentication services. These fixes are currently in the testing stage and will be released through upcoming OTA updates.
We are adjusting topic permissions to reduce fleet-level shared access, limit the scope of each credential, and establish stricter boundaries around control commands.
We are testing cleanup measures that include removing unnecessary reporting scripts, legacy cloud service dependencies, third-party agents, and non-essential DNS fallback configurations in order to reduce data flows that are not clearly visible to users. These changes will be rolled out through future OTA updates after testing is completed.
Can we fix the blocked camera in the rear because of the back brace mount. That has to be a easy fix, and should have been fixed months ago when they designed the brace.
@Yarbo-Forum - it’s been a while since I’ve posted anything on this forum, and that’s been welcomed, that means the unit has been working GREAT!
Unfortunately, after the latest hotfix, it looks like some backend settings related to no-go zones were changed. Since then, the unit has had no problem plowing into no-go zones. This is a new anomaly: it chewed up two landscape lights and took out half of my wife’s hostas around a tree before I got “track slipping error” and then got to have a “conversation” with my wife on taking out her flowers - thank you for that.
Please do not suggest that I need to be sending logs or screwing around as another beta tester for you, I just want it to work like it was a few days ago! I don’t have time to play pattycake with your support - use your own lab, use your own QA people, and figure out what’s going on please.
They have acknowledged that the last firmware release is causing issues with Yarbo potentially straying into no go zones, and have announced another firmware release that should resolve it.
Hopefully we all get this new patch soon. Supposedly we’ll have all have it within the next week.
My app updated today and now the enter yard/create map button is greyed out and unusable. My Yarbo is currently parked in my shop without GTK connection so not sure if that’s the problem. Wasn’t a problem before the update.
Reboot and disable Bluetooth on the Yarbo app and see if that helps. If not, I’d reach out to support to see if your map is still there. Might just be a file corruption or something simple to fix
The map doesn’t activate without a GPS signal. If the GPS doesn’t start after rebooting, try reinstalling Datacenter or Ntrip, whichever one you’re using.
Hi there, we’re sorry for the inconvenience caused.
The issue has been addressed in the latest firmware update. If you still observe the same behavior after receiving Firmware V3.13.7, please feel free to keep us updated.
