-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
My first project. #8
Comments
That looks amazing, is that the bigger version of the display from pimoroni? |
Yeah. The inky what Loads of work to do with the weather side of it. Layout needs some work. |
That looks impressive. I was pondering myself about writing something to work out the cheapest 3hr block strangely as I forever work out best time to run the dishwasher. |
Thanks. The cheapest 2 hours, 3 hours is pretty easy to do. No idea how to use GitHub either to be honest to upload it. I've got negative pricing sorted and can also graph it with an outline, not black or red. I've added a API call for prices upon reboot in case it's been off for a day or more. Still some tweaking to go, have loads of weather choices, not sure I need a min temp forecast. When I'm actually on the tariff (hurry up smart meter) I think I can call the API for my last half hours useage, which I plan to. |
You're not the only one who doesn't know how to use github!! It's not that hard to get some code on. I haven't a clue about the rest of the features though, every time I try to learn git my brain drifts off, I don't know why. I think there's a lot of unusual terminology that I can't work out. I've coded something for usage already in django so give me a shout if you need any of it. It's not that hard, the only pain is that it's half hourly and dealing with that is really annoying.
That's the bit to store your consumption for the last 1000 "half hours". Oh, some bad news though - the octopus API pretty much updates meter usage as and when it feels like it, around 5pm every day for the day before's usage. So, if you want live usage, well, I've managed it myself but using an energyhive/efergy clip on energy monitor..using their API. Which is really smart. That's a whole kettle of worms though, has nothing in common with octopus energy. How did you manage to upload a photo btw? I assume you know where the API reference is -> https://octopus.energy/dashboard/developer/ |
I would really like to change the cheapest price on the standard Inky pHAT to point me to the beginning of the cheapest 3 hour period. I'm no coder either, and I can't begin to work it out!! |
You could ask @Chipgit if he can upload his code, I had a look at his forked repository but either it doesn't show the code for the "cheapest 2 hours" or...I'm being dumb. Possibly the latter. |
You're right. Not used this before. I'm been messing around with the layout and function. I'll get round to updating shortly. The code for finding out the cheapest 2hr period is below. pricesonly = [i for i in prices[:48] if i != 0 ] # Removing Zero Prices with max 24hrs returned Initially just creates a new list of 4 added together, then gets the "min" value, and the time. pricechunk = [] cheapestChunkIndexs = [] Code to display the above min_offset = pricechunk.index(minimumchunk) * 30 |
It seems like a good thing to have so I'll try to merge it into the code...adding up groups of 2n (n=time period required) and looking for the min...now that is a cool way of doing it! |
Many thanks.
This was my first Pi project and although it's still work in progress it's been an amazing journey.
I've added the use of a weather API to bring in live weather data to fill in the display.
Added code to deal with negative pricing and displays this as a black outlined clear blocks on the graph.
Also displays the cheapest 2hr block to use dish washers, washing machines etc.
Printed a 3d case.
The text was updated successfully, but these errors were encountered: