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

Añadir opción para seleccionar la fase del Envoy a monitorizar #91

Open
jmatiasGH opened this issue May 31, 2023 · 2 comments
Open

Añadir opción para seleccionar la fase del Envoy a monitorizar #91

jmatiasGH opened this issue May 31, 2023 · 2 comments

Comments

@jmatiasGH
Copy link

Actualmente realizamos la adquisición de datos mediante la lectura de un stream del monitor ENPHASE ENVOY
http://ipdelenvoy/stream/meter
Toca salir un Stream que da datos cada segundo. Si se analiza lo que sale se puede observar que hay tres fases. Por defecto, trabaja con la ph-A. La idea sería poder seleccionar la fase a monitorizar (ph-a - "FASE A", ph-b - "FASE B" o ph-c - "FASE C") en la configuración. Esto permitiría funcionar para quién tenga que monitorizar otra fase diferente a la A, e incluso, poder poner un FREEDS individual para cada fase para personas con instalaciones trifásicas.
Adicionalmente, un usuario con trifásica, comentó que le sería de interés que hubiera una cuarta opción (tipo "FASE MIX") que fuese la suma de las 3 fases, es decir la media de voltaje, la suma de intensidad, la suma de consumo, porque al final a este usuario se ve que la compensación se la contabilizan así y no por una fase individual. Dejo una muestra de 3 segundos donde se observan valores para las 3 fases, las fases B y C con valores 0 pero que en otras instalaciones se pueden tener otra configuración.

data: {"production":{"ph-a":{"p":-2.199,"q":130.71,"s":137.243,"v":232.698,"i":0.59,"pf":0.0,"f":50.0},"ph-b":{"p":0.0,"q":0.0,"s":0.0,"v":0.0,"i":0.0,"pf":0.0,"f":0.0},"ph-c":{"p":0.0,"q":0.0,"s":0.0,"v":0.0,"i":0.0,"pf":0.0,"f":0.0}},"net-consumption":{"ph-a":{"p":262.63,"q":-225.749,"s":359.985,"v":232.853,"i":1.545,"pf":0.71,"f":50.0},"ph-b":{"p":0.0,"q":0.0,"s":0.0,"v":0.0,"i":0.0,"pf":0.0,"f":0.0},"ph-c":{"p":0.0,"q":0.0,"s":0.0,"v":0.0,"i":0.0,"pf":0.0,"f":0.0}},"total-consumption":{"ph-a":{"p":260.431,"q":-356.459,"s":496.965,"v":232.776,"i":2.135,"pf":0.52,"f":50.0},"ph-b":{"p":0.0,"q":0.0,"s":0.0,"v":0.0,"i":0.0,"pf":0.0,"f":0.0},"ph-c":{"p":0.0,"q":0.0,"s":0.0,"v":0.0,"i":0.0,"pf":0.0,"f":0.0}}}

@pablozg
Copy link
Owner

pablozg commented May 31, 2023

Hola, contacta conmigo por el grupo de telegram.

@helderfmf
Copy link

Just a heads-up, enphase are updating firmwares of theirs envoy. Mine was FW 5 and got the stream option, then it was updated to FW 7 and that option is no longer available. I was using an addon for Home assistant to stream that JSON to MQTT and FREEDS, here vk2him/Enphase-Envoy-mqtt-json#5
Just made some changes and now is working again via the addon.
Don't know if it is possible for FREEDS to work with the new firmware, it now uses a token and not a password, it's a rest API, so it needs to be pulled, and it only responds in HTTPS.
The token part is easy as it is valid for 1 year, the HTTPS don't know if it is that easy, because you have to ignore the certificate.

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

3 participants