The recent upgrade broke Google home commands, so I have to use the app instead of the Google home voice commands
Any idea how long this is going to take to fix it? Sorry, I’m lazy…
What, specifically, is broken? Also, what are the answers to the questions I asked in your other recent topic?
Again, without additional detail about your experience and what you’ve attempted so far, providing assistance here is going to be difficult for anyone who wants to be helpful.
I’m still able to control my Wyze lights and locks (e.g., Bulb Color, Bulb Color v2, Light Strip, Palm Lock) by talking to Google Assistant on smart speakers, so I’m not seeing evidence that something is broken with the integration.
1 Like
no wyze devices are working with GH … third party is setup. google home login is with [Mod Edit] but wyze is using [Mod Edit]
the wyze app works fine
thanks
[Mod Note]: Personal information has been removed for privacy and security reasons.
I believe you need to link or re-link your Wyze account to Google Home.
In the Google Home app, you’d tap the upper-right icon for your profile, then tap Home settings in the menu, then tap the Works with Google tile in the Services section, then find Wyze Home and go through the steps to link or re-link your Wyze account (using the e-mail address you use for Wyze) to Google Home. If the Wyze devices haven’t already been assigned within Google Home, then they’d need to be added to a “home” and to “rooms” within that home.
Given what you’ve shared here so far, I’m not sure where you are in this process.
1 Like
If that’s what you’re seeing when you authenticate to your Wyze account while attempting to link/re-link that to Google Home, then it appears that something goofy is happening with the browser hand-off back to the Google Home app after authenticating. I’d attempt this with a different device, if possible, or change your default browser and try again. It’s also possible that you could change a setting in your current default browser that might resolve this. What browser is your current default on the phone?
good news and bad … switching to chrome browser let me add my account to GH
I could unlock the lock from GH but when I tried to lock it again it asked for the PIN, I had the option to enable one one-tap unlock BUT when I clicked OK it said Something went wrong and it didn’t lock…
and just left it unlocked.
I’m hopeful!!
tom
1 Like
good news it has started working…the only thing that is not fixed is the Enable one-tap unlock …. we are getting closer and I am getting happier! LOL
1 Like
What were you using before? I’ve read of other Forum users having Wyze login difficulties with Edge and Samsung’s default browser unless they change something in settings like “allow links to open in external apps” (or something to that effect). I’ve set Firefox as my default Android browser for years and haven’t had these problems.
Progress! 
I was using Comet browser by Perplexity. It’s quite new …here’s what it says about itself
Comet is Perplexity’s own AI‑native web browser, built on Chromium, with Perplexity tightly integrated as a personal assistant for searching, reading, and automating tasks on the web.perplexity+2
What Comet is
-
Comet is a full-featured Chromium-based browser (like Chrome/Edge under the hood) with Perplexity as the primary search and answer engine.comet-help.perplexity+1
-
It is available on desktop and mobile (including iOS and Android) and is free to download globally.perplexity+2
-
There is also a Comet for Enterprise variant with additional security and admin controls for organizations.perplexity
Key capabilities
-
Built‑in AI assistant: Sidebar assistant that can summarize pages, verify claims, translate, find related sources, and answer questions about what you’re viewing.perplexity+2
-
Personal Search: Uses your browsing history (if you allow it) so you can ask things like “find that article about Thai elections I read last week” and get it back via natural language.perplexity+1
-
Browser commands: You can manage tabs and actions in plain language (e.g., “close my shopping tabs” or “open the docs I was using for my trip”).perplexity
-
Workflow automation: Comet Assistant can execute multi-step tasks such as researching options across sites, filling out forms, drafting emails, or preparing briefs from multiple pages.perplexity+3
-
Cleaner browsing: Integrated ad blocking and hybrid search results (traditional links plus AI answers) tuned for a smoother reading experience, especially on mobile.perplexity+1
How it feels different from a normal browser
-
Instead of manually clicking through search results, you “think out loud” (chat-style) and the assistant drives the browsing for you, keeping context over many steps.perplexity+2
-
Any page becomes interactive: highlight text to get instant explanations, ask for counterarguments, or request related reading without losing your place.perplexity
-
For power users and enterprises, it unifies research, task execution, and everyday browsing into a single environment rather than bouncing between apps and tabs.perplexity+1
Getting it and setting it up
-
You can download Comet from Perplexity’s site at the Comet download page (linked from perplexity.ai/comet and the Comet Help Center).comet-help.perplexity+2
-
After installing on Windows or Mac, you sign into your Perplexity account, optionally import data from another browser, and can set Comet as your default browser in system settings.comet-help.perplexity+1
If you tell me your OS and whether you’d want to replace your current default browser or run Comet alongside it, I can outline concrete setup steps tailored to your machine.
then it added…. Why Chrome worked but Comet didn’t
Most likely causes on Android include:
-
The Google Home app expecting Chrome or a Google WebView for certain OAuth/account‑link pages, and not fully recognizing Comet’s browser identity.
-
A redirect or pop‑up window in the device‑add flow that Comet is handling differently (e.g., blocked by settings, extensions, or an in‑app webview constraint).
-
A fragile vendor integration (Wyze, other smart‑home services) that only tests against Chrome and not third‑party browsers, so the “Link account / Add device” step fails to return the right token when Comet is used.
Because Comet is compatible with most sites and Chrome extensions but still not literally “Chrome,” some Google sign‑in or device‑linking workflows can behave differently until they’re explicitly tested and fixed by Google or the device vendor.
Practical workarounds
On Android today, the safest pattern is:
-
Use Comet for normal browsing, research, and AI‑assisted tasks.
-
When you hit a critical device‑setup or account‑linking flow (Google Home, smart devices, banking, etc.) that fails in Comet, temporarily switch to Chrome for that one task.
If you’d like, tell me:
-
The exact smart device/vendor you were adding, and
-
Whether the flow started in the Google Home app and then “opened browser,” or you started fully in Comet.
I can then suggest a concrete step‑by‑step path (e.g., starting from the Home app or Wyze app directly) that minimizes the bouncing between Comet and Chrome.
If one-tap would work I would be SO happy! 
I enter the passcode and the remember is checked but it doesn’t remember 
[Mod Note]: Personal information has been removed from the image for privacy and security reasons.
What PIN are you entering into Google Home? When setting up “One-tap unlock”, you must use the PIN you assigned to your Palm Lock (or whatever other lock you might be using) when enabling the third-party integration in the Wyze app.
- In the Wyze app, from Palm Lock’s main page, tap Settings ➜ Third Party Integration. Set or Reset a PIN here.
- In the Google Home app, tap your Palm Lock’s tile and then follow the on-screen instructions. When prompted to “Enter PIN” to verify and save for one-tap unlock, use the PIN you set in the Wyze app.
Note: If you want to enable one-tap unlock on a second phone using the Google Home app, you will have to repeat Step 2 on that phone. If you later wish to disable one-tap unlock and require a PIN every time you use Google Home to control the lock, then navigate to the lock’s main screen in Google Home, tap the upper-right Settings, and then toggle off One tap unlock.
I tested this with Palm Lock and Lock Bolt v2, and it worked as expected on two different Android phones.
I still no luck. What kind of phone are you using? Mine is a Pixel 10
thanks
These particular phones are a Motorola moto g⁷ running Android 10 and a Google Pixel 4a running Android 13, but I wouldn’t expect phone hardware or Android version to be a factor. They’re both running Google Home app version 4.13.52.0, as is my Pixel 6.
I’m on Android version 16 ….
Questions:
- What—exactly and with detail—isn’t working for you?
- Does the one-tap unlock feature in Google Home save the Wyze PIN for your Palm Lock?
- Are you able to lock and unlock your Palm Lock from its screen in the Google Home app?
- Are you still trying to use voice commands to Google Assistant for controlling the lock?
If your main hangup at this point is with #4, then I wonder if you need to adjust your expectations. In my experience—even with one-tap unlock enabled for a Wyze lock product within the Google Home app—if I ask Google Assistant on a smart speaker to lock a Palm Lock or Lock Bolt v2, then Google Assistant will lock the appropriate lock; however, if I ask Google Assistant to unlock one of those locks, then Google Assistant asks for my PIN (the PIN I set within the Wyze app for the lock in Settings ➜ Third Party Integration), and I have to say those digits to Google Assistant before it will unlock the lock. I believe this PIN requirement is an immutable safety/security feature.
When unlocking in Google Home I tap to unlock and it then prompts me for my passcode which I enter. The option to enable one-tap is checked and I enter the code and the door unlocks/locks
However when I tap to lock I am again prompted to enter the code … it never remembers/saves the pin.
It works every time but I would love to not have to enter the PIN … I am not using voice.
Basically it never saves the pin…
What troubleshooting have you done with the Google Home app? I’d probably consider clearing the app’s cache and data at the OS level and then trying to save the PIN for one-tap unlock again if you haven’t done that.
cleared the caches but same problem