Enever null values for next day results in an incomplete chart

[jvdk]

Sometimes the values from Enever have null values as shown below:

{
"datum": "2025-02-19 01:00:00",
"prijs": "0.099700",
"prijsANWB": "0.277377",
"prijsBE": "0.264487",
"prijsEE": "0.265277",
"prijsEN": "0.269137",
"prijsEVO": "0.277377",
"prijsEZ": "0.277377",
"prijsFR": "0.261697",
"prijsGSL": "0.277377",
"prijsMDE": "0.277377",
"prijsNE": "0.265397",
"prijsTI": "0.268302",
"prijsVDB": "0.265377",
"prijsVON": "0.263462",
"prijsWE": "0.268397",
"prijsZG": "0.277377",
"prijsZP": "0.263497"
},
{
"datum": "2025-02-19 02:00:00",
"prijs": null,
"prijsANWB": null,
"prijsBE": null,
"prijsEE": null,
"prijsEN": null,
"prijsEVO": null,
"prijsEZ": null,
"prijsFR": null,
"prijsGSL": null,
"prijsMDE": null,
"prijsNE": null,
"prijsTI": null,
"prijsVDB": null,
"prijsVON": null,
"prijsWE": null,
"prijsZG": null,
"prijsZP": null
},
{
"datum": "2025-02-19 03:00:00",
"prijs": "0.097670",
"prijsANWB": "0.274921",
"prijsBE": "0.262031",

As a result the chart stops at 01:00 hours:

Graph with missing hours.png (174.04 KiB) Viewed 788 times

Is there something I can do to solve this?

Regards,
Jan

[waltervl]

See the advise I also gave in another topic on this subject: contact Enever why they do this.... Perhaps they are not aware.
viewtopic.php?t=43181

[jvdk]

I just sent a message to Enever about this problem. I hope that helps.

It might be great, however, if Domoticz could handle these missing values.

Regards,
Jan

[waltervl]

Enever also has a Forum so perhaps post the bug report for Null values there too https://enever.nl/forums/

[jvdk]

I tried to post the problem to the Enever forum, but all forums are closed, so no posting is possible.

[HvdW]

At what time are you reading the data.
Enever writes in its website that the data for tomorrow are published at 15:00 and if not at 16:00 utmost.

[ricvee]

I am having the same problem.
I just did send a message to Enever, hoping that they can and will fix it.

[ricvee]

I deleted the Enever hardware, and added it again.
Now there are only 3 new devices added, not the one for Actual Electricity Price:

Schermafdruk van 2025-02-19 19-36-52.png (112.57 KiB) Viewed 618 times

[ricvee]

Answer from Enever:

No, that's something that the developers from the plugin for Domoticz should fix.

So the Enever-plugin is useless for me now ( I am using the latest Stable Version: 2024.7).
Is there someone that can and will fix this?

[waltervl]

Make a GitHub issue related to this forum topic and hope someone can fix this (Domoticz is opensource software...)

[jvdk]

At what time are you reading the data.
Enever writes in its website that the data for tomorrow are published at 15:00 and if not at 16:00 utmost.

I use the "Domoticz built-in Enever "hardware". I do not know when it is updated exactly, but normally the values for the next day are available in Domoticz after 15.00 hours.

[jvdk]

Make a GitHub issue related to this forum topic and hope someone can fix this (Domoticz is opensource software...)

I just did.

Regards,
Jan

Edit Waltervl: the issue: https://github.com/domoticz/domoticz/issues/6265

[HvdW]

What might be your problem is that most of the time 1 or 2 suppliers didn't deliver their values, so your choice has NIL values.

dynamisch.jpg (144.23 KiB) Viewed 519 times

These are the values for today.
I solved it by calculating the average value per hour of the data provided.

[waltervl]

Looking at the first topic it seems enever sometimes shows null for all suppliers on a specific timeslot.
and null should perhaps be interpreted as 0 (zero). Or as the same value from the hour before (if that also is not null...)

"datum": "2025-02-19 02:00:00",
"prijs": null,
"prijsANWB": null,
"prijsBE": null,
"prijsEE": null,
"prijsEN": null,
"prijsEVO": null,
"prijsEZ": null,
"prijsFR": null,
"prijsGSL": null,
"prijsMDE": null,
"prijsNE": null,
"prijsTI": null,
"prijsVDB": null,
"prijsVON": null,
"prijsWE": null,
"prijsZG": null,
"prijsZP": null
},

[jvdk]

It will be solved in the next beta release. See https://github.com/domoticz/domoticz/issues/6265