With 2.0 are we supposed to see two Mobile App devices?

Just upgraded to 2.0, and first of all - amazing work, it looks awesome.
After the upgrade, I’m seeing two separate devices for the mobile app integration (with just one phone). Both have an identical name, but only one of them contains all the entities.
This is what I’m seeing in my device registry config:

{
    "area_id": null,
    "config_entries": [
        "SAME_AS_OTHER_DEVICE"
    ],
    "connections": [],
    "id": "XXX",
    "identifiers": [
        [
            "webhook_id",
            "XXX"
        ],
        [
            "device_id",
            "SAME_AS_OTHER_DEVICE"
        ]
    ],
    "manufacturer": "Apple",
    "model": "iPhone Xs",
    "name": "My iPhone",
    "name_by_user": null,
    "sw_version": "12.4.1",
    "via_device_id": null
},
{
    "area_id": null,
    "config_entries": [
        "SAME_AS_OTHER_DEVICE"
    ],
    "connections": [],
    "id": "XXX",
    "identifiers": [
        [
            "mobile_app",
            "SAME_AS_OTHER_DEVICE"
        ]
    ],
    "manufacturer": "Apple",
    "model": "iPhone Xs",
    "name": null,
    "name_by_user": null,
    "sw_version": "12.4.1",
    "via_device_id": null
}

Is this the normal behavior?

I just noticed the same last night after I finished migrating my iPhone to 2.0…looks weird.

It’s normal. No idea why though.

I used IOS 1.0, V2.0 Beta and now the new 2.0. There are a total of 6 iphones in the integrations page now, instead of 1. I don’t know which ones to delete…

Additionally; is there any use for .ios.conf file now? Is it safe to remove it?

Reset the app, delete all the integrations, del ios.conf, restart HA, run the app again, restart HA again.

1 Like

.ios.conf can be deleted but you will see an warning in logs relating to ios.notify service being started but no devices configured. Hopefully we will fix this pretty quickly. It can safely be ignored anyway

Odd I don’t have that service… or that error… but I also don’t have ios: in my config. Wonder if that’s why?

Check that you cleared out the IOS integration per the docs. I made the transition and don’t have those errors.

I’m rather familiar with that guide :wink:

I should have said may not will sorry. I believe it is set up dependent.

I’ve asked this question already during the beta testing

there is as well a fix in that thread.

1 Like

Thanks! Feels a bit like cheating, though. I wonder what’s the intended behavior.

It is a known issue but I believe would involve breaking changes to other apps that use the mobile_app integration