sending msg to own IR does not work any more?

skyeye That is how it is inteded to work. The inreach address will only work from inReach device to inReach device. It is not meant to be used as an identifier for sms or e-mail messages to be sent to the inReach device. Understanding the inReach Address

this is not fully correct, at least not until end of September 2022.

From first time using inreach, the standard procedure to test own device was to send a message to own inreach address.

Yes, earlier devices had some means for testing build in, but this was not transparent to the user. Initially we were sending a message to the supervisor in the company, who in turn was replying and thus testing all.

We were then advised by Garmin to do a loop test, addressing a message to own inreach device. This we do so since 1916. All devices were able to send a message to own device. Few minutes after, the message was received, the device di ring the bell, the LED was correctly flashing, announcing the reception of a message.

Suddenly, in last days, this was cut off, leaving all users without the usual test. Those users are in the field, this is not just some Sunday afternoon hikers. We have more then 200 users, instruction manuals, field and maintenance procedures and they all fail.

I am not aware of any announcement by Garmin that the loop service would terminate at some time. This would be minimum I would expect before just simply cutting the service off.

“From first time using inreach, the standard procedure to test own device was to send a message to own inreach address.”

That feels like a very insecure way of testing delivery on outgoing messages, as it keeps communication within the Garmin system.

I assume each individual user has an email and phone number that they can use for testing.

By setting up one Preset Message with three recipients; own email, phone number and MapShare – the user can easily check endpoint delivery to 3 sources, as often as they want, for free.

...and then replay to that received message??

How? via phone SMS? Or via email? Or what exactly you mean?

Note the maximum the user has is an Iridium or Thuraya phone. for other communication.

In fact, as described above, the first test procedures was to send a message to an external destination and this had to replay to it. Not very efficient

The test procedure is meant to test the devices ability to send and receive messages and demonstrate it clearly to the user. This is done each time the device is switched on for use. This procedure is older then Garmin inreach, it is part of the concept of Inreach by Delorme.

The bad thing is, that it was cut off without any announcement, or at least we did no receive any information about it.

My example is for testing outgoing messages to non-inReach user.

To test incoming messages to device, you must follow the procedure for that.

All inReach devices have a simple way of self-testing. link

skyeye said:

When loop test is done, user gets his full feedback

Again, sending communication only within the Garmin ecosystem I would consider an unsecure test.

Only when an inReach message pops up on my phone as an SMS, email or MapShare entry, I would feel safe on actual delivery.

Only when an inReach message pops up on my phone as an SMS, email or MapShare entry, I would feel safe on actual delivery

then you are one who has all nice things like phone or internet probably

our users are less lucky, no idea how should something pop up on phone , email or mapsahre for them

Even when using Inmarsat terminal and a computer attached to it, do you really think you will ever see something like mapshare on it?

Step down from your oversupplied environment, this is not reality in the world of rescue teams, disaster recovery  etc.

If you provided context on your use case, it would be easier for others to give relevant advice. 

my main problem is, that loop test did work from early beginning of inreach without problem until end of September 2022. Does not even has anything to do with Garmin, it was by concept so by Delorme, as only way to have some test at all.

Cutting this from busy customers without any notice is irresponsible.

BTW: loop back messages do not stay in any kind of Garmin Ecosystem

They travel with Iridium and are from there forwarded to Garmin servers like any other mails or data, processed there, and returned by same way back to Iridium. This  way is used by other Iridium customers the same way, there is nothing Garmin-special on that.