Hi,
about your second concern, I have the same findings.
After successfully joined and package send, LoRa-E5 is disconnected from power.
Couple moments later, after power up, I need to manually rejoin to send new package.
If there will be no need to rejoin it will be great.
Best regards,
Miha
Yes, it completely defeats the low power nature of LoRaWAN for my use case, and I would imagine a huge number of others too. I would categorically consider it a bug in the implementation of the AT slave firmware, and I hope someone from Seeed engineering support team will reply someday with a response, since it’s been almost two weeks since my original post at this point.
The research and development of this issue about power consumption has been followed up, and we will release a firmware to fix this problem later.
Since I’m trying to use these on a product, it would be very helpful to know a target date for when the firmware fix will become available, and it would further be useful to know if the fix will be made available as a binary (e.g. a hex file) that I can load onto existing units that I already have with an ST-LINK over JTAG.
Because the requirements have been submitted to the R&D department, they need to schedule to complete, there is no way to give you a very certain time, it is expected to be completed within a month.
What about my question about whether it will be possible to update the AT Slave firmware on existing units with Seeed providing a hex file to use with an ST-LINK and JTAG connection?
They provide bin files, which can also be updated using st-link.
Please is there a way I can be notified / emailed when this new binary becomes available, I would be happy to help try it out and confirm it before pubic release if that’s helpful.
Ok, I have recorded the link of the forum, I will reply to you when there is news
Hi @Citric, please can you check if there has been any progress from your engineering team on this very important issue 
?
Can you point me to the binary I should load?
Not sure I replied to your post, please can you show me where the updated binary is for the updated AT firmware?
The installation is detailed in GitHub, as well as on the wiki page. Unfortunately, the AT firmware is encrypted and we cannot provide it.
I don’t care about the firmware source code, just the binary that can be loaded through STLINK. I have 20 assemblies I built as a prototype run, and without this fix, they are basically useless to me.
I’d be happy to sign an NDA or whatever if that’s necessary or helpful to your process. My goal is simply to have a working set of prototype boards, and then eventually to go to production with e5 modules in my product. Please, help me to get there.
I asked them, they said they can not give, my side also nothing to do …
I understand that you are doing the best you can and that you are not in a position to solve my problem. Is there any way you could put me in direct contact (e.g. by email) with your management and/or a sales representative?
I have to prove this works before I can even consider scaling up to production with the E5 module. Right now this issue is a deal breaker for me, and I thought the point of the E5 module was to support actual product development, not just hobbyist activities. I have to say, you guys aren’t acting like it right now.
You can contact the technical support email and they will have more access to handle it. But when you send the email you need to restate the problem and not attach a link to the forum, otherwise they will ask me to follow up and deal with … which goes back to the dead end.
Please can you DM me the email address that I should send an email to?