I designed this case so I could wall mount my Omega Dash. The case is in two parts that clip together using snaps. I designed this using the Dash Beta device and the LCD moved around a bit so some adjustment to the LCD recess may be required, I'll update it once I receive my production devices.

Here is a photo of the rough 3D printed version, it needs finishing and I am a terrible photographer.

This is printed on a FlashForge Guider2S using PLA filament, the extruder is set to 220 degrees, the bed is heated to 20 degrees and I use a glue stick for adhesion. I print the top plate face down so there is no need for supports, no brim and no raft.

STL files are here: https://github.com/crispyoz/Omega-Dash-Casing.git

@DumTux The process is:

git clone https://github.com/OnionIoT/omega2-bootloader/
cd omega2-bootloader
./setup_env.sh
chmod +x build.sh
./build.sh

This produces 2 files:

uboot-omega2-<date>.bin
uboot-omega2p-<date>.bin

The latter is the Omega2+ uboot

I've posted the details of my wall mount in Projects.

https://community.onion.io/topic/4173/3d-printed-wall-mount-case-for-omega-dash

I don't work for Onion but if I did, I'd have as many complaints about the cost as I would have about why there was only features. In the end you just have to make a decision as to what is the best combination of features and price, or you will never release anything. The market then responds and you adjust your design or you offer new models.

As a Beta tester, memory was not my issue, LittleVGL is not perfect but I looked at so many other potential GUI candidates for my specific requirements and in the end I came to the same conclusion as Lazar and Zheng. LittleVGL is a great fit for the Omega2 and if you need more, you can always build a custom board or an expansion board. The underlying technology is solid.

I was lucky enough to join the Beta for this product. It's a great device, the GUI LittleVGL takes a little effort to understand but it's pretty full featured and works well. It's got an Omega2S+ under the hood so if you're familiar with Omega2 it's easy to get started.

Love it!

@supczinskib Intelligent watering systems are not a new idea, but any exiting idea can always be improved so I am interested to see what you come up with.

I currently have a home automation system installed in my apartment and a very large garden (image attached ) which I integrated with my home automation system so I've been tweaking this for about 7 years now. I do see a potential flaw in your "Automatic" system. Watering plants is more than just weather, it is about soil moisture and soil moisture is impacted by numerous factors, including the type of soil, ground coverage and obstructions. For a very basic garden maybe this idea would work, but a garden of any complexity will require reading soil moisture otherwise you'll end up over watering or under watering. Different plants require different moisture levels to survive so I ended up using moisture sensors in order to allow my system be able to understand the moisture content of the various areas of the garden and any specific plants that need special attention.

@MK When I switched from OpenWrt 18 to 22 is was quite smooth, but it depends on what functionality you are using. Initially the network setup was a pain, then changing MUX setting of a couple of pins was an issue. Then an issue with ledchain, then an issue requiring conversion of sqlite3 db. Mostly these were easily resolved so now I run 23 on my devices without issue. Also initially I started experimenting with OWRT 19, jumped to 22 then went into production on 23.

@MK thanks, yes I saw your time clock gizmo, nice piece of kit. Congratulations.

@Lazar-Demin The reason why I think a PoE version would be useful is as @MK mentioned, getting power to devices is often a pain, I think especially in a development of IoT devices I want to test devices in various locations and honestly I prefer to cable my stuff for reliability as WiFi is not often reliable in some locations. Especially when I'm fixing things to walls or up in the ceiling of a building where cables, metal and fluorescent lights may be found. Getting an ethernet cable to some of these locations can be a challenge, but getting power there as well can get really complicated and expensive.

I also think a solid reference implementation for use with Omega2S+ would be a bonus, or even better with the Omega3S+

While perusing the source today I noticed there have some recent additions to the uboot code referencing Omega3.

"Onion Omega3 IoT computer. Has a MT7688 SoC with 128 MiB of DDR2
RAM, 2 MiB of SPI-NOR and 256 MiB of SPI-NAND flash."

Is it so?? @Lazar-Demin

@baby-Onioneer Since the Omega2 devices utilise OpenWrt and u-boot, the question really is for the OpenWrt team. I watch the OpenWrt developer lists and there has been a lot of discussion on this topic over the years and they seem to always come back to the same point. If you need to rescue a device you need to be able to access the console for safe mode or reflashing using the u-boot tools. Once you're in safe mode it is possible to mount the overlay file system. Locking that down would hinder recovery.

Even if you locked down the console, anyone who gains physical access doesn't even need the console, you can simply remove the cover and access the flash directly. So now you have to look at an encrypted file system, but that presents range of issues.

