Can'r reach the HC2 locally with web browser...

[Robrob 0]

Updated yesterday to 4.11 or whatever the latest version is called as I've had problem to access the system with my Mac/Safari. 

The only thing that happens it that the blue balls circle on the screen forever...

 

All my devices eventually can connect after adding new login using FIBARO ID. If I connect with my browser through Fibaros homepage and my FIBARO ID I can connect for a few seconds and make the equipment to change status etc. but after doing it once it's sooooooo slooooow that it's impossible to use. 

Why can't I connect directly to my HC2 over my own network any longer? 

What is the purpose of FIBARO ID to be honest? It have just messed up everything and slowed down connections. 

 

I've tried to delete cashes in the browsers and restarted everything but nothing seems to work. How am I supposed to write LUA code with a system that takes 15 minutes between and page change? 

 

It's usually a real pain doing upgrade with Fibaro stuff but I think they reach a new low this time. I'm think of throwing everything out the window....

 

 

[Guest FredrikKarlsson]

How come you are so sure this is related to Fibaro ID? 

Is it possible for you to connect when you are on you local network? 

Is the hc2 really busy doing something ? What is it doing?

 

[Robrob 0]

Hi

 

Everything started when I enrolled with Fibaro ID, that's why I see the connection. Everything works fine before. 

I can't get local access it seems but connection through Fibaros page and through ID I can connect but it's extremely slow.

All apps on iOS and Android works but I can't connect locally with a web browser. 

The HC2 doesn't seem to be busy at all. 

[Sankotronic 2,370]

@Robrob,

 

After upgrade did you leave it for at least an hour to do necessary conversions and internal things? Did you try to restart HC2 after that time and then connect again with web GUI? What was previous firmware on your HC2 before upgrade to 4.110?

 

I ask you all that because I also upgraded my HC2 from 4.100 to 4.110 and didn't have any problems afterwards, on the contrary it seems to work faster when connected locally with web GUI.

[andyp 6]

Have you tired using the Fibaro Finder - It might be as simple as your IP address for the HC2 has changed after the upgrade - mine did.

 

[Robrob 0]

I upgraded from 4.100 to 4.110.

I've restarted HC2 twice and it has been on for a long time in between. 

I've used the Fibaro finder and it shows the same IP as before and when you connect it starts and you can see the panel in the background but the spinning blue balls just continues forever. 

If I go through the Fibaro web site and connect remotely it works but is very slow.

[RH_Dreambox 189]

Quote

If I go through the Fibaro web site and connect remotely it works but is very slow.

 

Note that Fibaro ID has nothing to do with your local login. You can still login locally with your "old" super user password (ie. your e-mail address).

(I guess you did not change your local logon???)

[Sovereign 1]

I have the same issue as Robrob. How is it resolved?

[Sovereign 1]

Just now, Sovereign said:

I have the same issue as Robrob. How is it resolved?

 

On 2/12/2017 at 9:47 PM, Robrob said:

when you connect it starts and you can see the panel in the background but the spinning blue balls just continues forever. 

 

[Robrob 0]

My case is still ongoing with Fibaro support for more than 2 weeks now. They've connected many times through the ports as well as with Teamviewer. No, solution yet except that they say that it's a very unusual problem that is hard to fix. They will continue Monday again...

[Tran hieu 0]

I have same issue as you. So waiting new information from you.

On Ngày 25 tháng 02 năm 2017 at 4:08 PM, Robrob said:

My case is still ongoing with Fibaro support for more than 2 weeks now. They've connected many times through the ports as well as with Teamviewer. No, solution yet except that they say that it's a very unusual problem that is hard to fix. They will continue Monday again...

 

[Robrob 0]

They continued the investigation and connected again. Then they just mailed me and said that I have a very unusual problem and they don't know how to fix it. Good luck on your own was the last thing I heard from them. I asked for how to get a solution or to escalate my problem but they never replied. I'm thinking of throwing every f**king piece of Fibaro equipment out the window.

I have 25 new devices that I can't connect and I can't write an scripts anymore. Anyone wants to buy the *abuse*?

[Jamie mccrostie 82]

3 hours ago, Robrob said:

They continued the investigation and connected again. Then they just mailed me and said that I have a very unusual problem and they don't know how to fix it. Good luck on your own was the last thing I heard from them. I asked for how to get a solution or to escalate my problem but they never replied. I'm thinking of throwing every f**king piece of Fibaro equipment out the window.

I have 25 new devices that I can't connect and I can't write an scripts anymore. Anyone wants to buy the *abuse*?

 

So did they go through recovery process?

[Jamie mccrostie 82]

2 hours ago, Jamie mccrostie said:

 

So did they go through recovery process?

Im only asking because I had problems with the previous upgrade to yours back in December similar issue from reading your post. Eventually i had to bite the bullet and do full recovery. PITA but I guess some times is the only way forward.

[Sankotronic 2,370]

I have my HC2 for more than a year now and despite some problems I never had to do recovery full or partly. So before you go with drastic measures I suggest that first you repeat some of the steps that where mentioned here on forum in the past. I have upgraded my HC2 from 4.100 to 4.110 and everything went smoothly and in that time I had 80 devices included, in total 367 devices and 80 scenes!!!

 

