Energy report 0.3.6

Hi, could you upgrade to HC3 as it's totally different.

TKS!!!

Thank you! Very good!!!

Hello, 

 

works well. 

Is it possible to make the report by hour ? 

(day 2 , 13:00  hour consumption 100 kwh )

 

thank you 

 

4 hours ago, Lenny22 said:

Hello, 

 

works well. 

Is it possible to make the report by hour ? 

(day 2 , 13:00  hour consumption 100 kwh )

 

thank you 

 

Thank you too

 

If I understood you correctly, for this purpose you need to change the trigger (conditions) on the left.

Analogous to your example: value = { "00", "13", "2", "*", "*", "*" }

Here the script would start every 2nd of the month at 1:00 p.m.

In order for an email to be sent, you also have to change the variable maildays.

the deal is that i´m buying energy from  stock exchange and the price changes every hour.  

so i would like to have report for every hour of the day oft the month. 

 

to e.mail it will send what ? report or notification ? 

 

thank you 

 

Actually the script is not designed for such short periods of time. But you can do it with a little unsightly hack.

 

In the left side (Conditions/triggers) change the value to 1 hour so that the script starts every hour. " value = { "0", "*", "*", "*", "*", "*" } "

 

In the script itself, replace the line "sek = ndays * 86400" with "sek =3600" as the basis for the calculation.

 

After the lines:

local consumption= 'Total consumption-------------: '.. kilowatts .. ' kWh'..'</br>'

local tcosts = 'Total costs-------------------: '.. sum .. ' '..currSymbol

 

Add the following lines:

hub.alert('push', {2,}, "Last hour consuption:".. kilowatts.. " kWh") -- for push message 

print (consumption)

print (tcosts)

 

And finally, at the beginning of the script, change the variables to this value:

local maildays = {}

local debugout = false

local debughtml = false

local defDays = 1

 

This is how it should work for your needs

 

Good luck

 

54 minutes ago, jwi said:

Actually the script is not designed for such short periods of time. But you can do it with a little unsightly hack.

 

In the left side (Conditions/triggers) change the value to 1 hour so that the script starts every hour. " value = { "0", "*", "*", "*", "*", "*" } "

 

In the script itself, replace the line "sek = ndays * 86400" with "sek =3600" as the basis for the calculation.

 

After the lines:

local consumption= 'Total consumption-------------: '.. kilowatts .. ' kWh'..'</br>'

local tcosts = 'Total costs-------------------: '.. sum .. ' '..currSymbol

 

Add the following lines:

hub.alert('push', {2,}, "Last hour consuption:".. kilowatts.. " kWh") -- for push message 

print (consumption)

print (tcosts)

 

And finally, at the beginning of the script, change the variables to this value:

local maildays = {}

local debugout = false

local debughtml = false

local defDays = 1

 

This is how it should work for your needs

 

Good luck

 

 

 some thing is wrong here. 

what should i change ? 

Thank you 

Ohh, do you have an HC2?

Just now, jwi said:

Ohh, do you have an HC2?

Yes

 

I no longer have HC2, just replace the word "hub" with "fibaro"

ok, 

 

Replaced the words still the same 

I'm no longer familiar with the HC2 syntax

 

Just try: fibaro:call(2, 'sendPush', consumption )

This is wonderful and I simply do not understand why the HC3 has so bad energy reporting to start with and ok some " solar" but face it most of them have no use for that and like

function like this to track the use, the green " bug"  must have hit hard in Fibaro home offices making so much energy stuff that nobody in fact is able to use 

 

BUT this is what we need, the ability to track use, pr device and for a full setup,  I might be outside bell-curve as just finished putting in energy meters on most things that use power

washing machines, water pumps, aircon etc.  

 

Im trying to modify your script,  I'm not a coder, so for now, I do not get emails but Im struggling with the automatic part, ( I want to try to avoid the manual that works fine as I have so many devices )   I see as I have miz of brands and also some ( don't tell anybody ) Zigbee

 

that " power" misses a few things, so I was thinking that the below might work but still only process the first line.  if look under the device in HC3 and use 

 

   pwrIDs = fibaro.getDevicesID({interfaces = {"power"} or {"energy"} or {"electricity"}, visible = true, enabled = true})

 

Wonder if you are able to point me in the right direction.

 

 

 

@Jasper Waale , I hope you know that ZigBee is still in beta at fibaro, so there may be problems.

At the time I coded this script, fibaro didn't have zigbee yet. But let's see, maybe there is a solution.

 

As far as I know, a property of the device must be "power". But you can also try “light”. The "ROLE" is only for filtering and you can set it for each device in the "General" tab.

I have 3 different ZigBee devices and all 3 are addressed with "power". But you can also combine a combination of manual and automatically found IDs.

 

For that paste this code at this point:

if manually then
   -- Manual entry of device IDs for evaluation.
   pwrIDs = {213,224,256,264,285,305,322,339,383,391} 
else  
   -- Automatic determination of electricity consumers.
   pwrIDs = fibaro.getDevicesID({interfaces = {"power"}, visible = true, enabled = true})  
end
-------------insert -------------
mpwrIDs = {999,1201, }   -- enter manualy your IDs
for _,v in ipairs(mpwrIDs) do -- this code joins both tables 
    table.insert(pwrIDs, v)   -- 
end
-----------------------------

 

Good luck