With ‘manually’ do you mean:
- ‘manually created in the console’ using the LoRaWAN Device Registry option?, or
- created in the console using the ‘Manually’ option?
If 2. then try to redo registration using 1. instead so that required settings will be configured correctly automatically. This requires the current device to be deleted first and a new device-id for the re-registration.
MIC mismatch errors may be caused by incorrect (mismatch in) network layer settings.
My Kona Home Sensor devices (T0004895 Rev D) use the following network layer settings:
LoRaWAN version: MAC V1.0.2
Regional Parameters version: PHY V1.0.2 REV A
I’m in the EU868 region:
Frequency plan: Europe 863-870 MHz (SF9 for RX2 - recommended)
When registering a device using the LoRaWAN Device Repository option the correct network layer settings should be configured automatically.
(Be aware that changing network layer settings in the console after the device has been registered may be possible in the UI but then not be effective. Not sure if that issue has been fixed already.)
When registering a new device in the console (using the device registry) be aware of the following:
The Tektelic ‘Kona Home Sensor’ was rebranded to ‘Smart Room Sensor’ so this is what should be selected.
In the ‘Model’ list Smart Room Sensor entries will show up TWICE:
Smart Room Sensor - Base
Smart Room Sensor - PIR
…
Smart Room Sensor - Base
Smart Room Sensor - PIR
The first instances currently allow only hardware version ‘D’ to be selected, the second instances allow only older versions to be selected.
Also see: Migrating Tektelic Smart Room Sensor devices to V3