Open kineticscreen opened 2 years ago
Yeah it's gotten bad
I didn’t get much time to look at it over the weekend, but it appears to be getting worse.
It will be interesting to see what happens this week - if it fixes itself it will confirm a theory I have about the API
ive been running some alternate core on my test setup to see if that helps, but it’s not been as successful as I would have liked
The zeroes are taking over
Mine has stopped working completely this morning - will need to look into it tonight
Weird, might have just kicked itself back to working...
Yeah everything unknown here as well
I'll have a new version up shortly that should fix the unknown issue - the API has been reporting null values which I didn't factor in
Seems to be populating again with that update. Thanks.
0 values are back after a brief reprieve after updating.
Mine is still ok except pumps is showing unknown
@bacco007 is your pumps unknown as well?
No - it must have come out of the NSW dataset
Price data hasn't really recovered. Extemely spotty update frequency, and often reverting to 0.
It seems to be an issue with the API that I’m not sure is fixable now - it often reports zeros for the most recent values but these later get updated as new data flows through (Which makes the graph on the opennem page not report zeros)
im really not sure how to fix these issues with any confidence now - it’s a real pain
Weird, what's changed? It's been fine until recently.
I don’t know, they’ve pushed a new version or two through recently
Hey nik from OpenNEM here - we had some issues with crawling and parsing the raw AEMO data that we have solved over the past week. That endpoint should be a lot more stable now and very current. I'll have a dig into this project when I have a moment and help out on getting it working and stable, I run Home Assistant myself
Sweet, thanks!
Hey @nc9 , just nudging you in case you have any time to have a look at this. The issue of repeated 0 values is now pretty much consistent, at least for the price attribute.
Getting blasts of '0' values on the price attribute again unfortunately: