You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the console the Activation mode (OTAA, ABP, Multicast) shown for an existing device is read-only.
Unable to change Activation mode for existing devices.
Steps to Reproduce
Add a new device to an application, select create to add it. Afterwards try to change its Activation mode.
The text was updated successfully, but these errors were encountered:
lnlp
changed the title
[bug][console] Unable to change Activation mode for existing devices
[bug][console] Unable to change Activation mode after device has been created
Jan 31, 2021
lnlp
changed the title
[bug][console] Unable to change Activation mode after device has been created
[bug][console] Unable to change Activation mode after device has been created, is read-only
Jan 31, 2021
This is working as intended. In The Things Stack OTAA and ABP devices are really different things, and it's no longer possible to switch between the two. Also, an ABP device can't suddenly turn into a multicast group or vice versa.
htdvisser
changed the title
[bug][console] Unable to change Activation mode after device has been created, is read-only
Unable to change Activation mode after device has been created, is read-only
Feb 1, 2021
Summary
In the console the Activation mode (OTAA, ABP, Multicast) shown for an existing device is read-only.
Unable to change Activation mode for existing devices.
Steps to Reproduce
Add a new device to an application, select create to add it. Afterwards try to change its Activation mode.
What do you see now?
Activation mode parameter is read-only.
What do you want to see instead?
Activation mode read-write so it can be changed.
Environment
The Things Network V3 Console.
How do you propose to implement this?
Make Activation mode changeable.
The text was updated successfully, but these errors were encountered: