My Omegas are now gathering dust. They can't connect to the 802.11n network.
How would I get a hint of what's not working?
My Omegas are now gathering dust. They can't connect to the 802.11n network.
How would I get a hint of what's not working?
Well, bad news, it broke again. After I rebooted the newly installed b162 running on the Ω2+, the orange light flashed slowly for a few seconds as if booting normally, then turned off. It didn't broadcast any SSID.
I then tried to put it on the small expansion board, same result.
Tried pressing the reset button while turning it on, same result, no light and no SSID.
What can I do now?
@Luciano-S. Actually I did contact the Onion team about the issue, they just acknowledged the problematic switch, but didn't offer an RMA. The switch is broken "away from the GPIO", i.e. OFF, and I can't move it back on. This Expansion Dock is essentially unusable until I replace the switch. I surely won't ask a professional to replace a 50cents part on a $15 board, that would cost me $50 at least (last time I asked for surface soldering service). This is a board to be tinkered with (somewhat), after all!
Indeed, I managed to get the latest, b159 version on a USB key (FAT32), and install it manually. After that, it finally connected to the router. The Onion team has some great ideas, but should really test their firmware before shipping!
For the record: I plugged the Ω2+ on the Battery Expansion Board, and didn't need the CP2102 standalone converter I had. Also, the USB key didn't mount automatically, but issuing command /etc/init.d/mountd restart mounted the key at /tmp/run/mountd/sda1, not /tmp/mounts (this directory doesn't exist)
Buggy firmware + outdated documentation…
Well, I did just that, attempting the upgrade from a previously downloaded image on a USB drive formatted in FAT32. I took the b157 version, the latest when I attempted to make the Ω2+ work.
However, I still can't make it connect to my router
I tried to create an unsecured, ad-hoc network on my computer for the Omega to connect to, but it also fails, and still doesn't give out any details.
What would be next?
@Ken-Conrad said in Omega2+ can't connect to wifi network during initial setup:
@Patrick-Nou You have the tools to update your Omega to working - the broken switch on the Expansion dock has been common problem, can you use a small needle to make it work?
Actually I already tried the needle, but ended up breaking the switch further, in the OFF position. I guess I will have to replace it, but the solder points are really tiny and I may well tear away the fragile printed circuit.
From the updated instructions, should I understand nor the serial connection or the Ethernet Expenasion aren't required anymore? I do have access to the SSH server, even if the Omega isn't set up yet.
What filesystem should the USB key be formetted in?
@Luciano-S. I read somewhere the Battery dock didn't feature a CP2102 chip.
However, I do have a regular Expansion Dock (for the Ω) whose power switch is broken.
I also have a standalone CP2102, Breadboard Dock.
The only missing information would be the full pinout of the Ethernet Expansion Board
Broken switch below:
@Luciano-S. Already tried regular USB charger that has no problem charging an iPad (notoriously power-hungry), already powered the Omega (non-2 version), the Raspberry Pi (also very sensitive to bad power quality).
I don't have another laptop handy, but a USB voltmeter shows it doesn't go lower than 4.75V, still within the 5% tolerance required.
The documentation pages don't state explicitly how to manually update the firmware; however, I found this old documentation page through a G search, and deducted this would be the correct path to fetch the latest image for the Ω2+: http://repo.onion.io/omega2/images/omega2p-v0.1.9-b157.bin
So the next step would be to
1- somehow put this image into the /tmp directory
Related problem: how do I perform a file transfer over SSH when SFTP is not available?
2- perform:
sysupgrade -n /tmp/omega-v0.1.9-b157.bin
Am I correct?
What are the chances of bricking the Ω?
Not sure how I should feel knowing that a device I waited for months can't even complete its own simple setup.
@Luciano-S. 1- Tried while connected to my laptop's USB port: FAILS.
2- None of those have any special character in them.
3- What old firmware? I can't update if I can't connect to the Internet, anyway.
aps command yields:
3 Zhone 22:02:71:XX:YY:ZZ WPA2PSK/AES 89 11b/g/n NONE In
And the last part of /etc/config/wireless shows:
config wifi-iface
option device 'ra0'
option network 'wlan'
option mode 'ap'
option encryption 'psk2'
option key '12345678'
option ApCliAuthMode 'WPA2PSK'
option ApCliEncrypType 'AES'
option ssid 'Omega-F835'
option ApCliSsid 'Zhone'
option ApCliPassWord 'Password'
option ApCliEnable '1'
I don't have a picture, but this is a rather short cable, 1m long approximately.
Any idea where the problem is? No other Wifi device have any issue, not even the current Omega (non 2) that are on the same network.
Hello there,
I am trying to get my new Omega2+ to connect to the Wifi network, but it fails for some reason. It is connected to a Battery Dock (without battery at the moment), has an Ethernet Expension sitting on it (no cable connected yet).
I first tried the GUI way, and it just reports being unable to connect to my WiFi router.
Then I tried to modify /etc/config/wireless, and I could see my router's SSID / password being there.
Also, it reports Ω-ware: 0.1.5 b130 on login through SSH, if that's any helpful.
But it fails to connect.
Any idea how to tackle this?
Similar problem here: my Omega 2+ can see my router, but refuses to connect. Doesn't give any error message, but the router doesn't register any connection attempt.
It's powered through a standard USB cell phone charger.
IdeaS?
An automatic router rebooter, but one that would use the relay expansion, not the big, fat relays also available.
Oh, and make it a full monitor, display average speed, data transferred, and last 5 pings on the OLED display. Sometimes routers fail by giving enormous ping, but don't disconnect.
@WereCatf Indeed turning it on every few hours was the classical way to deal with ice build-up for 10 to 15 min at a time, only. However, this is inefficient and to save electricity, modern fridges use adaptative defrost.
I don't have any data on the current sensors, they are just enclosed in white, unmarked tubes.
I thought about enlarging the openings, but I also understood air needs to be pulled through the maximum number of loops possible for proper cooling.
Hello there,
as I have this fridge whose parts are incredibly difficult to find, incompatible, etc, I thought about using an Onion Omega to replace the existing board whose specifications are frustratingly unknown, and where no manual is available.
Keeping the absorbing coil free of ice appears to be the most difficult part of the project: the air inlet at the bottom of the coils is tiny, and easily clogged by frost. As such, only 4 days of normal use are necessary to build enough ice the fan can't push enough cold air toward the fridge. (Conversely, when the coil is completely free of ice, it takes only 20 minutes of runtime to have it turn off for 25 to 45 minutes)
A still-unresolved question is: how does so-called "adaptative defrost" work?
Would such a project be feasible for someone who doesn't have a degree in refrigeration engineering or electronic engineering?
Is the Onion Omega the right platform for this project?
Existing inputs:
Temperature sensor in the freezer (likely broken, maybe reuse wiring?)
Temperature sensor in the fresh food section (likely analog)
Control panel inside to adjust temperature
Features would be:
Keep fresh food section at standard fridge temperature (4C or less)
Keep coil ice-free
Optional but nicer: make a LAN-accessible graph of compartment's temperature over time
In any case, just laying the idea here…
Hello there,
I have one Omega with a Mini dock. A while ago there was a power outage while it was plugged in, then the power was restored.
Now, the orange led flashes for ages, and the Omega is inaccessible through wifi. Power supply is a good Samsung cell phone charger.
How would I this random issue?
@Luciano-S. I am on the same IP range as the Omega, as are all other LAN-connected devices. However, SSH access works only when the computer is connected directly to the Omega, but not when both are connected to the same router.
As you point out, this may be on purpose, but annoying nevertheless. Shouldn't connections request from LAN be always trusted by default? How do I set the Omega for normal access through other LAN computers?
@Luciano-S. I don't really understand. The Omega is now connected to Internet on a common router (Though this router doesn't allow connections from the Internet to the Omega), and I try to connect using its DHCP-assigned IP address, just as I do in Firefox to reach the GUI.
I have no issues with SSH access from this computer to any other device.
The Omega still refuses the default password. Is user root allowed for SSH access?
Hello there,
I need to access the Omega from its command line, and since it's not connected to the Internet, I kept the default "onioneer" password. While it works from the GUI, the connection is refused from a standard Terminal on the host computer. Is this password different?
Also, I noticed the "-" character, as well as others accessible through "alt" key, are not passed to the Web-based Terminal. Is there a way to solve this bug?
thanks to all,
Hello there,
one question I had when trying, unsucessfully, to make a Mac OS X 10.11 Mac to talk to a CUPS-connected printer… Would I get better results by using a p910nd print server on the Omega?
How would I do that, as packages appear to be non-standard?
In fact I doubt the micro USB port would provide enough power. As this is a 3.5 inch hard drive, I thought it would be easier to use the existing 12V power supply, buck it to 5V to feed the Onion.
But no other option than FTP or SCP?
Hi there,
I got this 1TB USB 2 hard drive in a case that's rather roomy, enough for an Onion+Mini Dock. I just wondered if the Onion would have enough power to make it a decent networked drive. More specifically, would there be file sharing protocols packages available for it?
I know this isn't really IoT.