If it is virtualizing MAC and they are not set to static it can be an issue. Typically the virtualized mac would only change if container was restarted, or is spawning multiples. Seems odd to me. From what one poster mentioned that support asked to add specific MAC I would think that they are using the actual hardware MAC. Normally would be NAT for the the containers through this and would stay solid.
If you are running a pihole or some other DNS filter add the hardware MAC to the exempt/whitelist. Also many routers are using services to identify suspicious or categorized malicious entries. I often have geo specific blocks which also can interrupt this. The other option is indeed to set a Mac for a reservation then use that reserved ip(s) in the white lists. Do note router, firewall, acl rules are processed top down. Your allows need to be above the deny.
Does anyone know what device name the data center would show up as in the network? I lost the ability to remote in to the yarbo a few days ago unless I’m standing next to using Bluetooth. Cellular was on previously but that’s off now for some reason. Maybe they remotely changed some settings to “fix” the gps losing signal? For what its worth, that has been better but I have a blade speed issue that stops it every so often.
And it’s back. I did a shutdown via safety to change blades. When powered up, the Core comes back up in 4G claiming there’s no RTK connection. It’s mowing perfectly in 4G and not recording any cell data usage. I reopened ticket #102509, recoded issue and noted the timestamp in ticket. I’m not resetting the RTK until I get a response.
This is on firmware V3.9.29. App update not yet available.
Thanks for following up and providing the detailed information. Our support team will investigate the issue to determine its root cause. We’ll keep you updated as we work on resolving it.
If you disconnect the LAN side of the POE injector you can validate if it’s truly in HaLow or not. It would lose GPS at that point (really. RTCM). If it’s using cellular then it wouldn’t have a path for your rover and data center to communicate with Yarbo’s servers. If it’s truly using HaLow then it would continue to operate in offline mode using HaLow.
Yep. That exact process was on my troubleshooting list, but I’m hoping support will take a look before I mess with it. My unproven guess is that it’s a display bug. Your process will confirm.
I power cycled the DC at lunch today. It was still running in 4G and after 2 days support hadn’t looked at it. With the last update the Cell Data started showing correctly in Settings (another undocumented change - I hate those.), and it was using quite a bit. If it really does need Cell, I want some data left.
In summary, it was clearly hitting 4G and not just displaying it. This will randomly happen again in a week or two so there’ll be another opportunity for support to look. It sure looks like something is crashing in the DC.
Add: I disabled cell this time to see what will happen the next time HaLow craps its pants.
In my experience the stats don’t collate until around midnight. Or at least daily. Not sure if that’s a factor or not but I did notice it started working again too.
@cobradunn@bryan.wheeler Same with mine.” With the last update the Cell Data started showing correctly in Settings (another undocumented change - I hate those.), and it was using quite a bit. If it really does need Cell, I want some data left.” Mine has never showed it used any cell/4G. It always remained at 0. Now that maybe common with all the problems I was having, because he was just sitting for weeks because of the issues again. I check my numbers multiple times a day, because he running. After the update, I’m using Cellular / 4G now.
I had installed my own 4G sim. Rover used almost 500mb data in 24h mowing work. I unplugged the LAN cable from DC and tested this about 2 months ago. Yarbo application has always shown 0 data usage. Never anything else. I checked the installed sim-card data logs from my provider.
Same here. Mine always showed 0 and now it shows 83M. I kept having it switch to 4G and the only way I could find to revert it back to HaLow was to power cycle the DC.
Also, I live in the suburbs and have a relatively small yard. The rover is never more than 150 feet from the DC. The DC is mounted on my roof. There is really no reason it should ever switch to 4G.
