If only Mikrotik would actually write in more than partial sentence or have a proper KB-like system for these questions… My only guess is the API changed are for internal use with REST API. I think REST API just proxies to API, but uses cached/pipelined connection (based on login in log)… in which case knowing a tagged API request was !empty might be useful. But just guessing.
I have ask several times about what modems this works with, no response, now half-dozen times. The lack of clarity around eSIM is quite annoying. From reading the docs, it seems like a working feature on something. If it’s nothing, then say that in docs! Since I read the docs, and eSIM came up in another thread, the eSIM docs don’t mention if the QR code had a $$1 at the end. Which, I think, means the
confirmation-code=
be required… and the $$1 part should NOT be in the
matching-id=
- but it wasn’t clear at all… And working in theory here…
Now the bright spot is the new scripting changes are just wonderful. They made quick work of the theoretical problem eSIM activation codes use the $ dollar as the delimiter. So on the theoretical modem that support eSIM, you can cut-and-paste the eSIM code to CLI. This is possible by the new :deserialize delimiter=“$” specifically to deal with eSIM LPA format (with the new-ish /terminal/ask allowing cut-and-paste). See Interactively parsing eSIM Activation from LPA in QRCode... for example.
But there should be something like /ip/dhcp-server/setup for the eSIM. Or, Winbox4 could natively use camera to capture the QR code, too.