Perhaps modify timers from a clean/private browser session as the timer API and related javascripts have been changed. And that could mix up things if you go from old to new Domoticz environment in the same browser session.

That old login method is deprecated.
But still login is possible with user accounts, see: https://wiki.domoticz.com/Security

When you add a new counter device it will probably start with 0. And every 5 minutes it will be overwritten by the 0 value. (You can by the way switch this off in the settings/tab Log History that domoticz only stores a real changed value). And when you load the first value from your counter, say ...

Why is a couple of 0 counter values in the beginning nasty? I never have found this to be a problem. Try it with a counter which stores an actual much higher value as first value. Then it counts a way too high number as first value scrwwing up the graphs and statistics That has nothing to do with ...

If you test timers do you leave a time delta of min 2 minutes? As that is needed for Domoticz to detect and trigger on timers.

The timers are also enabled instead of disabled?

Why is a couple of 0 counter values in the beginning nasty? I never have found this to be a problem.

See also the scripts of user @psubiaco on his website: https://www.creasol.it/en/support/domotics-home-automation-and-diy/entso-e-electricity-prices-for-eu-countries-and-solar-photovoltaic-forecast and on his github: https://github.com/CreasolTech/domoticz_lua_scripts And his EMS project https ...

Check for example this topic: https://forum.domoticz.com/viewtopic.php?t=39709 See as a reference also the energy Dahboard https://wiki.domoticz.com/Energy_dashboard It is not a management system but only a dashboard. For Dutch users there is the Enever integration that loads the future energy ...

You can also use this procedure: 1. Disable your dzvents updating script (easily done in the event system editor) 2. Remove incorrect sensor devices (you can take your time as the update script is disabled) 3. Create new sensor devices. (you can take your time as the update script is disabled) 4 ...

Works for me with your settings. Only sometimes the value is not 1 digit but a lot more.

As the OpenZwave project has stopped a long time ago the Domoticz project is promoting to use Zwave-JS-UI.

See wiki https://wiki.domoticz.com/Zwave-JS-UI

This wil probably not help you when compiling the current OpenZwave part in Domoticz.

Then you should try to update to latest beta of Domoticz as some MQTT AD improvements are implemented there.

Check for example this topic viewtopic.php?t=3673

Or this plugin https://github.com/jgaalen/domoticz-apc-ups-plugin

You probably also have to update the Meter_Calendar table too.
But yes, fixing these counter values in the database manually is a PITA. I stay away from it if I can.
Better delete the incorrect high value the next day from the month graph by shift - click on it.

What is the -l curl option? You use in your script: domoticz.openURL({ url = baseurl .. stationid, method = 'GET', callback = 'JubileeLevel', }) Perhaps you need different OpenUrl options similar as the -l? What if you remove the GET method?

What if you go into the docker container of Domoticz and do the curl command? Do you get 200 or 403 status?

If you have 3 phase grid connection you can have for example usage from grid on phase 1 and return on phase 2 or 3. It depends on the connection of your solar production and usage devices per phase. Your P1 viruell meter shows "182 Watt, -968 Watt" meaning that in total there is on some phases in ...

because this should be changed into into something like

-918+182=-736