Sharing automations with ambiente options (3rd party scenes) included

[aschuetze]

In my case i'm trying to add Yeelight scenes for both home members. Even with the latest revamped version of Google Home app there is no way getting it working with just one account linked to the 3rd party account!

Let's say having member A linked to 3rd party Yeelight account and creating an home automation with Yeelight ambient scene included. The automation gets shared to member B who can access it, but the Yeelight ambient scene is missing in it, as 3rd party Yeelight account is not linked to Google Home account of member B! Linking that 3rd party Yeelight account to Google Home account of member B too, leads to the circumstance that whoever of the two members is saving the automation with Yeelight ambient scene included can run the automation. The other members Google Home automation (which should be exactly identical, as it's a shared one) the Yeelight ambient scene gets deleted! So sharing of 3rd party ambient scenes (at least tested with Yeelight for now) doesn't work - the new automation editor doesn't support 3rd party ambient scenes anyways and the old ones show the before mentioned behavior.

To make things even more complicated once again I tried the following. Sharing the Yeelight devices and scenes from Yeelight account of member A to a new Yeelight account of member B. Linking Yeelight account of member A to it's Google Home account and Yeelight account of member B to Google Home account of member B. When sharing home automation with Yeelight ambient scene, i still get the same result as before. The account that saves the home automation can run it, the other account the Yeelight ambient scene gets deleted - although this scene is now linked to two different 3rd party Yeelight accounts!

The only working way i found for now: creating personal automations for both members that include Yeelight ambient scenes linked to their own 3rd party Yeelight accounts!

Btw. almost forgot to mention the most "funny" thing out of it all: my guests, of course not part of my home and therefor without any account or voice match on my smart speakers can voice control my automations with Yeelight ambient scenes without any problems. Sounds absolutely logical to me *not*!

Google, there's a looooong way to go!!! 

[kcruzgonzalez]

Hello @aschuetze,

Thank you for posting on the community and clearly detailing the issue you are having with sharing automations that include third-party scenes from Yeelight. You have done excellent, thorough testing to isolate the problem, where a specific action within a shared home automation is either inaccessible or deleted from other members.

Given the extensive testing you've already done, we need to focus on two things: making sure all linked services are properly refreshed and checking the exact nature of the scenes.

Scene Type Clarification:

• Are the Yeelight scenes you are using (the "ambient scene") a static scene (a fixed color and brightness) or a dynamic scene (like "Sunrise" or "Candle Flicker" that changes over time)?

Unlink and Relink the Yeelight Service:

• Although you have tried linking and unlinking the individual member accounts, a clean unlink of the entire service often resolves lingering permissions or linking issues.
• Have both members unlink the Yeelight service completely from their Google Home accounts:
  • Open the Google Home app.
  • Tap your profile picture (or initial) > Assistant settings > Devices (under "Home control").
  • Find and select the Yeelight service (or the device group it belongs to).
  • Select Unlink Yeelight.
• Have Member A (the primary setup account) link the Yeelight service back first.
• Have Member B link their Yeelight account immediately after.
• After both are linked, ask Google Assistant to "Sync my devices" to ensure the new connection is registered everywhere.
• After this fresh relink, try creating one shared automation again to see if the deletion behavior has stopped.

Please let me know the type of scene you are using and if the full unlink/relink steps improve the stability of your shared automations.

Regards,

Kevin

[aschuetze]

Hello Kevin,

thanks for replying.

I spent the last 5 hours with unlinking, linking and synchronizing forth and back. Sorry to say, but without any success. I tried every possible combination once again - always with unlinking Yeelight account before and also shutting down Google Home app and clearing cache in between. I have no single sign of any working combination, besides linking every Google Home account to their separate Yeelight accounts and creating personal routines.

No matter what, every combination involving the linking of separate Yeelight accounts will lead to double devices in my Google Home.

