New integration: Energy monitoring device Circutor Wibeee

luuuis · November 24, 2021, 7:33pm

Just follow the installation instructions. You will need to remove other versions such as abacao because they share the same integration id.

Abruzzi04 · November 28, 2021, 9:11pm

Good afternoon. I’ve had this integration for almost a year, and I’ve had the same problem since forever.
The integration works fine and I’ve already made several changes.
The problem is that sometimes when I restart Home Assistant, the integration doesn’t start. it never fails to work well, taking off a few times when I restart, and then it doesn’t work again. I have to restart several times (2/3 times), until the integration entities started to work.
Someone with the same problem?

luuuis · December 3, 2021, 11:28am

This happens when the Wibeee device takes too long to respond or returns a bad XML.

Are you using the original @juanjoSanz integration or my fork? On my fork I have implemented retries so this is now very unlikely. I can’t remember the last time it happened.

rossiluis22 · December 3, 2021, 12:27pm

Hi!!, have any of you tried to managed and add this entity: sensor.wibeee_phase4_active_energy, to the utility meter, in order to get the total amount, by adding just the difference between last time and current measure, I think it would be more precise

Abruzzi04 · December 7, 2021, 3:22am

I’m using this integration: GitHub - abacao/hass_wibeee: Home Assistant Component: Mirubee or Wibeee

Ostracizado · December 7, 2021, 9:19am

You should read what has been said above.
Delete abacao’s integration in HACS, restart, and follow the steps in: GitHub - luuuis/hass_wibeee: Home Assistant: Wibeee (and Mirubee) energy monitor custom component

luuuis · December 7, 2021, 9:45am

Yes, check this post for instructions.

cassisn · December 14, 2021, 1:56pm

I already installed the beta version. I don’t understand how I configure the two wibeee meters, it’s in configuration.yaml. If yes how do I put it?

luuuis · December 14, 2021, 2:04pm

Just repeat the same configuration that your already have and edit the host to contain the other IP address.

cassisn · December 14, 2021, 2:18pm

sensor:
  - platform: wibeee_cons
    host: 192.168.xxx.xxx
  - platform: wibeee_sol
    host: 192.168.xxx.yyy

is working like that. I have two folders with their names wibeee_cons e wibeee_sol.
What do I change with your integration?

abacao · December 14, 2021, 10:48pm

hi luuuis

Can you please add to your repo the hardware and firmware you are currently using?
ex: one phase | fw: 4.4.124

luuuis · December 15, 2021, 12:57pm

Yes, I see that you have renamed the integrations so as to creating two platforms with different names and each one is handling one Wibeee.

With version 3.0 you will be able to manage multiple devices using a single integration so your configuration will look like this in the end.

sensor:
  - platform: wibeee # cons
    host: 192.168.xxx.xxx
  - platform: wibeee # sol
    host: 192.168.xxx.yyy

How I recommend that you make the change:

Install the component, preferrably by following the Installation with HACS instructions. You will need “Show Beta” option enabled in HACS to be able to install v3.0.0-beta.2.
Reboot, then add the above configuration. Perhaps use the scan_interval to only update the new sensors once a minute. This is to keep the from overloading the devices since you now have two integrations fetching data from each Wibeee.
```
sensor:
- platform: wibeee # cons
  host: 192.168.xxx.xxx
  scan_interval: 45
- platform: wibeee # sol
  host: 192.168.xxx.yyy
  scan_interval: 45
```
Make the necessary changes to HA. The sensor names are changed so you will need to update automations and so forth. You can rename the sensors after they’ve been created.
Once you’re happy with the new sensors. You can disable the wibeee_cons and wibeee_sol platforms and remove the scan_interval configuration. Now you will have the configuration as shown in the first code snippet in my post.

luuuis · December 15, 2021, 1:11pm

@abacao I added Device Compatibility · luuuis/hass_wibeee Wiki · GitHub to keep the known compatible devices.

Why do you ask? Do you have any compatible/incompatible devices to report?

abacao · December 15, 2021, 1:32pm

Not on my end but I know that there are several different firmware versions around and firmware version may be a hint about current or future issues.

I have a “incoming update” to do on my “one phase”. It would be great to know when people have any issues, asking and gathering FW information to discard firmware issues.

Currently on my one phase | fw: 4.4.124 I have some warnings:

1043 times

