My Internet providers offline, and so apparently is my new Yarbo. Can’t connect to the 2024 Core at all, not via WiFi, Bluetooth or cellular. What gives? Fairly useless to have a mower that can’t function without Internet. Maybe I should just return my Yarbo and pay a neighbor hood kid to mow, would likely be cheaper and less hassle.
2 Likes
Start a support ticket, if you haven’t. You can do so from the first page of the app, and the entire ticket can be managed from there.
Just remember that most replies will probably happen during the overnight.
Yarbo should pretty much always connect via bluetooth, and neither it nor the DC need any internet connectivity to run. You just lose remote management, and Yarbo must stay within HALOW range.
2 Likes
Yarbo works offline so there is likely another issue. I ran an entire plan for 4 hours with the LAN side of the POE injector unplugged. I was able to connect to the Yarbo Core and watch the app work over cellular the entire time.
Have you tried unplugging the battery for 5 mins. Also disconnect the power cord from the POE injector for the same amount of time. Reconnect the POE injector power, then the core’s battery cable and power up. If that doesn’t resolve the issue, then like @Steve mentioned, open a support ticket.
2 Likes
I wonder if the cellular fall back protocol might lack handling for no cell/cell data off.
I have terrible reception and the first time mine bricked mid mow my ISP had something going on.
Sadly I had not discovered this forum at this time. I am more prepared to check diagnostics thanks to @bryan.wheeler @steve and @Ken posts.
2 Likes
Could be?
The only thing needed is HALOW. If the DC has no 'net connectivity, cell on the core won’t matter as there’d be no network path if halow goes away.
I was having a heck of a time with crappy HALOW signal, only getting about 50 feet of reliable range out of it. The core would flop to cell or wifi and continue.
If you haven’t yet, park your core directly under your DC and check signal.
This is mine, 50 feet away. And it stays that way for good distance.
Directly underneath is -34. A hundred yards out behind some trees and a house, -63. Move behind a metal shed back there, and it’s -72.
I found the cause was lack of pin insertion of the HALOW antenna into the socket on the core. I took some measurements and it was literally like one or two thou.
If your numbers are horrible (I believe Bryan noted that HALOW gives up and swaps to cell or wifi at -80 or so) , it might be the tolerances between the whip and core socket.
I pulled the rubber gasket with no luck, then removed the gold hex nut from the core’s threaded HALOW socket and reattached the whip. Now I’ve got perfect HALOW signal for a really, really, really long distance. If that’s what you’re running into, removing that hex nut for more pin contact may help.
3 Likes
Awesome. Have to check this out because the both mid mow bricking’s happened in an area where it would lose gps on opposite side of the house from DC. I would manual back into very open area away from the house and it would get signal and i would have it resume. There is a lot at play i suspect in my situation, but this is an easy test to rule out first and to keep in mind to check when mapping and signal goes weak.
Other factors that may be at play that Im considering:
- I have terrible cell signal. like drop calls in certain rooms/areas of yard, much less reliable data.
- I have robust outdoor wifi with multiple APs bc see point above. this could be helpful and or problematic. Im still getting a better picture of all the networks at play and their functions.
- The data center is also on the opposite side of my house from the area in which the unit bricked twice during a mow.
- not sure how the recalculation after a manual back to signal can potentially eat up memory or find issue after repeated manual gps reconnection/resumes?
Unlikely. There are quirks when that happens, but they’ve not manifested that way for me, as of yet. Mostly it’d just be the core would stall while the TCP timeout expires, and xmit buffer not getting flushed. The various streams would be 15, 30, 45 seconds behind reality, lol. “Move forward for 5 seconds”, nothing happens for 20 seconds and then it moves forward for 5 seconds, etc. Of course by then you’ve told it to do a bunch of more things, and hilarity ensues… 20 seconds later. That was over wifi when my HALOW whip was unseated, however.
Once your core is safe to drive around, play with SmartVision to drive to various spots (directly under the DC, for starters) and see what that signal is. If it’s bad (mine was -74 before I fixed it to -30something), start there. If it’s decent, drive to some trouble points and watch that signal strength. -80ish is the kickover point. Grab a post-it note and make some notes about what and where, see if you can find where HALOW gets sketchy or ends. Although if you go all the way out, you’ll have to get into bluetooth range to get your core back, lol. So probably find where it gets sketchy and skirt it, unless you are walking with it.
If you have two phones (or a phone and the Bluestacks emulator), you can keep the diag screen open on the phone, and cruise around with SmartView on the other (on your PC for example), checking signals. And then you can be inside away from these freakin deer flies.
2 Likes
After 4 hours of letting it sit happy on the network doing nothing with apps closed I checked on it.
Wifi showed it only disconnected once and reconnected the following minute. This was 8 min in to its first connection and was preceded by 14 MB up and 495 MB down according to router software.
I took of in vision beta and tested some spots keeping notes on my sticky pad (had not read your post yet). I got down to - 66/67 in the worst area but I wasn’t trying to set low records and did not stick around. Lots of 40s and 50s without the house in the direct path.
Also took notes on the cores pass offs between my APs.
I had/have a similar experience.
I disabled cellular on the rover, since I dont need it with Halow.
The other day my home internet went down, and although I was connected to my home WIFI ( not dependent on my ISP ) along with the yarbo. I wasnt able to access the yarbo at all.
For the App side of the equation:
I have noticed. If I dont have internet access with my phone. then I cant see my yarbos.
Now yes I understand the “of course you cant see/access the yarbos, you dont have internet” response BUT there are 2 cases where that shouldnt be correct.
- If I am connected to the yarbos hotspot. I should always be capable of controlling it. Now yes this does work, however I have to launch the APP when I have internet, BEFORE I connect to the yarbo ( and dont have internet enabled ). Now this is a rare cases but something I had to do early on and was quite frustrating.
- Local network. With Halow, the yarbo has a constant ‘WIFI’ interface back to the base station, which then it uses to access the internet. The App should be able to directly communicate with the Halow base / Yarbo without the yarbo needing internet access.
The solution to #1 above, should simply be caching the yarbo device information in the mobile app. You can tell that it currently doesnt by disabing all internet on your phone ( no wifi/lte ) and then close and re-open the app. When doing this you get a “Request failed. Please check network” error code, and then it asks you to “add your yarbo”
So clearly the app does not remember your registered devices. This should resolve the cases where even your phone doesnt have internet, but is on the same network as the Yarbo.
2 Likes
Thank you for this insight and I can imagine how frustrating that is. I will have to do some experimenting after my unit finally updates to the latest firmware. I’m trying to leave it sit with good signal on all and the app closed until tomorrow. They said a week for this roll out. I don’t want to try to map and have it mess with the update.
I have other devices that have the same issue as they actually talk to each other through the cloud rather than locally.
The major component of the app restarting with or without internet is a much needed level of understanding of the app and network functionality.
should be in the #corewiki until its resolved