Adding "on-peak" and "off-peak" colouring to the production/consumption graph

Question

Adding "on-peak" and "off-peak" colouring to the production/consumption graph

solrak44 opened this issue 3 years ago · 19 comments

Kia ora,

I love your visualiser software. We have it proudly displayed in the kitchen and it's much remarked upon by visitors to our house! It frequently prompts us to ask "why are we using so much power?" and go looking for the offending appliance. It also prompts us to do something with the power once the hot water has finished heating. Awsome stuff!

Our power company is offering us on-peak and off-peak rates for our power at very set times of the day. I wondered how easy it would be add some background colour to the production/consumption graph to show these times (and prompt us to avoid them for high power use appliances). Is this a couple of lines or a complete re-write?

Thanks again for your awesome software, and please ignore this if it's a cheeky thing to ask :-)

Karl

Answer 1 · 2021-12-13T06:24:22.000Z

A quick question.

Do you have multiple off and on peaks or just the one on-peak.

One on peak might be easy to produce something like this

But not yet sure how to add config for it.

Answer 2 · 2021-12-13T19:56:37.000Z

Unfortunately there's two of them 7am–11am, 5pm–9pm. I realise that makes it way more complicated. The coloured bar looks perfect though :-)

…

On 13/12/2021, at 7:24 PM, dlmcpaul ***@***.***> wrote: A quick question. Do you have multiple off and on peaks or just the one on-peak. One on peak might be easy to produce something like this <https://user-images.githubusercontent.com/37256580/145762575-a7af0a2a-1a18-4429-9c96-525504c8528a.png> But not yet sure how to add config for it. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ7HQJ4NOVWG4WSFJ6IBJ3DUQWGSBANCNFSM5J45J7ZQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

Answer 3 · 2022-01-01T02:40:57.000Z

@solrak44

I have added some support for bands within the graph. Please try out the new release (See the readme for setup).

Have not added support in the docker image though so hopefully you run the jar.

Answer 4 · 2022-01-09T22:03:15.000Z

Sorry for the late reply - I've been away. While I was originally using the RPi, I'm running as a docker image on my new Synology. I'll see if I can get the RPi version up and running again and test this for you. It looks great!

Answer 5 · 2022-01-09T22:31:59.000Z

Ok, I am looking at how to add this feature to the Docker image so it will be there eventually

Answer 6 · 2022-01-31T23:47:47.000Z

The docker image should now also work with this feature, you will need to bind a new volume. I have added instructions to the readme.

Let me know of any issues

Answer 7 · 2022-02-01T04:05:41.000Z

Works perfectly reading the properties file from the NAS! http://thinkdifferent.co.nz:8000/solar/ The only issue I have is I can’t get it to remember the data from restart to restart. I have mapped /internal_db to a folder on my NAS, but it never seems to load it back in. Thanks so much for all you do. Your beautiful graphs and gauges never fail to intrigue people who visit our place!! Ngā mihi nui Karl

…

On 1/02/2022, at 12:47 PM, dlmcpaul ***@***.***> wrote: The docker image should now also work with this feature, you will need to bind a new volume. I have added instructions to the readme. Let me know of any issues — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ7HQJ2B5VR6HQNVWTIPSV3UY4NS3ANCNFSM5J45J7ZQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.

Answer 8 · 2022-02-01T05:08:15.000Z

Interesting, is a file being created in the folder you mapped /internal_db to?

Answer 9 · 2022-02-01T07:14:12.000Z

Yes, there is a file called “solar_stats_db.mv.db” but it hasn’t been modified since June last year. Should I delete it and let it recreate itself?

…

On 1/02/2022, at 6:08 PM, dlmcpaul ***@***.***> wrote: Interesting, is a file being created in the folder you mapped /internal_db to? — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ7HQJYEVGZFYCYM7YPNXPLUY5TETANCNFSM5J45J7ZQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.

Answer 10 · 2022-02-01T08:35:00.000Z

Not yet. Put the docker run command you are using and let me see if there is something there.

Answer 11 · 2022-02-01T20:07:53.000Z

So I don’t run it from the commandline – I’m running it via the docker GUI on my Synology box (DSM 7). Here is a screenshot of the running container, with the variables I selected at the start. You can see I have two folders on the NAS in a containing folder called “docker”. The properties folder contains the config file for the new version of your app. I know the app can see that folder because it correctly displays the bands I set for on-peak, offpeak (as well as the various charges and rates). Ngā mihi nui Karl

…

