You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not very confortable with HA so excuse me if this request is not relevant here.
As the title says, my ECU was replaced because not connecting anymore to network (either RJ45 or wifi).
I updated the configuration in HA APSystem integration so good so far. Now the problem is I get duplicated entities, like sensor.ecu_current_power and ensor.ecu_current_power2.
Is there a way to transfer the data from the first entity to the new one so we still have the production history in the new one and therefore in the charts?
Thank you for reading !
Kind regards
The text was updated successfully, but these errors were encountered:
foxtom22
changed the title
ECU-R replaced, transfer to new entuty/sensor
ECU-R replaced, transfer to new entity/sensor
Aug 30, 2024
foxtom22
changed the title
ECU-R replaced, transfer to new entity/sensor
ECU-R replaced, transfer previous data to new entity/sensor
Aug 30, 2024
Values of the new ECU should get updated in the new entities. Have you allready removed the old ECU? Settings > Integrations > "APSystems PV Solar ECU integration" > Devices > Select old ECU > then the three dots on top of eachother > Delete
This should also remove the associated entities.
Hi,
Thank you for this add-on, very useful.
I am not very confortable with HA so excuse me if this request is not relevant here.
As the title says, my ECU was replaced because not connecting anymore to network (either RJ45 or wifi).
I updated the configuration in HA APSystem integration so good so far. Now the problem is I get duplicated entities, like sensor.ecu_current_power and ensor.ecu_current_power2.
Is there a way to transfer the data from the first entity to the new one so we still have the production history in the new one and therefore in the charts?
Thank you for reading !
Kind regards
The text was updated successfully, but these errors were encountered: