Send request position about android

[jpmens]

I confirm that it is not working for me: upon publishing a reportLocation request

echo '{"_type":"cmd","cmd":"reportLocation"}' | mosquitto_pub --cafile $cafile -h $h -u $u -P $p -s -q 1 -t owntracks/jpm/s8/cmd

I do not see a location response with ”t”: “r”.

[growse]

Smells like a bug.

[jpmens]

Remote commands must be enabled on the device. After that, if you publish an MQTT message with QoS>0 to the topic owntracks/user/device/cmd with a payload as you rightly showed of {"_type":"cmd","action":"reportLocation"}, the device should report its current location via a normal _type: location message.

[GianZambo]

Ok, thank you so much ....

[GianZambo]

Sorry @jpmens and for HTTP what's the command?

[jpmens]

Sorry @jpmens and for HTTP what's the command?

for HTTP this is very difficult to accomplish, as the client (the app) gets data only when it speaks to your endpoint. When your endpoint gets a position request it can respond with an array of objects which are consumed and processed by the app. However this defeats the purpose of what you want to do: you are interested in telling the app to do something, but via HTTP it is the app that must initiate the conversation. This was a very verbose way to basically say: "it's not possible to do".

[GianZambo]

Ok, thank you again .....

[GianZambo]

Hi,
with difficulty (for my skills of course) I connected OwnTracks with MQTT (HiveMQ cloud) to my node red and works fine, but I can't to send a request to position.
IF when I receive data from mobile I have in node red this report ...

but if I publish an MQTT message with QoS>0 to the topic owntracks/giamma/001/cmd

I have this report ...

Please tell me where is the mistake ..... (remote command are enabled on mobile)

[jpmens]

The message must be published to owntracks/giamma/001/cmd with the correct payload. Note: /cmd with "_type": "cmd"

[GianZambo]

This is my mqtt node ....

and this is my function node with payload ....

It seem right, but evidently I don't see the mistake ...

[GianZambo]

I also tried ...

but without success ....

[jpmens]

Do you have remote commands enabled on the Android device?

[GianZambo]

Yes ....

[GianZambo]

Well, works but ....
the app must be only in "Significant Changes" and ...
the app must be open .....
I cannot close the app even if se app is always active because at the top of mobile I have the icon's app with the function of Report and changes monitoring mode ....

EDIT: also with the app open the report location works only one time, after stop works ...

[GianZambo]

Hi, there are news for the resolution of this bug?

[jpmens]

It is still pending. As soon as it is addressed, the status of this issue will change.

[GianZambo]

ok ....

[underdog]

is this issue back? I'm on iOS, running OT 16.4.1. seems the app has to be in the foreground to execute a cmd sent to it. I opened the app, went to another app and waited for my cmd to be sent. saw it sent from my mqtt stream, but never say a pub come back from app. Placed app in foreground, waited for pub to be sent for cmd. cmd was sent and location was sent back to mqtt feed from OT app.

[jpmens]

@underdog this is a closed Android issue, and you are reporting this for iOS. If you are having trouble please open a new issue on our iOS tracker (github.com/owntracks/ios/issues), but before you do so, iOS behaves differently from Android: make sure you are publishing a QoS>0 payload to /cmd, and if the app is in the background, you'll have to wait until it wakes to process your command.