On 1/02/2022, at 9:35 PM, dlmcpaul ***@***.***> wrote: Not yet. Put the docker run command you are using and let me see if there is something there. — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ7HQJZ6K2HZQTYPXRMEAPTUY6LL5ANCNFSM5J45J7ZQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.

Answer 12 · 2022-02-01T21:33:46.000Z

Hmm, sorry no image attached,

Maybe compare the ownership information of the 2 files and the 2 directories. It certainly looks like a lack of write permission.

Answer 13 · 2022-02-01T22:43:47.000Z

Is the image there now? And yes, I’ll check to make sure write permissions is correct. Thanks again for your help! I think I owe you a beer

…

On 2/02/2022, at 10:33 AM, dlmcpaul ***@***.***> wrote: Hmm, sorry no image attached, Maybe compare the ownership information of the 2 files and the 2 directories. It certainly looks like a lack of write permission. — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ7HQJYVHPMMGMQ6X6SPIGTUZBGULANCNFSM5J45J7ZQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.

Answer 14 · 2022-02-01T23:03:48.000Z

What it does do, is constantly write this to the logs now (these are the start times of the two bands I set up) 2022-02-02 11:57:46.516 INFO 1 --- [nio-8080-exec-5] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:57:46.552 INFO 1 --- [nio-8080-exec-4] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:57:46.552 INFO 1 --- [nio-8080-exec-4] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:57:54.517 INFO 1 --- [nio-8080-exec-3] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:57:54.518 INFO 1 --- [nio-8080-exec-3] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:57:59.155 INFO 1 --- [nio-8080-exec-7] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:57:59.155 INFO 1 --- [nio-8080-exec-7] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:58:02.520 INFO 1 --- [nio-8080-exec-9] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:58:02.520 INFO 1 --- [nio-8080-exec-9] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:58:10.501 INFO 1 --- [nio-8080-exec-2] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:58:10.502 INFO 1 --- [nio-8080-exec-2] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:58:11.531 INFO 1 --- [nio-8080-exec-4] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:58:11.531 INFO 1 --- [nio-8080-exec-4] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:58:18.501 INFO 1 --- [io-8080-exec-10] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:58:18.501 INFO 1 --- [io-8080-exec-10] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:58:24.555 INFO 1 --- [nio-8080-exec-4] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:58:24.555 INFO 1 --- [nio-8080-exec-4] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:58:26.510 INFO 1 --- [nio-8080-exec-6] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:58:26.511 INFO 1 --- [nio-8080-exec-6] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:58:35.500 INFO 1 --- [nio-8080-exec-7] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:58:35.502 INFO 1 --- [nio-8080-exec-7] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:58:36.841 INFO 1 --- [nio-8080-exec-8] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:58:36.842 INFO 1 --- [nio-8080-exec-8] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:58:43.569 INFO 1 --- [io-8080-exec-10] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:58:43.570 INFO 1 --- [io-8080-exec-10] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:58:48.828 INFO 1 --- [nio-8080-exec-5] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:58:48.829 INFO 1 --- [nio-8080-exec-5] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:58:51.524 INFO 1 --- [nio-8080-exec-6] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:58:51.524 INFO 1 --- [nio-8080-exec-6] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:58:59.517 INFO 1 --- [nio-8080-exec-9] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:58:59.518 INFO 1 --- [nio-8080-exec-9] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:59:02.260 INFO 1 --- [nio-8080-exec-8] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:59:02.261 INFO 1 --- [nio-8080-exec-8] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:59:07.851 INFO 1 --- [io-8080-exec-10] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:59:07.853 INFO 1 --- [io-8080-exec-10] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:59:14.697 INFO 1 --- [nio-8080-exec-8] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:59:14.697 INFO 1 --- [nio-8080-exec-8] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:59:15.574 INFO 1 --- [nio-8080-exec-6] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:59:15.575 INFO 1 --- [nio-8080-exec-6] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:59:23.522 INFO 1 --- [nio-8080-exec-9] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:59:23.522 INFO 1 --- [nio-8080-exec-9] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:59:26.763 INFO 1 --- [nio-8080-exec-8] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:59:26.764 INFO 1 --- [nio-8080-exec-8] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:59:31.525 INFO 1 --- [nio-8080-exec-2] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:59:31.527 INFO 1 --- [nio-8080-exec-2] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:59:39.580 INFO 1 --- [nio-8080-exec-5] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:59:39.580 INFO 1 --- [nio-8080-exec-5] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:59:39.943 INFO 1 --- [nio-8080-exec-8] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:59:39.944 INFO 1 --- [nio-8080-exec-8] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:59:47.382 INFO 1 --- [nio-8080-exec-4] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:59:47.382 INFO 1 --- [nio-8080-exec-4] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:59:52.238 INFO 1 --- [nio-8080-exec-5] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:59:52.239 INFO 1 --- [nio-8080-exec-5] com.hz.controllers.EnphaseController : 1700 2022-02-02 11:59:55.589 INFO 1 --- [nio-8080-exec-2] com.hz.controllers.EnphaseController : 0700 2022-02-02 11:59:55.590 INFO 1 --- [nio-8080-exec-2] com.hz.controllers.EnphaseController : 1700 2022-02-02 12:00:03.779 INFO 1 --- [nio-8080-exec-6] com.hz.controllers.EnphaseController : 0700 2022-02-02 12:00:03.779 INFO 1 --- [nio-8080-exec-6] com.hz.controllers.EnphaseController : 1700 2022-02-02 12:00:05.360 INFO 1 --- [nio-8080-exec-1] com.hz.controllers.EnphaseController : 0700 2022-02-02 12:00:05.360 INFO 1 --- [nio-8080-exec-1] com.hz.controllers.EnphaseController : 1700 2022-02-02 12:00:11.536 INFO 1 --- [nio-8080-exec-4] com.hz.controllers.EnphaseController : 0700 2022-02-02 12:00:11.537 INFO 1 --- [nio-8080-exec-4] com.hz.controllers.EnphaseController : 1700 2022-02-02 12:00:18.035 INFO 1 --- [nio-8080-exec-3] com.hz.controllers.EnphaseController : 0700 2022-02-02 12:00:18.036 INFO 1 --- [nio-8080-exec-3] com.hz.controllers.EnphaseController : 1700 2022-02-02 12:00:19.546 INFO 1 --- [nio-8080-exec-2] com.hz.controllers.EnphaseController : 0700 2022-02-02 12:00:19.547 INFO 1 --- [nio-8080-exec-2] com.hz.controllers.EnphaseController : 1700 2022-02-02 12:00:27.530 INFO 1 --- [nio-8080-exec-6] com.hz.controllers.EnphaseController : 0700 2022-02-02 12:00:27.530 INFO 1 --- [nio-8080-exec-6] com.hz.controllers.EnphaseController : 1700 2022-02-02 12:00:30.772 INFO 1 --- [io-8080-exec-10] com.hz.controllers.EnphaseController : 0700 2022-02-02 12:00:30.773 INFO 1 --- [io-8080-exec-10] com.hz.controllers.EnphaseController : 1700 2022-02-02 12:00:35.540 INFO 1 --- [nio-8080-exec-4] com.hz.controllers.EnphaseController : 0700

…

On 2/02/2022, at 10:33 AM, dlmcpaul ***@***.***> wrote: Hmm, sorry no image attached, Maybe compare the ownership information of the 2 files and the 2 directories. It certainly looks like a lack of write permission. — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ7HQJYVHPMMGMQ6X6SPIGTUZBGULANCNFSM5J45J7ZQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.

Answer 15 · 2022-02-01T23:31:37.000Z

Yes sorry, that's a debug I left in there.

Try sending any images to my email dlmcpaul AT gmail.com

Answer 16 · 2022-02-01T23:33:59.000Z

Yep, I’m not stressed about it, just though you might need to know :-) I’ll try the other email

…

On 2/02/2022, at 12:31 PM, dlmcpaul ***@***.***> wrote: Yes sorry, that's a debug I left in there. Try sending any images to my email dlmcpaul AT gmail.com — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ7HQJYQWPVMAWKCZWOB5N3UZBUOHANCNFSM5J45J7ZQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.

Answer 17 · 2022-02-05T23:59:51.000Z

Ok, I have added a default for the database to the docker file. Try the latest image. It should also remove the logging.

Answer 18 · 2022-02-08T00:07:08.000Z

Have updated the container, and it’s working perfectly. Thanks heaps!

…

On 6/02/2022, at 1:00 PM, dlmcpaul ***@***.***> wrote: Ok, I have added a default for the database to the docker file. Try the latest image. It should also remove the logging. — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ7HQJ5EEZBQYTJL6RY6VW3UZW2YDANCNFSM5J45J7ZQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.

Answer 19 · 2022-02-08T02:43:04.000Z

Cool. I will close this issue off then.