waltervl wrote: Wednesday 20 December 2023 17:17
What I would do is keep using the General kWh meter and get rid of the P1 meter.
Yup thats what I want to do
waltervl wrote: Wednesday 20 December 2023 17:17
You could already disable the python plugin (not delete!) in menu setup - hardware, so the P1 meter will not be updated anymore in the database.
Yup, Also done in test environment.
waltervl wrote: Wednesday 20 December 2023 17:17
Then recalculate the history P1 values of idx 433 in multimeter_calender and import those in the meter_calender table as history values of the new General Kwh device (idx926). Also check for overlapping dates as you are running them now both.
What do you mean by "recalculate the history of P1? I know "imported" the history by copy from multimeter_calender and paste in meter_calender.
Is this the right way to do? I use SQLite Expert Personal but can't find something like "import".
Since the external Python Plugin is still active on my production envirnment (Rpi3B) I want to migrate to new production environment (Rpi4b 8gb).
Simultanious I want te migrate from external Python Plugin Enphase to Native Enphase hardware.
So there is no "same" data since I can remove/delete data from the Native Enphase then first import from old external Python plugin and the enable the new native Enphase hardware..
waltervl wrote: Wednesday 20 December 2023 17:17
Dont change anything in the devicestatus table. After you have moved the history data from P1 to General kWh delete the python plugin in menu setup - hardware and all releated devices will be removed from the database.
Ok clear on that, I will leave the devicestatus table untouched.
waltervl wrote: Wednesday 20 December 2023 17:17
PS. Does the python plugin not have a General kWh meter already? Because then you could replace the 2 Gneral kWh meters and forget about the P1 meter.
No, the external Python Plugin only has 1 P1 meter.....