Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Recommended Posts

Posted

Could you advice how to fliter/eliminate power changing events of such minimal change? Thousands of them per hour - only from this single smart plug FGWPE-102. The screen is from Event Logger:

Please login or register to see this attachment.

 

Plugins parameters regarding power reading are the following:

Please login or register to see this attachment.

Posted

Why the fluctuations happen

  • When your device (consumer) is in standby or consumes very little power, the plug’s internal measurement circuit can still detect tiny spikes or noise.
  • These micro‑changes (from 0 W to 1–2 W, for example) are reported as events, which can clutter your automation logs.
  • The plug itself cannot perfectly filter out “0 W → small value” transitions, because it’s designed to be sensitive.

 

🛠️ Workarounds

  1. Parallel small consumer
    • Adding a small, constant load (like a night‑light or resistor) keeps the measured power slightly above zero.
    • This stabilizes readings and prevents the plug from bouncing between 0 W and tiny values.
  2. Parameter tuning (FGWPE‑102 settings)
    • In the device configuration, you can set thresholds for reporting:
      • Wattage change threshold → only report if power changes by more than X watts.
      • Percentage change threshold → only report if the change is greater than X %.
    • By raising these thresholds, you can ignore “noise” and only get meaningful updates.
  • Topic Author
  • Posted

    :) Hmm... OK.
    Looking at the parameters, this plug should not report so small energy changes.
    ...unless we assume that a change from 0 to 0.3 represents a 100% change (thresthold to report 15%), which is nonsense.

    Basically, it doesn’t bother me, but it clutters up already not all-reliable Z-Wave communication.

    Posted
    11 hours ago, Łukasz997 said:

    :) Hmm... OK.
    Looking at the parameters, this plug should not report so small energy changes.
    ...unless we assume that a change from 0 to 0.3 represents a 100% change (thresthold to report 15%), which is nonsense.

    Basically, it doesn’t bother me, but it clutters up already not all-reliable Z-Wave communication.

    This is the mathematical algorithm, change from 0 to any value is 100000000000000000...%

  • Topic Author
  • Posted (edited)

    I would like to bring this phenomenon to the attention of the Fibaro staff.

    Additionally, when I open the parameters of any wall plug, every parameter that I try to edit closes after 2-3 seconds (so there’s almost no chance to enter a new value). A series of “Configuration parameters refreshed” messages appears (8-10 times), and then it stops - until I open another parameter for editing.

    This happens in every browser, and it only concerns the Smart Plug FGWPE-102. Also, could you comment massive events of very little power changes and how to filter it.

    I think there are errors here. FW 5.190.36

     

    Please login or register to see this attachment.

    Edited by Łukasz997
  • Topic Author
  • Posted

    Solution was to enable counting device's own power consumption by selecting one of the parameters. It was not an easy task due to the "auto" closing parameters view.

    No repetitive events - hourly amount of events drop down from ~5000 to ~1200, CPU load has visibly (on the chart) decreased.
    So at the end it turns out that @cag014 was right ;) 

     

     

     

     

     

    Many thanks to the Fibaro team for their interest... 

    • Like 1
    • Thanks 1
    Posted
    3 minutes ago, Łukasz997 said:

    Solution was to enable counting device's own power consumption by selecting one of the parameters. It was not an easy task due to the "auto" closing parameters view.

    No repetitive events - hourly amount of events drop down from ~5000 to ~1200, CPU load has visibly (on the chart) decreased.
    So at the end it turns out that @cag014 was right ;) 

     

     

     

     

     

    Many thanks to the Fibaro team for their interest... 


    Great of you to share the experience! :D 
    Havent seen this before :) So good to know about it :D 

     

  • Topic Author
  • Posted
    3 godziny temu, Brors94 napisał:

    Great of you to share the experience! :D 
    Havent seen this before :) So good to know about it :D 

    It's nice that you see this, thanks!

    The recipe refers to wall plug only. The Walli Outlet does not need this (as far as can check).

     

    • Like 1

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Reply to this topic...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×
    ×
    • Create New...