administrators

@BitingChaos Yep, the Ethernet Expansion is compatible with both the original Omega and the Omega2.

See this FAQ post for info on the original Omega and its documentation.

@Alberto-Brosich Did you follow the documentation instructions to connect to a secure wireless network to set the client SSID and key?

I ask because wireless.client.ssid and wireless.client.key are set to the defaults.

@Alberto-Brosich The output of uci show wireless would be helpful as well!

Wanted to weigh in here - getting an Expansion Dock + Ethernet Expansion or an Evaluation Board will save you lots of time and headaches!

This was an oversight on my end. It went unnoticed because the p44 ledchain package is not part of our default firmware. So we never ran into the issue.

Resolution:
We've updated the image builder profiles in the OnionIoT/openwrt-imagebuilder-wrapper and OnionIoT/openwrt-packages (openwrt-23.05 branch) repos to include the new repo (http://repo.onioniot.com/omega2/packages/openwrt-23.05.3/core/).

Now firmware images that include the kmod-p44-ledchain package can be built out of the box.

Why was this an issue?

• The kmod-p44-ledchain package is no longer being built with the build system, so it's no longer available in the http://downloads.onioniot.com/releases/23.05.3/targets/ramips/mt76x8/packages/ package repo, as @DocHardinger noticed above
• Now, the OpenWRT SDK is being used to build the kmod-p44-ledchain package, this involved creating a new package repo
• The new package repo was included in the firmware and in the OpenWRT SDK wrapper configuration, but not the image builder configuration

See the relevant thread for more details

@DocHardinger said in 23.05.3 iwinfo scan disconnects AP:

It seems there has something changed inside the wifi driver? @Lazar-Demin

Yes, there have definitely been changes in the wifi driver between the 22.03 and 23.05 firmware releases:

• The 22.03.5 firmware uses the mt76 wifi driver with datecode 2022-09-06
  (https://github.com/openwrt/openwrt/blob/v22.03.5/package/kernel/mt76/Makefile#L11)

• While the 23.05.3 firmware uses mt76 wifi driver datecode 2023-09-11 (https://github.com/openwrt/openwrt/blob/v23.05.3/package/kernel/mt76/Makefile#L11)

We're not as up to date on the internal changes since the new beta firmware uses the open source mt76 driver.
But since it's open source, the good news is you can investigate this directly and open an issue if needed: https://github.com/openwrt/mt76

Yep, production is complete and the units are all set to be shipped out to Crowd Supply. Just ironing out the final details with the Crowd Supply fulfillment team.

@MK I agree with @crispyoz that rc.local is the lowest impact file.

To make it even more low impact, I would suggest adding a uci defaults file that changes rc.local instead of overwriting the default rc.local.

UCI defaults are generally used to pre-configure the UCI configuration (/etc/config) in your images. But we also use this mechanism to pre-configure other things, like the login banner for example: https://github.com/OnionIoT/OpenWRT-Packages/blob/openwrt-23.05/omega2-base/files/etc/uci-defaults/14_banner

More info on uci defaults here: https://openwrt.org/docs/guide-developer/uci-defaults

@Mark-C We've actually been working with our distributors to make the Omega2 LTE Global variant more accessible!

We're happy to report both Mouser and Digikey have reduced their minimum order quantity for the OM-O2LTE-G. Find the purchase links here: https://onion.io/buy?p=OM-O2LTE-G

@crispyoz DT overlay packages unfortunately won't work in vanilla 24.10

DT overlay depends on a few patches to the kernel that we add to the build system (See patches 251-253 at https://github.com/OnionIoT/openwrt-buildsystem-wrapper/tree/openwrt-23.05/onion/patches)