Accessing Webapp on T34 Chip with OpenBeken Firmware via Android Phone

Hello to all, and thanks to the people that help us to modificate this things. This is my first post, and although I have been reading a lot I can't find a way to get to the webapp from the device through my android phone. I have loaded the openbeken firmware without any problem on a T34 chip, and after that found the pins with the datasheet. I can control my smartplug. But I don't know how to get to the webapp page to be able to activate the drivers, or to make an autoexe.bat for example. I configure the webapp, but nothing happens, maybe I must to build a local net with a router ?

One note for those who need it: If you don't have a 3.3v TTL converter you can always make a voltage divider with two resistors (3k3 and 1k) for example and place it on the TX line that comes out of the converter and reaches the TX input of the chip, so the 5v TTL voltage is reduced to about 3v. I hope this idea is useful to more than one.
Thanks for reading and I hope someone who had the same problem as me can help me.

Pablo

Hm, are you able to access the device web page through a browser? You just need to connect to the device IP and it should load correctly...

For example:

How does it look for you? Or are you referring to some other issue with the page loading?

Or maybe... do you mean the Web Application, specifically? This page:

Well, Web App is an addon that is fetched from Github, so you need to have Internet Access in order for the Web App to work. Alternatively, you can host web app yourself in your local area network, for example by using Home Assistant for that. https://www.elektroda.com/rtvforum/topic3995065.html

The simplest way to get this working is to just to enter your WiFi information first, so OBK can pair with your local WiFi, and then access it via WiFi, when it's in WiFi client mode (not via OBK custom Access Point with default IP 192.168.4.1).

Thank you very much for answering and doing it so quickly. Thanks also to those who make all this work possible. In the end I have understood that to access the page on GitHub you have to program the WiFi network, IP and gateway on the device, in my case a plug. I do not have a WiFi network, I access it through the mobile phone but I can use it as a router to which other devices connect, for example the personal computer. In case someone is in this situation I explain the steps I followed to access the web page on GitHub. I understand that we already have the device flashed with the excellent instructions from Elektroda.
1- Connect the OpenBeken device.
2- Activate the router mode (shared network) on the mobile phone.
3- On the personal computer the two networks appear, the one from the mobile phone and the one from the OpenBeken plug.
4- We connect the laptop to the mobile phone network, and I write down the IP 192.168.221.20 and the gateway 192.168.221.1, for example.
5- We connect to the OpenBeken network (192.168.4.1), but we keep the mobile phone as a router because otherwise the DHCP would change the IP assignments.
6- Now when we connect to the OpenBeken device, we first configure the IP, it must have the last number different from the one we wrote down 192.168.221.10, for example, mask and gateway. Second, we configure the WiFi and web. At this point I think the device is already rebooting.
7- At this point the OpenBeken network has disappeared, we connect again to the shared network through the mobile phone and access the IP address that we put in the device in our example 192.168.221.10. If everything has gone well, the device screen appears and now when clicking on "launch web application" we can reach the web on GitHub.

These steps that I have described only work if we keep the mobile phone network shared, and once, since the phone assigns random addresses each time we activate it in router mode. But in my case it has helped me to program the autoexec.bat and load the latest update OTA. Many thanks again to the people who with their effort and time help us and expose their progress publicly. Pablo.

****If something goes wrong, you simply have to disconnect and reconnect the device five times in my case and the firmware enters safe mode resetting the IP to 192.168.4.1. You have to connect to the device and in the WiFi and web configuration select to make the network open, in this way the device creates its own OpenBeken network.****