Sure, but I don’t have enough info to help with this because you haven’t provided it yet. I have no idea what _2 entities are at this point.
If you can help me to guide you through troubleshooting then I’m sure we can arrive at a solution, which could be more documentation, a change in the component, or something in your configs. Then we can post here the outcome, which is what 99% of people here will care about. 
Don’t forget to “secure” the IP in your local LAN using MAC Address.
I transcribe the last email I received from Smilics support:
El acceso IP no varía, però el acceso API todavía no està listo en NEST. Esperamos tenerlo listo a finales de enero 2022. Por tanto mi recomendación es que sigas empleando Home/Business y NO te descargues las nuevas apps (ellas son las que realmente te harán la migración). Pongo en copia a [email protected] para que anote tu caso.
Seguimos en contacto.
Joan.-
Yes, both meters are configured with fixed IP.
Hello, good people of this thread! To go with the new year I’ve released a new version of the integration with a couple of goodies. Take a look and if there’s anything that interests you do take the new version for a spin (upgrade through HACS) and let me know how you go.
Check the Installation instructions in the README. Many thanks to @cassisn for their help testing the beta versions on multiple devices.
Adds multiple device support. All entities now have a
unique_id, which allows them to be customised and renamed in Home Assistant.Configuration is now through Home Assistant Integrations screens.
Adds multiple device support. All entities now have a unique_id, which allows them to be customised and renamed in Home Assistant.
BREAKING CHANGESunique_id on entities, which causes HA to create new entities.Any luck updating the new firmware, and using the Nest Wibeee App?
Keep getting error while trying to update the firmware and having to reset the device…
I put here the answer I got from Smilics (Wibeee) support regarding the new Nest platform. In Spanish so there are no translation problems. If it were possible for luuis to comment and say if it is possible for the integration to continue to work, which in my case as it is with two meters works five stars.
Buenos días Carlos,
El equipo envía los datos sea cual sea su firmware. La API es a nivel de software de plataforma. Con la nueva plataforma Wibeee Nest como le indico, no estará disponible. Con la API era posible acceder a los datos de nuestro servidor sin pasar por la web o APP, pero en éstos momentos no disponemos de API para la plataforma Nest.
No es posible hacer un downgrade de firmware.
As far as I know, this integration doesn’t interact with the API, what this integration does is parse the xml file and read required values in local, so as long as we can have access to “http://YOUR-WIBEEE-IP/en/status.xml” the integration should work
Mine is working fine the software version is: V3.4.634 maybe you should check that you device is pointing to their new nest servers. As you ca see in my device
As I understand it is already on the NEST platform, it has the latest firmware version of the meters and the Wibeee integration for Home Assitant continues to work correctly. confirm? What integration do you use? Luuis’s?
Hi @rossiluis22 ,
Did you perform the migration yourself by changing the server URL and port locally and then connect the device to Wibee Nest with a new user or Wibeee took care of the migration?
I am wondering if I can change it myself or I if I could face any future problems.
Thanks for your comments.
Was made automatically by the new wibeee nest app, I just placed my phone in the same wireless network as my wibeee and opened the app. and after a few minutes it was updated and working, the Nest app and the home assistant integration
I think there is some confusion in the conversation between yourself and Wibeee. It is clear to me that you are asking about the device /en/status.xml (which is not an official API) and Wibeee support is replying about the Wibeee Home/Business API and they say it does not exist on the Wibeee Nest platform. But that’s ok because we don’t rely on any Cloud API for Home Assistant integration.
Probably the people answering your question do not even think of /en/status.xml because they don’t consider it an API.
From the screenshot posted by @rossiluis22 it is clear to me that the firmware is unchanged and the Wibeee device page (the one that uses /en/status.xml) is unchanged. The device has simply been configured to send the information to a different server, therefore the integration will continue to work as before.
Do you mind adding your device to Device Compatibility · luuuis/hass_wibeee Wiki · GitHub? That will help others understand what device/firmware versions work.
Which version of this integration are you using?
Hi,
Tested the integration today and got it up running in a second. After a restart off Home Assistant the integration didn’t work anymore and now I can’t even log into to webUI of the Wibeee, I can still ping th device but no more, have also tried pywibeee without any luck. Someone that has had the same problem?
Think i have (cant remember, and cant see anymore) fw 4.4.150.
Done! 
.
The Integration version i’m using is v3.1.1
The devices are very buggy when it comes to the device /en/status.xml usage. This integration relies heavily on calling that repeatedly.
When it gets to this sometimes a power cycle of the Wibeee device is required. Before doing so you may want to increase the polling interval in the integration’s configuration, something like 30 seconds should be fine. I am running 15 seconds and it is stable but there are different generations of devices and different firmwares can be a factor.
Yes, I’m done with the migration, and it’s working perfectly. Nest just changed the path to the server, my meters keep telling me that the FW is out of date. I am not able to update. I don’t care about it, it’s perfect. I have Access to NEST and the integration is working. In fact there is no API, it’s the XML access I should have said. I thought it was an API. Thanks for your integration.
Buenas. LLevo un tiempo loco y ya no se que hacer.
Tengo un medidor monofasico con la version 4.4.159.
He seguido todos los pasos y ya no se que hacer.
en la direccion http://192.168.1.xxx/en/status.xml NO HACE NADA
Pongo dicha IP en la integración y no hay manera.
Lo ultimo que intentaba era lo de la aplicacion Wibeee Nest pero no la encuentro por el google play.
Me funcion perfecto las app de Wibee home y Wibee business
Hi there I had the Wibeee integration working for only a few hours and fail persistently with firmware 4.4.150 and I read that there was a possible issue between this firmware and Home Assistant.
I have 2 boxes, one delivered by Iberdrola one bought myself as “wibeee” and added (with pain) to the Ibredrola portal. Both were delivered with fw 4.4.150.
I managed to find the mobile app from Iberdrola that allows to upgrade the fw only on the Spanish appstore, and it failed again and again to upgrade to 4.4.159. Nevertheless, after many attempts, the wibeee own web interface manages to accept the new firmware and shows 4.4.159, and then miraculously, the box works very smoothly with Home Assistant and the Wibeee integration (I used 90sec refresh interval).
However, after 1-2 days of good work, the box “self reverts” to fw 4.4.150 without reboot, disconnect or anything else. And there is no more comms with Home Assistant whatsoever.
So I can clearly confirm a big issue with firmware 4.4.150 and the Wibeee integration (all on the fault of the firmware). I asked for support to Smilics and they fail to answer properly so far, just give me “tips” on how to flash a firmware correctly… but no investigation why a firmware would be downgraded by itself after a while.
Here is the moment where I managed to upgrade the firmware after rebooting the boxes and immediately apply the upgrade:
