Archived Forum

Showing off the results of the new features. :)

This are the multi-graph for the multi-rate calculations for the same input being derived to 3 feeds for each scheduled time interval and 3 feeds with total kWh for each schedule also :

Here is the used processlist configuration for the power input:

Hi,

This looks really good !!!

Looking forward trying it.

Eric

That looks awesome, looking forward to trying it out.

As a portuguese user this is REALLY an awesome feature :D

In my case I have 4 different rates per day! Let's see if I can manage to install it :)

Edit: Ups, I though this was already an existing module in github but it seems it isn't. chaveiro where can I get this module? :)

Bruno - this is a development project, having answered many of your other posts about a range of issues I think you should get a feel for the tried and tested stuff that help is on hand for and resolve some of the more basic issues before delving into this. 

Paul 

This is a needed feature, thank you.  In southern California, we have time-of-use OR amount-of-use pricing plans.  Check out all of the options... this is just residential!

https://www.sce.com/wps/portal/home/residential/rates/residential-plan/!ut/p/b1/hc9Bb4JAEAXg3-KBo-yDte7qbUkoLm2kimlxLw00uJIga5BK_PfdGi-mauf2Jt9LZogiGVFNfqx03lWmyevfrMafHo_ETKaQPKAhZIBkLpYCLwwWrC3AnRH4r_9B1DWJ3p5GkDFbgbHU48_sD1gy34L38DUJPB_cv4BJhHAWJxasFhSSLjBPhaDA-AIeHBkTpWtTnB9ei6agXBPVlpuyLVv3u7XrbdftD1MHDvq-d7Uxui7dL7NzcKuyNYeOZNeS7HcZKjlUxakf_AD6d_A9/dl4/d5/L2dBISEvZ0FBIS9nQSEh/

Oh, and it would be nice to incorporate a feature where the billing "start day" could be defined:  it is almost never the 1st of the month.  At my house thbe billing cycle is the 11th of the month, and one month is calculated from 11th of Jan to 11th of Feb etc.  

Would love to be able to calculate cost on a user-defined billing cycle.

You are right Paul! I found this thread while I was searching for other threads that could have some information to solve some of my doubts and got excited with the possibility to have this on EmonCMS :p

This can wait :)

Hi,

This is already on Extended branch, official github is here :

https://github.com/emoncms/emoncms/tree/Extended

As of today there is a commit waiting for merge that fix some issues with graphs on mobile devices and adds touch support, ask for the merge to Trystan or get it directly from here:

https://github.com/chaveiro/emoncms/tree/Extended

Pull request merged into extended thankyou Chaveiro

Hi Chaveiro, how is it possible to account for summer /winter time automatically? your example works only on winter time?

Hi Chaveiro.

Save me some work.

Are those schedule for the Portuguese distribuition company EDP?

Remember me from the Thomson firmware tweaking with JTAG?

Best Regards.

Hi.

I've came up with some expressions for winter and summer, but it seems to have some problems:

If I understood correctly correctly the pipe "|" means "or" and the comma "," means "and". I would use a more universal "&" for "and" and "|" for "or" but that doesn't metter.

Eco
Winter|Mon-Fri|00:00-06:59,Winter|Sat|00:00-09:29,Winter|Sat|13:00-18:29,Winter|Sat|22:00-23:59,Winter|Sun|00:00-23:59Summer|Mon-Fri|00:00-06:59,Summer|Sat|00:00-08:59,Summer|Sat|14:00-19:59,Summer|Sat|22:00-23:59,Summer|Sun|00:00-23:59

Normal
Winter|Mon-Fri|07:00-09:29,Winter|Mon-Fri|12:00-18:29,Winter|Mon-Fri|21:00-23:59,Winter|Sat|09:30-12:59,Winter|Sat|18:30-21:59Summer|Mon-Fri|07:00-09:14,Summer|Mon-Fri|12:15-23:59,Summer|Sat|09:00-13:59,Summer|Sat|20:00-21:59

