Hi @Paul-Koene, This is something we are working on. To wrap the irq into the edge file for the sysfs API of GPIO. You can take a look at what's already available here: https://github.com/OnionIoT/gpio-irq. You can already receive a hardware interrupt signal from the kernel, however we just have to wrap that into a better interface to make it accessible via PHP, Pythong, etc.
@Flint-Olsen, yeah, it will work every time for a given login setup. I meant that it would be very difficult to design an universal script that will be able to login to all the login screens out there.
Yes, you should be able to send POST request via curl. You will need to go into the HTML file of the setup screen to see what kind of information is passed to the router via the POST request. Then all you will need to do is to simulate that request, and you should be able to log in.
Hi @Fred-Blais, we agree, it's much easier to do the cross-compilation if we provide the SDK. But the problem with the SDK is that it's hard to predict what platform one is trying to compile the firmware on. We'll probably add some content to the tutorial to show how to setup the environment with the SDK. Also, we will be launching a cross-compilation service for you to upload packages to be compiled. Hopefully all of these will make it much easier for everyone who wants to create their own packages.
@Peter-Harrald Hi Peter, sorry for the late response. I was still trying to duplicate the problem and then you mentioned it was fixed. My best guess is that one of the apache configuration files wasn't setup properly. Re-installing the package is like the software version of "turning it off and on again", lol.
@Johannes-Zellner So there are a bunch of files under /etc/uci-defaults/ that's present on a new firmware image. When the devices starts up for the very first time, it will use these scripts to give name to it's AP based on MAC address, and do some other init setup. Once these scripts has been run once, they get deleted. I think your wifi configuration was written by these files. Perhaps we should build in a check to see if the device is flashed via a clean wipe or an upgrade procedure and determine which of the scripts should be run.
@Patrick-Nou I think the settings for uhttpd might be wrong. Can you try to do a factory reset of the Omega and see if it fixes the problem? First back up any files that you might have added to the Omega, and hold the reset button for around 30 seconds. Then release the button and wait for the Omega to reboot.