search

Daanoz / ha-google-photos

Home Assistant Google Photos integration
MIT License
87 stars 7 forks source link

Integration stops working on March 31, 2025 #64

Open Daanoz opened 2 weeks ago

Daanoz commented 2 weeks ago

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 commented 2 weeks ago

@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 commented 2 weeks ago

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 commented 2 weeks ago

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

cannondale0815 commented 2 weeks ago

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 commented 1 week ago

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 commented 1 week ago

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 commented 1 week ago

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 commented 1 week ago

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 commented 1 week ago

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:

Then restart HA.