The approach I take is to not keep any sensitive data on the device for any period of time. I also use some logic to determine if the device has been tampered with, or too many failed logins. If any of these checks fail then any sensitive data or configurations will be purged. I have an override mechanism for this process. None of this prevents a determined user from access the flash directly and perhaps getting some sensitive stuff, but in my experience hackers try a few other things before resorting to wiring up the flash and by that time anything sensitive has been purged.

I had an issue where my device would reboot after a couple of weeks, sometimes longer sometimes less but on average it was about 2 weeks. But as it was rebooting it was hanging, so effectively it would fail and never come back up.

This drove me mad for 2 or 3 months but eventually I managed to work it out. I was powering my O2+ via USB so I plugged in a USB power monitor and found that the device was crashing and as the boot sequence brought up the WiFi it would hang. We know that loading the WiFi service increases load while it scans for an AP so this was not unexpected. Eventually I worked out that the WiFi connection was dropping out during normal operation due interference to the AP, typically that was not an issue because the O2+ would automatically reconnect so it would go unnoticed. However when when the O2+ was working hard processing a stream of data from an SPI data source and at the same time the AP disconnected, the O2+ would crash. As it came back up and loaded the WiFi stuff it would then hang.

We did a few things to fix the issue. 1) Move the AP, it was close to a fluorescent light and when it blinked the AP would glitch; 2) Replaced the power supply of the o2+ with higher wattage.

That fixed the issue but didn't fully explain it, but we were busy with other things so I was happy My guess is that it was a load issue, restarting wifi while processing data required more juice than was available so the device would crash. Then when it was rebooting it was running out of juice starting WiFi because it was already loading another module that was consuming a lot of juice connecting to a sensor that was left in an undefined state due to the initial crash.

The moral of the story is ... don't be stingy with your power supply

How did we monitor the $22 USB power monitor? We took an old laptop, pointed its camera at the USB monitor so we had a video of the display, since the laptop was old it had only about 128GB of SSD so video was on a loop of about an hour. Then we had a bash script that pinged the O2+ every minute and if ping failed it sent me an email and stopped the camera so we didn't overwrite the video. A bit like gaffa tape and bits of string but it was what we had to work with at the time

Thanks @Zheng-Han that gives us clarity. Excited about the Omega3 !

@DocHardinger No response to my email so far. As an open source product they can just walk away. I don't know that they have, but they can.

@javadesigner You have there an Omega2Pro, this device uses the Omega2S+ SoC on a board that also incorporates additional 8K storage LiPO etc.

The LED behaviour you report is a known behaviour of this device, you need to update u-boot to version 1.1.3 or above. Here is the documentation on how to do this.

@matiaslao I don't know that the dissolution impacts on 2028 availability, perhaps it's just a reorganisation. I want clarity myself as it impacts my own planning. This is why I think @Zheng-Han needs to provide some form of statement.

Availability may just mean that if someone orders 500 units then they'll do a production run, I have no idea.

As my current work is on hold it's pushed my own planning out by about a year, so this is a concern for me. I think the uncertainty could be a killer.

I'll email Zheng directly and see what response I receive.

@DocHardinger The build system wrapper can build OWRT 24 including p44-ledchain. Some months ago (April) I merged some of the Onion patches from OWRT 23 into my 24 build and ended up with a working 24 system. I recall I was working on migrating some patches related to the DTS overlays as I want to use the SPI overlay stuff.

@matiaslao Unfortunately I'm voice typing this right now due to lack of hands otherwise I certainly would. I don't work for Onion just use their products in my products. @Zheng-Han (CEO) hasn't been online since July and @Lazar-Demin is no longer with Onion. Interestingly I note Onion Corporation was dissolved 30th April 2025.

Since this is an opensource product they have no requirement to support the product, but I think it would be nice if @Zheng-Han provided some sort of statement to users especially in light of the statement that Omega2 is going to be available until 2028

Perhaps another member can test, @luz may be able to assist.

@matiaslao Unfortunately I can't test myself due to lack of hands, one of the Onion guys will need to. @Lazar-Demin77 is no longer with Onion so I guess it is up to @Zheng-Han

@DocHardinger 24.10 do work on Omega2 it will depend on what specific packaged you need. p44-ledchain works on 24.10, I made a patch @luz has merged.

@matiaslao Apologies, I currently am recovering from 2 broken wrists so I'm a bit slow. My guess is that you're getting bitten by an addressing mismatch so the flash is in 4 byte mode when the cpu is booting in 3 byte mode.

Have a look at the docs related to special pins here it explains requirements for HW_RST_N