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


  • 0

Question

Posted

Hi,

 

I currently have my hc3 setup with the quickapp p1 meter for house energy metering and made my own quickapp for metering the solarpanels. I used most of the code from the p1 quickapp to make sure it would work simply because I am not a coding wizard sadly :).

I started running my quickapp and it worked like a charm, except for the energy panel aspect. I was producing megawatt houres of energy... 

The consumption also was acting up wierd at the same time.

Please login or register to see this attachment.

 

The child app resposible for reading the kwh data from the Growatt inverter is setup as an energyMeter like this:

{name="Zon productie vandaag", className="ProductionToday", type="com.fibaro.energyMeter"}

 

some more code of this child:

class 'ProductionToday'(QuickAppChild)
function ProductionToday:__init(device)
    QuickAppChild.__init(self, device) 
    self:updateProperty("rateType", "production")
end
 
function ProductionToday:updateValue(devicedata)
    self:updateProperty("value", tonumber(devicedata.epvtotal)) --tonumber(devicedata.epvtotal)
    self:updateProperty("unit", "kWh")
    self:updateProperty("log", devicedata.update_timestamp)
end

 

When I noticed it starting to register megawatts I removed the line of code responsible for saving the data.

self:updateProperty("storeEnergyData", true)

 

While coding this quickapp I came across multiple "special" ways of fibaro to register certain types of data.

My question now is, how does fibaro read this kwh data and process it?

 

Please login or register to see this image.

/monthly_2022_10/image.png.dffdc0ce0f6ef82406aa1f9aeeab7dfb.png" />

 

Recommended Posts

  • 0
  • Inquirer
  • Posted

    Best all,

     

    It looks like I found the issue, I dont want to celebrate too early but for now I suppect it was due to the following problem:

    Yesterday I noticed that the value of the today import and export child devices were displaying with more then 7 decimal numbers like 7.9500000043 or something like that (just to give you an idea of what I mean). Immediately I thought back to this commend @SmartHomeEddy made some time ago:

    On 10/31/2022 at 9:04 PM, SmartHomeEddy said:

    Yes it does. The energy panel is kind of sensitive to strange values. Look at the SolarEdge Quickapp what I had to do, to handle decreasing values. 

    I added some code to round up the values to 3 decimal places and sure enough the values are being displayed correctly the whole day now.

     

    I will keep an eye on the values the upcomming days to make sure this assumption is correct.

    But for now I want to thank you @SmartHomeEddy for you support, also again massive thanks to @Joep for writing the HW p1 meter QA in the first place.

    Join the conversation

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

    Guest
    Answer this question...

    ×   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...