bug of background activation of high accuracy mode

[DOK87]

Apparently activating the companion app's high accuracy mode works the opposite of how it should.

I configured the companion app to activate high accuracy mode when I enter a specific zone. But when I enter the zone, the high accuracy mode stays off. However, if I deselect the zone in the configuration menu of the companion app, then the high accuracy mode immediatly switch on. This happens whether the device is inside the zone or outside. (I did the same test in both cases)

Describe the behavior you expected I expect the correct operation is that when the device enters the zone, the high accuracy mode is activated. And is deactivated when the device leaves the zone.

Then as an implementation, it could be useful to be able to activate/deactivate the high accuracy mode via a switch entity

Steps to reproduce the issue 1- After configuring a zone in the system, and configuring the complementary app to activate the high accuracy mode when the device enters the created zone

2- Enter the device into the area (high accuracy remains off)

3- Remove the device from the area (high accuracy remains off)

4- with the device inside the zone, deselect all the zones in the "background position" menu of the companion app (high accuracy mode is activated)

5- with the device inside the zone, select one or more zones in the "background position" menu of the companion app (high accuracy mode is deactivated)

6- repeat points 4 and 5 with the device outside the area, and the result is the same.

Android version: 13 TKQ1.221013.002

Device model: Xiaomi Redmi Note 10 Pro

Home Assistant version: 2024.10.3

[dshokouhi]

what happened to the issue template? this issue is now missing important information like logs and we cannot help without logs.

[dshokouhi]

your desscripion is also incredibly difficult to follow....i have no idea what this issue is describing.

[DOK87]

I apologize for my bad English, and the use of Google Translator. But your response is very very rude. I only noticed a bug in the functioning of the app and I thought it was right to report it in everyone's interest. However, if this is a bother to you... no problem, close the thread.

My description is unclear... Maybe. As I said my English is not good, and I'm using google translate. Just tell me what isn't clear and I'll try to explain better.

Unfortunately, we are not all programmers or developers. And I'm not that much of an expert user. If you need the logs, no problem. Give me an indication of what logs you need and where to find them. I'll bring them back to you right away.

Thank you so much

[dshokouhi]

I apologize for my bad English, and the use of Google Translator. But your response is very very rude.

if you are using google translator then you really dont know if my response was rude. I simply said the issue template was removed and I could not understand you as the text is difficult to follow. You should expect responses like that if you dont speak english and rely on a tool to translate and convey meaning.

Just tell me what isn't clear and I'll try to explain better.

the whole text is hard to follow and uses terms not common with home assistant. Maybe a video recording will be easier to follow?

If you need the logs, no problem. Give me an indication of what logs you need and where to find them. I'll bring them back to you right away.

the logs were mentioned in the issue template you had removed when creating the issue, the text there was meant to provide information and guide you in the data the issue needs. Logs are required here.

Settings > companion app > troubleshooting > show and share logs

from there you need to replicate the issue and then grab the logs, they do not go far back either maybe only 10 minutes.

[DOK87]

thanks for the reply. And I apologize again for not understanding each other.

I will soon return home from the office and give you a more precise description using the new issue template. Thank you