Strange behavior with remote access and mobile app access - no rooms, devices, scenes, etc.

[robertg 2]

Recenty I experienced a strange behavior - it starts when my mobile app (iOS) refuses to connect to my HC2 via the remote access. I have a VPN setup and when the problem occurs mobile app is not able to connect to the local HC2 via VPN tunnel. At the same time, when connecting via browser and remote access it allows me to connect and login to my HC2, but displays an empty page (just the general layout is there - see attached screenshot). I can operate HC2 locally via the browser and can restart it - restart actually solves the problem.

 

I did get in touch with Fibaro support and had one of the support guys ssh'ed to my HC2, but the only thing he was able to do was restarting some services and was not able to say anything about the root cause and long term solution. 

 

Anyone seen such behavior before? I am running v3.600 and this problem happened now for the second time today (previously it happened two days ago).

Please login or register to see this attachment.

[MalvinYNJ 4]

Face that quite often too. After you restart, it will work fine for awhile and back to this soon after right?

 

I took out all of the scenes that were running background and updated its version and now it's slightly better.

[djtonsil 0]

Just to confirm, I experience exactly the same. After a couple of accesses from the mobile app, the remote access doesn't work anymore. Local access still works and rebooting HC2 solves the problem (remote access is possible again).

 

I'm running HC2 with 4.035.

 

To resolve the problem while I'm out I tried to configure an automated reboot. I have a reboot scene that works fine when I run it. But when I created the 2nd scene that should trigger the reboot scene regularly based on the timer, it is never triggered.

 

Does anyone know if purely timer based scenes actually work (they don't in my case)? Do scenes always need a triggering device in addition to the timer?

 

Either way, I think Fibaro should offer scheduled reboots as a critical reliability function given the instability of the remote access.

 

-djtonsil

[necrosis 1]

I have exactly the same issue! Just randomly stops working multiple times a day. System unresponsive. Needs a reboot to function again. Very annoying as my setup is unreliable.

[djtonsil 0]

Fwiw, I managed to get the automated reboot scene working and I hope that this way I manage to reconnect from time to time remotely.

 

E.g. yesterday remote access stopped working until the box automatically rebooted again today after which I could access it again.

 

@robertg: I saw exactly the same screen through browser based remote access until it completely dropped off and wasn't remotely accessible anymore at all.

 

Last time this happened when I was there (local to where the box is), remote access stopped working but the box itself and local access was still working. So it seems to be exactly the same like you describe.

 

In both cases the reboot seemed to solve the problem and I stick to daily reboots now although that shouldn't be the solution.

[robertg 2]

Fwiw, I managed to get the automated reboot scene working and I hope that this way I manage to reconnect from time to time remotely.

Could you maybe share some LUA code that you use for this reboot scene? I will probably need to have one on my HC2 as well. Luckily it seems to function OK for the last 5 days so fingers crossed (although I did not make any changes so it is still random problem).

 

Forget the first part - found it already in another thread

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" /> 

Please login or register to see this link.

[necrosis 1]

I also tried the rebooting script. But when it hangs in between reboots the script is not going to be triggered, so this renders it useless (at least in my setup).

 

What I have done is remove all my old backups (two remains), and it has been running for almost a day without any hickups.....

 

Can others try and confirm this?

[necrosis 1]

Well seems to still die on me... Also no way to look at a log file to investigate what is going on? This is starting to get annoying pretty fast.

[djtonsil 0]

@necrosis:

Is your box freeze/crash related to remote access at all? It doesn't sound that much like it if your box gets totally unresponsive even if connected locally. With a somewhat unreliable firmware I'd think about using a physical power time switch to reboot the box regularly independent of relying on the box to be able to logically reboot itself. That's not how it should be but a workable solution until Fibaro gets its Firmware more stable.