2.0 creating two devices

The 2.0 Beta app is creating two devices under integration

one contains all sensors the other is empty

https://companion.home-assistant.io/en/next/troubleshooting/beta-cleaning

this I did already but still get two devices (but sensors are only available for one device)

My problem is also like this, and it does not automatically create the file known_devices.ymal.

The Beta app does not use known_devices.

Which file does the Beta app use?
I can’t find my phone in service…:disappointed_relieved:


did you restart home assistant after connecting with the beta app?

Reconfigure home assistant
restart home assistant multiple times
restart app multiple times
restart raspberry pi multiple times

I have tried the above operations.

I had the same issue. Fixed it this by manually editing .storage/core.device_registry by removing the extra entry for my iPhone and adding the “mobile_app” entry to “identifiers”:

            {
                "area_id": "foo",
                "config_entries": [
                    "foo"
                ],
                "connections": [],
                "id": "foo",
                "identifiers": [
                    [
                        "device_id",
                        "foo"
                    ],
                    [
                        "webhook_id",
                        "foo"
                    ],
                    [
                       "mobile_app",
                        "foo"
                    ]
                ],
                "manufacturer": "Apple",
                "model": "iPhone 8 Plus",
                "name": "foo",
                "name_by_user": null,
                "sw_version": "13.1.3",
                "via_device_id": nulltype or paste code here
            }
2 Likes

great idea. it works

Thanks, looks like you’re onto something!

These are my two entries in that file:

            {
                "area_id": null,
                "config_entries": [
                    "HASH...1312"
                ],
                "connections": [],
                "id": "HASH...ae36",
                "identifiers": [
                    [
                        "webhook_id",
                        "HASH...88f43"
                    ],
                    [
                        "device_id",
                        "HASH...626d"
                    ]
                ],
                "manufacturer": "Apple",
                "model": "iPhone 11 Pro",
                "name": " iPhoneee",
                "name_by_user": null,
                "sw_version": "13.2.2",
                "via_device_id": null
            },
            {
                "area_id": null,
                "config_entries": [
                    "HASH...1312"
                ],
                "connections": [],
                "id": "HASH...a33a2",
                "identifiers": [
                    [
                        "mobile_app",
                        "HASH...a626d"
                    ]
                ],
                "manufacturer": "Apple",
                "model": "iPhone 11 Pro",
                "name": null,
                "name_by_user": "iPhone",
                "sw_version": "13.2.2",
                "via_device_id": null
            },

If I’m going to do what you suggest, I think I’m suppsod to remove the first entry, which is the one without the “mobile_app” identifier.
However, the last entry is missing both the device name (iPhoneee) and also the “webhook_id” identifier, and I’m not sure if those are needed?

Guys, don’t mess around in .storage for this UI issue. There’s already a backend fix for it and it’s probably going to be in 0.103

As olbjan notes, be very careful editing any files in .storage. It’s advisable to make a backup before editing. But if you don’t want to wait until the next release and you’re comfortable with editing JavaScript, I would cut mobile_app from identifiers in the second entry and paste it into identifiers in the first entry, and then delete the second entry.

0.104 is out and the duplicate entry is still there. I guess that the fix wasn’t retroactive?

I removed my mobile integration a week or so ago and re-added it and I only have one entry now. So I do not think so.