device\_tracker state unknown + log errors
for the past few weeks, the device\_tracker entities for the mobile\_app component have not been updating from the ios app, and always show a state of ‘unknown’.

i am able to see from the logs on the ios app that the location is being updated and is properly detecting when entering and leaving zones,…
after updating to home assistant core 0.107.5 this issues seems to have resolved. it’s been working properly for a few days now.
well, i raised an issue with id support whom escalated it with engineering or something and it's now working. they did say they'd text me updates and haven't received anything from them so whether they did anything or whether it just started working.. who knows. 

but yeah, looks like the answer is calling / talking to support. this is still on our list to investigate, and we hope to get to it once we complete our new icloud syncing for 6.0.

fyi, your original post is currently marked as pending. :slight\_smile:

[image]

[infuse doesn't detect current position in shows that have 'reset progress' (rewatching…](https://community.firecore.com/t/-/16638) Well just had TAC look into it. They restarted the management plane which fixed the issue.

The reason we believe was due to insufficient resource in the management plane at the time of the update.

Thanks Sandeep for your help.




[View solution in original post](/t5/general-topics/app-version-mismatch/m-p/45216#M33220) hey there,

a bunch of additional questions:

which version of blokada do you use right now? v.4.6.3 is the current one.

is private dns in your phone settings disabled? if not, please do disable it.

did you activate a dns in blokada?

did you enable traffic mode or data saver in your phone settings?

… try clearing cache in roon settings on the device. Please refer to the following FAQ regarding your phone's unlocking :
  

  
<https://ccm.net/faq/1038-why-ccm-doesn-t-help-unlock-mobile-phones-smart-watches-or-sim-cards>
  

  
Regards hey,

you can probably fix it by following the steps described here: <https://folivora.ai/blog/post/13010>

if that doesn't help, could you check whether there are any crashlogs in the macos console app under "user reports"? thank you for taking interest in my post.

i have solved the problem.it was mistake from my own part.

i have disabled some of the hardware detection services before the update.

i have disabled the "device install service" on the windows service

[[asas]](https://aws1.discourse-cdn.com/arduino/original/4x/5/0/9/509934b6660953c4e848dc95f40efd35d02bfe60.png "asas")

renabling it and rebooting it solved the … the otg port does not support isochronous mode when in device mode. timgoos,there seem to be a few threads about this issue. most people, at least those who bothered to respond back to this forum, seem to indicate that turning off the "lock screen controls" resolved the issue for them. my guess is that there's a bug somewhere in the app, and they haven't either figured it out, or looked at it. i'd suggest that you go to settings -> sonos -> lock screen controls and make sure it isn't green (on). it's inconvenient, if you're accustomed to using the lock screen like i am, but then again if it doesn't kill the battery, that's a plus.and if you'd be so kind as to come back and post here to let us know if it works for you, it might help the next person who may be in your shoes.thanks!