So, it seems to be a specific problem with very specific phones. I don't know if this is significant or not. cc / thirdparty / oauth-page / google / ewelink-google.html# / loginĪs you can see, the "called" domain name is absolutely different to the ones shown above. Nevertheless, on the Pixel and the Motorola, The url that actually gets open when tapping the "Connect eWeLink Smart Home" button at the top of the "Google Home" app is: this one (again, added spaces): Nevertheless, if I try to link again or reconnect the third party apps (Smart Life or eWeLink or any other from the large list on Google Home app), any of those will give me a "could not reach." message.Īnother interesting thing I have found: Using the app eWelink as a testing example: if I go to phone's Settings -> Apps, then look for eWeLink, tap on it and go to the "Defaults section", tap the "Set as default" on the next screen tap "Supported web addresses", I do get displayed: (I added the spaces, the domains are displayed correctly with no spaces): I finished configuring all the new devices using my Pixel, when I finished, all new setup and new devices everything, actually reflected on the S22+ upon syncing the devices on Google Home. ![]() The problem only happens in my Samsung Galaxy S22+, using the same Google account in all devices. but, I stopped configuring there and went to my other smartphone, a Google Pixel, using my same Google account as on the S22+ it worked perfectly fine there as well. ![]() then it occurred to me to try it on my wife's Moto phone and voila! it worked great. On the Galaxy S22+ I always get a "could not reach APP. I just experienced the same situation exactly: On my Samsung S22+ I was unable to link to any third party "Works with Google" app to setup any of a myriad of devices on Google Home despite having used that third party app to configure the device itself into my WiFi network and making sure the device works with their own app (Smart Life or eWeLink.for instance). (The one with the "G" logo.) Backing out of the Google app beta in Play Store, uninstalling the Google app updates, then updating it until I had a 13.47 version instead was the workaround that worked for me. The Kasa/TP-Link app works to control the plug I'm trying to add.ĭevice is a Pixel 4a, on Google Fi using ESIM.įinal update: Thread, and my own experience, indicate this is caused by a 13.48/beta build of the "Google" Android app. Device control for Works with Google devices/services I set up previously is working well, from Google Home app and elsewhere, but the related linked services were authorized w/ Google prior to this problem. I'm not having networking-type issues with other apps. I do have an unused SIM card in the phone, haven't tried ejecting it, but that's been there better part of a year. I've tried toggling network connection (LTE vs Wi-Fi vs. There was no Google Home app update available. ![]() Please try again." This appears to be systemic - it doesn't matter which service I tap, Kasa or otherwise, the app claims they're all unreachable. Wondering if there is any workaround info or known issue information about a behavior I'm seeing: when trying to add a new "Works with Google" device (Kasa/TP-Link) in the Android Google Home app, when on the screen where I search/select a linked service to add, tapping a service flashes the screen momentarily then shows a toast that says "Could not reach (name of service here).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |