Tell me I’m crazy. I remember posting that the S1 parallel pattern should push all the way through the parameter pass otherwise the augur just 
on the parameter pass.
As I am running my plan today, right now, it is doing just that running all the way through the parameter and not on the parameter pass. How is that possible without an update?
Am I tripping?
That sure sounds like new behavior to me. And a welcome change.
What does the work plan visualization show? Do the parallel path plans extend into the parameter?
I don’t know if it reflected it on the map @rgloverii. I just watched it. I’ll go out and record it next time. The only reason I noticed it was this was my first time back in action after a couple weeks away for work and having to swap my original S1. Yesterday I was preoccupied with the washing machine sound. So today I noticed it was pushing all the way through the parameter. Which I agree, is a great thing.
I also may be nuts but I swear it did 2 parameter passes with the inside pass being done first.
Now, it did do both my sidewalks on the plan in reverse as well. So basically, it’s popping off over here.
I hope you’re right about the perimeter. That would be awesome. Did you check your firmware version? Maybe you got a stealth upgrade??
Too bad about the sidewalk runs though. That really sucks
I was wondering about that version myself.
Still 3.11.7
I’ve been getting intermittent indicators in the app that there are new firmware versions available but if you leave the screen open long enough it goes away, or if you click on the FW version.
It always does that even if a new one isn’t even in the pipeline. It’s like the default is to say new until it connects to the servers and actually checks.
Everywhere
Question remains how it really works? I believe it works according to the workplan and it takes time to generate workplan in the beginning. Is workplan really generated locally? or yarbo sends coordinates of area, nogozones etc and plan is generated by remote server? In this case workplan is list of the commands and firmware is just the way yarbo acts on one or another command. So you do not need firmware update to make it perform differently, you just change algorithm generating workplan on remote server.
It works locally as far as I can tell. You can disable your DC uplink and work offline.
If plan is generated already and exists on yarbo it will work probably.
To confirm this please disconnect poe wire (connect it thru poe wall socket without data wires connected, just power), disable 4g (or block it by external device), modify area and trigger plan for modified area. If it works no more questions asked about local processing.
You’d need to leave POE wire and remove the LAN cable from the POE injector. DC is still needed for the core to get corrections locally over HaLow. I’ve actually done this when Yarbo’s servers had an issue early last year, disconnected the LAN cable from the POE injector and started a plan. It ran the whole time offline. I connected to the core via Bluetooth. I didn’t try editing or adding areas, but that would be something you could certainly try and see. The maps are stored on the core, always have been. They do back them up to the cloud now periodically. The plan is calculated at the time you execute it, so pretty sure that’s all local and dynamic. The app is a different story, that’s very cloud dependent. You can’t open it without internet because it logs into your account and pulls your core list. After that, you can kill internet on your phone, DC, and core and then use the core with Bluetooth.
Thanks for clarification. I am checking it now step by step.
First blocked any traffic for Yarbo and DataCenter and MyPhones Wifi.
Yarbo App returned error as mentioned above.
Enabled 5G for a moment to see list of the devices. Connected to the Yarbo, disconnected from 5G.
BT is only active, no access to the Internet for all devices (Yarbo, DataCenter, Phone), only LAN access.
Checked the following items:
Next steps (I will check in the next days)
3. Creating New Area
4. Running Plan
5. Scheduling
PS If App requires Internet access to access device from remote Yarbo server to Operate it this becomes the issue as it will block you from the using Yarbo in case of Internet is down or Yarbo server is down. If BT is used for the local connection remote server should not be used at all.
Completely agree, it’s an issue. Feel free to click the link below and heart this feature request and drop a comment to let Yarbo know we need full offline mode support.
At this time, we don’t have any updates related to this behavior.
This is a little conspiratorial but I think I did get pushed this update early but it didn’t reflect in the app. I feel this different behavior that the Forum is discussing now is what I was seeing during the timing of my original post.
My S1 was starting in weird positions it never started in before (S1 always started in the same position every time until it didn’t), new parallel maneuvers or lack of, weirder sidewalks, different bucket movement, etc.
Also possible you made a change that triggered the behavior. Even simple things like NGZ’s trigger different calculations for the path planning. Changes to overlap, new sidewalks, etc.
This new firmware has definitely changed some of Yarbo’s behaviors.
I’m still trying to figure it all out, but things have changed. And not all for the better in my opinion.
I’m not yet ready to call them regressions. Just ‘differences’ that I need to better understand.
