1.7.5 is supporting only COM.X LoraWan 470 and 915 modules but not the 868 MHz version M031-C?

@chefrocker Upvoting your request since I am waiting for the same. Unfortunately the 868 module seems to need a firmware update to match the same set of AT commands as the others. See https://community.m5stack.com/topic/3199/uiflow-1-7-5/11 for details.

Hello @sodoku. Many thanks for sharing the tutorial! I found it on m5stack.hackster.io and it helped me a lot. Registered two COM.LoRaWAN 868MHz modules sucessfully with TTN and managed to see uplinks (alas with long join latency and lots of retrying uplinks though I am in the very middle of Berlin - it seems coverage still has to improve a lot). I am still struggling with the adaption of the official P2P example. Especially regarding use with a sensor in a setup without use of buttons to initiate data requests. If you'd find the time to extend your tutorial his would be much appreciated.
Also I wonder about the real life range of the modules. I have currently set them to 5V and cannot pull data beyond 20m distance, line of sight. Seems odd ... what are your experiences? Can this be enhanced using 12V? Maybe a faulty antenna connection?
As a side note - all blocks in Flow 1.7.2 are dedicated to the older blue modules - but an implementation for the M031-C is in development, as confirmed by M5Stack support.

I can confirm they are for M2 screws. E.g. for mounting a stick on the battery stick you'll need M2x10mm like shown here https://m5stack-store.myshopify.com/collections/m5-hat/products/m5stickc-18650 Turns the Stick into a nice handheld device for mounting a joystick, thermometer etc.

COM.LoRaWAN Module 868MHz V2.0 (ASR6501, product code MS03031-C4) is now listed at retailers. Hopefully this new module will finally see full UIFlow support.

EzData 1 is running again, but the outages occur more and more often.

Hello everyone,
EzData with UiFLow1 stopped working a fortnight ago and currently doesn't accept new topics and refuses interaction with (my) ESPs. Web interface and Remote+ still are available but data section remains empty even when generating a new token. Anybody at M5 involved in this can give us a hint if and when it'll work again? Is there any roadmap for this databroker?

Switching to UiFlow2 seems to be a necessity in the near future. Unfortunately its EzData2 iteration still lacks a web dashboard. Any idea if this is going to be a planned featured?

Which firmware version are you using?

| Experienced problems pushing data to EZData with 1.9.8 on Atoms. Reproduceable error not occuring after reverting to firmware 1.9.7.

@ajb2k3 Kind of. I am using push of data in a time-based function (UIFlow). Tried normal and async save methods of a string and an integer. The Atom then freezes without transmission and the function is never terminated. Previous Firmware 1.9.7 allows continuous transfers of two values and reverts to the main loop after finishing the function.

Experienced problems pushing data to EZData with 1.9.8 on Atoms. Reproduceable error not occuring after reverting to firmware 1.9.7.

COM.LoRaWAN Module 868MHz V2.0 (ASR6501, product code MS03031-C4) is now listed at retailers. Hopefully this new module will finally see full UIFlow support.

@chefrocker Upvoting your request since I am waiting for the same. Unfortunately the 868 module seems to need a firmware update to match the same set of AT commands as the others. See https://community.m5stack.com/topic/3199/uiflow-1-7-5/11 for details.

@iamliubo Thanks for the info. I wonder about wether it's going to be possible to upgrade firmware of said LoraWAN module M031-C. How can this be done?

When connecting Burner or UI.FLow to a M5Stack account a device management is available to bind devices. Yet this tool is somehow cumbersome to use since the only device identifier is a MAC adress - a note field could let users add an own identifier / note on the currently used API key.

Hi @sodoku
first COM.X LoraWan blocks became available with UI.Flow 1.7.5. Unfortunately still no support for the european frequency model.

I now run a public TTN gateway myself covering a portion of the Gleisdreieck area filling a blind spot. Hopefully adding an external LoraWan antenna with higher gain will solve my range problem at my nodes location - half a kilometre distance in a dense urban area can really be a show stopper with LoraWan when there's no gateway around ;)