Question regarding importing open haystack devices

[aaronjrodrigues]

Quick question, I'm planning on purchasing a microbic to be able to flash open haystack on. I wanted to ask if it is possible to be able to import that open haystack device into the find my app itself so that I can view it on the find my app on my devices. In addition to that, if that is not possible. Does FindMy.py also have any way of importing these devices into home assistant?

Any help would be appreciated, thanks.

[malmeloo]

I don't use and have never used OpenHaystack, so I wouldn't know the answer to your first question. However, my hass-FindMy integration (see README) supports static-key tags in its current state. So you can simply enter the private key you used to deploy the device, and the integration will create device tracker entities for you.

[aaronjrodrigues]

I don't use and have never used OpenHaystack, so I wouldn't know the answer to your first question. However, my hass-FindMy integration (see README) supports static-key tags in its current state. So you can simply enter the private key you used to deploy the device, and the integration will create device tracker entities for you.

Just to clarify, when you say 'create tracker entities' does it mean it'll create it into the find my app of that device or is it in the script itself?

[malmeloo]

It will create them in Home Assistant. So Home Assistant will give you device tracker entities to show on a map, do automations with, etc. It's similar to the entities tracking your other devices (phones, etc.), except it tracks your custom FindMy tags instead.

[aaronjrodrigues]

@malmeloo quickly kqeustion I got find my for homeassistant setup however im experiencing a weird issue where it'll import my open haystack device and show the location however after a few minutes 10-15 minutes. The status of my open haystack tracker will go to 'Unavailable' in home assistant.

Please find the attached screenshot:

Please also find the attached debug logs:

Any help would be appreciated, I'm really loving the integration - it's just this one issue. Thanks.

[malmeloo]

The logs seem to indicate that the integration is losing its login session. This is usually caused by your anisette configuration.

Are you using your own anisette server? Public anisette servers are not supported. Also make sure that the anisette server you are using retains its configuration, as wiping it will cause the exact same issue as you are facing now.

[aaronjrodrigues]

The logs seem to indicate that the integration is losing its login session. This is usually caused by your anisette configuration.

Are you using your own anisette server? Public anisette servers are not supported. Also make sure that the anisette server you are using retains its configuration, as wiping it will cause the exact same issue as you are facing now.

ok I tried creating my custom server but it seems that the issue happens again. https://docs.sidestore.io/docs/advanced/anisette/ I followed this guide to create a custom server.

[malmeloo]

Could you try using https://github.com/Dadoum/anisette-v3-server instead? I haven't tested the sidestore server myself, so I'm not sure how it behaves. It might wipe its config routinely since it's intended to be used as a public server.

[aaronjrodrigues]

Could you try using https://github.com/Dadoum/anisette-v3-server instead? I haven't tested the sidestore server myself, so I'm not sure how it behaves. It might wipe its config routinely since it's intended to be used as a public server.

The docs that I followed told me to install the same one (https://github.com/Dadoum/anisette-v3-server) and I'm having issues on that.

Here's some more debug logs in case it has some extra information, thank you again for your support:

[malmeloo]

Ah whoops, I missed that part. Assumed it was a custom one. It's pretty late here right now, so I'll take another look tomorrow if you don't mind.

[aaronjrodrigues]

Ah whoops, I missed that part. Assumed it was a custom one. It's pretty late here right now, so I'll take another look tomorrow if you don't mind.

No problem mate, take your time.

Cheers,

[malmeloo]

Your log seems to be absolutely cluttered with errors from this integration, but one of them caught my eye. The rest are most likely caused by this error and raised due to bad error handling from me.

findmy.errors.UnhandledProtocolError: com.apple.mobileme login failed with status 1: Account limit reached.

This most likely means that the Apple ID you are using has never been used on a real Apple device. That's unfortunately required for this integration, since Apple only enables the mobileme API (which this integration uses) for your account after you have used it on a device at least once. Usually they show a different error in this case, but they seem to like switching up the error messages every once in a while.

There's a little more info about this issue here: #102

[malmeloo]

Oh also, I can see your email in at least one of the logfiles. Not sure to what extent you want to keep that secret, but you might want to remove them.

[aaronjrodrigues]

thats quite interesting as I did try multiple accounts - which didn't work because they didn't have an Apple device linked to them. However, the main account that I have (around 4 devices linked) is what gives the previous behaviour where it works for a few hours then it doesn't work.

…

-aaron

On Thursday, 27 March 2025 at 08:17, Mike Almeloo ***@***.***> wrote: Your log seems to be absolutely cluttered with errors from this integration, but one of them caught my eye. The rest are most likely caused by this error and raised due to bad error handling from me. findmy.errors.UnhandledProtocolError: com.apple.mobileme login failed with status 1: Account limit reached. This most likely means that the Apple ID you are using has never been used on a real Apple device. That's unfortunately required for this integration, since Apple only enables the mobileme API (which this integration uses) for your account after you have used it on a device at least once. Usually they show a different error in this case, but they seem to like switching up the error messages every once in a while. There's a little more info about this issue here: [#102](#102) — Reply to this email directly, [view it on GitHub](#120 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AJDRWEKZRDYFK3TUGOQYO232WMDN7AVCNFSM6AAAAABZRBTV3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJVG43DOMZRGI). You are receiving this because you authored the thread.Message ID: ***@***.***> [malmeloo]malmeloo left a comment [(malmeloo/FindMy.py#120)](#120 (comment)) Your log seems to be absolutely cluttered with errors from this integration, but one of them caught my eye. The rest are most likely caused by this error and raised due to bad error handling from me. findmy.errors.UnhandledProtocolError: com.apple.mobileme login failed with status 1: Account limit reached. This most likely means that the Apple ID you are using has never been used on a real Apple device. That's unfortunately required for this integration, since Apple only enables the mobileme API (which this integration uses) for your account after you have used it on a device at least once. Usually they show a different error in this case, but they seem to like switching up the error messages every once in a while. There's a little more info about this issue here: [#102](#102) — Reply to this email directly, [view it on GitHub](#120 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AJDRWEKZRDYFK3TUGOQYO232WMDN7AVCNFSM6AAAAABZRBTV3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJVG43DOMZRGI). You are receiving this because you authored the thread.Message ID: ***@***.***>

[aaronjrodrigues]

whoops my bad thanks

Oh also, I can see your email in at least one of the logfiles. Not sure to what extent you want to keep that secret, but you might want to remove them.