09-05-2016 02:24 AM
Downloaded Wemo 1.15.2 from the google play store to a Samsung T989 phone, running 4.1.2.
I tried set up an insight switch. The new app connected and ran through the setup and reported "remote access enabled".
Then, starting the Wemo app, "looking for devices" is displayed. The program is unresponsive after that, no devices are found, and the "looking for devices" screen will stay there forever.
I uninstalled 1.15.2, and found an earlier version with a google search (1.13.x), installed it, and when I opened the app, all 3 of my wemo switchs were found and displayed.
09-05-2016 02:35 AM - edited 09-05-2016 09:03 AM
I'm getting this too. Check out my post. http://community.wemothat.com/t5/WEMO-Application/Looking-for-devices-Thats-all-I-get-after-the-late...
Fortunately, I'm wise to Belkin's updates and I've reinstalled the previous version from a backup apk file and like you I've found that it works again.
09-09-2016 07:16 AM
What's the Android version of your device? The newest version of the app will only run with Android 4.1 or higher.
09-13-2016 07:18 AM
May we know what error message are you getting in your Galaxy S2? What is its Android version?
09-13-2016 08:32 AM - edited 09-13-2016 08:33 AM
I have a T-mobile Samsung Galaxy S2 Model SGH-T989
It has Android 4.1.2, Baseband T989UVMC6.
It waits forever at "Looking for devices" running wemo v1.15.2.
It also has stopped at the instruction to disable Smart Network Switching, but that android version does not offer that option.
It's also case #07010019.
09-13-2016 02:28 PM
There is a bug open for this and the development team is working on a fix. If you call or write in the same information will be given.
I don't have a date for the fix release but I'm pushing for it to be done as quick as possible.
09-13-2016 06:30 PM
09-14-2016 12:40 PM
Thanks for that, Robert_S
It's good to know that you're on the case. BTW I've unsubscribed from the other threads reporting this issue, but have received no reply after submitting system information as requested.
Is anything being done regarding those who can't even download the latest version 1.15.2 because it's supposedly incompatible with Android 4.1.2?