Amber API process

[petebitt99]

I am just starting trying to use the Amber API and have a few questions.
I have generated the API token - will I be able to continue to use this key or will it change over time?
I have used the key to authorise API calls and run some tests. I got my site ID doing this. Is the site ID static? Or can it change?
I intend to call the API's using Homey (homey.app) which is already integrated to my Tesla Gateway, so with the info from Amber I will be able to build some logic into a Dashboard which will either notify me of certain conditions, or allow me to control my load.
I'm hoping I can get this going and then contribute / test the Amber API so that I can develop further automations.

[rob0101]

Welcome.
The key and the site ID are static.

[petebitt99]

Ok, I will have to knock up some test code in Homey.
So do I need to do this
curl -X 'GET'
'https://api.amber.com.au/v1/sites'
-H 'accept: application/json'
-H 'Authorization: Bearer psk_f31a4b0b3ee67b8db63067a7d0385bd0'
before I make the call for current prices?
If the answer is yes advice on where I can go to work out how to use cURL would be appreciated.

[madpilot]

That call will return your site id, so you don't really need to do it before every call - you can do it once and then save it. The only time you need to do it again is if you leave Amber and sign back up (a new site is added to the results).

You should just be able to cut and paste that in to your terminal. What operating system are you on?

[petebitt99]

It is a home automation hub (https://homey.app/en-au/blog/a-technical-introduction-homey/) which has an ARM processor running Linux. It is Java script based and allows me to write what they call Homey script from which I would call the API.
Example Homey script:
// Function to shuffle an array
function shuffleArray(arr) {
let newArr = arr.slice();
for (let i = newArr.length - 1; i > 0; i--) {
const j = Math.floor(Math.random() * (i + 1));

[madpilot]

Looks like it's just a straight up Node-based JavaScript script.

Something like this should get you started:

const apiKey = 'psk_f31a4b0b3ee67b8db63067a7d0385bd0'
const siteId = '01H92N0GC70BAZHM48P2C52J3M'

const response = await fetch(`https://api.amber.com.au/v1/sites/${siteId}/prices/current`, { 
  headers: { 
    'Authorization': `Bearer ${apiKey}` 
  } 
}
const prices = await response.json()
const generalPrice = prices.find((price) => price.channelType === 'general')?.perKwh
const feedInPrice = prices.find((price) => price.channelType === 'feedIn')?.perKwh

[petebitt99]

Thank you. There was a missing ); just before const prices. Other than that it worked perfectly. Thanks again for your help.

[petebitt99]

Great, that's all working now and I can get notifications when the FIT is negative and my Battery SoC is >95% etc.

Looking at the API descriptions it looks like there is no way to find out programmatically when Smartshift canges state from Consume Battery. Can you confirm please.

Smartshift regulary puts my system into the Preserve state, meaning I draw from the grid, even though there is no need for me to do so. Unless I'm missing something. I would like to get notifications of these shifts in state.

[madpilot]

Coming soon

[petebitt99]

I don't suppose the "coming soon" might include the days sun outlook?

[petebitt99]

Yes I agree. It is the better option. Although with the javascript I can make both work. I am slowly putting together the components I need for a solar management system. I can now get how much solar is expected to be produced over the next 3 hours, the expected charge level of my battery in that time, and for how many minutes into the future the negative Fit is expected to last. Now I need to create the logic for when and at what level I throttle the inverter. Although I know nothing about HA I suspect that if I was using it this has already been worked out.

…

On 28 Mar 2024, at 11:25 am, Myles Eftos ***@***.***> wrote: There are two different end points - the /prices endpoint you are describing there. The current prices endpoint is /prices/current which takes next and previous attributes. Are you sure you aren't getting the two confused? — Reply to this email directly, view it on GitHub <#196 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7VEVGIWLKLYBWM2VY7OLHLY2NPPFAVCNFSM6AAAAABERLVM5WVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSMZUGU2TS>. You are receiving this because you authored the thread.

[madpilot]

The main reason you want /prices/current not /prices is with the latter at 5 minutes to midnight, you only have one forecasted price to work with, where as /prices/current will always return n forecasts in to the future.