Logger: custom_components.wibeee.sensor
Source: custom_components/wibeee/sensor.py:197
Integration: wibeee (documentation, issues)
First occurred: December 10, 2021, 22:09:06 (1403 occurrences)
Last logged: 13:27:00

    Error getting http://<wibeee_ip>:80/en/status.xml, will retry. ExpatError: not well-formed (invalid token): line 92, column 1
    Error getting http://<wibeee_ip>:80/en/status.xml, will retry. ExpatError: no element found: line 120, column 0
    Error getting http://<wibeee_ip>:80/en/status.xml, will retry. ExpatError: mismatched tag: line 72, column 25
    Error getting http://<wibeee_ip>:80/en/status.xml, will retry. ExpatError: mismatched tag: line 48, column 31
    Error getting http://<wibeee_ip>:80/en/status.xml, will retry. ExpatError: no element found: line 72, column 23

Traceback (most recent call last):
  File "/config/custom_components/wibeee/sensor.py", line 197, in fetch_with_retries
    dict_data = xmltodict.parse(xml_data)
  File "/usr/local/lib/python3.9/site-packages/xmltodict.py", line 327, in parse
    parser.Parse(xml_input, True)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 92, column 1

46 times



Logger: custom_components.wibeee.sensor
Source: custom_components/wibeee/sensor.py:185
Integration: wibeee (documentation, issues)
First occurred: December 11, 2021, 01:37:47 (46 occurrences)
Last logged: 09:31:49
Error getting http://<wibeee_ip>:80/en/status.xml, will retry. ServerDisconnectedError: Server disconnected

Traceback (most recent call last):
  File "/config/custom_components/wibeee/sensor.py", line 185, in fetch_with_retries
    resp = await self.session.get(self.url_api, timeout=self.timeout.total_seconds())
  File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 544, in _request
    await resp.start(conn)
  File "/usr/local/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 890, in start
    message, payload = await self._protocol.read()  # type: ignore
  File "/usr/local/lib/python3.9/site-packages/aiohttp/streams.py", line 604, in read
    await self._waiter
aiohttp.client_exceptions.ServerDisconnectedError: Server disconnected

code:

sensor:
  - platform: wibeee
    host: <wibeee_ip>
    scan_interval: 20

I’m already at 20s interval to try not to stress the device.

cassisn · December 15, 2021, 1:35pm

Thank you very much for the detail in the reply.
Entities with “_2” refer to the second integration? In my case IP 192.168.xxx.yyy. Whenever you reboot HA it will always have this order. If I remember, I chose to rename the wibeee integration (one for each meter), because when I rebooted, sometimes the entities were swapped.

cassisn · December 15, 2021, 1:42pm

Similics will profoundly update the Wibeee platform, they will merge Home with Business and this will affect IP access to the meters. I questioned Similics and they advised me not to upgrade yet. Are you aware of this situation? Will it affect integration?

luuuis · December 15, 2021, 1:44pm

This is getting very specific to your situation, please create a discussion in https://github.com/luuuis/hass_wibeee/discussions so everyone else doesn’t have to follow along.

luuuis · December 15, 2021, 1:49pm

Please edit the Wiki and add your device and firmware @abacao. Is it Wibeee BOX or the other one?

Regarding the Error getting http://<wibeee_ip>:80/en/status.xml, will retry messages, these are at WARN level and can be ignored. If there is a terminal error (still failing after retries) then the same message is logged again at ERROR—only at this point is the integration affected. The reason for this behaviour is that the remote API is known to be unreliable.

cassisn · December 15, 2021, 1:51pm

I understand the situation, however I don’t think it’s specific to my situation. I believe that those who have two meters, one to measure solar production and the other consumption. I think that this beta version that you created, I thank you, will be precisely thinking about the situation of those who have two meters. I think it is necessary to ensure that the integration assigns the correct entities. And that didn’t happen when I started using this integration.

luuuis · December 15, 2021, 1:57pm

@cassisn as I responded above in New integration: Energy monitoring device Circutor Wibeee - #199 by luuuis the change on their Cloud platform alone will not change anything in how this integration uses the device’s API. Cloud APIs will change but this integration works using “Local Polling”.

I see in this Smilics Confluence page that there has been some discussion on the APIs and from how I understand their replies there is no change to these device APIs.

Joan Villalta from Smilics says:

Actualmente es posible acceder a la página interna de configuración a través de la IP del dispositivo.

As long as the device page remains available the device APIs will remain in some form or another.