Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keep my enphase in this integration or move to the official one #205

Open
aperezva opened this issue Sep 8, 2024 · 2 comments
Open

Keep my enphase in this integration or move to the official one #205

aperezva opened this issue Sep 8, 2024 · 2 comments

Comments

@aperezva
Copy link

aperezva commented Sep 8, 2024

Hi all,

I have been used this integration more than one year, and as it´s konwn we have a disconnection everyday at 23 PM for one minute. This is s minor affectation, but I see taht this integration has no new version till february.

Is it still alive or do you recomend me to move my enphase to the offcial one?

Thanks

@aperezva aperezva changed the title JKeep my enphase in this integration or go to the official one Keep my enphase in this integration or move to the official one Sep 8, 2024
@catsmanac
Copy link
Collaborator

Hi @aperezva, that question has no simple answer. It depends on what Envoy components you have installed. In the Home assistant community you can find some experiences with moving to the new core version.

As for the 23 PM communication outage, that is an Envoy issue, it will occur/has been reported equally with this integration as with the core integration. I've seen someone that actually build a trigger mechanism to collect data every minute, but skip like 10 minutes right at 23 PM.

Whether this one is still alive or not, I can only share my view on this as I'm not the owner of this repo. I'm still trying to help out on questions and issues, just because @briancmpbll's work helped me out when I got stuck on the token issue with my new Enphase installation. These days I'm mostly contributing to the core version, so no big feature adds here from my side, though small items may happen.

Does that warrant you migrating to core? Only if it doesn't hurt (too much). You'll have to check what features you are using and if they are available in core and if you can migrate (without data loss if that would be an issue). If the 23 PM issue is the only issue, moving to core will probably make no difference.

@aperezva
Copy link
Author

aperezva commented Sep 8, 2024

Thanks

Hola, esa pregunta no tiene una respuesta sencilla. Depende de los componentes de Envoy que tenga instalados. En la comunidad de asistentes para el hogar, puede encontrar algunas experiencias con el cambio a la nueva versión principal.

En cuanto a la interrupción de la comunicación a las 23 p.m., que es un problema de Envoy, ocurrirá/se ha informado tanto con esta integración como con la integración central. He visto a alguien que realmente construye un mecanismo de activación para recopilar datos cada minuto, pero se salta como 10 minutos justo a las 23 p.m.

Ya sea que este todavía esté vivo o no, solo puedo compartir mi opinión sobre esto, ya que no soy el propietario de este repositorio. Todavía estoy tratando de ayudar con preguntas y problemas, solo porque el trabajo me ayudó cuando me quedé atascado en el problema del token con mi nueva instalación de Enphase. En estos días, estoy contribuyendo principalmente a la versión principal, por lo que no se agregan grandes funciones aquí de mi parte, aunque pueden suceder elementos pequeños.

¿Eso justifica que migre al núcleo? Solo si no duele (demasiado). Tendrás que comprobar qué funciones estás utilizando y si están disponibles en el núcleo y si puedes migrar (sin pérdida de datos si eso fuera un problema). Si el problema de las 23 p.m. es el único problema, pasar al núcleo probablemente no hará ninguna diferencia.

Than

Hi @aperezva, that question has no simple answer. It depends on what Envoy components you have installed. In the Home assistant community you can find some experiences with moving to the new core version.

As for the 23 PM communication outage, that is an Envoy issue, it will occur/has been reported equally with this integration as with the core integration. I've seen someone that actually build a trigger mechanism to collect data every minute, but skip like 10 minutes right at 23 PM.

Whether this one is still alive or not, I can only share my view on this as I'm not the owner of this repo. I'm still trying to help out on questions and issues, just because @briancmpbll's work helped me out when I got stuck on the token issue with my new Enphase installation. These days I'm mostly contributing to the core version, so no big feature adds here from my side, though small items may happen.

Does that warrant you migrating to core? Only if it doesn't hurt (too much). You'll have to check what features you are using and if they are available in core and if you can migrate (without data loss if that would be an issue). If the 23 PM issue is the only issue, moving to core will probably make no difference.

Thanks @catsmanac , my questions was only to be on the last version of integration, I don´t want to be outside the standards. I have been testing official integration in another HA installation and it seems everytinh works fine, the most important diferents, it´s taht in the HACS intyegration we can manage time to upgrade the data, in the oiffcial we need to setup an automation to force it.

But, if you are working in the official one and it will have improvements in the future , I will maybe move to it.

Thanks again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants