Here the box sends well the data to Home Assistant then stops all of a sudden:
Here is the app after the reading stopsā¦ the firmware reverted back. The second box did it the next day:
So the issue with the integration is very much related to the firmware accepted by the box.
Iāll share any workaround I could get from Smilics.
Sorry but I cannot replicate the issue.
Iām still on V4.4.124.
Can Iberdrola be pushing that firmware? That does not happen here: https://home.wibeee.com
My Mains and Solar inputs are far apart and Iberdrola only provided one wibeee with 2 clamps, useless. So I bought a second box myself, to find out that one was registered with Iberdrola the other one with Wibeee (smilics) and could not work on the same portal. So Smilics managed to change the āownershipā of the second box to āIberdrolaā then it could be added to their portal, but now I am stuck with the Iberdrola app to manage the firmware upgrade. And this app seems to have a problem, or my setup has.
But Smilics canāt come back to me with an answer, they only told me to switch off 4G on my mobile when running the appā¦
I think one key aspect why I donāt get support from the manufacturer with this issue is that from the Smilics/Iberdrola perspective, it āworksā on their portal with firmware 150. Upgrading the firmware to get stats in Home Assistant instead of their portal is maybe not their priority. I canāt say.
Hi, Congrats for this code. This week the installers of the solar panels (from iberdrola) added this device to my home and now Iām interested in grabbing the data in to HA. I already have some experience using modbus and I wonder if anyone has already tested that way of obtaining data in contrast of using a REST call.
FYI, if you switch on the MODBUS slider, the UI tells you the web server will be disabled and no information will be sent to the server (iberdrola host) at this time, I think if modbus is enabled HA integration should push back to the iberdrola cloud so they donāt notice the difference. Modbus could potentially be a way to overcome the current problems regarding refresh time and unexpected firmware downgrades ā¦
@ihr I agree with everything you say. I never tried it personally because I didnāt think people would want to to give up Wibeee Nest data.
For disclosure, I am working on a version that proxies the upstream calls to Nest and saves them in HA as well. This means that weāll have updates in HA every few seconds and also full Nest access, and more importantly no problems with the REST API.
Iāve most of the code in place and will release a beta some time over the next few weeks.
1 Like
Very interesting thing to come! thanks for sharing 
I got an answer from Smilics that ask me to try to upgrade the firmware through their āproā app not the consumer app. They think it should provide a more stable firmware upgrade process. Iāll try next week.
On a side note, please note that the wibeee boxes delivered by Iberdrola are ātaggedā in their database as only authorised to connect to the Iberdrola flavour of their portal, that is, it is possible that the API these boxes use is not exactly the āNestā version that you are trying to mimic.
I cannot say for sure, but I bought a second box myself in a shop and it was registering to the āwibeee homeā portal but was forbidden on the Iberdrola portal, and vice-versa for the other one. I had the support team of Smilics to retag the second box as if it was delivered by Iberdrola so that both boxes were aggregating their data to the same portal.
And now they guarantee me that upgrading the firmware through their āWibeee businessā app will not untag them from the Iberdrola portal. To be confirmedā¦
In parallel I am switching these boxes for two Shelly EM sensors, hoping to increase the reliability. If I can upgrade the firmware correctly Iāll try to reuse the wibeee for sub-circuit measurement, and maybe Iāll be able to test the modbus option when you share it.
footnote:
I spotted already 4 portals to manage wibeee boxes:
monitorconsumo.iberdrola.es/mirubee_front/ (Iberdrola portal)
home.wibeee.com/mirubee_front/ (Wibeee consumer portal)
nest.wibeee.com/ (Nest portal?)
smilics.com/wibeee/ (a.k.a. "Wibeee business" portal)
The portal incompatibility with my boxes was between the first two URLs, so Iām not sure if the Nest and Business are yet other databases or else?
For those interested, there is a beta version available with Local Push support. When configured correctly, the data recorded in HA will be the same āliveā data that is used in Wibeee Nest (not the energy counters but the gauge data such as Power, etc). Polling still occurs to update the other counters.
Configuration:
-
Enable the Wibeee Nest Proxy in the Integrationās configuration.
-
Go to the Wibeee web UI and in Advanced Options update the Server section as described below
Before: Server URL is
nest-ingest.wibeee.comand Server Port is80
After: Server URL the IP address of your HA instance and Server Port is8600
Click Apply to make Wibeee restart, after which it should start pushing data to the Wibeee integration within HA.
Data received by the Wibeee integration is forwarded to http://nest-ingest.wibeee.com:80. Here it is in action. Wibeee Nest continues to receive the same data so you can use the Nest app if you like.
Limitations:
- Only working with
nest-ingest.wibeee.comas the upstream for the time being (i.e. not working formonitorconsumo.iberdrola.esand others). - Home Assistant port 8600 needs to be accessible by the Wibeee device (previously only Wibeee needed to be accessible by Home Assistant and not the other way around).
Please report any issues in Issues Ā· luuuis/hass_wibeee Ā· GitHub.
Is this server working? Checking it, through a browser, I only get: ā{āErrorā: āNot foundā}ā
The only server/port that works for me is: www.smilics.com / 8080.
Yes, this is a Wibeee/Smilics API, you are not meant to access it directly @Ostracizado. It is where the devices send their data to be displayed in Wibeee Nest. To view the data you should be accessing https://nest.wibeee.com/ after you have registered your meter there.
After a week of testing I am very pleased with the results, Wibeee is keeping up with my Shelly 3EM that uses the built-in integration (IoT class: Local Push).
Here is HA on the left and Wibeee Nest on the right displaying data from the same meter.
I finally did it. Working great, @luuuis!
Still, itās hard to go over mqtt and a esp32 thatās receiving data from the shelly. 
Iām using it for FreeDS, but damnā¦ the transfer data is almost instantaneous.
1 Like
@luuuis, any idea why the value of Active Power, doesnāt show negative values, while it does on Wibeee Nest?
I could do a template to solve it, but stillā¦ just wondering.
Example:
I am just storing the values reported by the meter, it always reports a positive number. Wibeee Nest is probably multiplying by the sign of the power factor as I show in Sensor Examples Ā· luuuis/hass_wibeee Wiki Ā· GitHub.
I think I might do the same within the integration for the next major version so that the template sensor becomes unnecessary.
1 Like
Muchas gracias. Funciona todo perfectamente. Agradecerte enormemente tu trabajo, para ir solucionando los problemas que han ido surgiendo.
Tengo una duda sobre el funcionamiento de active_energy_l1_cost, ya que no me funciona. Estaria muy bien que viniera dando los costes que hemos integrado en Wibeee Nest .
Por ultimo L4 es la suma de L1+L2+L3?.De nuevo gracias por todo
1 Like
I just release a new version with more functions and tools. With the tools added you can emulate WiBeee and cloud side of the App (whatever use of the product).
Needs some improvements, I appreciate comments on that.
As well another tool is a firmware āfinderā and downloader (see firmare on repo).
All itās here: https://github.com/fquinto/pywibeee
Python package:
1 Like
Mil gracias por tu trabajo!
Esta tarde actualicĆ© vĆa HACS e hice como indicas para ponerle al medidor la IP de mi HomeAssistant.
Todo esta funcionando genial!
PD: Lo pongo aquĆ por si alguien lo necesita. Al entrar en la IP del medidor, en el usuario puse āuserā y en el password āuserā y me dejĆ³ entrar.
1 Like
Hi there!
Thanks for the integration!
Iāve two Wibeees those were more or less properly working with HA for a while, but now, it seems that with firmware v4.4.159, the internal web server works for only some minutes in the best of the cases.
I was trying to configure the proxy, but the HA doesnāt shows the values.
In my case, the Wibeee is reporting to http://wattius.mirubee.com. Iāve updated the nest.py file to include it here:
async def get_nest_proxy(
hass: HomeAssistant,
upstream=āhttp://wattius.mirubee.comā,
local_port=8600,
) ā NestProxy:
My questions are:
- Even if the proxy is setup, is it still querying to the local ip/status? or if proxy is setup then it just gathering the data from the push?
- Is it needed anything else to configure to have it working? (I see in the router that there is traffic from Wibeee to the HA but sensors show unavaiable data)
Thanks/Carlos
http://wattius.mirubee.com points to the old Mirubee service. I donāt think it works any more since April 2022. In any case, the integration doesnāt care too much what happens to the data that is sent upstream.
Yes, HA will still access the device API once in a while (according to the polling interval you configure). If the API does not respond then the sensors will be marked unavailable until they finally respond.
The only hard requirement is that /en/status.xml responds when it is used; the proxy configuration is currently only used to get more frequent updates but it does not receive data for all the sensors.
I think this could be improved, please raise an issue in GitHub to continue this discussion.
If /en/status.xml does not respond then the deviceās web UI should not be working either. Is that the case? I would try setting the polling interval to a high number (e.g. 5 minutes). I would also report to Wibeee that the device UI is not responding under this firmware.