Android App - Unable to connect remotely after local access

[Guest cberbecaru]

I'm facing a very strange issue with remote connection on Android app which drives me crazy from over a month. I have several Android phones which all behave in similar manner:

 

HTC One M8s, Samsung Galaxy S6 both on Android 6

HTC One M7 on Android 5

 

The problem is that remote connection will not work anymore AFTER a successfully local connection, failing with "Invalid login or password" message. There are 2 situations:

 

1. Install the app while connected to LAN. It will connect locally, but it will NOT connect remotely after that

2. Install the app while on mobile network. It will connect remotely and stay on remote connection even when connected to LAN. As soon as the Settings/Choose HC is opened, a toast pops: HC IP address updated, and after that no more remote connection is possible

 

Obviously the problem is not in the configuration of remote access because the app can connect remotely.

 

I used an app to sniff the requests made by the app and here comes the strange thing: While in mobile network (or other network), the app make a request to dom.fibaro.com which is successful, but after that, for some reason, it will try to login to the LOCAL IP (192.168.1.200) while on foreign network, which, of course fails. The above happens only after a successful local access (that is, after the IP update thing).

 

I used to stay on remote to circumvent this problem, but since I added 2 cameras to the system this is no longer feasible.

Edited October 11, 2016 by cberbecaru

[Manny 0]

On 11/10/2016 at 2:32 AM, cberbecaru said:

I'm facing a very strange issue with remote connection on Android app which drives me crazy from over a month. I have several Android phones which all behave in similar manner:

 

HTC One M8s, Samsung Galaxy S6 both on Android 6

HTC One M7 on Android 5

 

The problem is that remote connection will not work anymore AFTER a successfully local connection, failing with "Invalid login or password" message. There are 2 situations:

 

1. Install the app while connected to LAN. It will connect locally, but it will NOT connect remotely after that

2. Install the app while on mobile network. It will connect remotely and stay on remote connection even when connected to LAN. As soon as the Settings/Choose HC is opened, a toast pops: HC IP address updated, and after that no more remote connection is possible

 

Obviously the problem is not in the configuration of remote access because the app can connect remotely.

 

I used an app to sniff the requests made by the app and here comes the strange thing: While in mobile network (or other network), the app make a request to dom.fibaro.com which is successful, but after that, for some reason, it will try to login to the LOCAL IP (192.168.1.200) while on foreign network, which, of course fails. The above happens only after a successful local access (that is, after the IP update thing).

 

I used to stay on remote to circumvent this problem, but since I added 2 cameras to the system this is no longer feasible.

 

I have the same problem and I think ids a problem in the definition of the IP address

 

[Guest cberbecaru]

Migration to the new Fibaro ID solved the problem, so try to update. Actually, the new version of the mobile app solved it, not the new ID system .

[Manny 0]

I have the latest version, installed yesterday (1.12.0.1) and I cannot connect to the system once I leave the WiFi network. Not working

[fibarojiang 0]

You upgrade the app to the latest try

[DinoKustas 1]

Unfortunately this has began to happen for me again since the latest version of the app was installed.

 

Tried all the usual re-configuring the application, removing, reinstalling etc. Exact same issue as before, works on home WiFi (where HC2 is) works on other WiFi at other locations, get access denied over 4g.

 

[Guest cberbecaru]

IT IS HAPPENING AGAIN !!!!!

 

Fibaro please hire some programmers. Real ones.

[[email protected] 0]

I am not sure if this is related to this stream but I am using a Samsung S6E and although it connects, I only get to operate the last two button which are settings and help - all others are operators are greyed out. I can log in remotely using Fibaro ID to the same device via explorer but really want to have the app working for my client. Any thoughts please?

[Guest cberbecaru]

Fibaro, nothing ??? It worked, so it must be a source control issue, someone overwriting the fix...

Edited June 6, 2017 by cberbecaru

[jakub.jezek 370]

I just tested it and it works for me smoothly. Tested version 1.15.0.1 beta.

 

Tested scenarios:

• App in foreground:
  • on WiFi -> Try to control device ->Turned WiFi off -> Try to control device -> success
  • on LTE -> Try to control device -> Turned WiFi on -> Try to control device -> success
• App in background
  • on WiFi -> Try to control device ->Turned WiFi off -> Try to control device -> success
  • on LTE -> Try to control device  -> Turned WiFi on -> Try to control device -> success
• App killed
  • on WiFi -> Try to control device ->Turned WiFi off -> Try to control device -> success
  • on LTE -> Try to control device -> Turned WiFi on -> Try to control device -> success

 

 

[Guest cberbecaru]

That's weird, it doesn't worked when I started the thread, then it worked for a while when they introduced Fibaro ID, and then stopped again after last stable update (I think 1.14 or so). On this release (1.14) app also crash from time to time when I try to connect on 3G. I'll give a try to the beta ...

 

Edit: Just tested scenario 1. Crash after turning off WiFi

Edited June 6, 2017 by cberbecaru

[Guest cberbecaru]

Well, tried on 1.15 stable just released and still not working. What the heck is going on?

[T.Konopka 8]

@cberbecaru, are you using public IP address with forwarded ports in the app to connect with Home Center?

[Guest cberbecaru]

10 minutes ago, M.Baranowski said:

@cberbecaru, are you using public IP address with forwarded ports in the app to connect with Home Center?

 

No, UPnP

 

Sir, the symptoms are exactly the same as I described in the OP. At one time (after I started the thread), the app suddenly worked, and I think this was when you introduced Fibaro ID. Then, after last stable update, it failed again, but this time with the app crashing.

Edited June 9, 2017 by cberbecaru

[T.Konopka 8]

@cberbecaru, we need do have a closer look into your system. Can you please send me PM with ports 22 and 80 forwarded? Thanks to that, we will be able to analyze it directly.

[Guest cberbecaru]

18 hours ago, M.Baranowski said:

@cberbecaru, we need do have a closer look into your system. Can you please send me PM with ports 22 and 80 forwarded? Thanks to that, we will be able to analyze it directly.

 

Done.

[dimoulias 0]

Same problem for me only in android.

I agree with cberbecaru that the problem is only in the app because the android widgets works perfect in 4g but the app don't.

I have vodafone but i tried my sim in iOS and works with no problems.

 

Edited July 1, 2017 by dimoulias

[Guest cberbecaru]

After updating to 1.16.0 and some fiddling, the app works again. Thank you!

 

EDIT: False alarm  it works only if I set it up while connected to mobile data, but at least the HC IP does not auto change in this version, so I can live with that.

Edited August 8, 2017 by cberbecaru

[dimoulias 0]

cberbecaru in 4G you must go every time to settings and delete the updated ip and then save to reconect for remote acces.

hope next update be the correct one.

Edited August 11, 2017 by dimoulias

[Lenny212 2]

I too am not able to connect remotely - seems to be an intermittent issue with no obvious trend. Needed it for the first time today in a real life issue, instead of playing, and it failed. Had to leave work 2 hours early and drive for an hour to let someone into my house.

Can someone explain the comments about opening ports and if I need to do anything here? I would have thought the fibaro system would manager that.

Samsung S5

Android 6.0.1

[DinoKustas 1]

Personally getting fed up of the Android app with this intermittent connectivity issue. It's really not acceptable for something that costs so much. 

 

I'm now always carrying my work iPhone because that never has connectivity issues, because clearly more time has been spent on that app...