Smart Life Linking to Google Home Failed

[jordi_al]

Hello everyone,

I have a critical linking issue that appears to be a server-side error. I am looking for any user who may have found an unofficial workaround, as official support is currently escalating the issue.

The Problem: I cannot link my existing Smart Life account (which has over 80 devices) to Google Home. After the Smart Life login screen, I immediately receive the error 'Could not connect.'

Definitive Proof: The error persists even after the Bridge Account Test (linking using a completely new Google account). This suggests the problem is server-side token corruption tied to my Smart Life user ID, not my specific device or Google account.

Troubleshooting Steps Already Performed (Please do not suggest these, as they have already been performed and failed):
Cache/Data: Cleared cache and data for both the Google Home app and the Smart Life app.

Password: Changed the Smart Life password to a simple alphanumeric one (no special symbols).

Browser: Changed the default mobile browser (using Firefox) to bypass the system cache.

Network: Tested the linking process using both Wi-Fi and mobile data (4G/5G).

Device: Tested the linking process from two different physical phones (ruling out device/OS bugs).

Reverse Link: Attempted to link from the Smart Life app (Third-Party Services) to Google Home.

Ghost Links: Manually unlinked the service via the Google account linking webpage.

Google Account: Tested the link with my main Google account AND a brand-new, fresh Google account (Bridge Account Test) - both failed.

My Question is: Has anyone with an identical server-side error (failing the Bridge Account Test) found an advanced, non-official workaround that does NOT involve deleting and re-adding all 80 devices?

[samAndrew]

Looks like it’s a server-side issue tied to your account. Some users had luck asking Tuya/Smart Life to regenerate their account token—it might be worth pushing support on that.

[jordi_al]

Thank you so much for the confirmation and the patience. This has been a great help! Now all that's left is to wait for the technical support's solution.

[Mausy14]

I had that same problem, with Smartlife aswell as Tuya app. Delete all bindings in the Home app. Including the Binded with Google switch 

I also changed the passwords on the smartlife and Tuya account. After about 7/8 times it finally bounded again

[jordi_al]

I have already tried all of those steps and it's still not working. I even went as far as creating a new Google Home account with a different user, but I kept getting the same Smart Life connection error.

I’m not getting any real help from technical support either; they are just giving me the runaround while weeks go by without a solution. It’s extremely frustrating

[Mausy14]

I know, still haven't got a solution

[jordi_al]

I'm in the same boat. I’ve been in contact with both support teams and the experience is frustrating. Smart Life support is basically passing the buck, claiming everything is fine on their end and blaming Google Home. On the other hand, Google Home support hasn't provided any real solution either, stuck in a loop of basic troubleshooting steps that I’ve already performed.
​It’s a complete stalemate. I have over 80 devices, so deleting everything and starting from scratch is not an option. Even though my 'Bridge Account Test' (using a brand-new Google account) failed—which clearly points to a server-side token issue—neither side seems willing to escalate this to their engineers for a manual reset.
​It feels like we are stuck in a loop where the two clouds refuse to talk to each other, and we are caught in the middle

[Mausy14]

Ik deel je frustratie! Wat bedoel je trouwens met 'helemaal opnieuw beginnen '?

[jordi_al]

By 'starting from scratch', I mean manually deleting and re-pairing all 80+ devices in a new Smart Life account, or factory resetting them one by one to see if a fresh start fixes the link.
​Doing this would be a nightmare. It's not just about the devices; I would lose all my current automations, scenes, and complex routines that I've spent months fine-tuning. That's why I'm pushing support for a server-side fix—re-pairing 80 devices is simply not a viable solution for a bug that shouldn't exist in the first place

[Mausy14]

That also didnt work. I downloaded the LSC app and put all my devices in that app because lsc is fortunally binding with google