-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing APP EUI, KEY and DEV EUI without changing defined in the library #16
Comments
This is very easy to do, thank you for your suggestion, maybe we will make adjustments in the next version. |
Thanks. The last great limit is for the LICENSE variable and MCU activation. |
For automating DevEui, I change it from ChipId with this code : uint64_t chipid = ESP.getEfuseMac(); So if ChipId is 12 34 56 78 9A BC, my DevEui will be 00 00 BC 9A 78 56 34 12. |
@DeveloppeurPascal where to mention the user data in this library? i can't find one |
Yes, use like this:
|
@DeveloppeurPascal how did you defined the parameters outside the library. I've been trying it for weeks, all I get is ERROR:undefined reference. any one any hint @solotaker @gibus27 @Heltec-Aaron-Lee |
what parameters? |
The dev addr , netsessionkey.... But i found it thanks for the response |
An idea for a next release of this library.
It is convenient to have OTAA parameters (APP_EUI, APPKEY, DEV_EUI) as defined in the library when you only have one device, but when you have several devices it is useless. It must be possible to change them as a variable in the code of our programs.
As it stands, the proposed library does not allow to industrialize the work with Heltec cards. That's a pity.
The text was updated successfully, but these errors were encountered: