New integration: Energy monitoring device Circutor Wibeee

Thank you very much Juan Sanz, I can confirm that the mirubee moti-1 monophasic version works perfectly with Oscar’s modification. You can make very interesting automations thanks to your work.

mirubee moti-1

















































Error while setting up platform wibeee Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/", line 128, in _async_setup_platform SLOW_SETUP_MAX_WAIT, loop=hass.loop) File "/usr/local/lib/python3.7/asyncio/", line 416, in wait_for return fut.result() File "/usr/local/lib/python3.7/concurrent/futures/", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/config/custom_components/wibeee/", line 77, in setup_platform sensor_phase,sensor_name = item.tag.split("_",1) ValueError: not enough values to unpack (expected 2, got 1)

I recommend you to call directly REST API and check if response is similar to the one i posted. Also check csrp post, they have a different response format, and for that, they have done some modifications.

Or even better, compare your response with the ones I documented in github repo:

Hola Juanjo
Would it be posible to adapt the Mirubee component to new HA custom components structure (HA 0.88+) ?

Notable breaking change

We finished the great migration. All built-in platforms are now in their own folder. This means that if you had a custom component or platform that had the same name as a built-in one, you have to rename it. If you still have platforms in your custom_components/ directory in the old file format, sensor/ , rename it to my_platform/ . It still works but it will not be supported in a future release.

regarding the last two messages, thanks for the info. Unfortunately I have right now no time at all for those adaptions, just be patient or if anyone wants to do the work, all the code is accesible in github

1 Like

as it was just a name/folder rename, I was able to do it and test it with my wibeee device (3 phases)

Please, check git repository.

1 Like

Thanks @juanjoSanz , simply by renaming the component stops sending in message, everything continues to work as it should.

1 Like

It seems that when updating to version 0.92.0b1 and 0.92.0b2, the component stops working tomorrow I will investigate the issue, to see what happens with the final version.

For now it is recommended to use the version: 0.91.4

Test version 0.92.0b3

Log Details (ERROR)

Tue Apr 23 2019 22:20:35 GMT+0200 (hora de verano de Europa central)

Integration not found: introduction Integration wibeee not found when trying to verify its sensor platform.

An option to start the component, creating a file if there is a record of failures.

File: manifest.json

  "domain": "wibeee",
  "name": "Wibeee",
  "documentation": "",
  "dependencies": [],
  "codeowners": ["@juanjoSanz"],
  "requirements": []

Log Details (WARNING)

Tue Apr 23 2019 22:48:19 GMT+0200 (hora de verano de Europa central)

You are using a custom integration for wibeee which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.

Log Details (WARNING)

Tue Apr 23 2019 22:48:24 GMT+0200 (hora de verano de Europa central)

Your configuration contains extra keys that the platform does not support. Please remove [name], [host], [phases].

Thanks to @juanjoSanz and @Oscar , for their great work.

I already manage that the component is executed with the final version 0.92.0


File: manifest.json

“domain”: “wibeee”,
“name”: “Wibeee”,
“documentation”: “”,
“dependencies”: [],
“codeowners”: ["@juanjoSanz"],
“requirements”: []

File: >

This file creates it blank.

Do not make any modification of the component code and everything seems to work correctly.

thanks, I have added manifest file to github repo.


File: >

I understood, this file should contain now the initialization of the component.

I would need to rewrite the component, let’s see if I can get the time to do it.

1 Like

@juanjoSanz Thanks, the important thing was found a simple way to solve the problems generated by the new version 0.92.0

I fully understand your situation and I deeply appreciate that you share your work with the community, I can not be of help in the part of the code, but for any test you have all my help.

I will continue researching the subject to try to provide data to this group and to be of help, to maintain and improve the component.

@juanjoSanz I have a Mirubox voltimeter and i am trying to implement it into HA but i can´t, is there any tutorial from the beginning?
Thank you


Just check if your device expose the data as XML as wibeee does. In the GitHub repository I have uploaded one example of that XML format. If so, we may only need to adapt XML parsing to your format. Indeed we can define different parsing methods in this component to support all similar devices that exists.

Best regards,


Thanks, I have managed to not fail me the configuration, but It still do not give the data, when I get home I will test with the xml.

This is my XML, it seems the same as @dieandgo, I modified the code you told him but the sensors says “Desconocido”:




























































































When i add

- platform: wibeee
  name: "Wibeee"
  scan_interval: 5

to the configuration.yaml it says:

end of the stream or a document separator is expected at line 64, column 1:
    - platform: wibeee

I am on a Raspberry with Hassio and getting the following message “[homeassistant.setup] Setup failed for wibeee: No setup function defined.”

Finally i got it working, thanks for the info @juanjosanz

Thanks @Csrp for helping mi with mi device , works perfect!!!



First of all… congratulations… this will be great.

I already installed the custom component and when i test the configuration (after some try’s it finish with successful) i can find him.

How can i see the data? I don’t know… :frowning:

(Sorry for this basic question… hope someone can help me)
Diogo Reis