Pi Zero W is a loss leader. That part can someday disappear. I agree spec wise its better but Onion is much better when handling network tasks IMO. Dual WiFi, 5 Ethernet Ports, etc. It's also PCB board solderable. If the Pi Zero W was PCB board solderable I would of went with that part.
I am not sure if Micro Robotics could ship internationally but sure they can help you locate a local supplier. I ordered one from banggood.com in china but it hasn't been delivered yet after 3 months of waiting
Thank you for the suggestion with the power supply.
This morning I have tried a number of different power supply units (including the official rPi3 plug and cable) and this allowed me to get the device setup and SD card expanded as per the guides.
Issue now is the wifi looses connection to my home internet? The AP is still up but the 'second connection' to the router fails?
If it helps, I use apple airport router and a number of AP. The wifi failed on both router/ap AND also failed when tethering to my mobile phone wifi hotspot?
Now if I boot the device up with the ethernet expansion board connected (I use the expansion dock with my Omega2+) I can get network address/connectivity from my router/network. But again, remove the ethernet module and I am back to only having the ability to SSH/WebConsole via the Omega AP.
Could this be power related?, The Omega is using the latest firmware available from the Onion repos and flashed using the onion guides.
Thanks for the swift reply. Although it is a bit disappointing.
I am not that much worried about the display though. My major concern is that power management. I am wondering at the moment how this issue is being handled in a simple Amazon Kindle device? AFAIK it is Unix/Linux/Android based (not exactly sure) using 800MHz i.MX ARM processor and able to run for a whole month without recharging. Of course ever XX minutes it goes into deep sleep somehow. I will most probably continue the research with something like this, although the Omega was much more appealing with its 9$ price tag :)
Anyway ... thanks again for the reply and the involvement.
@peterh-peterh@peanut Here is the procedure on how to enable HTTPs for uhttpd and generate self-signed certificate.
From your command line issue the following commands:
opkg install px5g-standalone libustream-openssl
Restart the uhttpd service:
When you restart uhttpd service, it generates RSA private key and selfsigned certificate, here is the output that I've got after restarting uhttpd:
# /etc/init.d/uhttpd restart
4+0 records in
4+0 records out
Generating RSA private key, 2048 bit long modulus
Generating selfsigned certificate with subject 'C=ZZ,ST=Somewhere,L=Unknown,O=LEDEd1d8b179,CN=LEDE,' and validity 20180417162546-20200416162546
Now you can navigate to your browser and type: https://192.168.3.1 or https://omega-XXXX.local ( where XXXX are the last digits of your MAC address). Here is my screenshot: