Enever NULL values cause time shift in Enever_Electricity_tomorrow variable
Posted: Saturday 08 February 2025 21:34
Hi, I've been using the Enever price feed for several months and I automate stuff based on the price. Perfect.
However, recently I noticed sometimes that there's something wrong with the timing of my automations.
After investigating I found that the Enever price feed for tomorrow (9-Feb-2025) has NULL values for 05:00 and 06:00 for all suppliers. (via https://enever.nl/api/stroomprijs_morgen.php?token=abc), like this for 05:00:
{
"datum": "2025-02-09 05: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
},
However, Domoticz doesn't seem to check the time-stamp in the JSON: there are 22 price points from 0:00 till 21:00 in the variable Enever_Electricity_tomorrow. And I use this variable as the basis for my automations.
So in the variable 22:00 and 23:00 are missing, instead of 05:00 and 06:00.
The price at 07:00 became 05:00 in the variable, 08:00 --> 06:00, etc. and therefore my automation timings are off by 2 hours.
Does anybody else experience this? Or should I skip the variable/Domoticz functionality and read from Enever directly?
Thanks!
(Domoticz 2024.7 on RPi)
However, recently I noticed sometimes that there's something wrong with the timing of my automations.
After investigating I found that the Enever price feed for tomorrow (9-Feb-2025) has NULL values for 05:00 and 06:00 for all suppliers. (via https://enever.nl/api/stroomprijs_morgen.php?token=abc), like this for 05:00:
{
"datum": "2025-02-09 05: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
},
However, Domoticz doesn't seem to check the time-stamp in the JSON: there are 22 price points from 0:00 till 21:00 in the variable Enever_Electricity_tomorrow. And I use this variable as the basis for my automations.
So in the variable 22:00 and 23:00 are missing, instead of 05:00 and 06:00.
The price at 07:00 became 05:00 in the variable, 08:00 --> 06:00, etc. and therefore my automation timings are off by 2 hours.
Does anybody else experience this? Or should I skip the variable/Domoticz functionality and read from Enever directly?
Thanks!
(Domoticz 2024.7 on RPi)