We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I add a new concentrator without any client thumbprint, the device twin should not have any thumbprint set.
The device twin have a thumbprint with empty string:
Portal version: 3.3.0 LoRaWAN Stack version: N/A
The text was updated successfully, but these errors were encountered:
Additional information: When not specifying, the clientThumbprints in the device model should not be present at all.
Sorry, something went wrong.
The field should also be updated in the database:
Npgsql.PostgresException (0x80004005): 23502: null value in column "ClientThumbprint" of relation "Concentrators" violates not-null constraint
Fix #1409 - Client thubmpring should not be present in device twin if…
4b27599
… empty
3541eea
… empty (#1470)
kbeaugrand
Successfully merging a pull request may close this issue.
Expected Behavior
When I add a new concentrator without any client thumbprint, the device twin should not have any thumbprint set.
Current Behavior
The device twin have a thumbprint with empty string:
Steps to Reproduce
Context (Environment)
Portal version: 3.3.0
LoRaWAN Stack version: N/A
Logs
Additional Information
The text was updated successfully, but these errors were encountered: