@a-v

• App store is in private beta right now, and will be publicly available in the January II release of the console.
• Omega apps are divided into two parts, the front end is written in HTML5, and as @Stefan-Zucca mentioned, written in Polymer. The backend of the Omega can be written in whatever language we support, Python, PHP, etc. We currently write our backend in C/C++.
• There is an app in the console called onion-app-template that you can check out as an example. It is disabled by default, but you can change the icon setting in app.json.
• We have general guidelines to review apps before making them public for all the users. There will also be a rating system, so a bad rating for an app will signify poorly-made or even harmful apps.

Hope this answers your questions.

Hi @Austin-Kurpuis, I appreciate your directness in expressing your frustration. The reason that we haven't released Node.js for the Omega yet is not because we were lying about its existence. In fact, we have had version 0.10 of Node.js running on the Omega even before our Kickstarter campaign started (v0.12 has already been released then). So we are not claiming that we support it based on speculation that we will be able to get it to work. We claim that we support it because we have already gotten it to work. The reason that we did not release it because of the same reason that the Onion Cloud and the App Store for the Console are still in private beta. We didn't release it because we wanted to do better, we wanted to be able to get newer versions of Node.js working before we make it available for everyone. But as we've mentioned a few times on this forum, newer versions of v8 and node.js have very limited embedded systems support, especially for the MIPS architecture, and making it run on the Omega is no easy task.

All of us here at Onion have been working extremely hard, but we have underestimated the amount of work involved to get a product from concept to production, and to the hands of our users. As a result, we have not been able to deliver everything as quickly as we had hoped. I apologize for our oversight. This is our first campaign; we have learnt a lot from it; we'll know how to make more accurate predictions in the future.

@files_copying Ha! Posting our roadmap (for both software releases and tutorials) has been on the todo list as well! I'll make sure I have that online by tomorrow!

Hi @Owen-Melbourne, yes we will. We are focusing a lot of our efforts to create libraries for all of our expansions and writing wrappers for all the libraries. The wrappers we are focusing on right now are Python and Javascript, and we will be working on wrappers for PHP after that. Creating these libraries has taken a bit longer than we had anticipated as we are also tackling fulfillment at the same time. But we are committed to delivering every feature we have promised on our Kickstarter campaign, and we will continue to work extremely hard to have all of these features implemented as quickly as possible.

@Scott-Smith You are absolutely right! My mistake. I missed the left-most pin on the bottom row of pins on the Omega. This is the correct one:

Hi @Vyacheslav-Bachynskyi, sorry for the delayed reply. What we were imagining is something like this:

Please let me know what you think.

@Shamyl-Mansoor @Sawyer-McBride We're making a simple diagram to show you how to connect your mini dock to your OLED Expansion. We will post it in the next few hours.

Cheers!

@Tim-Smith We are still working on the wrapper for python and on a library to communicate with the Arduino Dock. Please stay tuned!

Hi Denis, API Cloud is on schedule to be released in the early December update of the Console.

Hi @chris-mccaslin, it seems that you have received an Omega that was flashed with the testing firmware. You can log into the Omega with the password 5up. Do you happen to have an ethernet expansion? You will need that to be able to restore the Omega to the default firmware.

Please let me know and I will show you how to restore the Omega.

I apologize for the inconveniences.

Hi @Jeff-Verive: That is what the Onion Cloud will eventually allow you to do. But for now you can do what's called a SSH reverse tunnel. To do this you will need to have a linux server somewhere. Then, just follow this tutorial to forward traffic going to your server to the Omega.

The tutorial can be found here: https://www.howtoforge.com/reverse-ssh-tunneling.

Let us know if you have any question!

Hi @Guest, the reason that three devices show up is because your drive is partitioned into 2 partitions. sda is the physical drive, sda1 and sda5 are two partitions within sda. When you are setting up the mounting procedure, you can choose to mount both sda1 or sda5 or one of them.

@Ates-Goral Unfortunately, we haven't gotten around to it yet...

Hi @Chris-McCaslin,

Can you open up the Console from Chrome, right click anywhere on the page and click on Inspect. A sidebar should show up. Then, on the top of that sidebar you should see a Tab called Console. Can you click on that and send me the screenshot?

Thanks!

Hi @Chris-McCaslin, just some simple syntax errors on the onion-rgbled.html. Here is a fixed version: https://gist.github.com/Bokenator/f2a53c480898d372a66aff7d75ebffc7

Hi @Juergen-Wissing, If you follow the steps on this page: https://wiki.onion.io/Tutorials/Cross-Compile, you can setup your own cross compile environment to compile the Omega firmware. There, you can customize the sub-components of busybox that you want to be included in the firmware. Under what circumstance is the loadkmap utility used? If it's something commonly used, we'll consider adding it to the firmware by default.

Cheers!

@T-NT Yup, that's what the U.FL connector looks like.

Hi @Ian-Carr, Does your Omega able to serve an access point? Can you connect to the Omega via serial terminal, and copy and paste the output on the terminal when you try to connect with the wifisetup command?

Thanks.

Hi @Kris-Hamilton, First of all, with regards to the Blynk accounts, I believe the Blynk team is performing some upgrades to their service this month, and as soon as the upgrades are done (their estimate is mid February), they will be releasing the Blynk accounts so that you can use Blynk to control boards such as the Arduino, Raspberry Pi, etc.

Second, integration with the Omega is still underway. It took much longer than expected because it seems that our GPIO library wasn't compatible with their program, so we are making a few changes to our GPIO library so that the Blynk app can make use of it to control the Omega.

Cheers!

Hi @Chad-Hadsell, The sound you are hearing is probably coming from the oscillator. A few people have reported this phenomenon, but so far it doesn't seem that it there's any side effect associated with it.

Cheers!