Hi. I also have the same problem the solar production on system… if the production it’s superior than consumption it should appears a negative value not positive. As i can see it’s possible to use the power factor because it appears also negative.
1 Like
Hi, you could use phase4 values. In my case if phase4_active_power is greater than phase1_active_power then phase1_active_power should be negative. I’ve created a sensor
iberdrola_active_power:
friendly_name: Potencia iberdrola
unit_of_measurement: 'W'
value_template: >-
{% if states('sensor.wibeee_phase1_active_power')|float < states('sensor.wibeee_phase4_active_power')|float and states('sensor.wibeee_phase2_active_power')|float > states('sensor.wibeee_phase1_active_power')|float %}
{{ states('sensor.wibeee_phase1_active_power')|int * -1 }}
{% else %}
{{ states('sensor.wibeee_phase1_active_power')|int }}
{% endif %}
Tras pegarme mucho con el sensor wibee/ mirubee decidí investigar y desde hace bastante tiempo Home Assistant trabaja con los servicios rest, tanto json como xml.
Así que decidí extraer los datos de esta manera.
Recordar poner en json_attributes los parámetros que queramos medir
- platform: rest
name: wibeee
resource: http://ip_del_medidor/en/status.xml
json_attributes_path: "$.response"
scan_interval: 2
value_template: 'OK'
json_attributes:
- "fase1_vrms"
- "fase1_p_activa"
- "fase1_irms"
- "fase2_p_activa"
- "fase2_irms"
- "fase3_p_activa"
- "fase3_irms"
##### FASE 1 WIBEEE #########
- platform: template
sensors:
consumo_fase1:
friendly_name: "ConsumoFase1"
unit_of_measurement: 'W'
value_template: "{{ state_attr('sensor.wibeee', 'fase1_p_activa') }}"
- platform: template
sensors:
voltaje_fase1:
friendly_name: "VoltajeFase1"
unit_of_measurement: 'V'
value_template: "{{ state_attr('sensor.wibeee', 'fase1_vrms') }}"
- platform: template
sensors:
amperios_fase1:
friendly_name: "AmperiosFase1"
unit_of_measurement: 'A'
value_template: "{{ state_attr('sensor.wibeee', 'fase1_irms') }}"
##### FASE 2 WIBEEE #########
- platform: template
sensors:
consumo_fase2:
friendly_name: "ConsumoFase2"
unit_of_measurement: 'W'
value_template: "{{ state_attr('sensor.wibeee', 'fase2_p_activa') }}"
- platform: template
sensors:
amperios_fase2:
friendly_name: "AmperiosFase2"
unit_of_measurement: 'A'
value_template: "{{ state_attr('sensor.wibeee', 'fase2_irms') }}"
##### FASE 3 WIBEEE #########
- platform: template
sensors:
consumo_fase3:
friendly_name: "ConsumoFase3"
unit_of_measurement: 'W'
value_template: "{{ state_attr('sensor.wibeee', 'fase3_p_activa') }}"
- platform: template
sensors:
amperios_fase3:
friendly_name: "AmperiosFase3"
unit_of_measurement: 'A'
value_template: "{{ state_attr('sensor.wibeee', 'fase3_irms') }}"
1 Like
Hola Viole,
yo también he decidido usar la plataforma rest para acceder a los datos.
Una duda, cómo estás gestionando los errores en la consulta? es decir, frecuentemente recibo None en el estado del sensor, a partir de ahí arrastro el error en sensores templates que calculo sobre estos datos.
saludos,
No me funciona esta configuración. ¿ Qué estoy haciendo mal ?. Si accedo a la dirección http://192.168.1.23/en/status.xml veo todos los valores del medidor.
Con esta configuración únicamente encuentro un sensor.wibeee con estado " OK ".
- platform: rest
name: wibeee
resource: http://192.168.1.23/en/status.xml
json_attributes_path: “$.response”
scan_interval: 10
value_template: ‘OK’
json_attributes:- “fase1_vrms”
- “fase1_p_activa”
- “fase1_irms”
- “fase2_p_activa”
- “fase2_irms”
- “fase3_p_activa”
- “fase3_irms”
…
Buenas, no se si has seguido el hilo, pero tengo previsto realizar la integración en HA cuando me sea posible de mi librería. Así quedará todo integrado y de manera fácil para todos.
Si alguien quiere avanzar es bienvenido. La librería: https://github.com/fquinto/pywibeee
ENGLISH:
Hi, I don’t know if you have followed the thread, but I plan to do the integration in HA when possible from my library. So everything will be integrated and easy for everyone.
If anyone wants to advance, they are welcome. The library: https://github.com/fquinto/pywibeee
Hola Javier, pues no sabría decirte, yo no estoy obteniendo errores.
Lo siento.
Hola, genial son buenas noticias que tengamos alternativas. Muchas gracias por tu esfuerzo.
Un saludo
Hola, efectivamente con esa integración, solo se recibe el OK, si te vas a Herramientas de desarrolladores -> estados y buscas wibeee, veras que los datos salen en los atributos, por eso con cada uno de los atributos creo un template que es que muestro en Home Assistant.
Espero haberte ayudado, un saludo.
Hola:
En mi caso cuando la phase2_active-power(solar) es mayor que la phase4_active_power(genral), entonces el valor de phase1_power_activa tendra que ser negativo. De esta manera me funciona ok. Creo recordar que para los modelos de BOX mono la entrada de las placas esta en la phase2 y para el modelo de BOX trio la entrada de las placas esta en la phase4.
Dejo un ejemplo de como lo he podido solucionar.
- platform: template
sensors:
iberdrola_active_power:
friendly_name: Potencia Casa
unit_of_measurement: ‘W’
value_template: >-
{% if states(‘sensor.wibeee_phase2_active_power’)|float > states(‘sensor.wibeee_phase4_active_power’)|float %}
{{ states(‘sensor.wibeee_phase1_active_power’)|float * -1 }}
{% else %}
{{ states(‘sensor.wibeee_phase1_active_power’)|float }}
{% endif %}
Hi again. The problem it’s that i have a Wibeee box only to solar and another ti mesure only the consumption… How can i get both?
In case some are, or will be, having problems with the integration, check if you can truly access the data at: http://“wibeee-ip”/en/status.xml
Just noticed my sensors kept giving “unknown” as a state. Then I tried to access the .xml and couldn’t connected, even though I was using the wibeee static ip and was on the same subnet.
I did some resets and always the same problem kept popping up; so after that weird struggle I simply decided to put aside the official app “Wibeee Home”, and did the configuration of the device itself, after another reset, and connecting to “Wibee_xxxxx” WiFi, and after that using the ip: 192.168.1.150.
User: user
Pass: user
When it connected with my network it was working as it should. The same with the integration.
Edit:
I’ll be damned… Thought it was a problem with the router. But, I just received an email from Wibeee Support:
“Con la nueva versión de firmware, el acceso a la página interna del dispositivo una vez configurado ha quedado restringido. Si deseas realizar exportación de datos te recomiendo que valores nuestros servicios de API y MODBUS. Te adjunto algunos manuales e información acerca de ellos.”
“With the new firmware version, access to the internal page of the device once configured has been restricted. If you want to export data, I recommend that you use our API and MODBUS services. I enclose some manuals and information about them.”
Hi! Can you provide the version that you are using? Are you upgrade the firmware?
Are you testing using the lib New integration: Energy monitoring device Circutor Wibeee ? Thanks!
Hey, fquinto.
It’s the fw: 4.4.150; out of the box.
I haven’t tried. Didn’t seem much use because every time I tried to reach the host-ip I only received: “ERR_CONNECTION_TIMED_OUT”.
There’s just that limited space of time - something like 1-3 min - after the configuration, when HA is able to receive the data and I’m still able to access the host / or before I restart HA.
I find the URL of the firmware: https://app.mirubee.com/api/fw/wbb/FOTAFile_V4.4.150_WBB.bin
with MD5sum a5d4e5a4a242a3f033288098eea78a61
Maybe you (or another) can investigate this new version.
Or maybe you can do and downgrade…
Yeah, it would be great to do a downgrade; but I have no idea how to go around it.
Anyway, just to be sure, I checked your pywibeee:
Unfortunately, and as expected: “Connection refused”.
Maybe you need to create a host in your local network, with for example Nginx called mirubee.com and local DNS pointing there, and build local mirubee website and stablish there a lower version.
Something similar to this idea: https://obrienlabs.net/redirecting-weather-station-data-from-observerip/
Exits another versions:
064051bbcac01fb0928258cf52494fb1 FOTAFile_V3.4.584_WBB.bin
57d8c4a3c77e510fe0ae6ff44cdb7afc FOTAFile_V3.4.614_WBB.bin
35d3552df1ad540a92dd7437905caf75 FOTAFile_V4.4.124_WBB.bin
280499581dbd263f0de2761edef30be6 FOTAFile_V4.4.134_WBB.bin
b79052b74b5a846e4fd819ead9b39657 FOTAFile_V4.4.135_WBB.bin
a5d4e5a4a242a3f033288098eea78a61 FOTAFile_V4.4.150_WBB.bin
Sorry I don’t check anything. And thanks for testing the lib.
@abacao boas… segui o vídeo do Roberto e está tudo a trabalhar na perfeição. O único problema é os error e os warning que estou a receber nos logs. Não existe maneira de os diminuir ou eliminar?
Obrigado e bom trabalho 
Como posso apagar as entidades que não uso?
