Hi @kl3m3n,

LB UID works now well, thanks

Best regards

Hi @kl3m3n,

I have so far been unable to reproduce or verify any pattern. What is certain is that now it doesn't happen as often as it did a few months ago.
Of course, I understand that it is not easy. Notifications being a strong feature, if you get better, maybe researching how WhatsApp restarts in case it gets frozen is already a step towards a solution.
I apologize for being a nag, but it's in a good way.

Best regards

@Bernard Hi Bernard!

Nice that you've solved the issue!

It would be very strange indeed if baud rate would affect the widgets responsiveness!

@Bernard said in Speed problems with Flick Area:

When switching from 9600 to 19200 baud, I also added "YASC:1" for the 2 graphs (SWEEP).

This is strange, sweep chart should support YASC parameter!
I will check this.

Regards,
kl3m3n

@Bernard Very nice!

Thank you for sharing!

BTW, was your wife happy with your answer? 🙂

Regards,
kl3m3n

Hi @kl3m3n,

Thanks, I really have to change my glasses

Regards

@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

Hello @kl3m3n,

Works very good, Thank You

Best regards

@somasundaram-i Your were missing the position. When you create a widget, the position is mandatory. Please check the manual.

Best regards,
Kl3m3n