Sorry, I was replying to this comment above regarding the Energy tab. The examples that I linked to above show how to configure the production and consumption sensors using my fork of the custom component.
Could you share what energy monitor and the firmware version that you are running successfully with this custom component? Thanks
I was finally able to integrate it.
I am using the Home Assistant Energy monitor.
The firmware of the two Wibeee devices is 4.4.134.
I just saw today that there is a new firmware version but at the moment I am not going to update.
Best regard
1 Like
For those interested in using multiple Wibeee devices I have made Release v3.0.0-beta.0 · luuuis/hass_wibeee · GitHub, which adds a unique_id to all entities. This means the entity id can be changed, the entity can be added to a zone and so forth.
Note: upon seeing the unique_id Home Assistant will consider these to be new entities and the old Wibeee entities will become unavailable. Configuring the integration with unique_id: false suppresses the unique id but also doesn’t allow multiple devices to be used.
You need to select Show Beta in HACS to be able to update to this beta version.
1 Like
Thank you luuuis for your interest in putting the integration to work with one or more meters. I haven’t tested it yet, I’m preparing a test installation. Smilics will change the cloud where the data is, will change it to WIBEEE NEST, you know if the integration will be compatible.
Thanks
This integration does not use Cloud APIs, it is doing Local Polling so should not be affected by those changes. Only if you upgrade the firmware on the device could those APIs possibly be affected.
I don’t know how to get the beta version into HACS, can you help?
I can’t find the integration in HACS. Isn’t the name I have to look up Wibeee? I only find “Wibeee - abacao”
Just follow the installation instructions. You will need to remove other versions such as abacao because they share the same integration id.
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?
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.
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
I’m using this integration: GitHub - abacao/hass_wibeee: Home Assistant Component: Mirubee or Wibeee
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
Yes, check this post for instructions.
1 Like
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?
Just repeat the same configuration that your already have and edit the host to contain the other IP address.
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?