Cheias
Winter | Mon-Fri | 09:30-11:59, Winter | Mon-Fri | 18:30-20:59, Summer | Mon-Fri | 09:15-12:14

Until now the Eco and Normal worked but the Cheias didn't, the expression returns false when it should return true. now (09:54 28-10-2015) is in "Winter | Mon-Fri | 09:30-11:59"

I will try to look at the javascript code and try to understand how it works to see if I can deduce where the error comes from.

Best Regards.

Hi, what is the timezone setting on emoncms for your user?

Hi.

I'm in Portugal. UTC / GMT +0 Lisbon, London as you wish...

Best Regards.

In /user/view the setting is Europe/Lisbon or UTC ?

Also please  post the debug text that appears when you click the eye icon next to that schedule rule.

The meaning of the operation characters:

• -  Range
• ,  Addition
• |  Granularity separator

As a note, that expression can also be written more efficiently as:

Winter|Mon-Fri|09:30-11:59,18:30-20:59 , Summer|Mon-Fri|09:15-12:14

Off topic: Só reparei agora que já tinhas falado disto, sou o mesmo do forum dos thomson. :)

Hi chaveiro, don't forget my question!

br

Hi.

In user setting was UTC (GMT +00:00), I changed now to Europe/Lisbon (GMT +00:00) but I believe it is the same...

Now the "Normal" applies and returns TRUE, but that should have already happen this afternoon and didn't.

I was thinking of a way to test other dates/times but I don't want to mess with the computer date... A data/time selection to test the schedule against would be cool...

