So, what are you doing with the API? #65
Replies: 51 comments 101 replies
-
I'll start. Obviously, I'm using Home Assistant. I've written an appdaemon script that automatically turns my air conditioner (central heating and cooling) on and off based on the price, and current temperature, and whether my wife and I are home or not (That is less interesting at the moment, given lockdown). The next thing to take into consideration is current solar generation and house consumption. |
Beta Was this translation helpful? Give feedback.
-
Smarts around car charging
Sep 1, 2021 1:32:46 PM Myles Eftos ***@***.***>:
… Everyone in the office is insanely interested in what you are using the API for.
We'd love to hear about the automation you are building or the reports you are building.
So, come on! Time for some showing off!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub[#65], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ABGOASB74ASM4NHGVDXT4J3T7WNFZANCNFSM5DFPU6XQ].
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]. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAFQAAABUCAYAAAAcaxDBAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAySURBVHic7cEBDQAAAMKg909tDjegAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAeDVulAABbzDScQAAAABJRU5ErkJggg==###24x24:true###][Tracking image][https://github.com/notifications/beacon/ABGOASFQ66UPAG53FD6AFWLT7WNFZA5CNFSM5DFPU6X2YY3PNVWWK3TUL52HS4DFVJCGS43DOVZXG2LPN2VGG33NNVSW45C7NFSM4ABWFETA.gif]
|
Beta Was this translation helpful? Give feedback.
-
Tesla
…On 1/9/21 6:34 pm, Myles Eftos wrote:
What car do you have?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#65 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGOASFZZTFR7OWIRE2WQLTT7XQQ3ANCNFSM5DFPU6XQ>.
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>.
|
Beta Was this translation helpful? Give feedback.
-
I have a selection of grafana reports from my PV inverter, Amber electric and other environmental metrics. I have a more generic view in home assistant so the family can plan around energy price |
Beta Was this translation helpful? Give feedback.
-
This is in the kitchen/lounge so everyone gets a sense of what's going on with prices. Especially around that hot-spot for pricing around dinner time. . . . . Again, using Home Assistant of course. Purple is super-cheap . . . . . 14c and under. I think it has really conditioned me into being responsive because I even think energy is expensive (and get the urge to turn stuff off) when I see the red LED's are glowing on my sons bed . . . . even thought it's not at all connected . . . Oh yea .. . . |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
It's not as interesting as anything above, but this is what I've been doing with the API today. The code's online if you're interested. |
Beta Was this translation helpful? Give feedback.
-
This is cool & very useful to compare against bills. Thanks.
From: Graham Lea ***@***.***>
Date: Sunday, 12 September 2021 at 00:10
To: amberelectric/public-api ***@***.***>
Cc: vijvis ***@***.***>, Comment ***@***.***>
Subject: Re: [amberelectric/public-api] So, what are you doing with the API? (Discussion #65)
It's not as interesting as anything above, but this is what I've been doing with the API today. Code's online if you're interested.
#70<#70>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#65 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASLLY3ODFB67KSOAIZOJXLTUBNPPBANCNFSM5DFPU6XQ>.
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>.
|
Beta Was this translation helpful? Give feedback.
-
Just ran this on macOS Big Sur & worked perfectly. Got data downloaded from 27 November 2020 to date. I think that was the date I moved to Amber.
We are building a new home next year so this will help with solar planning.
Thanks, heaps.
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: Graham Lea ***@***.***>
Sent: Sunday, September 12, 2021 12:10:56 AM
To: amberelectric/public-api ***@***.***>
Cc: vijvis ***@***.***>; Comment ***@***.***>
Subject: Re: [amberelectric/public-api] So, what are you doing with the API? (Discussion #65)
It's not as interesting as anything above, but this is what I've been doing with the API today. Code's online if you're interested.
#70<#70>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#65 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASLLY3ODFB67KSOAIZOJXLTUBNPPBANCNFSM5DFPU6XQ>.
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>.
|
Beta Was this translation helpful? Give feedback.
-
Thanks for this. I will try out this automation with my light strip.
From: RatMondeo ***@***.***>
Date: Saturday, 11 September 2021 at 17:09
To: amberelectric/public-api ***@***.***>
Cc: vijvis ***@***.***>, Comment ***@***.***>
Subject: Re: [amberelectric/public-api] So, what are you doing with the API? (Discussion #65)
Hi,
I am not great at Home Assistant stuff, so there are likely better ways of going about it.
I created an Automation following the details below. (Configuration->Automation) Then duplicated that Automation and adjusted for each price range and associated light colour.
I then have them all running.
I also run another Automation to turn the light off at 10:25pm.
Let me know if you have any questions . ..
Automation:
Trigger Type: Numeric state
Entity: sensor.general_price
Above 1
Below 14
[Capture0]<https://user-images.githubusercontent.com/34613491/132939769-95aab150-d849-4dab-91b2-831470c7024b.JPG>
Condition:
Condition Type: time
Fixed time
After 06:30 am
Fixed time
Before 10:24 pm
Mon - Sunday
[Capture1]<https://user-images.githubusercontent.com/34613491/132939665-8f0f5b0e-15c1-434b-9bad-2ac0175d4648.JPG>
Actions:
Action Type: Call Service
Service: light.turn_on
Target: yeelight (or choose your hue light)
Color name: choose your colour
[Capture2]<https://user-images.githubusercontent.com/34613491/132939683-993e9bb4-56b1-472d-a11f-e4b861ab23c2.JPG>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#65 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASLLY3MMZIGLNYMJTCMAVNLUBL6EDANCNFSM5DFPU6XQ>.
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>.
|
Beta Was this translation helpful? Give feedback.
-
I use Node Red as my primary engine and then feed stuff into Home Assistant when required. My system is setup for grid arbitrage and am just putting tweaks to it as i go - only got the batteries and inverters for them last month
So here is my main energy screen - enables me to see the current and forecast prices as well as the 5 min interval prices for Buy and Sell It also lists my house consumption, grid, Solar and Battery - averaged over 1,5,15 minute intervals. Heating and Cooling - just got a new AC with Airtouch so am busy automating that and integrating it in and the battery control screeen which is a WIP at the moment Obviously my strong suite is not visual presentation !! Our node red system keeps track of overall house useage, amber prices and battery SOC, as well as expected solar output and then schedules loads around these - some things can be turned on automatically - such as the pool pump, others have emails sent out to advise it would be a good time to turn the dishwasher on, put on a load of washing etc. Today the system estimated we would get 95Kwh of Solar (seems to be tracking pretty closely at the moment) so it ran the batteries down overnight to 2% SOC, then took up the load this morning - but rather than charge from excess solar - suggested to hold off charing until 10am as Amber Solar prices were >= 5c, then suggested to put the batteries on auto charge mode, put the heatpump on to heat the downstairs area of the house (Hydronic heating) and push the pool pump on time back to 12:30 I am trying to get all of these suggestions done through telegram bots at the moment but struggling with that short term (not enough time in the day) Craig |
Beta Was this translation helpful? Give feedback.
-
Automated battery charging/discharging, and HWS control based on realtime pricing and current PV output! https://www.youtube.com/watch?v=kk8ODGYoLLs&list=PLT7ckgz8vcoaKxfTzRYrETgsowRkP41y3&index=1&t=7s I'm in the process of plugging in weather forecasting, so if looks like it's going to be a low-solar day tomorrow, tweak the price thresholds so the battery charges up on cheap power overnight. |
Beta Was this translation helpful? Give feedback.
-
I'm just pulling data so i can search for data-points such as how many times does the value "cost" have a - after it, and then manually checking how many times there is a sequential negative cost event etc, I'm mainly using the API to gather information manually from the JSON file so as to get a better result from load shifting. |
Beta Was this translation helpful? Give feedback.
-
The tuning process has been removed as of June and they have instead allowed you to define two solar plants instead
Craig
From: RatMondeo ***@***.***>
Sent: Thursday, September 30, 2021 11:10 AM
To: amberelectric/public-api ***@***.***>
Cc: Craig Curtin ***@***.***>; Comment ***@***.***>
Subject: Re: [amberelectric/public-api] So, what are you doing with the API? (Discussion #65)
@solrai38<https://github.com/solrai38> I have noticed that Solcast have a "Tuning" process that allows you to upload your data so they can tune your site for shading and other impacts so the forecast is even more accurate. Have you had a look at this, what are your thoughts?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#65 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM6OST7U474RVCS2REDV7ULUEO2GHANCNFSM5DFPU6XQ>.
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>.
|
Beta Was this translation helpful? Give feedback.
-
I am feeding current price data into OpenHAB along with current usage via Rainforest Eagle that talks to the meter via Zigbee. Some basic automation of reserve cycle heating based on price (mainly to shut it off). Looking to get the home solar figures in there so I can calculate a true renewables figures and use this for automation as well as price. |
Beta Was this translation helpful? Give feedback.
-
@madpilot - I was using your ESP32 code to make a simple desktop LED to show the current kWh price; soon to add a 10A relay to automatically control a heater (interlocked with PIR sensor for extra safety). Just for anyone else doing this, note the difference between HTTPClient.h - espressif/arduino-esp32 & amcewen/HttpClient: Arduino HTTP library - same name, different libraries. I wasted a fair bit of time figuring this out :) |
Beta Was this translation helpful? Give feedback.
-
I just made an ios shortcut in siri shortcuts app where you get real price with a voice command and also made a youtube video on it |
Beta Was this translation helpful? Give feedback.
-
@madpilot helped me on my way with this back on March 12. I don't use HA but an automation hub called Homey Pro from Athom. Since I started I have now developed a functioning system that has the following basic functions built around the Amber API and the data I pull from my Tesla Gateway and the Fronius inverter. Alerts on my Apple Watch (via Homey Pro) et al. re Amber sell and buy prices, basically when the FIT changes from -ve to +ve, when the sell price goes -ve, and when the sell price is low (set to <10c at the moment but it can be adjusted. Alerts for when SmartShift changes state. Charging, Discharging, Preserve and back to consume. This has been great for those times when I know I need extra power to charge my car, or run the heater overnight, and I don't want to Sell, or at other times I don't want to charge. Curtailment of my Fronius inverter. I started thinking I would use Solcast as the basis for this, but even Solcast ended up being too inaccurate to do this properly. My current solution is simple. Using the Amber API I calculate the number of hours (I'm pretty sure you can only get the number of 30 min slots) the the FIT will be negative for. Then using my current battery level I calculate how long it will take at the current solar production level to take the battery to 100%. If this time is greater than the negative FIT duration then do nothing. If it is less then calculate the WMaxLmtPct value to send to the Fronius inverter so that 100% will not be reached before that time. I run this every 10 minutes. I actually have 2 inverters, an old Solax, and I can't curtail that one, so the algorithm takes that into account. So far this is working well. I now have all of my Solar system data on a wall mounted dashboard as well. No where near as sophisticated as those I have seen developed by the HA guys, but good enough. I would be happy to share any code I have developed as I'm sure someone may come back with improvements, but as I'm not using HA it may not be of use, although the main algorithms are pretty standard javascript. I hope this is of some interest. I have certainly learned a lot doing that. I used to write a lot of code in the far distant past but never Java. I started out using copilot (which can be quite frustrating) and found this a good technique to learn a new language. |
Beta Was this translation helpful? Give feedback.
-
Thanks for sharing, I'm I big Home Assistant guy, but I do appreciate the other eco systems out there and at the end of the day I'm all for open data so people can utilise in the systems they want to.
I'm very interested in how you are determining which states Smart shift is going to as this is really useful to understand what it is trying to do. Indeed the AmberAPI sharing which mode SmartShift is currently in would be a useful extension. I can tell when the battery switches to Import/ Charging or Export/ Discharging, with the help of the Powerwall Gateway Grid Services flag, but have not been able to determine rules for when SmartShift is in Preserve or Consume modes. Can you share how you are determining those modes of SmartShift? |
Beta Was this translation helpful? Give feedback.
-
Ok, I’ll start a new discussion, I’ll call it “Amber SmartShift State Alerts”Peter0419852304On 25 Apr 2024, at 11:44 AM, Mark Purcell ***@***.***> wrote:
You can share here, or maybe even start a new discussion.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Done
… On 25 Apr 2024, at 11:44 AM, Mark Purcell ***@***.***> wrote:
You can share here, or maybe even start a new discussion.
—
Reply to this email directly, view it on GitHub <#65 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7VEVGKOSTBQKLW3BKXKCKTY7BNX5AVCNFSM5DFPU6X2U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TSMRRHE2TSMI>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
that error suggests the tesla is no longer on the network, at least at that ip. |
Beta Was this translation helpful? Give feedback.
-
Integrating my Shelly EM power meter and the Amber Controlled load price to turn off/On my Hot water system. |
Beta Was this translation helpful? Give feedback.
-
This is more of a comment on how I would like to be using the API, rather than how I am using it today. I would first and foremost like to be able to issue 'manual control' commands back to control my batteries (Tesla Powerwall 2). This is the missing piece of the puzzle for me. In short, I would like to write my own algorithm to either work alongside SmartShift, or replace it for our use case. It was explained to me via support ticket, the parameters used that SmartShift uses to make decisions. I would like to use some different parameters. First consideration in my case - I have a constant workload at home, depending on time of year, of about 2kw, 24/7 (varying by 0.4kw either side). This would be one consideration in my planning of how we would buy and sell electricity in the day, as it is a known factor, that is site specific. I am sure SmartShift will eventually figure this out, but after my first month, it doesn't seem quite there yet (my suggestion in my ticket was allow SmartShift to get some 'hints', including constant workload, to help it make better decisions). Knowing my workload may influence how much I keep in the battery to 'get us through' until pricing is cheaper if I was able to buy earlier at a cheaper price. Second thing is I would like the algorithm to consider is the actual (well, approximate) cost of import vs likely or current sell price, as well as future pricing, to decide when to sell, how much to sell, and so on. Not just on a short-ish trajectory, but for the day ahead, and what we're seeing as common in the season. I believe we could make estimates on cost of import working directly with the Telsa Powerwall API to see what we are doing periodically (say every 5 minutes), and the Amber API to get the cost at that time, to figure out approximate total cost of incoming electricity, including solar imports (which I would assign a cost of $0). I could source the 'what are we doing' via amber as well instead of Tesla, but it would not be as up to date if this was made available (I'm not sure I see it at first glance, but could have easily missed it) - this would make sense to support all batteries you support. From there, I would be thinking I would store that average cost of current electricity held in battery in some variable, and be looking at current cost to charge more, current solar forecasts, electricity buy and sell price forecasts, and also want to consider in terms of buying and selling what the cost is, but how much electricity we will really get less expected overheads (as we don't have 100% efficiency to buy or sell), to then make decisions from there based on all the data we have available (from amber, Tesla and solar forecast data, as well as array performance estimates). Third thing I would like to address is the Tesla Powerwall API battery charge state vs. real-world usable charge state. The Tesla Powerwall API in my case reflects ~5% left in the battery, when this is not actually usable energy, and I know you're reading the same values - so Smartshift thinks there is 5% available, which there isn't in real terms. The Tesla app at this point reflects 0% and will not use that last 5%. I would, as a result, want the personalised algorithm to consider the 'usable' battery rather than what is actually left in there technically speaking - because it is only the usable capacity we can use, so that is what decisions would need to be based on. To workaround this issue for the moment, I've told SmartShift to align at 5%, but it means the battery numbers SmartShift is going off remain wrong, but at least it knows it cannot discharge below 5%. What it doesn't known is as a result, the numbers are offset by a variable amount (which shrinks as you approach and reach 100%). This also impacts the statement Amber makes about not discharging below 25%... in my case, reality is, Amber will discharge the batteries to 19-20% usable, then stop, because of this offset between API and real usable capacity. Forth thing I would like to do is add some decisions for future control (rather than me say, staying up to 'control my battery') - say 'at 3AM, if pricing < $x, or until pricing is < $x, then, charge battery until pricing > $y or battery charge % == $z)... things like this would be useful. If I could give SmartShift programmatically determined manual direction, via the API, that would be awesome, but would also be happy to write my own algorithm from scratch that fits my needs exactly - either way, I really need (or desperately want) 'manual control' to be available via API. Is there any chance you could make this available to us? Pretty please! I am super keen. So keen I've considered using a different API that can control and iOS app and click buttons for me (Quamotion - https://github.com/quamotion/python)... but that's a total hackjob workaround, and I would much rather use a proper API published by Amber! I also understand much of what I want could be written into SmartShift, and a lot of it is there in some form (just not exactly how I want it to work for my specific use case). If you choose to add similar features or address some of the things I want to address in time directly there in SmartShift, I'd be very happy with that too. Other things I want to do (like some more logic based decisions) may be more advanced than you want in an app form. Either way, I am happy to experiment with writing my own bits and pieces, and share them in case you want to include them in your own software later too if you can please, please, please provide 'manual control' in the API! |
Beta Was this translation helpful? Give feedback.
-
You must not understand how the.vendor portals (tesla, fronius, solaredge, sungrow etc work) - what you are asking for is amber to individually send those commands just for your battery - rather than a bulk command to say allow all batteries in Sydney in the tesla portal that are registered to amber to do the same thing (I.e. one api call versus hundreds/thousands. To.do what you want you have to take local control - have a look at.home assistant as an example
Sent on the go with Vodafone
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: gmo81 ***@***.***>
Sent: Saturday, June 22, 2024 12:29:46 PM
To: amberelectric/public-api ***@***.***>
Cc: Craig Curtin ***@***.***>; Mention ***@***.***>
Subject: Re: [amberelectric/public-api] So, what are you doing with the API? (Discussion #65)
This is more of a comment on how I would like to be using the API, rather than how I am using it today.
I would first and foremost like to be able to issue 'manual control' commands back to control my batteries (Tesla Powerwall 2). This is the missing piece of the puzzle for me.
In short, I would like to write my own algorithm to either work alongside SmartShift, or replace it for our use case.
It was explained to me via support ticket, the parameters used that SmartShift uses to make decisions. I would like to use some different parameters.
First consideration in my case - I have a constant workload at home, depending on time of year, of about 2kw, 24/7 (varying by 0.4kw either side).
This would be one consideration in my planning of how we would buy and sell electricity in the day, as it is a known factor, that is site specific. I am sure SmartShift will eventually figure this out, but after my first month, it doesn't seem quite there yet (my suggestion in my ticket was allow SmartShift to get some 'hints', including constant workload, to help it make better decisions).
Knowing my workload may influence how much I keep in the battery to 'get us through' until pricing is cheaper if I was able to buy earlier at a cheaper price.
Second thing is I would like the algorithm to consider is the actual (well, approximate) cost of import vs likely or current sell price, as well as future pricing, to decide when to sell, how much to sell, and so on. Not just on a short-ish trajectory, but for the day ahead, and what we're seeing as common in the season.
I believe we could make estimates on cost of import working directly with the Telsa Powerwall API to see what we are doing periodically (say every 5 minutes), and the Amber API to get the cost at that time, to figure out approximate total cost of incoming electricity, including solar imports (which I would assign a cost of $0). I could source the 'what are we doing' via amber as well instead of Tesla, but it would not be as up to date if this was made available (I'm not sure I see it at first glance, but could have easily missed it) - this would make sense to support all batteries you support.
From there, I would be thinking I would store that average cost of current electricity held in battery in some variable, and be looking at current cost to charge more, current solar forecasts, electricity buy and sell price forecasts, and also want to consider in terms of buying and selling what the cost is, but how much electricity we will really get less expected overheads (as we don't have 100% efficiency to buy or sell), to then make decisions from there based on all the data we have available (from amber, Tesla and solar forecast data, as well as array performance estimates).
Third thing I would like to address is the Tesla Powerwall API battery charge state vs. real-world usable charge state. The Tesla Powerwall API in my case reflects ~5% left in the battery, when this is not actually usable energy, and I know you're reading the same values - so Smartshift thinks there is 5% available, which there isn't in real terms. The Tesla app at this point reflects 0% and will not use that last 5%.
I would, as a result, want the personalised algorithm to consider the 'usable' battery rather than what is actually left in there technically speaking - because it is only the usable capacity we can use, so that is what decisions would need to be based on. To workaround this issue for the moment, I've told SmartShift to align at 5%, but it means the battery numbers SmartShift is going off remain wrong, but at least it knows it cannot discharge below 5%. What it doesn't known is as a result, the numbers are offset by a variable amount (which shrinks as you approach and reach 100%). This also impacts the statement Amber makes about not discharging below 25%... in my case, reality is, Amber will discharge the batteries to 19-20% usable, then stop, because of this offset between API and real usable capacity.
Forth thing I would like to do is add some decisions for future control (rather than me say, staying up to 'control my battery') - say 'at 3AM, if pricing < $x, or until pricing is < $x, then, charge battery until pricing > $y or battery charge % == $z)... things like this would be useful.
If I could give SmartShift programmatically determined manual direction, via the API, that would be awesome, but would also be happy to write my own algorithm from scratch that fits my needs exactly - either way, I really need (or desperately want) 'manual control' to be available via API.
Is there any chance you could make this available to us? Pretty please! I am super keen. So keen I've considered using a different API that can control and iOS app and click buttons for me (Quamotion - https://github.com/quamotion/python)... but that's a total hackjob workaround, and I would much rather use a proper API published by Amber!
I also understand much of what I want could be written into SmartShift, and a lot of it is there in some form (just not exactly how I want it to work for my specific use case). If you choose to add similar features or address some of the things I want to address in time directly there in SmartShift, I'd be very happy with that too.
Other things I want to do (like some more logic based decisions) may be more advanced than you want in an app form. Either way, I am happy to experiment with writing my own bits and pieces, and share them in case you want to include them in your own software later too if you can please, please, please provide 'manual control' in the API!
—
Reply to this email directly, view it on GitHub<#65 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM6OSTZB27MGPQBOHXAX7XLZITORVAVCNFSM5DFPU6X2U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TSOBUGQ3TSOI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I've been using it historically just to turn off all my heating/cooling in the house when a spike comes using first IFTTT and now Home Assistant. However, I've just taken it to the next level, now I set an offset based on the power descriptor tags. For example when the price is low, my climate system will aim for the target temperature, say 21. When it's high it'll aim for between 18 and 24. Insulation is good in my house, so intending to just leave it on 24/7. |
Beta Was this translation helpful? Give feedback.
-
If you are on FB – then check out the Home Assistant with Amber forum – Mark Purcell is quite active up there and is one of the leading proponents of EMhass and appears to know it inside out.
Craig
From: petebitt99 ***@***.***>
Sent: Monday, June 24, 2024 9:34 AM
To: amberelectric/public-api ***@***.***>
Cc: Craig Curtin ***@***.***>; Mention ***@***.***>
Subject: Re: [amberelectric/public-api] So, what are you doing with the API? (Discussion #65)
Thanks for this discussion. I am following with interest.
I would appreciate your view on a couple of thoughts I have on the topic.
1. Not sure if this is one of the basis' of SS decisions but I note that when SS decides to Discharge it does it with an explanation that we are getting a good price for our Solar. It does not seem to have an awareness that in Victoria at this time it is basically cold with no sun, and therefore the power in my battery has been purchased from the grid at the lowest possible price. In which case the FIT is generally not a good price.
2. Is the EMHASS algorithm, or simply your way of thinking, based on mathematical models to reduce your energy cost to the lowest possible value regardless of your batteries SoC? The reason for my question is that for me, based in Victoria, and being the middle of winter, I simply set a target that my battery is 100% full (sometimes @ 40c/kW) by 3pm and that all power intensive loads are carried out before 3pm. I have 27kW of battery, and when it is cold and I'm running heaters I need more than that to get me from 3pm until 9 or 10am the next day, so generally need a charge overnight to get me through. It would be great to be able to schedule that based on the price data we get back through the Amber API. Bring on that SS API!!
So - does this make sense, or is my logic flawed and would I get cheaper power by using different logic?
—
Reply to this email directly, view it on GitHub<#65 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM6OST3QTDKLI3TRWFQI3ALZI5LQHAVCNFSM5DFPU6X2U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TSOBVGQ2DEMY>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Beta Was this translation helpful? Give feedback.
-
Thanks for jumping in Mark.
Quick question – is there a way to set demand tariffs in EMHass ? Currently all of my stuff is locally controlled in Node Red – but I keep on meaning to try and get around to trying Emhass – if it supported demand tariffs that might be something that tipped me over the edge
Craig
From: Mark Purcell ***@***.***>
Sent: Monday, June 24, 2024 10:26 AM
To: amberelectric/public-api ***@***.***>
Cc: Craig Curtin ***@***.***>; Mention ***@***.***>
Subject: Re: [amberelectric/public-api] So, what are you doing with the API? (Discussion #65)
2. Is the EMHASS algorithm, or simply your way of thinking, based on mathematical models to reduce your energy cost to the lowest possible value regardless of your batteries SoC? The reason for my question is that for me, based in Victoria, and being the middle of winter, I simply set a target that my battery is 100% full (sometimes @ 40c/kW) by 3pm and that all power intensive loads are carried out before 3pm. I have 27kW of battery, and when it is cold and I'm running heaters I need more than that to get me from 3pm until 9 or 10am the next day, so generally need a charge overnight to get me through. It would be great to be able to schedule that based on the price data we get back through the Amber API. Bring on that SS API!!
EMHASS will calculate that optimisation for you, for both your battery but also your household loads. (SmartShift only optimisations for your home battery but soon EVs as well.)
image.png (view on web)<https://github.com/amberelectric/public-api/assets/79175134/41fc9b4d-eb83-4bd4-9977-af957b255b6c>
You can see here in my forecast that it has scheduled my loads; EV charging, pool Heater, hot water and home battery charging to 100% to all complete before sunset because the cost of consumption for those is the lowest at that time. It then schedules export of my home battery during the evening price peak, but holds back reserves until.
You can see my heaters in the load forecast and it takes this into account when working out how much to export and how much to hold back. SmartShift does the same calculation. So it does work well in the Victorian winter, when solar production is low and overnight consumption demands are high.
—
Reply to this email directly, view it on GitHub<#65 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM6OSTYDB3LZ6D44PMIZTMDZI5RQXAVCNFSM5DFPU6X2U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TSOBVGQ3DGNI>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Beta Was this translation helpful? Give feedback.
-
Thanks Mark – whilst I could switch back to a TOU tariff with no demand window – it would only be for a year when Ausgrid then make demand tariffs compulsory. So better off with the pain now as it comes with some other benefits.
We already have the feed in “tax” from Ausgrid and I have setup my inverters to ramp down output during that time so all good there.
Might set myself a task to start with emhass and see how I go
Will investigate the link you provided to Cruickshank – thanks
Craig
From: Mark Purcell ***@***.***>
Sent: Monday, June 24, 2024 10:58 AM
To: amberelectric/public-api ***@***.***>
Cc: Craig Curtin ***@***.***>; Mention ***@***.***>
Subject: Re: [amberelectric/public-api] So, what are you doing with the API? (Discussion #65)
Quick question – is there a way to set demand tariffs in EMHass ? Currently all of my stuff is locally controlled in Node Red – but I keep on meaning to try and get around to trying Emhass – if it supported demand tariffs that might be something that tipped me over the edge
NodeRed and EMHASS work really well together. cf @rcruikshank<https://github.com/rcruikshank> above.
EMHASS doesn't have a calculation for demand tariff per say, but you can control the inputs and outputs and modify them as you want. So you could use HA to keep track of your highest peak consumption window so you know what your demand tariff bill will look like.
You could also inflate the prices during the demand tariff window before you inject into EMHASS so it would avoid importing at that time and then finally you could have conditions on your battery automation so even if EMHASS did want to import you could blacklist your demand window so it wouldn't import. Demand tariffs are hard to optimise for but it is something I'm going to need to get across as Energex are going to be introducing a reverse demand tariff with their two way tariffs as a disincentive for exporting during the day.
My best advice is to switch to a ToU tariff without a demand component if you can..
—
Reply to this email directly, view it on GitHub<#65 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM6OST56UNBFP3HNFC7C3ATZI5VLBAVCNFSM5DFPU6X2U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TSOBVGQ3TKMY>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Beta Was this translation helpful? Give feedback.
-
Everyone in the office is insanely interested in what you are using the API for.
We'd love to hear about the automation you are building or the reports you are building.
So, come on! Time for some showing off!
Beta Was this translation helpful? Give feedback.
All reactions