Topics created by SteveV

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

@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

@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 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