@Hub

I am happy you find the improvements useful!

Thanks.

Regards,
Klemen

@SteveV Hi!

You mean you cannot enter IP address due to not having any period ('.') character available?

This is not normal. Can you try changing the keyboard from Android settings and see if the issue persists?

I am "forcing" the number keyboard when user touches the IP field... In most cases, the keyboard also shows other characters. Anyway, I will fix this ASAP - I have a release lined up right now. I will probably take a day or two...

Best regards,
Klemen

@Bernard Yes, you have wrong credentials. This is what's causing the problem. You have changed the settings somehow...

I advise you to clear application data or uninstall and reinstall the application. This will reset the settings to default. Alternatively, you could input the correct settings, but I recommend reinstall... It will be easier for you. Then retry pairing.

Note that you must keep the default settings if you want to connect to GUI-O server!

Best regards,
kl3m3n

@somasundaram-i Hi!

Why is your image placed at X:80 Y:-20?

Try placing it in at X:50 and Y:50.

I will try to simulate your conditions (1280x720 resolution) and test this.

I will get back to you, meanwhile please try placing the image at the center. Also you can try using other scale modes and see what happens.

Best regards,
Kl3m3n

@Sato Hi,

try setting the RTCR parameter to a low value, e.g. 0.1. This should give you updates with an interval of 10 seconds, which should be enough for you to disable the RTC. You can even go lower, up to 100 seconds.

Note that when creating the RTC, it will give you the time immediately and then with a specified interval.

Regards,
Kl3m3n

@Sato Hi!

Yes, the localisation can be a problem.
I will fix the RTC so it will return the day of the week as a number.

@Sato said in command that returns the date and time and the day of the week:

No, it not works, the date is wrong 2025/37/13, the time is correct

Can you please provide the initialization for RTCF for this?

Thanks.

Best regards,
Kl3m3n

@Sato Yes, you were missing the '|' character.

BR,
Kl3m3n

@Sato No problem!

@Sato Hi!

You can do this in the following way:

Set the format to:

"yyyy-MM-dd hh:mm:ss dddd"

The dddd part should give the days:
Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday.

Create a lookup table to convert this into a number from 1 to 7.

P.S.: You can replace dddd with ddd, which will give you the short names for the days (e.g., Mon, Sun, ...).

Best regards,
Kl3m3n

@RudiP Hi!

Thanks for reporting the issue. To help diagnose the problem, could you please provide a minimal example where this happens? Specifically, I’d like to see the widget initialization code that triggers the problem.

Also, what is the make and model of your Android device? If it’s an older or lower-end device, the issue might be related to limited system resources like RAM or GPU memory. Initializing complex widgets with a lot of data can sometimes cause delays or rendering issues on such devices.

Lastly, does the app crash or freeze, or is the screen just black but still responsive to touches?

Best regards,
Kl3m3n

@Sato I am glad to hear that!

Best regards,
Kl3m3n

Hi!

Ok, I understand!

@Sato said in On close with > clear some flags:

If Guio loses its internet connection, after a short time the Esp restarts and all the flags are cleared.

How does the ESP know to restart if GUI-O loses connection?

@Sato Hi,

which connection type are you using?

If you are using MQTT, and you have a bad connection, the "exit" action could actually take longer and the app may seem unresponsive to the user. This is not a good solution.

What do you do if GUI-O suddenly losses internet connection? How do you clear the flags then?

Kl3m3n