Hi,

I found that the following code works as I expected. I want to share for your reference until official examples are provided.

Thanks,
Shigeru

Hi,

I want to publish examples for UIFlow using HTTP requests. I did as follows.

1. Create an example with the actual API key
2. Replace the key with API_KEY
3. Save as a .mf5 file
4. Open the .mf5 file with a text editor and check if the API key is not available in the saved file

I found that the variable for URL is replaced as I expected. However, the original URL containing the API key seems to be available in the http_request block.

How can I remove the key in UIFlow? Alternative ideas are removing it with a text editor or creating a utility tool, but I want to know if there is a way in UIFlow.

Thanks,
Shigeru

Hi,

I want to write a code to connect an AtomS3 Lite to a Wi-Fi access point. The following code works fine until I add the WLAN STA connect block.

However, once I added the block, I got an error as follows.

Traceback (most recent call last):
  File "<stdin>", line 40, in <module>
  File "<stdin>", line 18, in setup
OSError: Wifi Internal Error

It would be much appreciated if you could show me a way to specify a pair of SSID and PASSWORD.

Thanks,
Shigeru

Hi,

I found that the following code works as I expected. I want to share for your reference until official examples are provided.

Thanks,
Shigeru

Hi,

I found that the print block in the Text category works fine without configuring pins.

I overthought about this issue.

Thanks,
Shigeru

Re: Can't connect servers other than http://api.m5stack.com/v1 with UIFlow_Lite firmware versions after v.1.9.7

I confirmed that this issue is still reproducible with the latest version (i.e., v.1.12.6). Am I the only person who can reproduce this issue?

Hi,

I want to use the USB CDC port on AtomS3 (Lite) for serial debugging. It seems that there are no dedicated blocks for USB CDC in Alpha-26. Is it possible to use USB CDC with the UART blocks (e.g., Init UART 0 with or UART 0 setup) with a particular configuration?

Thank you very much in advance,
Shigeru

Hi,

I'm trying to implement an HTTP client on AtomS3 Lite with UIFlow 2.0. I have implemented on ATOM LITE with UIFlow 1.0 as follows:

https://github.com/kotobuki/Toolkit-for-Collaborative-XR/blob/main/examples/uiflow/update_attribute_atom.png

My questions are as follows:

• When should we use HTTP close, right after an HTTP request block or after handling a response?
• What is equivalent to Get Data in UIFlow 1.0, get content or get text?

It would be much appreciated if you give me advice regarding this topic.

Thank you very much in advance,
Shigeru

Update: I found the shadowed URL by removing a variable connected to the http_request block. At first, I directly specified the API key as a part of the URL, then replaced it with the variable.

Update: I confirmed that I can reproduce this issue with the latest version (i.e., v1.12.3). I also tried specifying the SSID and PASSWORD using a Network block but got no luck. Can anybody else reproduce this issue?

Hi,

I want to publish examples for UIFlow using HTTP requests. I did as follows.

1. Create an example with the actual API key
2. Replace the key with API_KEY
3. Save as a .mf5 file
4. Open the .mf5 file with a text editor and check if the API key is not available in the saved file

I found that the variable for URL is replaced as I expected. However, the original URL containing the API key seems to be available in the http_request block.

How can I remove the key in UIFlow? Alternative ideas are removing it with a text editor or creating a utility tool, but I want to know if there is a way in UIFlow.

Thanks,
Shigeru

Hi,

The following code works fine with the UIFlow_Lite firmware versions between v1.7.5 and v1.9.6.

https://gist.github.com/kotobuki/aab0a8b0e65e501c8a354198bdc4d969

However, the HTTP request fails with versions after v1.9.7, including v.12.2. If I change the URL to http://api.m5stack.com/v1, it also works fine with those versions. It seems that firmware versions after v1.9.7 only accept the URL for GET HTTP requests.

I'm sorry if this is a false alarm.

Best,
Shigeru