Locate from Mapshare not working

The locate feature can take quite a while to update. The device must have a clear sky view. When a locate is requested, the servers send a message to the device. The device responds, which updates your position. If the device does not have a clear ski view, the original message is missed. (Apparently this is not like a normal message, which is queued in the iR network until received.) The web site resends the request at intervals for up to 5 days (it says). The web site also mentions a delay of up to 20 minutes. I am pretty sure that 20 minutes is an outdated number, but I don't know for sure.

I am trying this now. Will report back if I get an locate.

I just tried it. Twice. It worked both times. Note that you must wait for a message check to receive the locate request.. I confess to speeding up the process by forcing a message check after posting the locate request from the web. Also, I did this with a different device, not the M1. Should not matter.

Note that the web site apparently no longer shows the circle-star symbol for a locate response. Instead, the "head pointer" (the big blue triangle) simply moves to the new location.

To test this the same way I did, post a locate request from the web (map tab at explore.garmin.com, or MapShare or whatever). Request a message check on the device. Depending on what you did with the device recently, the head pointer may or may not move. (For example, if you sent a message a track point but did not move the device before attempting the locate, it won't move.) Whether it moves or not, it will show the location at which you triggered the mail check which received the locate request. If you click the head pointer, the pop-up balloon will show the time of the mail check - which is when the device received and responded to the locate request.

Not to put too fine a point on it, actively tracking has a lot of safety benefits (besides letting the family know where you are). In particular, if you are incapacitated to the point of not being able to trigger an SOS, the track points give SAR a starting point for the search (once somebody reports you missing or overdue). If your use is seasonal and you are not using a monthly "freedom" plan, you might want to do the math to see if that is cheaper than the annual plan for seasonal use. Even on the safety plan, track points are 10 cents each. Your life vs. 60 cents an hour?

Thank you so much for taking the time to do some testing for me!

That was a great point about the message check on the device, but unfortunately I'm still stuck on this issue. I just tried again with the InReach outside and requesting the location and then manually checking for messages on the InReach, but still no location update. I also tried sending a message from the mapshare page as well as the explore.garmin page and still nothing.

My location still shows on the trail I did yesterday where I manually sent a preset message.

I totally hear you about enabling tracking. I'm on the safety plan so each tracking points will cost me. I'm totally fine with spending money for safety, that was the whole point of buying an InReach in the first place. But I have an issue paying extra for something that used to work, and should work with my current plan. So purely on principle I'd like to get the locate feature working again.

I'm determined to solve this and will update once I do in case anyone else has the same issue.

This begins to sound like it might be a problem with the device. Can you successfully send a message FROM the device? Can you successfully receive a message sent TO the device? (Check your Inbox at explore.garmin.com to be sure things are making it to/from the Garmin servers.)

Edited to add: If you can successfully send and receive a message, then I would suggest opening a support ticket for locate. If not, you may need a support ticket for the device itself.

The good news is my issue is resolved.

The bad news is that this is a massive flaw in the Garmin Backend that is not communicated to its subscribers, and when an account is locked it's not communicated to the user. This is a huge safety issue! Safety is the only reason for someone to purchase an inReach.

Here's a scenario to consider: My wife submits a location request because I'm overdue on a hike. When getting no response she contacts search and rescue who then request my location again. So now at this point because there have been 2 requests within 5 days the location request feature is locked and nobody has been notified about this?! So again at this point nobody has the ability to location me via my inReach while I may be dying in on a trail somewhere unable to use the SOS feature myself?!

If that statement is true this is a massive flaw that needs to be fixed ASAP!

If I don't get a response to this message I will absolutely be cancelling my contract and selling this useless piece of "safety" gear.

You can submit an enhancement request here: https://www.garmin.com/en-US/forms/ideas/

At the risk of preaching, I will repeat my point that you lose a lot of safety features by NOT tracking. 

>>Note that the web site apparently no longer shows the circle-star symbol for a locate response. Instead, the "head pointer" (the big blue triangle) simply moves to the new location.<<

it displays the normal triangle first, but when this moves, the asterisk is still produced and left on the map. While it is possible to mark the asterisk and then select delete, it will stay on the map for ever. :-((((

I was told it can not be deleted, I found this funny, as everything what can be written to some data base can be also deleted

I did try moving after getting locate to work. Apparently I did not move far enough.