cancel
Showing results for 
Search instead for 
Did you mean: 

Android Unleashed app update

Alleprt
New Contributor II

The Android app has not been updated since the release of Unleashed 200.19. After updating to 200.19, when I click any Wi-Fi network, the app drops to the login screen, and I have to log in again. And the process repeats. I cannot control networks with it now. Can you please fix it?

25 REPLIES 25

DaJoJo
New Contributor III
Sanjay,
It works. Can see my R510's have firmware 200.15 now. Firmware update also wasn't working properly before. Lots of try and error, but now it fast and working. Thank you for your time to adres this issues.

Hi @Alleprt,

We have done a speculative fix as we were not able to reproduce the problem will release in couple days.
I will keep you posted once the update is pushed.

Thanks, Sanjay. I will update the app as soon as it's released to Google Play (it's not there yet). Don't you guys have a device with Android 16 for testing? I suspect the Android changes cause this issue. There is a review now on Google Play that describes exactly my issue. I am not the only one who has it.

P.S. And how did this thread end up on Lennar support? When I was posting it, I selected Unleashed. I didn't even know what Lennar was until I googled it.

Hi @Alleprt,

Thanks for the update, I have already reported the new comment in playstore to the team.

About the thread moving to Lennar, I'm not sure on that. I can look into it.

DaJoJo
New Contributor III

Pretty much automatic response. It's Unleashed and in a home environment, so it get automatically treated as Lennar home.
I just checked the app to make a new wifi network, this now works instead of giving errors like before. The only downside is the wifi network doesn't show up in the wifi network list. Made a screen recording.

room1 is an existing wifi i made in the web-interface. blablatest the new in the app itself. 

screencap 

edit: seems to me a variable doesn't get parsed properly. wifi name is not showing in the popup. Probably also related to @alleprt's issue.