Posts made by mikeH

@Lazar-Demin
Thank you very much. That explains a lot. I am sorry I did not see the notice on this before. I now know how to avoid this in our factory without having to manually re-flash anything.

The following:
https://api.onioniot.com/firmware/omega2p/stable
is queried by the Omega to determine the latest "stable" version. The result is:
{
"version": "0.3.2",
"url": "http://repo.onioniot.com/omega2/images/omega2p-v0.3.2-b233.bin",
"build": 233,
"device": "omega2+",
"stable": true
}
Is there a reason why the latest stable is still reported as b233 when b257 is required by newer hardware?

Thanks, and regards,
Mike Hanson

I had three dozen O2P with this issue in our manufacturing facility. I recovered with this procedure:
https://github.com/OnionIoT/Onion-Docs/blob/master/Omega2/Documentation/Doing-Stuff/Advanced/Firmware-Flashing-Web-Recovery.md
I loaded b258 (the latest at this time 9/5/24). This worked.
If I re-install b233 (the latest "stable" build loaded by" oupgrade -force") the error returns. This is highly repeatable. Therefore, there is more to it than "factory partition messed up".

No, you're not the only one who stumbled across this. It's 5 years later, and the Omega still has issues joining and staying joined with, a network with apostrophe's in the SSID?

We are shipping 250 end items per year to paying customers - paying a lot, I might add. Anyone know of a solution that doesn't require a custom hack job into each product that has already been shipped? Anyone from Onion listening?

Cheers.

I also followed the guidance on this thread, and successfully created a mosquitto client in our pre-existing C++ application. Thank you very much for both the questions and the answers. I cannot express how useful this thread has been to me. Very unlikely I would have ever succeeded on my own.