Enever plugin doenst work anymore

[Havym]

Version: 2024.7
Platform: Raspberri pi 3B+

Since 1 april at 0:00 the build in Enever plugin doenst work anymore and i'm getting errors.

Code: Select all

2026-04-13 09:42:48.128 Error: Enever: Invalid (no) data received (gas prices, date object not found). Check Token!
2026-04-13 09:42:48.487 Error: Enever: Invalid (no) data received (electricity prices, date object not found). Check Token!

I contacted Enever and they told me the token was valid and working.

[gizmocuz]

Probably because you refreshing to much? You can only run 1 instance

I know it is working because:

1. I am using it myself
2. See this topic viewtopic.php?f=6&t=44561

[Havym]

I'm just using the plug-in that is build in Domoticz. No scripts. How could it be possible to use more than 1 instance?
The plugin is turned off right now for over 2 weeks but when I turn it on it reports this massage instantly.

And the funny part is that the plug-in doesn't work anymore from the beginning of April. Until April it worked perfectly and I didn't change anything.

[Henry]

It seems that the url for Enever has changed from https://enever.nl/api to https://enever.nl/apiv3/. I had the same problem and after an update to 2026.1 the plugin was working again. Don't know if this is related to your problem

[Havym]

That could be the problem but since when did they change the api?
Updating to Domoticz 2026.1 requires a new OS on the pi. Updating the pi isn't easy for me.
Is it possible to manually change the build in plugin? Where can I find the file?
Maybe I can try to change the file.

[waltervl]

That is not possible or you need to build domoticz yourself. If updating a Pi is not possible I would not advise to cahnge the C++ code and do a build yourself...
If you do not want to change the RPi then you have the option to use the docker environment: https://wiki.domoticz.com/Docker

[gizmocuz]

You are running an old OS for more then 2 years.
Updating the OS is not difficult if you follow the right guide/instructions.

If you do not have any extra python scripts running, or anything else on the raspberry pi, it is even more simpler:

-> Domoticz -> Settings -> Backup database

Shutdown the raspberry pi.

Now you have two options, keep your existing SD card and use a new 16/32/64gb SD card

Install the latest Raspbian OS on the SD card, enable SSH, make sure it is up 2 date (sudo apt update followed by sudo apt upgrade)
Install Domoticz from the command line, check if it is working by browsing to its webpage
Next goto the domoticz folder and issue
./updatebeta

Browse to Domoticz again->Settings->Restore Database

Done.

---- Upgrading the OS (if above will not work because you have more running)

Code: Select all

sudo su -

Code: Select all

apt-get update
apt-get upgrade
apt-get dist-upgrade
apt full-upgrade

If everything went smoothly, perform database sanity and consistency checks for partially installed, missing and obsolete packages:

Code: Select all

dpkg -C

If no issues are reported, check what packages are held back:

Code: Select all

apt-mark showhold

Packages On Hold will not be upgraded, which may cause inconsistencies after Buster upgrade. Before you move to the next part, it is recommended to fix all issues produced by both above commands. The following command might be of a further assistance:

Code: Select all

dpkg --audit

Update Package Repository to Debian Buster Now, that we have a current system fully upgraded, it is time to re-synchronize the package index files with new Debian Buster sources. This is done by editing /etc/apt/sources.list file to include Debian stretch package repository. First, make a backup the current /etc/apt/sources.list:

Code: Select all

cp /etc/apt/sources.list /etc/apt/sources.list_backup

Assuming you are running bookworm, but you can check this by running cat /etc/os-release

Code: Select all

sed -i 's/bookworm/trixie/g' /etc/apt/sources.list

Once the above /etc/apt/sources.list file edit is completed, use apt-get command to update packages index:

Code: Select all

apt update

Upgrade to Debian Simulation
Before we hit the UPGRADE button, let's use apt command to see a preview of what we are facing. To do this execute apt list --upgradable command in order to get a quick survey of the number of packages to be installed, updated and removed without affecting the system.

Code: Select all

apt list --upgradable

Actual Upgrade
We have come to the most exciting part, which is the actual Stretch upgrade to Debian Buster system. During the upgrade you may be asked:

There are services installed on your system which need to be restarted when certain libraries, such as libpam, libc, and libssl, are upgraded. Since these restarts may cause interruptions of service for the system, you will normally be prompted on each upgrade for the list of services you wish to restart. You can choose this option to avoid being prompted; instead, all necessary restarts will be done for you automatically so you can avoid being asked questions on each library upgrade.
Restart services during package upgrades without asking?
The choice is about whether you wish the system to restart your services automatically during the system upgrade or you wish to do it manually or after the system is fully upgrade to Buster. When ready, execute the bellow commands to commence the Debian Buster upgrade process:

Code: Select all

apt-get upgrade
apt-get dist-upgrade

Modernize Debian Sources
Optional but recommended: Switch to deb822 format for the sources.list. This will write /etc/apt/sources.list.d/debian.sources and /etc/apt/sources.list.d/debian-backports.sources

Code: Select all

sudo apt modernize-sources

At this stage you should have your Stretch Debian Linux system fully upgraded to Debian Buster 10. Follow, this guide to check your current Debian version. Once again check for obsolete packages so there are no surprises down the track:

Code: Select all

aptitude search '~i(!~ODebian)'

[Henry]

That could be the problem but since when did they change the api?
Updating to Domoticz 2026.1 requires a new OS on the pi. Updating the pi isn't easy for me.
Is it possible to manually change the build in plugin? Where can I find the file?
Maybe I can try to change the file.

I guess the old api was terminated somewhere around 1 april, because that's when I don't see any new values in the db.
As stated earlier running Domoticz in a Docker container is a solution, or follow the steps in gizmocuz post

[DzJan]

I run docker stable 2026.1 now for 4 days and this item still does not work. Is it needed to get a new token?

[Henry]

Enever should work with 2026.1 without the need for a new token. Are there any messages in the log about this?

[RonkA]

Try this:

Code: Select all

https://enever.nl/apiv3/stroomprijs_vandaag.php?token=YOURTOKEN&resolution=60

And replace YOURTOKEN with your token...

[WilcoEHV]

Hi, since a couple of weeks I've been watching this thread for news but noting. I have a system of my own running Domoticz 2026.1 and i manage a system at my parents place (also 2026.1). Since may 2nd Enever no longer updates on both systems. When I use the link in the last post i get this

{"status":"true","data":"API token deactivated. Contact us via the contact form","code":"3"}

Both systems run on a up to date Raspberry os on a pi 3b and 5.
Any suggestions?

[Arjan2019]

Are you running both with the same token?
If yes then you have to make a second because if you use the same token on both systems you use more then 250 request which is not allowed.
Or pay for a small subscription.

Check here how many request you have left
https://enever.nl/resterende-aantal-requests/

[WilcoEHV]

They're on different tokens and the number of requests left on both the `accounts' is 240.+.
I've sent them a mail but they are not really responsive.

What happend on both systems late april/ early may is that I've restored the sensors from a backup on a fresh installed Domoticz. Not a qlue if that has got something to do with it.