Hello, I have ran out of data on my yarbo, how do I use my own sim card?
The SIM card is located in the battery compartment at the top right.
I don’t believe they support customer SIM card activations yet. Not sure if an already activated card will work or not.
Can I ask why you think you ran out of data and why you would even be running out of data in the first place? HaLow should provide adequate coverage range for most properties.
I honestly am not sure. I know my Wi-Fi does not cover my entire property. I walked the unit to the end of the property and had solid HaLow connection. I have already used 4gb this month so I believe that is why it was cut off. I cannot troubleshoot Yarbo remotely without the wi-fi/4G. Any thoughts?
You may want to walk the property with it again and check your HaLow connection strength. -78 or less is what you want. It sounds like that may be having an issue and causing the failover to cellular. Most of the time it’s just a loose antenna. The rubber grommet on the antenna sometimes makes for a poor connection if not properly seated. If you’re having HaLow signal issues, you could try removing that grommet and see if it improves.
Awesome, we will try that, it seems we have had some issues with the Yarbo saying it needs to be returned to its boundary area even though it is in it boundary.
That’s probably boundary set back being at zero instead of 4. You can set back to 4 and it will probably work again. To fix it for zero, you have to look to the map. There may be a pinched area on your map or a section where the boundary overlaps on itself that is causing that issue. If you generate a preview you can sometimes see the path lines go outside the boundary in those areas. If you see that, that section needs to be remapped/edited.
Dude! You are a wealth of knowledge.
Thank you. I just try and share what I learn from others and from Yarbo. The community as a whole is really helpful, creative, and supportive.
@Yarbo-Forum can you give some more information on sim cards and if we can use our own? It is really frustrating to not be able to remotely troubleshoot the device or even check the status of the unit remotely when the LTE service is being disabled.
We are sorry that we currently do not support using your own SIM card. We have added another 4GB of data to your account. Please let me know if you can use the 4G service normally now.
It worked! Thank you. Is there a very easy way to figure out where all the usage is coming from? I will keep an eye on the usage this month to see if I can identify any issues. (I did remove the rubber grommet on the antenna like @bryan.wheeler suggested previously to see if that would help at all.
Can you post some screenshots of your diagnostics? You can omit the GPS coordinates.
Include Rover, Status, Data Center and HaLow sections. Ideally do this when it is at the furthest extent of your property, middle, and dock. This will give a baseline of what might be the issue.
I was shipped a replacement core and it does not have a sim card!!!
I’m guessing you’ve already shipped the original one back?
If so I suspect a support ticket is your only recourse.
If not move the SIM card from the other unit? SIM card slot is in the battery compartment.
Have you physically verified the is or are you getting an activation error? The error is “normal” but as long as you have a status of 1 under cellular diagnostics, it should be working.
I’m sorry to hear about the issue with the replacement core. I’ve reviewed your support ticket, and it has now been escalated to our R&D team for further investigation.
We will proceed with the next step based on their conclusion. In the meantime, we’ve also passed your request for a new core to the relevant team.
Please rest assured that we’re doing our best to resolve this for you as soon as possible.
yes i did i was not aware it even had a sim card until i saw it on here and people talking about it. then i went and looked at my replacement core and sure enough no sim card was in it.
I’m just asking for Yarbo to do the right thing. i have had issues with the replacement core from day one. i fully believe yarbo sent me a returned core with repairing it or without checking it out to see if every thing was operational. then because of the battery issue they put a offset on the temperature sensor to trick the core into thinking the battery was cool when it was not. i put a temp sensor inside the battery compartment and it’s reading 10 degrees hotter than the reading on the app. this is only going to cause the battery to fail.
if it’s reading 10 degrees hotter on the outside it just makes me wonder what the internal battery temp is?
Thank you for reaching out — we truly understand your concerns.
First, please rest assured that your case has been escalated to our R&D team for further investigation. We will get back to you as soon as we receive any updates from them. We absolutely recognize the importance of providing fair and proper service, and we’re committed to ensuring your concerns are addressed appropriately.
Regarding the battery temperature, we would like to clarify that we do not apply any offset to the battery sensor — the readings shown in the app reflect the actual temperature detected by the internal sensor. However, differences in readings can occur depending on the sensor placement and airflow conditions, especially when comparing with an external thermometer.
We sincerely appreciate your patience and thank you again for bringing this to our attention.
if the yarbo is reading the internal temp of the battery and i am reading the external temp of the battery then please explain to me how i am getting a higher temp on the case of the battery the the internal temp. this makes no sense what so ever. i am a engineer by trade and all my temp meters are certified. heat flows from hot to cold. this is basic physics. as i stated before this issue only showed up on the replacement core. i did not have this issue with my original core. it always ran between 38c and 45c at the most. i have seen temps as high as 62c with this core. So please help me understand this issue.