@adamm5

Well ChatGPT solved my problem....increasing the spreading factor to 11 has suddenly made everything work. Not sure why such a high SF would be needed between two devices on the same desktop? Will soon find out.

In the meantime, the following table gives some interesting perspective on the transmission time for a 19byte payload.

SF	Symbol Duration	Payload Symbols	Total Symbols	Airtime
7	1.024 ms	37	51.25	0.052 s
8	2.048 ms	37	51.25	0.105 s
9	4.096 ms	37	51.25	0.210 s
10	8.192 ms	37	51.25	0.420 s
11	16.384 ms	37	51.25	0.839 s
12	32.768 ms	37	51.25	1.678 s

Trying to get a pair of LoraAS923 units working in P2P mode, using AtomS3.

Sending is reported as working, but the second unit will never receive. I've triple checked all parameter settings, they match on both units.

Has anyone actually got this working (on this or other frequency units?).

I'm seeking to remotely monitor a solar pump using a Lora unit and AtomS3 Lite, and need to count pulses from a water meter's hall sensor.

I see UIFlow1 provides blocks for capturing events on rising (or falling) GPIO inputs, which is what I need, however UIFlow1 won't work with this hardware. I can't find an equivalent on UIFlow2. Or is the PIN BTN 'is pressed' event effectively the same thing? Or do I need to do this in python?

Adding to my confusion, I get the following from the M5 AI assistant:

3. UIFlow2 Block Configuration
Initialize Pin: Use the "Pin" block (under "Hardware") to set the pin number, mode (IN), and pull resistor.
Set Interrupt: Use the "Pin Interrupt" block to select the trigger edge and assign a handler function (defined via the "Function" block).

Thats exactly what I want...but there is not such "Pin Interrupt" block that I can find.

@bozho did you have any luck. It is clear on Uiflow1 how to detect rising inputs but I don't see this on Uiflow2...or is this is actually what is meant by the 'button press' block on the 'pin button' hardware module?

@adamm5 Ive rebuilt this project from scratch and can confirm that ignoring the i2c load error is possible even when using the AIN i2c unit and PAhub unit. This seems to be a change to my earlier experience but perhaps something else was happening with the code.

in my case i need to query an AIN unit, which is i2c...so this error is a total blocker.

i'm getting the same i2c driver error on an Atom Lite, the error began following an erase but persists regardless of the UIflow2 version I attempt to refresh with.