# Firmware Update Issues on Brand New Core - TICKET # 232825 **URL:** \ **Category:** Software Issues\ **Tags:** data-center, yarbo-app, firmware-update, core, yarbo-core\ **Created:** [August 20, 2026, 5:52am UTC](https://forum.yarbo.com/t/firmware-update-issues-on-brand-new-core-ticket-232825/7320 "2026-08-20T05:52:19Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![steves](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/steves/32/371_2.png) [@steves](https://forum.yarbo.com/u/steves)\ **Post date:** [August 20, 2026, 5:52am UTC](https://forum.yarbo.com/t/firmware-update-issues-on-brand-new-core-ticket-232825/7320/1 "2026-08-20T05:52:20Z")
I am posting here because I need some desperate assistance. I am a new Yarbo customer and this has been the most painful, ridiculous tech experience I have ever had. My brand-new Yarbo is currently a total paperweight, and the Field Service Engineering (FSE) / Senior Technical Team has completely gone radio silent on my ticket. I was promised an update within hours every time I chat with or call support but absolutely nothing happens. I receive absolutely no update. Here is my exact diagnostic history and network proof showing that my local setup is completely flawless, yet the machine is totally locked out of Yarbo’s cloud servers. **📋 The Ticket Timeline & History** - **Aug 12–13** : Received my brand-new Yarbo Core unit. (Note: I am running a bare Core chassis right now; my Lawn Mower Pro and Snow Blower modules have not arrived/shipped yet). Left the unit on the charger, online overnight for 12+ hours— **firmware update failed to trigger**. I wanted to get the DC and Docking Station setup and Core updated before my module arrived. - **Aug 14** : Support claimed the Core wasn’t on Wi-Fi. To be honest, I think I disconnected the core from my WIFI after the first couple of nights because I was getting nowhere. I pointed out that the Data Center was hardwired to my local network via PoE, and I could communicate with the unit remotely from 150 miles away. Support insisted the Core itself must be directly connected to a home 2.4/5GHz Wi-Fi network in addition to the Data Center / HaLow bridge for firmware updates. I completed this setup. - **Aug 15** : Confirmed the Core was successfully assigned a local IP address on my router via home Wi-Fi, cellular was enabled, sitting on the dock charging, and connected to HaLow/GPS. I could see \*some\* traffic flowing, both transmit and receive to the core, DC, and the core HaLow connection. Support stated they officially escalated the case to the **Senior Technical/FSE Team** to manually force-push the firmware package from the backend. - **Aug 16–19 (Current)**: Total radio silence from the senior team. Day 7 with zero progress. As of this morning, the situation became significantly worse. **I can no longer connect to my Yarbo remotely over Wi-Fi, HaLow, or Cellular**. The app throws a generic “Network issue / Offline” screen. If I walk right up to the machine, I can successfully connect locally via Bluetooth. When I pull up the local **Diagnose Tools** screen, it reveals a massive backend server failure: - **Data Center Status** : Confirmed **Connection Mode: 2** - **Radio Link** : HaLow is **True** with a highly stable, signal of **-60**. - **RTK GPS Link** : Status 4 with **23 locked satellites**. - **The Critical Failure Point** : Despite a flawless local network, the Core reads **MQTT Server: Disconnected** and **Ping: 0 ms**. My router cleanly shows all three components online: the Data Center, the Core’s internal Wi-Fi card, and the Core’s HaLow connection point. The MQTT Server is reading Disconnected. My home network is up and online, so the network is not the issue. In fact, I work for the ISP and know the network. **CPU, memory, and disk metrics are all at 0**. I can manually operate the Core from my phone via Bluetooth. When I reboot the Core, it boots up and says “Ready to Work.” I have tried everything and cannot make any progress with Support. I am on the verge of sending this paperweight back. Any insight? Please HELP! ---
**Author:** ![Yarbo-Forum](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/yarbo-forum/32/126_2.png) [@Yarbo-Forum](https://forum.yarbo.com/u/Yarbo-Forum)\ **Post date:** [August 20, 2026, 10:47am UTC](https://forum.yarbo.com/t/firmware-update-issues-on-brand-new-core-ticket-232825/7320/2 "2026-08-20T10:47:11Z")
Hi there, I’m really sorry for the inconvenience this has caused. I just checked your support ticket and saw an update from our support team about five hours ago confirming that the latest firmware has been pushed to your Yarbo. Based on our remote records, your Yarbo is now showing as connected normally. Could you please confirm whether you’re able to connect to and use it normally on your side now? Please rest assured that I’ll continue following up on your case until your Yarbo is working smoothly. ---
**Author:** ![steves](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/steves/32/371_2.png) [@steves](https://forum.yarbo.com/u/steves)\ **Post date:** [August 20, 2026, 1:30pm UTC](https://forum.yarbo.com/t/firmware-update-issues-on-brand-new-core-ticket-232825/7320/3 "2026-08-20T13:30:19Z")
Yes, All is good now. Thank you!