This isn’t a magical secret but it can definitely be helpful if you’re trying to figure out how to do something not covered in the documentation. The docs on the Omega are still very scarce so if you’re trying to do something beyond getting started you probably won’t find it there. The docs and info on OpenWrt are aplenty so you’re much more likely to find help if you seek it out in those forums. Google is your friend on this one.
Again, not something that’s hidden but it’s also not super apparent if you are shopping on the website especially if you are a beginner. It’s important to know because that means you can’t just connect it to a breadboard and start prototyping with it. You will definitely need one of the available docks from their website. I recommend the Expansion Dock to get started.
There are multiple power options when working with the Omega but there are some things you need to be aware of so you don’t fry it. First of all the operating voltage of the Omega itself is 3.3V so it is NOT 5V tolerant. If you have a Battery Dock you can hook up a 1s LiPo as there is an onboard voltage regulator. The Expansion dock is a little different though. You can power the Omega via the micro USB port however a LiPo won’t work in this scenario. If you connect it to the 3.3V breakout pins you’ll potentially supply up to 4.2V on a full charge which could damage the Omega. That doesn’t mean you’re out of luck for battery power though. Two AA or AAA batteries supply 3V which I confirmed is sufficient to operate the Omega. You just connect the leads up to the 3.3V and GND pins that are on the header like this.
When you first set up the Omega it’ll have a name like OMEGA-1ACD which means to access it via the browser after setting it up you’ll use something like http://omega-1acd.local/ which is fine but can be hard to remember. Just rename it by going into the General Settings tab in the Settings app.
Out of the box the Omega is configured to act as an access point so that you can connect directly to it. This solves the classic chicken and egg problem with IoT devices. You need to give the device info to connect to your network but until it’s connected to your network you can’t connect to it without a hard connection. Access point mode solves this by allowing you to connect directly to the Omega and from there you can give it credentials to connect to your local network. However, if you don’t close the door behind you, you’ll end up with an Omega that can connect directly to your home network but still has wide open access via the access point mode. In the Settings app you can change the SSID and add credentials to the AP mode to solve this problem. I’d also recommend changing the default password.
I personally bought the Omega because it promised NodeJS support but quickly found out that it’s still not there. There are some posts in the forums where people have gotten NodeJS to run but it’s a very old version and there is no available documentation on how you’d use it to interact with hardware even if you did manage to get it setup. That said, the team is working like crazy with new hardware updates coming pretty much weekly. Filming a getting started tutorial has proved difficult because new things are being added so quickly.
From what I’ve seen so far I have no reason to suspect that the team won’t deliver on its promises and they are very active in the community forums. Just know that it’s not quite everything it’s billed to be on the marketing pages yet but appears to be getting there fast.
Have any questions about the Omega? I’d love to try to answer them for you and am feverishly trying to put together some µCasts to help you get started with it. Ask below in the comments and I’ll see if I can dig up the answer for you.