LTE /interface/lte/settings/set sim-slot=esim

Hi,

we tried to get an eSIM working. First step is AFAIK to enter this command:

/interface/lte/settings/set sim-slot=esim

https://www.xsbyte.com/blog/xsbyte-blog-1/activate-esim-on-routeros-37

But on our tested devices this command throws:

expected end of command (line 1 column 1)

My question, will this change if we buy a physical-eSim adapter or is this a hard-limitation (don’t want to buy a useless physical eSim-adpter). MT documentation is not clear on this point.

Tested devices are:

https://mikrotik.com/product/hap_ax_lite_lte6

https://mikrotik.com/product/wap_lte_kit

Which RoS version?

Check your devices modems against this table:

We tested with ROS 7.20.1 (LTE Kit) and ROS 7.19.4 (hap ax lite LTE6).

For me documentation is clear.

AX Lite LTE uses FG621-EA.
That device does not have an esim embedded but you can use an external esim which has to be handled as a regular sim.
The command to switch to esim is not applicable here.

However, and that's also in the documentation, it can not handle an empty esim without profiles.
You first have to populate a profile on that esim using another device which can.

You mean the command:

/interface/lte/settings/set sim-slot=esim

can simply be skipped? This was our concern, this command is not documented and it is not clear to us, if we need it to switch from physical-sim to physical-esim.

All tutorial mention this command, like:

https://www.xsbyte.com/blog/xsbyte-blog-1/activate-esim-on-routeros-37

https://www.youtube.com/watch?v=v0WtU1xBB-Q

For the AX Lite LTE, we saw the advisory with the empty esim.

The command you posted:

/interface/lte/settings/set sim-slot=esim

ONLY works on a few (very recent) devices that have provisions for e-sims in the software/hardware, not on older devices that need anyway a physical e-sim support (sim card in the physical slot).
Imagine that "sim-slot" is in this case a "virtual" slot, only few devices support that.

On the FG621-EA, you NEED a PHYSICAL e-sim AND - ADDITIONALLY - it must be ALREADY configured outside the Mikrotik device.