LUBA 3 1500 & LUBA mini 2 AWD 1000: firmware update check returns "No Data"

What happened

The app's firmware-update check returns "No Data" instead of connecting, even though the mower is otherwise online with a strong WiFi signal. The original report described a LUBA 3 1500 that had worked fine for a month, tested across three different networks (including a 2.4GHz-only one) and a second device, with reboots of both the mower and the phone — none of it resolved the "No Data" result¹.

The same specific symptom was independently reported by several other owners in the same thread, including one confirmed on a different model line (LUBA mini 2 AWD 1000, "Same issue no WIFI data!"), plus reports giving no clear model¹. One owner ruled out their own network as the cause by testing on a neighbor's WiFi and getting the same "No Data" result¹.

Workarounds reported

Temporarily disabling 4G — repeatedly confirmed

The most consistently effective workaround reported: open the connection-status page in the app (tap the Bluetooth/WiFi/4G icon), disable 4G, run the update over WiFi, then re-enable 4G afterward. Multiple owners independently confirmed this worked for them, including one who found the same tip on a different thread and verified it against their own unit¹.

One owner who used this fix also reported a side effect afterward: some app functions (including manual mowing) were temporarily missing from the app¹. Unconfirmed whether this is connected to the 4G-toggle process itself or a separate issue — unconfirmed.

Forgetting and reconnecting the WiFi network — reported, but does not work for everyone

A second workaround (forgetting the saved WiFi network in the app, then reconnecting) was suggested and tried by other owners in the same thread, but did not work for at least two of them who tried it¹. Worth trying, but don't expect it to be reliable.

What this isn't

• Not a local-network issue. The 4G-disable workaround's effectiveness, plus the neighbor's-WiFi test above, point at something in how the mower or app negotiates the update-check specifically over WiFi with 4G active — not a router, ISP, or Bluetooth pairing problem.
• Not (as far as reported) the same as the separate "forced update to a mismatched version" lockout documented on this site for other LUBA 2/3 owners, where the app blocks all actions until a specific firmware version installs. That symptom is the app actively demanding an update; this one is the update check itself failing to return anything.