Here is a graph that shows the times no schedule was applied (The rules for the schedules are the ones from my post @10:55.

Off topic:
I've made some changes to the dial widget, here is the code it you want to use it:
 

(...)  
          [11,   "Blue <-> Red, Zero at upper-left"],
          [12,   "Voltage 300V Dial"] // Green colors at acceptable voltages
(...)
  switch (parseInt (type))
    {
    case 0:
      // Standard dial from 0 to maxvalue if offset is not set.
      // TODO: seperate between needle position at maximum/minimum and the value displayed.
      // TODO: Do we need to limit the value being displayed? Only needle position should be limited.
      if (position<0)
        position = 0;
      break;
    case 1:
      angleOffset = -0.75;
      segment = ["#e61703","#ff6254","#ffa29a","#70ac21","#378d42","#046b34"];
      break;
    case 2:
      if (position<0)
        position = 0;
      segment = ["#046b34","#378d42","#87c03f","#f8a01b","#f46722","#bf2025"];
      break;
    case 3:
      angleOffset = -0.75;
      segment = ["#046b34","#378d42","#87c03f","#f8a01b","#f46722","#bf2025"];
      break;
    case 4:
      if (position<0)
        position = 0;
      segment = ["#bf2025","#f46722","#f8a01b","#87c03f","#378d42","#046b34"];
      break;
    case 5:
      angleOffset = -0.75;
      segment = ["#bf2025","#f46722","#f8a01b","#87c03f","#378d42","#046b34"];
      break;
    case 6:
      angleOffset = -0.75;
      segment = ["#f46722","#f8a01b","#87c03f","#87c03f","#f8a01b","#f46722"];
      break;
    case 7:
      if (position<0)
        position = 0;
      segment = ["#a7cbe2","#68b7eb","#0d97f3","#0f81d0","#0c6dae","#08578e"];
      break;
    case 8:
      //temperature dial blue-red, first segment blue should mean below freezing C
      angleOffset = -0.25;
      segment = ["#b7beff","#ffd9d9","#ffbebe","#ff9c9c","#ff6e6e","#ff3d3d"];
      break;
    case 9:
      //temperature dial blue-red, first segment blue should mean below freezing C
      angleOffset = 0;
      segment = ["#e94937","#da4130","#c43626","#ad2b1c","#992113","#86170a"];
      break;
    case 10:
      //light: from dark grey to white
      if (position<0)
        position = 0;
      segment = ["#202020","#4D4D4D","#7D7D7D","#EEF0F3","#F7F7F7", "#FFFFFF"];
      break;
    case 11:
      //temperature dial blue-red, first 2 segments blue should mean below freezing C
      angleOffset = -0.5;
      segment = ["#0d97f3","#a7cbe2","#ffbebe","#ff8383","#ff6464","#ff3d3d"];
      break;
    case 12:
      if (position<0)
        position = 0;
      segment = ["#f8a01b","#f8a01b","#f8a01b","#378d42","#046b34","#bf2025"];
      break;
    }
(...)

I've been testing and now this expression should return false but it returns true:

Summer | Mon | 13:00-21:59,23:00-23:59, Wed | 15:30-18:30,22:00-23:59, Winter | Mon |19:30-20:29,22:00-23:59

I believe that there is some problem with the winter and summer usage in the same expression.

What is the file that has the code that analyzes the expressions so I can analise it and try to understand the code?

Alert Output:
Schedule expression returned 'true'.Details:Expression =Summer | Mon | 13:00-21:59,23:00-23:59, Wed | 15:30-18:30,22:00-23:59, Winter | Mon |19:30-20:29,22:00-23:59Input =22:50:35 Wed 28-10-2015 0 GMT+0000Day =00:00:00 Wed 28-10-2015 0 Europe/LisbonHrMin =22:50:35 Wed 28-10-2015 0 Europe/LisbonWeekDay =Wed________________________________________MATCHArray(    [0] => Summer | Mon | 13:00-21:59,23:00-23:59,     [1] => Summer |     [dst] => Summer     [2] => Summer     [3] =>     [4] => Summer    [5] =>     [days] =>     [6] =>     [7] =>     [8] =>     [9] => Mon |     [daysweek] => Mon     [10] => Mon     [11] =>     [12] => Mon    [hours] => 13:00-21:59,23:00-23:59,     [13] => 13:00-21:59,23:00-23:59,     [14] => 23:59,     [15] => 23:59)________________________________________MATCHArray(    [0] => Wed | 15:30-18:30,22:00-23:59,     [1] =>     [dst] =>     [2] =>     [3] =>     [4] =>     [5] =>     [days] =>     [6] =>     [7] =>     [8] =>     [9] => Wed |     [daysweek] => Wed     [10] => Wed     [11] =>     [12] => Wed    [hours] => 15:30-18:30,22:00-23:59,     [13] => 15:30-18:30,22:00-23:59,     [14] => 23:59,     [15] => 23:59)    Wed <- FOUND A WEEKDAYH 15:30-18:30        15:30-18:30  ---->Wed 2015-10-28 15:30:00 Europe/Lisbon - Wed 2015-10-28 18:30:59 Europe/Lisbon ? Wed 2015-10-28 22:50:35 Europe/LisbonH 22:00-23:59        22:00-23:59  ---->Wed 2015-10-28 22:00:00 Europe/Lisbon - Wed 2015-10-28 23:59:59 Europe/Lisbon ? Wed 2015-10-28 22:50:35 Europe/Lisbon <- FOUND A HOUR1________________________________________MATCHArray(    [0] => Winter | Mon |19:30-20:29,22:00-23:59    [1] => Winter |     [dst] => Winter     [2] => Winter     [3] =>     [4] => Winter    [5] =>     [days] =>     [6] =>     [7] =>     [8] =>     [9] => Mon |    [daysweek] => Mon     [10] => Mon     [11] =>     [12] => Mon    [hours] => 19:30-20:29,22:00-23:59    [13] => 19:30-20:29,22:00-23:59    [14] => 23:59    [15] => 23:59)    Mon________________________________________MATCHArray(    [0] =>     [1] =>     [dst] =>     [2] =>     [3] =>     [4] =>     [5] =>     [days] =>     [6] =>     [7] =>     [8] =>     [9] =>     [daysweek] =>     [10] =>     [11] =>     [12] =>     [hours] =>     [13] => )    

Update:
I've found the php where the expression is tested, I will try to understand it to see if I can get to the error that causes the test expression to give the incorrect result.
Is there a reason not to remove the expression spaces right in the beginning instead of several times later?

I've updated my expressions to this (Some errors corrected and where improved as you suggested):

Eco
Winter|Mon-Fri|00:00-06:59,Sat|00:00-09:29,13:00-18:29,22:00-23:59,Sun|00:00-23:59,Summer|Mon-Fri|00:00-06:59,Sat|00:00-08:59,14:00-19:59,22:00-23:59,Sun|00:00-23:59

Normal
Winter|Mon-Fri|07:00-09:29,12:00-18:29,21:00-23:59,Sat|09:30-12:59,18:30-21:59,Summer|Mon-Fri|07:00-09:14,12:15-23:59,Sat|09:00-13:59,20:00-21:59

Cheias
Winter|Mon-Fri|09:30-11:59,18:30-20:59,Summer|Mon-Fri|09:15-12:14

Best Regards.

Cidi,

The expression was executed at 22:50:35 Wed 28-10-2015 0 GMT+0000

Summer | Mon | 13:00-21:59,23:00-23:59,
Wed | 15:30-18:30,22:00-23:59,        <- Wed 22:50 fits here
Winter | Mon |19:30-20:29,22:00-23:59

It's returning true on the bold part, it is correct.

cab123: I dont understand your question, can you give an example of what you want?

Hi Chaveiro.

The expression says Summer, the present date is winter.

So 22:50:35 Wed 28-10-2015 0 GMT+0000, does not fit the winter part of the expression:
Winter | Mon |19:30-20:29,22:00-23:59

Cheers.

Again.

I believe I understood it.

If we select various hours intervals it will assume they are on the same day/day interval of the before, but if we specify a day/day interval it will not be interpreted as the same day light period as the one before.

So we have to spec iffy the Winter/Summer for each day/day interval or it will be applied without distintion of winter/summer.

I changed my rules to this, and I believed that it answers cab123 question:

Eco
Winter|Mon-Fri|00:00-06:59,Winter|Sat|00:00-09:29,13:00-18:29,22:00-23:59,Winter|Sun|00:00-23:59,Summer|Mon-Fri|00:00-06:59,Summer|Sat|00:00-08:59,14:00-19:59,22:00-23:59,Summer|Sun|00:00-23:59

Normal
Winter|Mon-Fri|07:00-09:29,12:00-18:29,21:00-23:59,Winter|Sat|09:30-12:59,18:30-21:59,Summer|Mon-Fri|07:00-09:14,12:15-23:59,Summer|Sat|09:00-13:59,20:00-21:59

Cheias
Winter|Mon-Fri|09:30-11:59,18:30-20:59,Summer|Mon-Fri|09:15-12:14

Cheers.

I think i got it, i've set up the schedulers like this:

cab123:

It seems you enhanced the expression on overlapping periods that are the same in summer and winter.

I will do that to my expression too and post it later.

Best Regards.

Nice you figure it out.
As a reference this is what im using for PT.

Tri Weekly Empty
Winter|Mon-Fri|00:00-06:59, Winter|Sat|00:00-09:29,13:00-18:29,22:00-23:59, Winter|Sun|00:00-23:59 , Summer|Mon-Fri|00:00-06:59, Summer|Sat|00:00-08:59,14:00-19:59,22:00-23:59, Summer|Sun|00:00-23:59

Tri Weekly Full
Winter|Mon-Fri|07:00-09:29,12:00-18:29,21:00-23:59, Winter|Sat|09:30-12:59,18:30-21:59 , Summer|Mon-Fri|07:00-09:14,12:15-23:59, Summer|Sat|09:00-13:59,20:00-21:59

Tri Weekly Top
Winter|Mon-Fri|09:30-11:59,18:30-20:59 , Summer|Mon-Fri|09:15-12:14

Bi Weekly Empty
Winter|Mon-Fri|00:00-06:59, Winter|Sat|00:00-09:29,13:00-18:29,22:00-23:59, Winter|Sun|00:00-23:59 , Summer|Mon-Fri|00:00-06:59, Summer|Sat|00:00-08:59,14:00-19:59,22:00-23:59, Summer|Sun|00:00-23:59

Bi Weekly Full
Winter|Mon-Fri|07:00-23:59, Winter|Sat|09:30-12:59,18:30-21:59 , Summer|Mon-Fri|07:00-23:59, Summer|Sat|09:00-13:59,20:00-21:59

Hi.

My last changes and improvements gave this for Weekly Tri schedule on EDP Portugal (Also Applies to bi, normally the meters are tri even when the tariff is bi so we can check the three).

Eco:
Mon-Fri | 00:00-06:59, Sun | 00:00-23:59, Sat | 00:00-08:59,14:00-18:29,22:00-23:59, Winter | Sat | 09:00-09:29,13:00-13:59, Summer | Sat | 18:30-19:59

Normal
Mon-Fri | 07:00-09:14,12:15-18:29,21:00-23:59, Sat | 09:30-12:59,20:00-21:59, Summer | Mon-Fri | 12:00-12:14,18:30-20:59

Cheias
Mon-Fri | 09:30-11:59, Summer | Mon-Fri | 09:15-09:29, Winter | Mon-Fri | 12:00-12:14

Lets see how it works.

Great! Very nice implementation, thank you chaveiro!

After a few tests I've seen that my last implementation don't work correctly.

In my last expression I tried to put first the most occurring options first so that the script can exit at the first true (if it's programmed that way), and like that, the situations where the winter and the summer are equal would come first.

For now I've changed the order and put the winter/summer options before the other, lets see how it goes....

Semanal Eco
Winter | Sat | 09:00-09:29,13:00-13:59, Summer | Sat | 18:30-19:59, Mon-Fri | 00:00-06:59, Sun | 00:00-23:59, Sat | 00:00-08:59,14:00-18:29,22:00-23:59

​Semanal Normal
Summer | Mon-Fri | 12:00-12:14,18:30-20:59, Mon-Fri | 07:00-09:14,12:15-18:29,21:00-23:59, Sat | 09:30-12:59,20:00-21:59

Semanal
Cheias Summer | Mon-Fri | 09:15-09:29, Winter | Mon-Fri | 12:00-12:14, Mon-Fri | 09:30-11:59

Update:
This rules failed to work correctly too:
- This morning the very first part of the rule Eco didn't apply from 09h to 09h30;
- I have too assume one of two things: there is something about making this rules I didn't understand yet, or there are bugs in the processing.

Chaveiro, please shed some light on this.

Best Regards.

A bit off topic, but related, how do you guys track the price/kWh on each period?

my previous implementation was a cron job feeding emoncms a couple of flags and the €/kWh. Now the flags are not necessary because of this great scheduler feature, but to track current price i think i have to keep a separate script that feeds emoncms with the price so i can make the correct multiplications on the live feed. Also it is important to be able to change the price several times since utility companies are always increasing the tariffs

Hi,

Landed here when searching for multi-tarif kWh calculation...

Any update on this feature?

Good job so far.

Thanks this is definetely what I was looking for: Italy schedules are fractioned in F1 F2 F3

For Italian Users

Here is the schedule definition of our timewindows

id Name Expression Public
2 F1 Mon-Fri|08:00-18:59
3 F2 Mon-Fri|07:00-07:59, Mon-Fri|19:00-22:59, Sat|07:00-22:59
4 F3 Mon-Sat|23:00-06:59, Sun|00:00-23:59, 1/1, 1/6 , 4/25, 5/1, 6/2, 8/15, 11/1, 12/8, 12/25 , 12/26

Now testing with the input process list from Chaveiro seems perfect

When I make changes to a schedule they will only work if I reboot. Is this how it should be?

Hi xino, can you explain exactly the problem?

é assim ...

If I make changes to a schedule the result will show true or false depending on this change, but independently of the schedules result, there is no change on the feed of this schedule. It will only work correctly after a sudo reboot. There's obviously a service that can be restarted instead of a reboot but I haven't discovered that yet.

Thanks for the support.