@abacao and @DennisHagebrand v3.3.0-beta.0 is now released with support for different Clouds and Local-only mode. You need to enable beta releases in HACS to access this release.
Please test this out using your Cloud service and if possible with the mobile app in parallel. Updates should be instant on all platforms as shown in this older post.
Local Push support must be enabled in the integration’s configuration in HA.
Hi,
Perfect! I will try out as soon possible, do I also need to change the server address in the wibeee config? Will that not “destroy” thje normal functionality of my wibeee? Or is it that we just need to check that box in HA as you wrote in the post?
Yes, you need to configure Server URL in Wibeee. The way it works is that Wibeee sends the push data to HA, the integration updates the sensors and sends the push data to the configured Cloud. If all works well there is no loss in functionality (been using like this with Nest for over 1 year now).
You can check everything is OK by opening the Iberdrola platform side by side with HA and you should see frequent updates happening in both at roughly the same time.
Or you can compare against the values shown in the device’s Web UI, though in my experience that UI is highly unstable.
Alright, I will try that. Now I understand how you are trying to pull this functionality off 
I will try and update you later on.
Hey @luuuis
I am using the beta version.
Do you have any documentation stating what every option do?
I don’t have iberdrola or solarprofit. About the rest, what do you need to be tested?
Settings are in the integration options, version must be v3.3.0-beta.0. 
Just general stability of the Local+Cloud configuration (especially the Cloud part).
In order to support multiple Clouds I have had to start parsing and inspecting every payload before forwarding to Cloud services, which I did not do before (diff).
I found that my Wibeee device will often send invalid JSON and in the integration I try to work around this. It would be good to see if this occurs to others and if the workaround is effective (DEBUG messages “Error parsing JSON…” and “Fixed invalid JSON…”).
Going forward this change should allow me to stop polling completely as long as the device keeps pushing data, which should fix a lot of issues with the integration.
I see the options but as i’m not a user of iberdrola or solarprofit, I cannot help you with that.
Currently, I have setup like this:
Any thing in particular to pay more attention?
The main thing is to check for parity between HA and the (Nest/other) Cloud-based apps. If in Local only mode, do your sensors update with high frequency as you expect?
You can see in my post from Jul 2022 that the HA sensor is updating every few seconds and matching the output in Wibeee Nest.
This is now harder for me to test because since 2022 I moved the L1/L2/L3 clamps to measure specific devices (instead of 3 phase grid power) and the Wibeee does not send push data so often, only every 45 seconds. Does that make sense?
It does. I have setup the local only but with a 25s polling. Are you saying that I can lower it down with confidence to a lower update frequency?
How low?
Heads up: I’m using firmware 4.4.124
No don’t lower it, raise it. 
Local push is initiated by the device, it is totally independent from the polling interval configured in the integration. If local push is set up correctly you should be able to set polling interval to e.g. 1h and still get updates every few seconds.
v3.3 (final) will handle this internally and only poll if the push data is not arriving as expected. Hope that helps.
I have raised it to 360.
I have updates but the updates are not consistent.
They can take 4 seconds or almost 1 minute. Is that normal?
If there is no change (or only a very small change) in the values then the device will not push new data. For example, if you turn on and off a hairdryer every 2 seconds you should expect to have new data being pushed every few seconds. Then after you stop you should expect around 1 update per minute.
All the Cloud services (such as Wibeee Nest) operate solely on this push data, they are never able to poll for new information. So it is sufficient to use the push data.
Hello, I’m having some issues, can somebody help me?
So I have it configured to push the data to the nest cloud, and I have an app that is a clone of Iberdrola’s app (solideo). When I open the app, the data is correct. It shows that I’m consuming for example 300 W. But when I look at the data in HA, it changes every few seconds between 300 and 8.000. What I found is that this 8.000 is roughly the double of my solar panel’s production.
the fact that it’s sending the data to nest, and in the official app it’s displaying only the correct values, makes me think that the problem is this integration. can someone explain me how could I fix this or what can be happening?
Enable debug logging for the integration and then create an issue in GitHub please.
thank you for the quick response. I will do it tomorrow since now it’s night time and the solar panels are not producing anything, so it doesn’t show any of this interferences.
Hello,
I’m having problems with the integration. Sometimes the entities become unavailable and I can solve by restarting the HA.
Anyone having the same problem?
I already changed the polling time from 10 seconds to 30 seconds, but it didn’t work.
I have this in the log:
Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:360
Integration: Sensor (documentation, issues)
First occurred: 10:58:07 (1 occurrences)
Last logged: 10:58:07
Error while setting up wibeee platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 360, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/wibeee/sensor.py", line 228, in async_setup_entry
device = await api.async_fetch_device_info(retries=5)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/wibeee/api.py", line 65, in async_fetch_device_info
device_id = devices['devices']['id']
~~~~~~~^^^^^^^^^^^
KeyError: 'devices'
And this:
Logger: custom_components.wibeee.api
Source: custom_components/wibeee/api.py:111
Integration: wibeee (documentation, issues)
First occurred: 10:58:07 (1 occurrences)
Last logged: 10:58:07
Error getting http://192.168.1.95/services/user/devices.xml after 5 retries: ClientResponseError: 400, message="Expected HTTP/:\n\n b'AT+CIPSENDBUF=4,325'\n ^", url=URL('http://192.168.1.95/services/user/devices.xml')
hi all
question, trying to move the devices into this integration (thanks for the work @luuuis )
I try to install the add-on, it ask me to provide the device IP address… but it fails with “could not read device info”
I put the device to send the data to the HA IP address, and I see it arriving, but the integration can’t be configured, as it is stuck on this “add wibee device” initial page
the devices are 4.4.154, Wibeee BOX S3P
Any ideas?
Thanks!
Thanks for the quick response
the devices are killing the HTTP access, once they connect to the SSID, they remain pingable, but HTTP is not open (maybe it is behavior on this firmware version)
I can only access the web interface if I do full device reset (when they broadcast the wibee_XX ssid, etc)
is there a way to bypass the add device, and manually add the entries?
as it seems they data push is done while they are on this mode (at least, I see traffic to HA IP, port 8060)
or if someone is aware of different firmware to test
Thanks!
You can check here the firmware versions that have been reported to work.