I Might Be Back .....
I'v actually been having really good luck with the Omega2. AP mode works well, STA mode works great. Accessing the Internet via wireless works well. Serial console works well. Setup went smoothly. Web UI is functional. Cloud access doesn't work yet. I'm not very knowledgeable of WRT so there are things I am used to in a typical Linux that are missing. But so far so good. I am supplying the device with ample power
In Omega2 Docs, under First Time Setup, Using Setup Wizard,
under the bold word Mandatory, showing 2nd picture. What did you put in? I could not find OnionWiFi in the drop down. All I could see was my router, and 2 or 3 other wireless routers in the area. This is an example of confusion.
WereCatf last edited by
@Don-DeGregori You were supposed to connect to your wireless network during that step. The OnionWiFi in the example is just that: an example of their wireless network.
So their wireless network is named OnionWiFi. Not very typical at all for the average first time user. I did however use my own SSID before, but then got in trouble down the line. Retracing my steps and entering what's happening in Notepad.
OK I think I got everything working so far again except Terminal, Editor, Cloud, and AP (I'm afraid of it!) Think I'll let the whole thing sit for a few days and just play with it. Shut it down, bring it and make sure it doesn't have a mind of it's own.
BTW, it's working on an open router right now. I guess it doesn't like my older Netgear router. It's WPA-TIRK. Would like to secure it again. Any ideas?
Right... we didn't realize connecting to our office OnionWiFi network would prove to be confusing!
We'll work to fix that!
Yesterday Omega was working pretty good. I had to open the wireless on the router. I brought it up from cold start at least 5 times. Fast and smooth. All settings remained the same Console opened no problem. Didn't install Editor, Terminal, or Cloud. Didn't enable AP. Not sure if I should. Well this morning I thought it would come up right away. It didn't. Here's the setup. Windows 10 PC. Has built in wireless, but connected by LAN to open router. Omega right beside it and connects to it. Turn on PC, And look at wireless connections. Then power up Omega. Blue LED on, in few seconds amber flashes, after minute amber solid. Now see Omega-(my ABCD) icon. Click on Connect. Never connects by itself. Why? In a few seconds It's connected. Then use Chrome and input 192.168.3.1 Console comes up, but had to do it twice? From then on it was a pain having to try this and that to make them appear. Like an old car warming up. Never any error messages. Me kind of bit-banging till Omega decided to fully wake up. From then it's OK, like yesterday. Who knows what problems I'll see if I close the router. So I leave it open.
I think people like me get trouble and don't know what to do and start fooling around. Soon Omega may become a brick. Omega2 + is not a no brainer to me yet. In a month, I'll fire it up again. Maybe the baby will be running by then.
Just put router into WPA-TIRK from None. Now not getting Omega to do it's thing like before with None. Can't do Firmware Update in Console. Wheel keeps spinning. What am supposed to have in Wi-Fi Access Point Setup in Console and should AP mode be enabled? This is when I have router in WPA-TIRK.
I think Omega2+ should be renamed Erratic2+. Every time I fired it up, I never know what to expect. I'm 79 and this experiment is the biggest time waster. My time is valuable. I'm done. I give Onion a month to fix 90% of the problems or I'm going to talk to Kickstarter or Indiegogo. Onion: You need to hire 100 good guys and get it done.
If you can turn off your wifi security and get the omega connected to the internet, I would recommend trying to do a manual firmware flash using the latest firmware update. It has cleared up a lot of the weird issues I was having. I did the firmware update, then a factory reset, and my unit has been working really well so far.
I get the frustration but just in the past two weeks the documentation has been greatly expanded, we're getting new firmware which is fixing issues, and the devs are getting more involved on the forums. It's a new unit, have patience! It's the nature of a kickstarter
@cusackph Thanks for being positive. I'll give your suggestion a go in a few days. I think one problem causes another. It's really frustrating to start the Console and see the gear turning and turning and nothing, And then I look with something else and then go back to Console, all of it comes up in a second. What could I have done to "fix" it? And I see the wireless connection just break with no apparent reason. And then I re-connect, but that doesn't do any good unless I start all over. And then I see something strange I never have seen before. And why does it quit with router encryption. And then all the info I filled out in the Console disappears. The AP Setup in the Console will show one thing and then another. The worst is not knowing the meaning of WHY this is happening. Like a big plot against me.
I totally get that. My suggestion is to just take things one step at a time. I'd say first, leave your wifi open and get the latest version of your firmware installed using the instructions I linked. Don't try to do it through the console, SSH in and do it that way.
After that, figure out why your unit won't connect to your wifi connection. I think I remember seeing that you were using TKIP for security, which may be the problem. Could you switch it to AES without any problems? Like, are there any devices you own that need TKIP? I use AES and have everything from my laptop to old Kindle connected with no problems.
Regarding the web console, it's definitely still a bit buggy. Try using Edge on your windows 10 box. I have an apple laptop and most things in the console don't work at all in Safari so I use Firefox.
What dock/expansions do you have?
I decided to write a step by step of what I see trying to bring up the Omera2+. The latest firmware is now used: 0.1.8(b145). Downloaded and installed via PuTTY, not the Console. Followed: Manual Firmware Installation in Omega2 Documentation.
Omega2+ and Power Dock Notes
Router not Secure, Open
- Switch off, power connected, charge LEDs flashing.
- Switch on, blue LED on, amber LED solid, then flashing.
- After minute amber LED solid.
- See Omega-9ED7 Secured, comes up very slow and not connected in PC tray.
- Finally click on Connect.
- Now see Omega-9ED7 Connected, secured.
- Open PuTTY, see Linux prompt, login root, password onioneer, Firmware says 0.1.8(b145)
- Open Chrome, 192.168.3.1.
- Console opens, but have to login. Sometimes entries are already filled in
- Click on Settings.
- See 192.168.0.103, my Wi-Fi network.
- Click on General Settings.
- See Omega Name Omega-9ED7 and my Timezone OK.
- Nothing in Security Settings.
- Click on Wi-Fi Settings.
- See NETGEAR 3 times, and 2 unknown icons with checkmarks. Enable Wi-Fi checked.
- Click on Wi-Fi AP Settings.
- See Omega-9ED7, WPA2, onioneer, 192.168.3.1 in correct locations.
- Didn't click Configure AP. Many times I see root in SSID location and onioneer in Password. I don think this is correct. I put in in Omega-9ED7 and 12345678.
- Click on Firmware Upgrade.
- Firmware says 0.1.8(b145), but Latest Firmware says 0.1.7(b139), No Upgrade required.
- Wi-Fi still connected as in Step 6. This would disconnect. Much better now.
- Did not try any Tools in Console.
- Did shutdown by closing Console and switching Omega off.
It seems there is a bad relationship between login and password not filled out automatically, root and other entries in Wi-Fi Access Point Setup incorrect, and Wi-Fi disconnecting. However, improved over 0.1.7(b139). Don't know results when router is returned to secure. I think timing between processes in the source code is part of many problems. Plus operator error.
Still having pretty good luck with Omega and Omega2+. Wireless needs to be tweaked a bit but it works great. I got Ethernet to work with just a few fiddles. I even put the Omega2+ and the GPS dongle into a window and eventually got solid GPS data from 13 satellites. GPIO seems broken with the current build. At least when following the examples. Granted being a computer and Linux and network guy helps with all of this. But it does work.
Making progress! A couple things:
- It's good that your PC doesn't automatically connect to the Omega2's access point. You don't want your PC switching network connections constantly every time you turn your unit on. Once you get your Omega set up on your home wifi network with security on, you really won't even need to worry about it. Which leads me to...
- Have you tried switching to AES encryption on your home network? If none of your devices need TKIP it'd probably be better to just set your router to AES. The Omega2 should work just fine then and I doubt any of your other devices will flinch. Again, only if you don't have anything that has to have TKIP. Once you get the Omega2 connected to your AES-security home wifi, you can SSH into it without having to connect your pc the Omega2's AP, so you won't even need to worry about #1 here.
- It sounds like Chrome may be saving some passwords in the wrong fields for you. This isn't an Omega2 problem; in Chrome under Settings, then Advanced settings, click 'Manage passwords' and remove anything saved that has to do with the Omega2, that should prevent it from filling passwords in on those fields you mentioned. Save the login for the Console again if you want to.
If I were you I'd worry about getting the wifi stuff sorted out. Once you have the Omega securely connected to your home wifi you can SSH in and take care of a ton of stuff via the CLI. The console still isn't working 100% for me either, but I can at least connect to my unit reliably 100% of the time now.
I just changed router to WPA2-AES. And I'll look at Chrome next. You're right, I might have said Yes to saving passwords. I hate that question in non-Linux OS's! cusackph, I'll get back, you have been most helpful. It would be great to just add the updates for a while and not to wonder what misery I'll have today! Thanks,
Well, no joy again. Changed router to WPA2 AES. Now amber won't stop flashing after it's solid on! Went back to Open. Still flashing! The same erratic condition of not seeing root or login starting Console, not seeing my local Wi-Fi IP from router, wrong stuff in looking at AP setup, and Omega-9ED7 disconnecting is still happening. What I noticed, even with amber always flashing, I can still use PuTTY to get into Linux. And can still get into Console. The correct condition I think is seeing root and onioneer when starting Console, seeing the IP 192.168.0.104 from router in Settings, correct I think of Omega-9ED7, WPA2, password of 123456768, and IP address of 192,168.3.1
Nothing has really changed for the better with the 01.18(b145) firmware. at least for me. Too bad fsck doesn't work in this brand of Linux. Maybe, it would help.
Back into the woodwork! Think I'll rebuild my XTAL SET.
Shoot! It looked like you were good to go.
The Omega's amber light should have nothing to do with your wifi security settings. If the rest of your devices are good with WPA2-AES, keep it that way. It's better no matter what
Try this: Unplug and replug the power to your Omega 2. Let the unit sit for ~10 minutes without doing anything just to be safe. Then, connect to its AP from your desktop and SSH in. Then let it sit for 10 minutes and run a command (ls is easy enough). what happens?
It's been a few hours, I can bring it up, no forever blinking. This has happened before. A couple of times I powered with a bench supply and saw current going from 200 ma to 0 and 2 seconds back to 200. This happened over and over. Let it sit for a while, it went to normal. Anyway, if I leave it on and not touch anything, it behaves. All the parameters have to be right. Now, router still open. PuTTY usually never fails.
Which one? I tried the 2nd so far. The 2 others are None and WEP. Think that's when continuous blinking started. I could try again. Can you tell me what you show on your various screens? Where you located? I'm in LA, USA
I put back WPA2-PSK[AES]. Did a cold re-start. Amber started blinking, but will not stop. Stumped!