@Inunekko received the report but data comes in correctly from apple
So if the data is not correct it’s on the apple side
App keeps loosing its connection
When i restart app and login with apple icloud it has its connection a couple of hours … and then nothing is updating again
report when stuck
e9b3d372-0aae-4042-9f80-fae9fc5ea60d
Report after restart ( takes a few mins to update )
b7df36ba-3b98-49c2-bda3-bc2f2d1d3cf9
@Dennis_H74 will check it
New app update (
TEST: 1.7.1):
Changelog:
NEW:
1: NoneFIXES:
1: FIX: session disconnects
If you find any issues, send a diagnostic report
Note: Before sending a report make sure to reproduce the issue so the issue will be visible in the report
Via Homey Mobile app:
More - apps - Apple Findmy - settings wheel right top - send diagnostic report (put your email in the input field to make it easier)
Via Homey Webapp:
Settings wheel bottom left - Select Apple Findmy - Click on send diagnostic report
You can install this version by clicking the link above and press install (do not remove the app, only press install)
Don’t want to be part of a test version? Install the live version → Find My | Homey
@Dennis_H74 I just made an update. Can ypu try the test version? See post above
Installed it will check a couple of day
Really was the app i think because it was ( temporarily) fixed with a restart. no need to login apple again.
Will let you know when it does not update… or let you know no connection lost in a couple off days
I already note a difference . The distance is checked “ a few seconds ago “. 1.7.0 sometimes had minutes without an update if it was updating. -EDIT- also with 1.7.1 so disregard remark
Thanks again for the quick service 
Since I installed version 1.7.0 and changed the server polling interval from 60 to 120 seconds, touch wood, I haven’t had any problems. I did add a new email address to my iCloud account just for authentication with this app, I don’t know if that made any difference.
My flow that gets Alexa to announce when my phone needs charging has been working flawlessly since 
Unfortunately same issue with 1.71
Did not update for the last 6 hours
c0f16c06-3ddb-4c28-835a-279445e020c3
After restart of the app working instantly without needing to login again with apple ( so looks like app issue )
8766c90a-d67d-41ff-aa4e-b51944b7f756
@Dennis_H74 I expect more a apple issue than a app issue
Nothing has changed to the integration
So maybe apples session management has changed
But have to investigate that. Will check if the SDK had a update
You’ll be happy to hear that my iPhone 14 Pro Max is still updating fine, as far as I have seen, on version 1.7.0 with the amended Server Request Interval. And I have also got my iCloud calendars sync via another app working too.
I’ve just written some basic Python scripts located on one of my Raspberry Pis using the imaplib to login to my iCloud email. One gets the quota usage, another two get the number of total emails and unread emails, and the fourth is a mailbox clean-up that my Homey can run if used space exceeds a value I set in a Homey variable and deletes emails older than 6 months. I have a flow that calls the first 3 scripts in turn and populates an Advanced Virtual Device with the values, and a time stamp of the last successful update.
it’s that last part I thought quite helpful, and wondered if you could add similar to your app. Then it would be a bit more obvious for all if the app was making successful requests at regular intervals or if it was just Apple not sending up to date values for the device in question, or the device is failing to update stats to Apple. I hope that makes sense, and I’m not just talking 
I’ve replicated this for a number of other mailboxes I have hosted elsewhere. but it was the iCloud one I thought relevant, as it adds to the number of calls I’m making to Apple’s servers from our app, the calendar app, and my IMAP mailbox scripts, all using the same iCloud account.
Checking above posts i changed to 2 mins ( from 15 secs ) also and restarted you app
Now its not doing much at all 
3d6b77b4-0d69-40b7-b7f5-0515d4f22c9a
15 seconds, not surprising it wasn’t working, the servers probably blocked / rate limited you. It may take a 24-48 hour period for a block / rate limit to expire. After which time, it’s possible that the amended server request Interval of 120 seconds will start working.
It might be worth trying to wait and see if that resolves the problem?
Also worth considering, how many Apple devices do you have accessing the same iCloud account? Each device you have accessing the same account will add to your server request rate. I don’t know what limits Apple has on their servers, but I only have 3 sometimes 4 devices connected to my iCloud account, and my Homey was getting blocked with a 60 second request interval.
Thanks
That is weird though .. it worked for years at 15 seconds. Furthermore … like describe above … if i restart the homey app … it will immediately work gor 1 to 3 days normally .. and then it stops again
Also .. i restarted the homey app after my previous post. Its working for the past hour so that 24/48 hour cooldown is not correct i think
but will try and see what happens the commings days
It could be that each time it restarts it creates a new authentication token, and it’s being blocked/dropping connection is based on the authentication token rather than say source IP address. (I’m just making an educated guess here though, as I don’t know how their authentication operates.)
It having worked previously is not a given that it will work now, or necessarily a fault of the app. It is quite possible that Apple have just changed their security and authentication. They may have imposed more strict rules if their servers were getting battered with requests due to the number of devices people have these days increasing, and the rise in smart home tech.
I know I had to recently perform a major upgrade of my home network, due to the increase in smart home tech I have decimating my old WiFi setup.
All I’m trying to say is it’s worth bearing in mind the other parts of the systems between your iPhone and your Homey… those little data packets are probably travelling half way around the world ha ha 
I have a Flow that when I leave home it changes the server update interval for my iPhone to 10 minutes, as I don’t need it as often for automations. And then changes it to 2 minutes when I arrive home. Since I made these changes, reducing my volume of requests, after a day or so it settled down and has worked faultlessly since. My Flow that triggers when my iPhone battery drops below 25% and gets Alexa to announce I need to charge my phone hasn’t once failed to trigger telling me my iPhone is at 24% battery (which it gets the % value from the device property tag for the announcement). It used to fail frequently.
@martijnpoppen another thank you for your help getting this working, you are a legend sir.
Yes always had the same kind of setup
10 mins when sleeping .. 15secs ( now 2 mins ) when awake .
Will try the coming days and let the both of u know
It would appear I spoke too soon… Earlier today I noticed that the battery, location, and distances from Home(y) had not updated for 24hrs. I tried all the usual restart the app, repair and re-authenticate etc… and all I got was a big “get stuffed”.
This displeased me greatly, as it had been working perfectly for several weeks, zero problems… so I went digging around on t’intermawebnet thingymajig… seems there are some bad actors out there that apparently find it highly amusing to perform DoS attacks on random iCloud accounts by just using a bot to repeatedly attempt to sign in with a username and just random garbage for the password, therefor triggering account lock-outs.
Weirdly this doesn’t affect your iPhone. Nor do you receive any sort of notification on your iPhone that your account has been locked, so can’t be accessed from anywhere other than said iPhone. How infuriating…
After fishing out my Yubikey and jumping through all Apple’s hoops to unlock my account… hazzar! it’s working again, and so is my calendar sync.
Apple really need to improve this. For example, blocking source IP from an account, rather than a blanket block. Sending a notification directly to your trusted iPhone. Anything would be better than just silently nuking your account 
@Drako74 oh wow that’s really interesting. Didn’t know this was a thing…
Is that also causing the flood of “your account is used to login” mails from apple ?
and does that also mean a 15 sec server interval was not the cause and can be used ?
The occasional email is to be expected, but at most I would guess once a day… any more often than that would definitely be suspicious.
Not necessarily… a 15 second server update interval could be classed as a DoS attack in itself. At very most I would say no more often than 60 seconds (as was set as the default). But if you have multiple devices accessing the same iCloud account, I would suggest slowing it down to for example the aforementioned 120 seconds… but maybe just suck it and see what works for you.
I have at least 4 mails per hour 
