Hello.
I’m currently at my wit’s end with this license.
My CHIP ID is: ESP32ChipID=482AFCBD9E7C
I’ve also generated the license.
However, when I try to enter it using the AT command, I always get a license error.
See screenshot.!
HT-M00 Error license
Single & dual channel gateways aren’t supported on TTN, so the license issue isn’t a thing.
@nmcc while I wouldn’t dare argue with you on your TTN forum, this reply does not point OP into an useful direction. You’re dismissing his issue which is a valid issue, turning it into an XY problem because now he doesn’t know what the actual source of the issue would be.
Yes, TTN doesn’t support gateways such as the M00. So OP shouldn’t get it connected to TTN. But the issue is an actual issue. As the Heltec database is currently reporting errors, I can’t verify your entry, but it looks alright.
As per this post, I’d contact Heltec directly:
And please, don’t connect this gateway to TTN - check the TTN forum for the reasons behind it if you want to understand why.
If someone is clearly going to cause harm to a system through misguided, ignorant or wilful application, why on earth would you want to facilitate them along that path?
There really isn’t much use for the HT-M00 without totally alternative firmware. The OP’s intent for this unit & record thus far hardly inspires that once the serial problem is solved they aren’t going to start inflicting mayhem on TTN.
If someone asks how to combine glycerol, nitric & sulphuric acid, do you oblige because it allows them to advance their chemistry knowledge?
I just happened to have this gateway lying around.
And after the firmware update, this error occurred.
I have 10 fully functional gateways in operation myself. But for just one location per day and only one sensor, it was unnecessary to set up a large one.
YES, I used the ESP ID to generate it.
Yes, I included the Kayak because it’s useless without the embedded ESP ID.
I just want to get the gateway working again. Which isn’t possible without the license. It’s quite possible that this data will later be sent to HELTEC or their own Chirp Stack.
@Lordcyber for such an occasion, the solution would be the use of a One Channel Hub, which is something you can get running on a LoRa32 V3 for instance. The MT00 isn’t meant for anything LoRaWAN.
@nmcc my issue with your response is the fact that you deliberately obfuscated the license issue to having something to do with the TTN link. Your example doesn’t really apply here, as this was not a question how to configure the MT00.
It is explicitly mis-sold as being as a “LoRa” gateway with instructions to connect it to TTN or Chirpstack. So it is very definitely meant for LoRaWAN by the vendor.
The OP was trying to activate a device using settings for TTN that is known to disrupt the worlds largest community LoRaWAN network with a device that was only designed to do exactly that with no other firmware options, despite the product page notes, the instructions explicitly reference TTN.
So whilst my response maybe succinct, given the product information it was not “deliberately obfuscated”. The OP could find the enormous number of Google hits related to this topic from my response. Or just read the product home page.
Not sure how entering a serial number correctly is not configuring a device. Deliberately obfuscated would be “the serial number is probably rejected because the device isn’t compatible with TTN”.
Just answer the question if you disagree. If you have issue with the technical content, then find a way to sugar coat it, possibly using some sweetened Dutch, then do so. If you have issue with the style of response, then do so privately. Exactly like I just haven’t done, my bad.