Even this is already worn out I would still clean browser cache, even two, three times just to make sure that is really clean. Instead of rebooting HC2 I like to switch it off with power button on rear side then leave it for at least 5 to 10 minutes to cool down. After turning it back on it is good to leave it for some time until z-wave led start faintly and randomly blinking. Even after HC2 booted up correctly, it is possible that you see blue page with 503 error, but fi you wait for short time it should show you home page.

 

After this is done and you are able to login, then go and check your settings for z-wave network. Remove tick for pooling dead devices first and save. Put tick for mark nodes as dead and save. Now monitor your network and wait to see if any device will be reported as dead. If there are dead nodes (sensors or even actors) then you need to see how far they are from HC2 and if there is any manis powered devices between. If it is too far then you will have to buy smart plug or additional dimmer or switch and find them some role. Also, if any device is reported dead then you can do mesh network reconfiguration for neighbor devices, one by one and also for dead device.

 

When you do that and you don't have any more devices reported dead for some days then you can say that you have builded z-wave network successfully and you can then focus on HC2.

 

There are some good practices in developing scenes and VD's that is good to keep!

1) Avoid writing looping scenes as much as possible. I really recommend to use 

not because I wrote it but because it is working perfectly on my HC2 for long time without any issues. Only scenes that loop on my HC is Main scene and VSL scenes when are triggered by motion sensor. This is were block scenes fail because all of them that are checking some scheduled time then they are actually looping endlessly until are stopped by some internal bug. So if you have HC2 then use LUA because BLOCK sucks!

 

2) Avoid using Main loop on VD's whenever is not really necessary! I have 30 Philips HUE VD's that are successfully controlling my HUE bulbs with 0,09 % misses and their main loop is empty. I don't need them to be refreshed since I use only HC2 to control them.

 

3) If you are sending commands to more than one actor then add some delay between them like fibaro:sleep(100). In most cases 50-100ms is enough, but again it depends if actor is communicating directly with HC or is hoping over other devices. Same is if you want to check status of the actor after sending command.

 

4) if you are using REST API then use localhost IP (127.0.01) instead of HC PI address that then anyway needs to be authenticated. Also when using localhost then you eliminate any interference with network devices since it bypasses any local interface hardware.

 

5) New devices should always be included in vicinity of HC2 at no more than 2 meters away. More close is better! It can be difficult but that will ensure that device is properly included and thus provide proper functioning. Before inclusion it is good to insert battery and wait few minutes.

 

6) When you start building your home automation with Fibaro or any wireless system in that matter, don't just buy stuff, do a plan first. When I started building mine I took floor plan of our house and started placing devices from HC2 vicinity to outwards more distant places. Also I immediately mixed battery and mains powered devices. You need a good strategy. You can't just buy Fibaro motion sensor and then install it on some distant places. It just wont work reliably if there are some thick walls between sensor and gateway. Good planing is 80% of job done! Almost all Fibaro battery operated sensors have built in communication test so use it!

 

I can now go on, but I think it is enough. Too long posts are rarely carefully read, but if you came to this sentence then thank you for your time!  

[SchneiderKlaus 0]

Please login or register to see this code.

Edited March 21, 2017 by SchneiderKlaus

[Jamie mccrostie 82]

On 2/25/2017 at 10:08 PM, Robrob said:

My case is still ongoing with Fibaro support for more than 2 weeks now. They've connected many times through the ports as well as with Teamviewer. No, solution yet except that they say that it's a very unusual problem that is hard to fix. They will continue Monday again...

Any update on this?

Are you 100% sure this is not a home network issue.  A client had issues for a couple of weeks sounds very similar, blue balls of death very slow changing between 

screens un reachable at times. Was a internet issue changed router and leads  as a final resort now all works ok.

 Rest of network worked completly normally whole time must have  been flakey connection somewhere. Worth checking if your still having issues, maybe try pluging in to another network and check UI 

[Robrob 0]

Thanks for your tip! But I've tried that and no change. This behavior occur directly after my upgrade to 4.11 and before I never had the problem. So in about 5 minutes it went from working to not working. Would be a very big coincidence if my network meanwhile stopped working for this specific application. 

Im giving up as I don't get any support from Fibaro for their bad software version. And it seems I'm not alone either...

[Jamie mccrostie 82]

6 hours ago, Robrob said:

Thanks for your tip! But I've tried that and no change. This behavior occur directly after my upgrade to 4.11 and before I never had the problem. So in about 5 minutes it went from working to not working. Would be a very big coincidence if my network meanwhile stopped working for this specific application. 

Im giving up as I don't get any support from Fibaro for their bad software version. And it seems I'm not alone either...

So going forward recovery then is possibly your next step.

My HC2 tripped up on this version too and i couldnt get passed "restarting services" after install.

 

 

Edited March 23, 2017 by Jamie mccrostie

[Michiel Prins 0]

Rob, we're now two months further... I also have this problem. Did you find a solution?

[JJ1964 0]

Just in case, I faced the same issue, different firmware. Problem mysteriously disappeared when I changed my local network cabling:

I connected the HC2 directly to my router network port NOT to the network switch (which is connected to the router) as it had been for months...

 

Suddenly it works again...  Maybe useful?