Nest to turn off their API

Blog
97

@Corey_Maxim @Matt112

You can try copying the entry from the old .storage/core.config_entries file into the new one, but you have to be careful how you do it. The file is JSON formatted, so you have to copy it into the correct place, and you have to be careful about whether or not the entry should end with a comma. (Basically, if you put it at the end then it should not have a comma at the end. And if there are any other entries after it then it should have a comma.) So…

{
    "data": {
        "entries": [
            {
                "connection_class": "cloud_push",
                "data": {
                    "impl_domain": "nest",
                    "tokens": {
                        "access_token": "REDACTED",
                        "expires_in": 315360000
                    }
                },
                "domain": "nest",
                "entry_id": "7aec0ca1587246ea8d822fb23588a773",
                "options": {},
                "source": "user",
                "title": "Nest (via configuration.yaml)",
                "version": 1
            },  <== REMOVE THIS COMMA IF THIS IS THE LAST ENTRY IN THE LIST
                    OR ADD A COMMA IF IT IS NOT THE LAST ENTRY AND THERE'S NO COMMA
        ]
    },
    "key": "core.config_entries",
    "version": 1
}

I’m not sure about the other Nest related entries from the other files in the .storage folder. That may be enough for it to discover everything again. (I’d try just that and see how it goes.) If not then you may need to copy the Nest related entries from .storage/core.device_registry, and maybe even .storage/core.entity_registry.

5 Likes