I put it in /etc/development under the impression that it wouldn't be erased, which was not the case.
Fortunatelly it was only some simple nodejs scripts to test the Omega features.
Thanks for the tip about /etc/sysupgrade.conf, I'll try this one.
I'll try to answer your questions, let's see if it helps!
the Omega is a very small computer, but just like your desktop/laptop it has a wi-fi connection. This means it can communicate (and others can communicate with it) through a local network (your home wi-fi) or even through the internet. One difference is that you can pair the Omega with the expansion dock and then also use it to interact with hardware (temperature sensors, infrared sensors, you name it!).
Yes, there are numerous ways you could approach this. You could have a mobile app on your phone with a geofence setup around your house, then everytime you enter the geofence the mobile app could communicate with the Omega via 3G/4G and the Omega would turn on the AC. Another alternative is using the Omega with the Bluetooth (BLE) expansion, this way the Omega could detect the presence of your smartphone and also turn on the AC. One important point is that your AC needs to provide some way to be turned on, easiest one would of course be via wi-fi. Other than that you would probably need an infrared blaster connected to the Omega so it can simulate the AC remote control.
I don't know how Zwave and Zigbee work but you could probably have some kind of antenna (or sensor) connected to the Onion that can pickup their signal and then you could do whatever you want with it from the Omega.
I don't know how much experience you have with this kind of stuff but one thing to have in mind is that none of this will be super easy . It will demand some knowledge of electronics and software development, but the internet is full of tutorials and examples!
@Rudy-Trujillo I haven't tried this, but i think theoretically if you solder a bi-directional antenna on the Omega, you just need to make sure that the Omega is placed between your router and the target, and that the three things form a straight line. Not sure what it would be like if you were to put an uni-directional antenna on the Omega. Perhaps if you point the antenna away from the router, but if you place the Omega close enough to your router, it'll still be able to pick up the signal, in which case you can aim the uni-directional antenna at the object you are trying to range-extend to, and it might work.
WinSCP is great but I am on a mac and tired to use Bootcamp (to boot windows)
So I use Wine https://www.winehq.org/
Not realy fancy
So I try Interarchy https://nolobe.com/interarchy/
Worked great on my old openWrt Piratebox.
Here is not, I try to connect with (doesnt work)
If some body here have a mac....
Yes, I should go to linux.
@Enrico-Bermudez I had a similar problem after installing a cross-compiled image.
The way I got my Omega back to the standard image was as follows:
Downloaded the file omega-v0.0.5-b259.bin from http://repo.onion.io/omega/images/
Copied omega-v0.0.5-b259.bin to /tmp directory on my Omega
On the Omega, cd to /tmp
Run the command: sysupgrade omega-v0.0.5-b259.bin
This should have you back to a standard 0.0.5-b259 version of the Omega code image.
@Onion-Rings The firewall is currently configured to route traffic back and forth between the AP and the home wifi. To allow forwarding of packets between ethernet and AP, you first need to create a new network under /etc/config/network by adding the following block:
config interface 'wan'
option ifname 'eth0'
option proto 'dhcp'
option hostname 'OnionOmega'
Then, you will need to go into /etc/config/firewall and add the wan interface (which you have just created) into a firewall zone named wan.
Simplying add `list network 'wan' to the following block:
option name wan
list network 'wwan'
#list network 'wan6'
option input ACCEPT
option output ACCEPT
option forward REJECT
option masq 1
option mtu_fix 1
Finally, you need to restart your network and your firewall with the following commands:
Then your router should be able to route packets between eth0 and AP.
The way you disable AP through commandline is by using the following command (assuming your AP network is interface number 0):
uci set wireless.@wifi-iface.disabled=1 ; uci commit ; wifi
And to enable it again, you run:
uci set wireless.@wifi-iface.disabled=0 ; uci commit ; wifi
Hi Harshad, your BLE as part of your Kickstarter reward should have been shipped out already. Please open a support ticket here and we will look into this further: https://onion.freshdesk.com