I have a web server set up on my Omega2+ that acts as a user interface which is reachable by the omega-xxxx.local domain on Windows(with bonjour installed)/Mac/iOS when connected to the Omega2+'s WIFI Access Point.

As some of you may know, this does not seem to work for Android mobile browsers because, I assume from what I've read, Android doesn't use mDNS. It is still reachable by IP address, just not through the .local namespace.

Has anyone found a work around for this so that Omega can be reached by domain name instead of IP on android mobile devices through its browser?

Will the AP IP always be 192.168.3.1?

Could some kind of Omega2+ DNS trickery be used to force the android browser to resolve the (m)DNS?

Has anyone had any experience creating a custom wifi setup interface via omega webserver (php/html/js)

I have tried to find a way to create a link to the existing wifi setup that you use during the initial OnionOS configuration screen but haven't had much luck.

I am trying to create a wifi setup page that is styled the same as my existing web pages I have hosted on my omega2+

I know there is a command line interface but I would like a web based one that includes the ability to turn on/off network discovery as well as setup.

Anyone know of any existing code that has been written or a way to link to the existing OnionOS wifi setup page?

@Lazar-Demin

This is what I have in my rc.local file:

# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.
omega2-ctrl gpiomux set i2c gpio
gpioctl dirin 4
gpioctl dirin 5
gpioctl dirin 15
gpioctl dirin 16
gpioctl dirin 17
python /root/mdt/serialtest.py

exit 0

However, I am still unable to use A5 as an analog input and A4 as a digital input (which is what I am trying to achieve) on the arduino side as those pins seem to still be pulled up to 5VDC either through a resistor or from the TSX0108

@György-Farkas
So this doesn't do anything.... I'm pretty sure this script doesn't get called until you actually program the mcu... and I believe the pins get reset by the omega after the script runs.

I think the issue here is I'm holding my radio IC's Chip Select pin high (to communicate with it from the arduino) and at the same time the omega is also trying to use the bus, since these two are connected and since the omega uses the spi bus to communicate with flash memory there is really no way to turn it off, with the omega still remaining useful.

I could be wrong but from all the tests I've done this seems to be the case. It just seems odd that they would break these pins out when they are totally useless on the arduino side.

@György-Farkas thanks for the response... i will give that a try and report back.

@György-Farkas
I am also trying to use the SPI port on the arduino.... but alas it is also connected through the voltage converter.

Is there a trick (like maybe setting the Omega SPI port to gpio) that I can use so that the arduino's SPI port is usable????

As it stands now my Arduino SPI port works fine (Its hooked up to a lora radio) until the omega fully boots... then it seems all comms end from the arduino to the radio.

If I am also unable to use the arduino SPI port, I'm gonna smash this god damn thing with a hammer.

So looking at this post http://community.onion.io/topic/2500/arduino-dock-2-analog-read-issue it seems there is no way to fix this without cutting traces.

It sure would be useful to have a bit of a warning in the documentation that these pins are pretty much useless... something in a large red font detailing pins that can't be used would be nice.

Am I crazy or do the A5 and A4 pins not function as Digital inputs/outputs? Unless I have done something to wreck two boards... which is possible i guess. Any one have any info on this?

I have tried these pins on my Uno dock and they function as expected as Analog inputs, and Digital Inputs/Outputs with both INPUT and INPUT_PULLUP settings.

The documents say the dock functions exactly like an Uno, which is the same except for the mcu package.

EDIT:

So looking at the schematic it looks like it has to do with the Omega I2C connection through the TXS0108E level shifter chip. I have added to rc.local:
omega2-ctrl gpiomux set i2c gpio
But I am still unable to successfully pull the pin to ground through a 10k resistor... the pin stays at around 3.5V

Another way would be to make your startup script a "pre-startup script". Have the pre-startup script loop until the service was available, then call your actual startup script from within the pre-startup script.

I think you could use the shell ps command to get a list of all running processes (https://explainshell.com/explain/1/ps) and check for the one you want.

@György-Farkas Thanks again for replying! About the 3 seconds... it is desired and acceptable, having to hold the momentary switch down for 3 seconds to turn on/off the device ensures that it is not turned on or off accidentally. (This project is being run from a battery) I'm just a little annoyed that it takes LONGER than 3 seconds (10-13) to boot up the MCU.

I agree your suggestions would work, but I would like to avoid having to make hardware changes to the board... in case this project happens to be manufactured in any considerable number. (The arduino dock is mounted on a pcb, so I was kind of hoping there would be a hardware fix that I could make to MY pcb to fix this... without resorting to altering the Arduino Dock board)

I wonder if anything could be done in the Omegas boot code to pull pin 19 low sooner in the boot sequence or if is something that can't be avoided due to the Omegas internals.