After doing some deeper research on sharing routines i found that this problem is already discussed online since 2022 without any development by Google. Sad to see, that spending so many time the last weeks may lead to nothing again. Only solution seems to be a workaround by setting up Samsung smart things and linking everything from there to Google Home. 😞

Please prove me wrong. 😉

To answer your question: We are talking about static scenes with and without customized but fixed colors and brightness.

Alex

[kcruzgonzalez]

Hello @aschuetze,

Thank you for your response and for confirming the details after your troubleshooting. I am sorry that you spent many hours trying every combination without success. Given that you’ve tried unlinking/relinking, clearing the app cache, and confirming the issue with static scenes.

Based on your findings and similar reports, the most reliable conclusion is that the sharing mechanism for third-party scenes within Household Automations is currently limited in this way.

Your working solution of creating personal automations for each member, each linked to their respective third-party account, is the most reliable way to achieve shared functionality at this time.

The most constructive step we can take from here is to ensure your detailed feedback is formally logged with the development teams. This issue touches on core account linking and sharing functionality that needs to be more seamless.

Please submit a formal feedback report directly through the Google Home app:

• Open the Google Home app.
• Tap on your Profile icon (top right).
• Tap Help and feedback.
• Tap Send feedback (at the bottom).
• In the description, explain the issue exactly as you did here (shared household automation, Yeelight static scene disappears for other members, even with multiple linked accounts).
• Ensure you check the box to "Include system logs and diagnostics," as this provides the developers with the specific data from your home structure.

We appreciate your time isolating this problem. By submitting this detailed feedback, you are directly contributing to the resolution of this experience in a future update.

Regards,

Kevin

[aschuetze]

Just a quick follow-up to my temporary solution until Google will break everything once again. 

One should know, that activating scenes by voice command "activate scene" is still working, but is limited as soon as you enable voice match on your device and have a second member in your home that can't use your shared automation then. Workaround is to create automation with customized voice command to start your scenes! Don't use automation with Ambiente scene!!! as it gets interfered as soon as you're linking to a second 3rd party account of same manufacturer or use voice match.

• link Google Home account of member A to 3rd party account of member A and sync all devices
• create automation with custom voice command for your scene "activate scene", not ambient scene!
• link Google Home account of member B to 3rd party account of member B (before you have to share you devices from 3rd party A to 3rd party B!) and sync all devices
• voice command scenes AND voice match should work now for both members! 

What happened to me and I cannot explain exactly: when linking Google Home account of member B to 3rd party account of member B, I usually had to add the devices to rooms again and then I had every device twice (member A and member B). I then did add all devices of member B into a completely new room (called the member room) and voice command for scenes was already working, but I still had virtually twice as much devices as in reality. So I tried unlinking Google Home account of member B with 3rd party account of member B and linking Google Home account of member B to 3rd party account of member A once again. Of course, I got the same problems as stated in my posts before (you simply can't link one 3rd party account to two Google Home accounts at the same time, it will always mess things up). So I re-linked Google Home account of member B to 3rd party account of member B and this time every device was already added the same way to it's room as setup by member A! No device occurred twice and number of virtual devices match theirs in reality. For now everything seems to work as expected. Sometimes Google assistant tells my "one or more device is missing" when starting a scene, but this it totally random! The next time the scene gets started without any reply or missing statement... That's Google...

[aschuetze]

The last missing bit: 

When adding 3rd Party account of member B to Google Home account of member B all it's devices need to be added to rooms and you'll have twice as much of your devices.

• unlink 3rd party account of member B from Google Home account of member B
• link 3rd party account of member A to Google Home account of member B and all devices are already added to their rooms like member A set it up before
• unlink 3rd party account of member A from Google Home account of member B
• link 3rd party account of member B to Google Home account of member B and all devices still stay in their rooms like setup before by member A

Finally you have two Google home accounts linked to their 3rd party accounts but without having every device twice in your home! 

Sometimes you're still getting crazy answers about missing devices, but everything works as expected and it's still Google... Let's see how long this findings may last.