Hi Brendan, Did you by any chance change the return type of the macro? If I recall correctly I had some issues when I did that recently. I had to recreate the macro with the correct type and copy the code to that new macro to resolve that. (Reloading the project and even restarting Flowcode didn’t s...

There are known compatibility issues between Python 3.11 and 3.12, perhaps you can try 3.11?

Create an empty sting of sufficient length, loop over the array and add the output of NumberToHex$ to the end with whatever needs to separate the hex numbers if there is another element in the array.

You need to keep in mind Flowcode does not set your clock settings for you. The clock speed you provide is only used to calculate delays etc. To set the clock speed you need to add a C code block to your flowchart. Did you do so?

For TTN you need LoRaWAN, not just Lora. And you need to be in vicinity of a community gateway, if you’re not you need to deploy a LoRaWAN compliant gateway as well (think about 100 euros for an indoor one) For the embedded part you need a LoRaWAN component for Flowcode (which is being worked on) an...

It seems Heltec considers the HT-M00 a LoRaWAN gateway (it is not as it does not meet LoRaWAN specifications and will disrupt LoRaWAN networks). That means the Lora component will not be compatible because the data transmitted will not have the right headers, checksums and encryption applied. You co...

There are register differences between the SX1272 and SX1276 that might make the component incompatible. When using the modules you should check the local regulations to check if there are any limitations on frequency use in the band used, the bands are free to use without a license but are regulate...

Sorry to disagree, the space is not a bug. And putting URL escaped characters in it would break json compatibility and would introduce a bug. Modifying the URL code to make sure all characters in the URL are properly encoded would be a better solution. Keep in mind there are json use cases that do n...

The issue is that you can’t ever use a get request with a space in the URL. If required it should be URL encoded (something like %20).

Whitespace is allowed within json. However there shouldn’t be backslashes before the double quotes. Valid json looks like this: { “element1name”: “string value”, “element2name”: true, “element3name”: 3 } Where all quotes should be regular double quotes which the forum software keeps messing with. Se...