Myles Eftos
Myles Eftos
> > This is an issue on the Amber side, not the integration. > > The 500 error certainly suggested that, but since it worked by accessing the API directly,...
A single actual sensor would always read the correct actual price, which fixes the history revision issue you have. Perhaps that’s a better compromise? Call the sensor “Last actual”, and...
> I'm not sure how true this is. I do notice that AEMO occasionally [reviews](https://aemo.com.au/market-notices?marketNoticeFacets=PRICES+SUBJECT+TO+REVIEW) the historical prices and [adjusts](https://aemo.com.au/market-notices?marketNoticeFacets=PRICE+ADJUSTMENT) them in some rare cases. > But to be honest,...
If they are showing up in your Amber app, then uninstall the integrations and reinstall it. if they aren’t showing in the app, contact [email protected] - either your installer hasn’t...
@homeassistant close
Can you please email [email protected] - I need to have a look at your account
Tagged the release https://github.com/madpilot/amberelectric.py/releases/tag/v2.0.1
Amazing. Thank you!
Not sure how to fix this - we use the Home Assistant built in polling mechanism. I'll ask on discord.
Are you a new customer? It might not be able to find a valid site yet.