@kl3m3n

Thank you

Regards

@kl3m3n
Thank you. Now it works.😊

Screenshot_20240703_160215.png

@Sato I will update the example, so it is compatible with the new esp32 version.

@Sato No problem.

Best regards,
Kl3m3n

@Gemini-cricket-0 said in Help on pairing mqtt for esp8266:

@kl3m3n Hello

Thanks a lot for your help, I will try following your advice as soon as I have some time. Have a great day.

Best regards

If you have any issues, please let me know.

Regards,
Kl3m3n

@kl3m3n Hi,
Thanks for reviewing my issue.
I have resigned to the fact that the cheapy ATMPC is probably not going to work with the 'ethernet' connection, and have taken on your suggestion to do the development on the Samsung and use the initialisation strings on the ATMPC.

I tried a test UI created on the Samsung using the GUI-O Live Designer, copied the initialisation strings into modified ESP32 code, created a new IoT device on the ATMPC and - Bingo! - worked a treat.

Thanks very much
Cheers
Steve

@SteveV Hi.

Did you enter only the name or did you also specify the IP and port. All parameters must be specified...

If the tablet has WiFi, you can connect via "Ethernet". Please see my other answer here:
https://forum.gui-o.com/topic/198/could-the-gui-o-designer-be-made-to-work-with-wifi/2

True, "Ethernet" is usual terminology for internal wired connections. But in this case "Ethernet" means internal wireless connections. I think other (more technical) terminologies would be even more confusing for the user.

Best regards,
Klemen

@SteveV said in Purchased Pro but hasn't activated:

I unreservedly apologise for my mistake and sorry to have bothered you and wasted your precious time.

No problem 🙂

@SteveV said in Purchased Pro but hasn't activated:

Would you please advise what the license entails - how is it applied?

Please check the DEMO and PRO difference here:
https://www.gui-o.com/home#h.udqy5odkk9

Best regards,
Klemen

@kl3m3n
The new release (1.0.73) fixed the problem with the wrong? keyboard on my Samsung tablet.
I was then able to connect to GUI-O Live Design, and downloaded the TemperatureReader.gdp. All appears to work, although I am struggling to do anything different with the Designer in these early stage
Good job - thanks.
Cheers
Steve

@SteveV

No problem! Thanks for the feedback 🙂

If you have any more issues, feel free to ask!

Best regards,
Klemen

Hi @kl3m3n,

I see, thank you

Regards

Hello @kl3m3n,

You are right, tested it now with two Esp32 and it works.

Thanks
Regards

@tgpa123 I understand.

In my opinion, this is not a very transparent user feature - updating field from another source, while user is typing in the same field.

I will put this on hold for now. If there should be a need for this feature in the future, I will consider it again.

Best regards,
Klemen

@Hub said in Selectable language:

Hello @kl3m3n,

I can help with translation into Polish.

Regards,
Hubert

Thanks! 🙂
First, I need to prepare some stuff for this feature. I will let you know.

@Hub Hi!

What about using |TI (text input) widget? I can probably add some validators to ensure the entered text is HEX.

Regards,
Klemen

@tgpa123 Hi.

I tested this on my device with ESP32 and can send longer data than 20 bytes. It seems that the server and client negotiate a larger MTU value in my case.

Nevertheless, I can chunk the data so that there is never more than 20 bytes by default. So, for messages greater than 20 bytes, multiple packets will be sent. Of course, the last packet will still be terminated with CRLF.

Regards,
Klemen

@kl3m3n Excellent, I look forward to it!