@kl3m3n,

Thank you

Best regards

Hi @kl3m3n,

Not see it, thank you
In a few days i will test it and give feedback

Best regards

Hello @kl3m3n,

The read how many lines exists in the files is no problem.
Next week i will see how to handle it with FAC and FP

Thank you
Regards

@kl3m3n

Ok, thank you

Regards

Hi @kl3m3n,

If not possible, it's ok

The long name can be part of a street name or if to long it can be in short form.
With the name i can immediatly know where the connection is to.

Regards

@gašper-medved Based on some quick research, the DIP position are:

When programming:
USB UART connection with ESP8266 in programming mode (GPIO0-GND) - DIP 5 and 6 and 7 ON

When operating:
USB UART connection with ESP8266 - DIP 5 and 6 ON

Regards,
Kl3m3n

@cayon Hi,

the bug should be fixed in v1.0.64.

Best regards,
Klemen

Hello @kl3m3n,

Thanks for the tip

Regards

@wolerdbon Hi!

So, when you connect GUI-O app (client) to the ESP32 (server) a persistent connection is established. If the server closes the client connection, client will detect this and show an error. If autoconnect is enabled client will try to reconnect every 5 seconds...

When you just "kill" the server, the client is not disconnected properly and no "goodbye" message is sent. That is why nothing happens on the client side (there are ways to handle this, e.g., keep-alive as MQTT uses for example, but this is currently not implemented in Ethernet connection.

If you try the GUI-O design tool (and exit when the connection is established), you will notice that the client (GUI-O app) reacts immediately, because when the tool closes it implicitly disconnects the client.

I can suggest you use "home" button. So, when you reboot the ESP32, swipe GUI-O from the left side of the screen to the right to open the settings menu. Press the "home" button in the upper right corner.

Hope this helps.

Best regards,
Klemen

Hello @kl3m3n,

I've already answered in the other thread

Regards

@kl3m3n Excellent, I look forward to it!

Hi @kl3m3n,

I see, thank you

Regards

Hi!

Thanks, it works!

BR
A

Here is the new RFID access control screen.
https://i.imgur.com/8NE7gvC.png

Hello gammda!

Thank you for trying the GUI-O application. I hope you will find it useful for your use cases.

Regarding your question... The line's rotation point is located at the start of the line. Specifying the rotation of 37 degrees means that the rotation is performed CCW (counter clockwise). To perform the CW (clockwise rotation, set the value to -37 degrees).

In order to extend the line to the edge of the screen you need to use a little trigonometry trick to calculate the new length:

new_length = current_length / cos(37°) = 100 / cos(37°) = 125.2

So, your initialization must be modified to:

|BSL UID:bsl3 X:0 Y:50 ROT:37 LEN:125.2

NOTE THAT PARAMETER AND VALUE MUST NOT BE SPACE SEPARATED, e.g., ROT:37 works, while ROT: 37 does not!

Hope you do some interesting project with the GUI-O application. You can always share them in our Share your projects category.

Best regards,
kl3m3n

@sato Hello!

The final price depends on the country (due to VAT), but it is roughly 8€ for PRO license. You can check your local price here:

https://play.google.com/store/apps/details?id=com.guio.guioapp

This is the easisest way to purchase a single license.

Alternatively, for multiple licenses we offer different purchasing options (not via the Google Store).

I hope this answers your question.

Best regards.

Implemented in v0.11.4 (already available).

Added touch response to image and video widgets. Touching the image (video) widget now sends the message in the following format: @<uid>, where <uid> denotes the widget's unique identifier set by the UID: parameter.

Hello!

You mean like a boolean flag to enable / disable date time prepending to each line in a file. For example:

[date_time] text [date_time] text2 ...

when flag is enabled and

text text2 ...

when flag is disabled?

Can you confirm this?

Thanks.

Hello,

you can create both widgets with one invisible (or opacity set to 0):

VIS:0 or OPA:0

Then you delay on the microcontroller side and send the VIS:1 or OPA:1 command when the delay expires. This will then show the widget to the user.

Hope this helps.
Best regards.

@sato said in Timestamp through Gui-o MQTT server:

Hello,
If there is also a possibility, when connected to the Gui-O MQTT server, to be able to receive, whenever requested, the Timestamp, without the need to have a Gui-O APP open?

If so, how to do that?

Regards
Fernando

Hello Fernando.

The MQTT protocol by itself does not include a timestamp, so you would need to create the timestamp on the client side.
You could also have a reference device (could also be a PC) that publishes the timestamp to some topic. You can then subscribe to this topic on your microcontroller.

Best regards,
kl3m3n