Perfectly said and so true. The software is the ABSOLUTE problem, but the the responses are completely incompetent and dismissing. There hasn’t been a recent comment on how this is being addressed; which likely means means it isn’t and they’re bleeding to death. This can’t continue or we’ll all have bankruptcy paperweights!
So true, and now even worse is they are ignoring tickets and just letting them sit. By the time they do get to them, there is no data to try to figure out what happened.
The current hope you are in good health line is getting a little old…
I’ve said before - What Yarbo needs to do is abandon their current 1.x software platform and develop a totally new refined 2.0 platform that doesn’t need all the workarounds, kludgy fixes, and an efficient algorithm for work zone management.
I think this is the only way to get the Yarbo platform where it needs to be. No more band aids. A new refined platform that incorporates all of the accumulated Leasons Learned is what needs to happen.
Exactly start over, this system is broken and has band aids all over it.
I would anticipate that’s not going happen with the current management and resources. I’m done expecting anything useful from the current Chinese team. They don’t have the same expectations as the rest the world. Make it barely work, log everyone’s data and move on.
If you think about it, the current software stack was intended for use with a snowblower. The modular stuff came later.
The platform is suffering in part because the software wasn’t originally planned or intended for use with different modules. Hence the need for more and more band aids.
A platform designed with modularity from the start would make a world of difference.
I have been the CIO for major organizations for over 20 years, with the advancement of AI in coding, specifically Claude, they should get CLI installed for all dev’s and start burning API credits now. In a few weeks this SH!T Show could be resolved and within a month the IoT platform is squared.
And when they start over can we only see maps for the module that is installed. Messy pathways and stuff will everything over lapping.
Exactly!! If/when they start from scratch, they can get rid of the silly retrofit stuff like “one map for all modules”.
Pretty sure we’ll all be starting from scratch soon. They’re in a death spiral currently.
Between supply chain worms and a complete lack of harness effectiveness, I’m pretty sure our resultant cores would spend all their time either mining bitcoin or playing online poker to offset the support costs
I could always use another miner for my solar mining farm…
Hahahaha " it’s fixed… trust us"
If they do hit the rocks, and I sure hope they do not, hopefully they will release the software to this community so we can take it over and try and revive it on our own servers to keep the community going. I would step up to keep it going.
Stop the presses, folks! Hotfix Firmware V3.13.11 and App V3.18.5 has officially dropped!
What critical, yard-destroying emergency warranted a rapid-response hotfix, you ask? Did they finally patch the algorithm that turns the mower into a kamikaze hostage-taker in our No-Go-Zones? Did they stop it from performing search-and-destroy missions on my landscape lights?
Nah.
But hold the phone we had some minor grammatical errors in the Slovenian translations. This is a full on RED ALERT.
ARE YOU KIDDING ME?! A hotfix for that? COME ON!
Good to know the development team’s priorities are rock-solid. My landscape lights might be in a million pieces, but thank God the app menu is grammatically flawless in Ljubljana.
Sorry to hear about your disappointment. At the moment, we are unable to retrieve the logs, so we cannot perform further diagnosis on this case.
That said, I completely understand how frustrating the No-Go Zone issues have been. This topic has come up frequently recently, and we have already reflected all similar cases to our team for a deeper analysis.