Integration stops working on March 31, 2025

[Daanoz]

Due to Google Photo API changes announced by Google, this integration will stop working on March 31, 2025. The new API will only allow for the integration to access photo's and albums which are uploaded by the integration itself, which renders this integration useless in my opinion.

Alternatively, if you want Home Assistant to upload photos, and download them back again, starting from HA 2024.10, you can use the official Google Photo's integration.

[arcsur]

@Daanoz What about the picker API? Sure it is inconvenient making the user choose which photos to allow an app to see via the Google Photos App (URI/QR Code) but it still seems like selection of photos to "share" with an application would be feasible based on the information on that google announcement:

Migrate to the Picker API: If your app currently uses the Library API for photo selection from content not uploaded by your app, you'll need to migrate to the new Picker API to ensure a seamless user experience and enhanced security.

[Daanoz]

Yeah, as I understand it, it's like a one time access thing. So once the user selects "a couple" of photos, the integration can download/store them locally. To me that eliminates a lot of use cases as you would constantly need to update the photos by manually selecting them via HA. If you want something like that you could also just manually download the photos and place them in HA.

However, if you think it makes sense, you could see if the core integration is willing to take this on as a feature.

[Inglan]

This could be transitioned into showing photos from Google Drive if that isn't being removed as well...

[cannondale0815]

FYI -- the new official Google Photos integration that is available in 2024.10.0 (out now) cannot be configured until one removes this custom integration here (presumably due to exact same name).

Also, the official integration is only capable of uploading images -- sadly there is no way to manually grant it access to anything else in your photos library.

[AlenHodnik]

Your integration was one of the best. Hopefully I don't ask a stupid question, but would it be possible to change this integration without too much hassle to do the same as it did with google photo now with local folder?

[Inglan]

Your integration was one of the best. Hopefully I don't ask a stupid question, but would it be possible to change this integration without too much hassle to do the same as it did with google photo now with local folder?

Or a Google drive folder for the same functionality

[Daanoz]

Your integration was one of the best. Hopefully I don't ask a stupid question, but would it be possible to change this integration without too much hassle to do the same as it did with google photo now with local folder?

It's not a bad idea, and I think it should be possible. It will take some effort though for which I can't estimate when I have the time.

[trevornorcross]

FYI -- the new official Google Photos integration that is available in 2024.10.0 (out now) cannot be configured until one removes this custom integration here (presumably due to exact same name).

This is a problem right now - I can't even test out the new native integration (nobody can who has HACS installed) because the name on the custom integration is the same and overrides the native integration. Right now there is no way for me to even start to setup the native integration without removing HACS and all the integrations I use from that unless custom or native integration get renamed.

[Daanoz]

FYI -- the new official Google Photos integration that is available in 2024.10.0 (out now) cannot be configured until one removes this custom integration here (presumably due to exact same name).

This is a problem right now - I can't even test out the new native integration (nobody can who has HACS installed) because the name on the custom integration is the same and overrides the native integration. Right now there is no way for me to even start to setup the native integration without removing HACS and all the integrations I use from that unless custom or native integration get renamed.

Yeah it's quite unfortunate, but not much can be done... I can rename the custom integration, but then you (and everyone else who updates) loses all the current entities and settings. I don't think there is a way to do clean rename integration migration.

If you really want to run them side by side (and reconfigure this integration from scratch) you can rename the "google_photos" directory in the "custom_components" directory.
Take the new name, and update it in the following places:

• const.py, line 4
• __init.py__, line 19
• manifest.json, line 2
• services.yaml, line 6

Then restart HA.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[Inglan]

Your integration was one of the best. Hopefully I don't ask a stupid question, but would it be possible to change this integration without too much hassle to do the same as it did with google photo now with local folder?

I might fork or start another project with this at some point...

[Daanoz]

Your integration was one of the best. Hopefully I don't ask a stupid question, but would it be possible to change this integration without too much hassle to do the same as it did with google photo now with local folder?

I might fork or start another project with this at some point...

That's probably the fastest at this point, I have a bit of shortage in time recently. Happy to help if you have any questions, you can find me in the HA discord channel.

[splitsec2]

Due to Google Photo API changes announced by Google, this integration will stop working on March 31, 2025. The new API will only allow for the integration to access photo's and albums which are uploaded by the integration itself, which renders this integration useless in my opinion.

Alternatively, if you want Home Assistant to upload photos, and download them back again, starting from HA 2024.10, you can use the official Google Photo's integration.

Would setting up a new google account for use by the plug in and then do partner sharing with it get around this? Ie my_ha_photo_acct@gmail.com is tied to the add in, and then myaccount@gmail.com does a partner share with them?

[Inglan]

Due to Google Photo API changes announced by Google, this integration will stop working on March 31, 2025. The new API will only allow for the integration to access photo's and albums which are uploaded by the integration itself, which renders this integration useless in my opinion.

Alternatively, if you want Home Assistant to upload photos, and download them back again, starting from HA 2024.10, you can use the official Google Photo's integration.

Would setting up a new google account for use by the plug in and then do partner sharing with it get around this? Ie my_ha_photo_acct@gmail.com is tied to the add in, and then myaccount@gmail.com does a partner share with them?

Don't think so as I think the new API transitions to using the picker API, which allows users to be directed to google photos to pick what the website or app (integrating with google photos) can access.