@kl3m3n Hi Klemen,
That certainly fixed the problem - I went back to v2.0.17
I'm a bit long-in-the tooth and I'm not as switched on as I used to be. Thankfully I (we) have a wonderful mentor in yourself, and one who readily picks up the slack when people like me struggle. Thanks for your on-going support.
Cheers Steve

@kl3m3n G'day Klemen,
I'll try to provide as much info as I can,

My physical board is marked "ESP32_DEVKITC_V4"

The ESP32 by Espressif Systems v3.0.1 has been installed.

The "https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_index.json" had been set in preferences.

Unable to specifically find board "ESP32-WROOM-32" (as shown in the video tutorial) - the one that seems to fit closest is uPesy ESP32 Wroom Devkit. (I select com6).

Using this board, I can load TemperatureReader (Episode 1) from the tutorials, set up the network, MQTT in/out compile/run (without error) and run the GUIO on the tablet and everything works perfectly.

As indicated in my last post, I sourced the BasicMQTT code by copying the code snippet as well as downloading from the link in the tutorials just in case there was a code discrepancy

And yet I still get the error previously posted.

Where are the ledc* functions declared? I can't find any reference to them!

I'd appreciate any help as I'm keen to learn more about MQTT for a project I'm developing.
Cheers

I am trying to run the BasicMQTT example but get the following error.

/*****************************************
C:\Users\SteveV\Documents\ESP32_WROOM-Devkit\Projects\BasicMQTT\BasicMQTT.ino: In function 'void setup()':
C:\Users\SteveV\Documents\ESP32_WROOM-Devkit\Projects\BasicMQTT\BasicMQTT.ino:42:3: error: 'ledcSetup' was not declared in this scope
42 | ledcSetup(led::LED_CHANNEL, led::LED_FREQ, led::LED_BITS); // channel, freq, resolution_bits
| ^~~~~~~~~
C:\Users\SteveV\Documents\ESP32_WROOM-Devkit\Projects\BasicMQTT\BasicMQTT.ino:43:3: error: 'ledcAttachPin' was not declared in this scope; did you mean 'ledcAttach'?
43 | ledcAttachPin(led::LED_BUILTIN, led::LED_CHANNEL);
| ^~~~~~~~~~~~~
| ledcAttach

exit status 1

Compilation error: 'ledcSetup' was not declared in this scope
*******************************************/

I have reloaded the code from the web and from the code snippet - both give same error.

Where are the two functions in error supposed to reside?
Cheers

@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

@kl3m3n Hi Klemen,

Let me try to explain:-

1. Run GUI-O Live Designer on PC and entered PC IP and selected Port 50000
2. On ATMPC tablet:
   2a. Run GPI-O application
   2b. -> Add
   2c. -> Add new device
   2d. -> Select 'Ethernet'
   2e. -> Enter 'New"
   2f. -> Enter new device name and press return
   2g. Screen returns to that at 2f. with message showing
   'Invalid Input'

Neither the Device IP or Device Port can be selected (if attempted, screen returns to 2f. but doesn't have an 'Invalid Input' message)

So I'm at a loss on how to setup a device on the tablet that will make the connection with the PC (IP) running GUI-O Live Designer.

I had followed the same procedure with the Samsung tablet and a new device is able to be setup and it works with the Designer.

So the question is - how can I make the WiFi only tablet connect to the GUI-O Live Designer when I can't make a new device with an appropriate Name/IP/Port?

Cheers
Steve

G'day,
Not really a problem, but had me fooled for a while.

I was trying the create a new device (to access GUI-O Live Design) so selected
Ethernet in the 'Add new device'.
The page opened up and I selected 'New device'.
The next page asked for a Device name (and IP, Port etc), so after attempting to enter a name, the app reported 'Invalid input' and cleared the entry.
Tried several times with the same result.
Given that I had only recently reported a problem with the keyboard in a similar situation and a new release (1.0.73) fixed it, I was not sure if another keyboard issue had arisen.

As it turned out, there was no keyboard issue - the Android tablet I was using only has WiFi (now I find out!!) and therefore wouldn't setup an ethernet device (as you might expect).

Not sure if an app can detect if USB, Bluetooth or Ethernet is available (fitted), but if it can, maybe the 'Add new device' options could not shown functionality not available.

As I said before, not a real problem once you know the limitations of your Android device!!

Cheers
Steve

Hi,
I'm new to GUI-O and working my way through as many of the examples as I can in the limited time available.

I have successfully exercised the Live Design on the PC to control GUI app on a Samsung tablet via the ethernet mode. Works great!

I'm working on a project that I wish to make an Android tablet into a data entry terminal, and the Samsung would be suitable but an overkill.

I purchased a cheap Android tablet (ATMPC IT-1001A) that is marketed for kids - and has limited functionality, RAM etc but I think will be enough.

Unfortunately the ATMPC doesn't support ethernet, and I'm not able to design an app using the GUI-O Live Design with it.

It works great as an IOT device (with an ESP32-WROOMD WiFi module).

I'm not aware of the limitations, inabilities or complexities involved, but could WiFi connectivity be added to Live Design?

That would neat .......... !!

Cheers,
Steve

@SteveV Hi Klemen,

Now this is embarrassing!

I had completely missed the fact that I had used another device for trying GUI-O, and only picked up on it when I put all my devices on charge!.

So I checked that device (ATMPC IT-1001A) and lo and behold - GUI-O unlocked!

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

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

Cheers,
Steve

@kl3m3n Good evening,
Thank you for responding so quickly.

I'm really not sure what happened - but I think I was using my Google account sv88797@gmail.com.

Let me say, this was the first time I ever (reluctantly) purchased anything from Google (or anything outside Windows), and in order to purchase the GUI-O app, I had to go through the 'hoops' as everyone I suppose has to. That said, I was not happy with the options they required (credit card, PayPal, debit card) but I elected to use the debit card.
However, in the current Demo Mode, selecting 'purchase Pro' a dialog box is presented showing I can select PayPal!
I don't know why that should be the case - just interesting.

Anyway, I did both of the suggestions you made (several times and in reverse order as well) and to no avail.

What do you think the next step should be?
Cheers
Steve

Hi,
On May 8 (South Australian time zone) I paid to 'Unlocked pro) but it hasn't seemed to work.
When I load GUI-O application and go to settings, the 'Unlock-pro' still wants me to purchase to unlock.

I'm not sure how I did the actual purchase (doing too many things at once!!) - the only reference I have is that Google debited my account as follows:

Can you help?

I think the unit I was using at the time was my Samsung Galaxy Tab A (2016) Ser No R52J70778DA

Regards,
Steve