You’re welcome. Not a problem. Like I said, so far, NetRTK has been absolutely perfect for me. (Knock on wood!)
If you see connection status 4 for the DC section of the diagnostics vs 2 or 3 then you are truly on NetRTK. Yes as @rgloverii mentioned it can be used over HaLow and is the Yarbo recommended implementation.
Thank you Bryan!
FYI, this is the communication I received from Yarbo, which is why I wanted some clarification.
Dear Andrew,
We are really sorry to hear that you lost your maps after switching to Net RTK. We understand how inconvenient this can be.
After switching to Net RTK, remapping is required, and as you have already completed the mapping again, you should now be able to use your Yarbo with the Net RTK service.
Regarding your current setup:
Your Yarbo is still showing HaLow connection because it is not connected to Wi-Fi
In this case, HaLow is being used for communication, not for Net RTK correction data
To ensure proper Net RTK usage, please follow these steps:
-
Go to Yarbo Settings
-
Select Network
-
Tap on Rover Wi-Fi
-
Choose your home/router Wi-Fi network
-
Enter the password and connect
Once connected to Wi-Fi:
-
Your Yarbo will use the internet connection for Net RTK correction data
-
There is no need to rely on the Data Center (HaLow)
-
You can turn off the Data Center if you are fully using Net RTK
Regarding your question about account setup, in most cases Net RTK does not require additional manual account creation from the user side, so this is normal.
After completing the above steps, your Yarbo should be properly using Net RTK for correction data.
If you are unsure or would like us to verify from the backend, please let us know and we will be happy to assist further.
Thank you for your patience and cooperation.
Best regards,
Simon
Team Yarbo
There are so many things wrong with that. I see why you were confused. @Yarbo-Forum switching to NetRTK doesn’t cause you to loose your maps. I’ve done it a dozen times and just did it again today. What will is if you tap NetRTK and the app hangs while it’s switching (it does). If the user taps a few times thinking that’s going to unfreeze it, I suspect they are unknowingly tapping relocate yard and then on the confirm pop up that says it’s going to initialize and that you should back up your maps first because they will be lost. I recommend that this link be moved under the Data Center section or somewhere benign. I would also prompt the user when switching that they need to wait for solid and green GPS and then go correct for map drift.
Additionally, telling people to connect to WiFi and power off their DC is NOT the way. Not everyone has solid WiFi throughout their property and they WILL have GPS issues if the WIFi drops out, especially if Cellular isn’t enabled or has reached its data cap. While removing the Data Center or powering it off is an option, I don’t think Yarbo should be suggesting this unless there are special circumstances (IE the user doesn’t want to install the DC, it failed, etc).
Exactly, It makes total sense to use HaLow. I would even go so far as to suggest that they make a DC for just that purpose, or an antenna and cable to mount separate from the DC module, just to broadcast HaLow. It broadcasts further than WiFi and would be suitable for most applications. This would save the need to use 4G and some expense.
Yea, the messaging you received from Yarbo is quite confusing at best, and incorrect in multiple areas.
Like Bryan indicated, you should NOT be losing your maps when switching between RTK and NetRTK. What is needed whenever you switch is to perform a “correct map drift” function which basically just realigns the map with your Yarbo’s physical location when it is docked.
And like I mentioned previously, the “best” communication method is to leverage HaLow no matter what. There are some fringe use cases where WiFi or even 4G might be needed, but for the vast majority of people, HaLow is the most reliable way to go.
All that said, sorry you lost your maps. Were you not able to restore from backup?
For the redesigned DC they are making a NetRTK only version. I don’t agree with this, I think there should just be one DC that does both. Less development, overhead, etc for the backend support and more importantly less confusion for the end user. But both versions (NetRTK and Local RTK) can be mounted indoors or outdoors. If you want to use Local RTK, obviously it would need to be mounted properly outside. Otherwise, plug it into your router and sit it right beside it. Won’t have the strongest range, but still will probably be much better than WiFi.
No, the back ups would not save for some reason. I’m sure i did accidentally hit the “relocate Yard”. But not a big deal a little bit of time and back in action. I really appreciate the advice and feedback!
Still did not get the latest firmware update v3.13.3 still on V3.13.1. Does anybody else still waiting for thefirmware update?
Do you have a ticket opened for this? If not, I’d recommend it.
Coincidentally, I just got the update, just when I was going to ooen a ticket. YARBO read my mind.
Thank you YARBO
ok, I have the latest app (3.18.3) and firmware (3.13.3). I’ve noticed the following issues:
- Yarbo occasionally announces something, I’m normally in the house when this happens so I can not clearly hear it, but I think it has something to do with GPS strength. This happens at random times day/night. The Yarbo is just sitting on the charger, no plan, no schedule. I have the leaf blower attachment on it.
- The lights on the core come on and stay on all night. I’ve gone in to the app → controller and shut off the lights, only to find them back on a few hours later.
Are other people seeing these issues?
Do you have your sound muted? It can certainly announce things like weak GPS if not. The lights is a known issue. Are you using the Home Assistant integration? If so, make sure it’s not set to working mode but set to sleep. If not, make sure you don’t have an app open. However, they are aware of the issue and working on a more long term fix.
@bryan.wheeler yes, I had installed the HA integration. I checked and it was set to Working. I changed it to Standby. (Sleep was not an option) Thanks for the suggestion.