@György-Farkas it was about 2h 30min, most of time it was idle. I consider to put there QI receiver coil for wireless charge. Actually the lack of hibernation or sleep mode could be potential problem in future.
@Maximilian-Gerhardt I agree on your idea for laying this out. USB for the disk, the built-in µSD card slot for the µSD card. Add some LEds, buttons, and/or expansion boards for a physical user interface if you want one.
USB 2.0 will be limited to ~60 megabytes per second, but that might be fast enough for many uses, like if you just want to leave the µSD card in this auto-backup-dock-thing whenever it's not in use. If you want more speed, it's probably time to use a more powerful device with USB 3.0 or native SATA. That might be an old laptop, or a faster single-board computer (some have USB 3.0).
As to software, I bet this will be possible using some combination of scripts or programs that do the actual sync, and something to start it when a new card is inserted, probably procd. For copying, I'd consider rsync, as I bet there's some combination of flags that will make sure that your data only gets copied off once, not multiple copies of the same data.
Assuming you want to delete the files off of the uSD card once they're copied, you could mount the µSD card once as "read-only", copy the data off, then remount it as "read-write" for just a few seconds to delete the files, then unmount. This is pretty safe, as you can safely yank the µSD card out at any point in time except during that time when it's mounted "read-write".
I ended up using my RPI 3 to run homebridge and used the script plugin to contact my omega2+.
The on script: ssh root@omega-ABCD.local "relay-exp 0 1"
The off script: ssh root@omega-ABCD.local "relay-exp 0 0"
Initially the delay was noticeable due to the new ssh connection every time but then I used the ControlMaster feature of OpenSSH, which opens a unix domain socket for the first connection and reuses this connection in all subsequent calls.
The achieve this you should place this in your ~/.ssh/config of the RPI 3 that will contact the omega2+:
# I chose to persist it for 5 days
It is now very responsive and I don't wast a full RPI to this single button
@Aurélien-Fi At the end of the day, the MT7688 chip in the Omega2 is really targeted in in a router, access point, or similar. It's good at connectivity (Wifi AP and client, ethernet), but not at things like cameras or displays.
The chip in a Raspberry Pi is the opposite - note that a Pi Zero doesn't have any way to connect Ethernet, but has HDMI, a camera interface, and USB device support.
My point here is that different processors have built-in hardware support that will make some things easier than others. The Pi Cameras are only so cheap because of the dedicated hardware in Pi.
So, this isn't something the Omega2 will be really great at doing. That said, there are ways. The main issue is one of bandwidth - I2C isn't that fast, so I'd look at SPI, UART, or especially USB. I think the Omega2S even breaks out PCIe, which opens lots of possibilities.
but it does not help (Lede is now installed and I also don't know, how to go back to omegaOS)
BusyBox v1.28.3 () built-in shell (ash)
/ /\ _ ___ ___ ___
/ LE / \ | | | | | |
/ DE / \ | || || |) | |
// LE \ |||/|| lede-project.org
\ \ DE /
\ LE \ / -----------------------------------------------------------
\ DE \ / Reboot (17.01-SNAPSHOT, r3497-033367e)
Device Firmware Version: 0.1.10 b160
Checking latest version online...
Repo Firmware Version: 0.2.0 b187
Comparing version numbers
New firmware version available, need to upgrade device firmware
Downloading new firmware ...
/usr/bin/oupgrade: local: line 377: not in a function