j’ai un souci avec mon ECU_R.
Depuis un moment, je perds tous les jours la communication avec l’ECU-R.
Je suis obligé de rafraichir l’intégration, qui elle me demande de redémarrer HA.
Ce que je fais et cela fonctionne de nouveau.
J’ai donc regardé la documentation pour avoir de l’aide et là je tombe sur :
Bon je me dis que je dois y passer et changer d’intégration, si cela peut corriger ce problème, tant mieux…
Ma question est : Si je suis la procédure de migration ici, est-ce que je vais conserver mes historiques de production ?
Par contre, la version est juste une invitation à aller sur l’autre intégration.
On aura pas le choix de changer si on souhaite continuer de recevoir des majs et bénéficier du support du développeur.
Go to [Settings] > [Devices & Services]. In the default integration tab you will find the « APSystems PV solar ECU » integration. Select the integration and choose the overflow menu. Delete the integration. You are prompted to restart Home Assistant, do so but note that this will not remove the integration files from the custom_components folder, you will have to go to HACS in order to remove the files entirely.
Removing the old « APSystems PV solar ECU » integration files from Home Assistant
Go to [HACS] and under « Downloaded » you will find the « APSystems ECU-R » integration with on the right the overflow menu. From that menu select [X Remove]. When prompted again select [REMOVE]. The integration files are now permanently removed.
Installing the « APsystems ECU Reader » integration
The installation of custom integrations is done in three steps (assuming HACS is already installed):
Downloading the custom integration
Navigate to HACS and choose the overflow menu in the top right corner of the Home Assistant Community Store.
Choose Custom repositories and paste the url: GitHub - HAEdwin/homeassistant-apsystems_ecu_reader: A Home Assistant custom integration for local querying APsystems ECU's. in the Repository field.
Choose Type > Integration and select the [Add]-button. From this point it might allready have been added to the personal store repository. If not, wait for it to appear then close the Custom repositories dialog window.
In HACS search for APsystems and the APsystems ECU Reader will be listed in de Available for download section.
From the overflow menu on the right select [Download] and automatically the latest version will be listed for download so choose [Download].
HA Settings will now show the repair action that a Restart is required, submit the action and HA will restart.
After HA’s restart the downloaded custom integration will be detected by HA. The integration will need to be configured in order to fully integrate it in HA and make it work.
Integrating the custom integration into Home Assistant
Navigate to [Settings] > [Devices & services] and choose the button [+ ADD INTEGRATION] in the lower right corner.
In « Search for a brand name », choose APsystems and the APsystems ECU Reader will be listed.
Select it and the Configuration dialog will show, enter IP-Address of the ECU, rest of the defaults are fine so choose [SUBMIT].
APsystems ECU Configuration
ECU-IP address: The address you have assigned to the ECU must be entered here
ECU query interval in seconds: I strongly recommend keeping this value set to 300 since data in the ECU is only refreshed every 5 minutes.
Retries when ECU fails to respond: The integration tries to open the connection to the ECU for this number of times. If that fails it a +1 for the cache counter.
Cache count before auto ECU reboot (ECU-R-Pro & ECU-C models): The integration will reboot the ECU and sets the Using Cache Counter to zero. If you own a ECU-R (2160xxxxx) or ECU-B a reboot will not take place, the ECU firmware does not provide this option on these models. Instead you can use an automation where you use the UCC sensor to trigger a smartplug to turn Off and On again after a 10 seconds wait. When you use a smartplug to reboot the ECU, you should set the UCC value higher than the value you would like to reboot the ECU at. The UCC will increase until the set value.
Update graphs when inverters are offline: You can turn this on or off. In the On state most entities will be set to zero when the inverters are offline. The temperature and zigbee sensors will never be plotted when the inverters are offline.
SSID and Password (ECU-R-Pro & ECU-C models): Using these fields will force the ECU to reboot when submitted. It’s a workaround for the missing command to enable a forced reboot by the integration. The fields are not used to authenticate so can be randomly filled.
j’ai ensuite renommé les 3 sensors avec les anciens noms pour être sur d’avoir le lien avec les anciens datas (je ne suis pas sur si cela change quelque chose)
