I provided a general solution to pulse counting in the following post: https://forum.pycom.io/topic/6006/water-flow-sensor-looking-for-advice/2?_=1632413513467 At some point I may provide a micropython library for this.

I've had success using Atlas Scientific's embedded flow processor for water meter pulse totalizing: https://atlas-scientific.com/embedded-solutions/ezo-embedded-flow-meter-totalizer/ I connect it to a FiPy via I2C then forward the readings to my server over MQTT. Seems like a good option since the flow processor will keep totalizing if your LoPy restarts.

Yes, as the reading is only caught on the interrupt, before the microcontroller wakes up, we cannot see the data

Hi Samuel, Please check the network connection you are planning to use. For your application, it seems a direct LoRa RAW connection would be ideal, though I do not know about the separation distance. The problem I foresee in your current setup is the need of a central server able to relay communications between the devices, as cellular is a centralised network, requiring the need of a separate server (its not possible to connect between devices directly). Other than that, the Fipy / Gpy should work fine for the application :)

I just figured it out, it was actually my firewall on the wifi network that I was using to test. THanks

@Gijs Hi thank you for your reply. I intend to use the same antenna as the OEM module uses. According to 25450AT43B100 datasheet, the layout will be like the one below: [image: 1629537196609-layout.png]

See https://github.com/jczic/MicroWebSrv2 for the updated version

@cbourne Some convoluted history which has indeed confused many people. The origins are explained in the post I linked to above. Note that IIRC you can use either the P or the G names when instantiating the pin. Personally I believe I've always used the P names.

thanks for the advice

I would have thought that would be ok. I run the same code on my devices that have an Expansion Board and the one that has a PyTrack. If the code finds a PyTrack board, then the unit will use it, otherwise it will adopt another role.

@jcaron Noted, thank you.

@Gijs OK> Just did that. Let's see if they can pick it up this time..;-)

@jcaron Hello, thank you for your answer. About the last picture, these 5 seconds are the "RX1 delay" that happens right after a TX window. I was thinking it had to be 1 second for OTAA, but in my tests, I found it was 5 seconds (Both uplinks and downlink were verified by TTN), and making a quick search on the internet seems like is the default for it using TTN V3. I'll try to find a way to reduce it, seems like I have to use the TTN "CLI". Cheers.

Currently, you can already use Pymakr online to update the micropython code, and use Pybytes to update the firmware. I believe both should work over LTE as well. I will add the feature you describe to the feature list, as sending custom downlink messages is currently not possible in the interface.

@jcaron Gotcha, we will perform new tests and get back. Thanks a lot.