I got the Onion Omega2 Pro last month. I like it because:

• The CPU is MIPS architecture, allowing me to gain some experience with this unfamiliar architecture.
• It has 8GB eMMC storage, giving me plenty of space to install packages.
• It has LiPo battery port, USB host port, and pin headers with SPI and I2C, leaving possibility of building battery-powered IoT projects.

However, I'm unhappy with OnionOS. Apart from GUI differences, it uses a custom WiFi driver wifi-warp-core that has several flaws. Most notably, my WiFi SSID is + (a plus sign), and the Onion would not connect to it. I want to replace OnionOS with a standard OpenWrt installation!

I figured out how to do that, and wrote up a guide in case others have the same need:
https://yoursunny.com/t/2019/omega2pro-openwrt/

The outcome would be an Omega2 Pro with normal OpenWrt 18.06 WiFi driver complete with Luci user interface, installed to the 8GB eMMC storage.

@Modest-Polykarpovich said in [GUIDE] Install OpenWrt 18.06 on Onion Omega2 Pro:

I don't see real feature to change OnionOS, I hoped to see OpenWRT 19.07.

The main reason I changed to OpenWrt is that the Onion WiFi firmware is unable to connect to my upstream WiFi, because its SSID is + (a plus sign).

I am now running OpenWrt 19.07 on my unit. The installation procedure is the same.
However, it's no longer possible to install any Onion specific software on 19.07. I want that battery indicator!

Device won't break so easily. The worst case is needing an online firmware flashing. Don't worry.

@davidsi said in lack of understanding, physical space vs logical space:

Mounting the sd card at /mnt will give me lots of space under /mnt but I do not know how to make that give me enough space across the file system mapped to

You need to setup extroot, so that you can install more software.
Official guide here: https://openwrt.org/docs/guide-user/additional-software/extroot_configuration

I got the Onion Omega2 Pro last month. I like it because:

• The CPU is MIPS architecture, allowing me to gain some experience with this unfamiliar architecture.
• It has 8GB eMMC storage, giving me plenty of space to install packages.
• It has LiPo battery port, USB host port, and pin headers with SPI and I2C, leaving possibility of building battery-powered IoT projects.

However, I'm unhappy with OnionOS. Apart from GUI differences, it uses a custom WiFi driver wifi-warp-core that has several flaws. Most notably, my WiFi SSID is + (a plus sign), and the Onion would not connect to it. I want to replace OnionOS with a standard OpenWrt installation!

I figured out how to do that, and wrote up a guide in case others have the same need:
https://yoursunny.com/t/2019/omega2pro-openwrt/

The outcome would be an Omega2 Pro with normal OpenWrt 18.06 WiFi driver complete with Luci user interface, installed to the 8GB eMMC storage.

@Enrico-Trevisanello said in Omega2 and LUCI:

I was connecting to the Omega through the IP address of the ethernet wan network interface and not the br-wlan 'access point' interface. Is there a way to get LUCI working on that one?

It should be possible by adjusting firewall port forwarding settings.
Another way is tunneling HTTP over SSH: https://openwrt.org/docs/guide-user/luci/luci.secure

@Enrico-Trevisanello said in Omega2 and LUCI:

Still, after reboot, I cannot connect to Luci at the Omega's IP address but I get forwarded to 'IP_addres_omega/OnionOS'. Any suggestion on how to proceed?

This is caused by browser caching of http://192.168.3.1/ URI. You can either clear browser cache, or navigate to http://192.168.3.1/cgi-bin/luci/ directly.

I reflashed my device with standard OpenWrt 18.06 and it works great.
Procedure and experience on my blog:
https://yoursunny.com/t/2019/omega2pro-openwrt/

@Michael-Lynch

opkg remove onion-os
opkg install luci

My house WiFi is named + (a plus sign) because I like short, non-identifying names. However, it seems impossible to associate with this WiFi from the Omega2pro as STA.
While wifisetup could scan and find this WiFi, association never happens, as observed from AP side.
I tried to create another AP with a boring name that consists of letters only, and it works.

I suspect there are some bugs in the warp-core package.
Is there any way to get rid of so-called "enhanced warp-core" and use a normal wireless driver?