[Solved] Fibaro api/refreshStates call incredibly slow

[Harald 0]

I've recently purchased a Fibaro Home Center 2. And linked up three fibaro dimmer 2, two nexa AD-146 Dimmers and one AD-147.

 

Suddenly (as within adding the first few devices) the admin interface has become unusable due to slowness. I'm seeing that the api call api/refreshStates often returns at around ~30s which is propably a timeout in the code.

 

Since this call is used quite a lot in per page. I'm often getting 3-5 minute page load times. 

 

I'm really unsure about where to start debugging this issue. Mem and CPU and other systems stats seem to be working fine. But my home center admin interface is now basically unusable. Anyone seen similar issues?

 

Update: I disabled one of the Nexa AD-146'es. And the problem disappeared. Funny thing is, the sluggishness didn't return when i Re-enabeld it. 

Edited August 20, 2017 by Harald
Solved

[tinman 1,070]

nexa is actually everspring, and everspring i known for bit strange COMMAND_CLASS_NOTIFICATION_V4 implementation, which definitely can slow down HC2 (where HC2 itself know COMMAND_CLASS_NOTIFICATION_V4 and have no issues with other devices using it, seems to be very everspring related)

 

 

 

[Harald 0]

22 hours ago, tinman said:

nexa is actually everspring, and everspring i known for bit strange COMMAND_CLASS_NOTIFICATION_V4 implementation, which definitely can slow down HC2 (where HC2 itself know COMMAND_CLASS_NOTIFICATION_V4 and have no issues with other devices using it, seems to be very everspring related)

 

That seems to be my exact issue. The notification center was filling up. I think I'll limit the use of Nexa/Everspring to the Dimmer/Wall plug from now on.