I’ve got a aqara smart plug with energy monitoring, in theory. it shows up as plug.lumi.maus01
I saw this issue:
opened 04:11AM - 30 Dec 19 UTC
closed 11:15AM - 05 Jun 20 UTC
Using ConBee II with deCONZ docker image on Ubuntu 18.04. I went through the ste… ps to add a new switch, but it's automatically added as a light lumi.plug.maus01. Let me know if you need any other info.
ConBee II
Version: 2.05.71
Firmware: 264A0700
and this one, which I now am not totally sure is the same plug:
opened 07:49AM - 10 Jan 20 UTC
closed 11:15AM - 05 Jun 20 UTC
lumi.ctrl_86plug.aq1 work in phoscon, but power measurement sensors absent.
so I’ve tried redoing the pairing process a few times, with and without loads plugged in. It shows up in home assistant, as either unavailable, or with a constant 9W, which matches the light that was plugged in, but could be a coincidence because its still -1W for one sensor and 9W for the other when its plugged into a mini fridge, or a laptop.
I’m comfortable fiddling with the settings, but I haven’t had to do it before. What all should I try to edit to see if I got a dud plug? If I did, can anyone recommend a decent plug with energy monitoring? The only one I found was the sinopé model that has a pull request open, but seems to have been stalled for awhile.
so turns out its…slightly weirder
this entity seems to get updated when I switch the plug, and every few minutes, then drops back to unavailable. the data also seems to persist when I delete the plug in deconz and re-add it.
apologies for triple posting here, but I can’t add more than one image to a post
the analog input (02) updates relatively quickly after I switch the light, so that’s kind of a relief. Does anyone have an idea of where to look to get that data to show up in home assistant?
Smanar
December 12, 2021, 9:32am
4
And you are not alone, I have found some more issue about this bug
opened 06:18AM - 06 Nov 21 UTC
Bug report
<!--
- Use this issue template to report a bug in the deCONZ REST-API.
- A… nything that is not clearly a bug can implicate manual closure. For support we recommend the forum: https://forum.phoscon.de
- If you want to report a bug for the Phoscon App, please head over to: https://forum.phoscon.de
- Make sure not to remove any headers and fill the template completely. If you remove the headers, the issue will be auto-closed.
- If you're unsure if the bug fits into this issue tracker, please ask for advise in our Discord chat: https://discord.gg/QFhTxqN
- Please make sure sure you're running the latest version of deCONZ: https://github.com/dresden-elektronik/deconz-rest-plugin/releases
-->
## Describe the bug
Hello,
I received this plug today (lumi.plug.maeu01 / SP-EUC01) and paired it with deCONZ:
Then I went into Home Assistant and there it was showing with a lot of weird entities like Motion and Battery:
Then I went back into deCONZ and went to Sensors > Add new > Other and pressed the button on the plug. It said sensor added successfully (but no sensor actually appeared in the list of sensors).
Going back to Home Assistant, the device now fixed itself and displayed energy metering etc:
However, the problem is that the power consumption sensor becomes unavailable a few minutes after satrting deCONZ. In those few minutes, the value of the power consumption updates like it should when the power draw changes, but then the sensor becomes unavailable and stays that way.
## Steps to reproduce the behavior
## Expected behavior
<!--
If applicable, describe what you expected to happen.
-->
## Screenshots
<!--
If applicable, add screenshots to help explain the problem.
-->
## Environment
<!--
The deCONZ and firmware versions are found in the Phoscon App: Menu -> Settings -> Gateway,
as well as in the deCONZ GUI: Menu > Help > About deCONZ.
-->
- Host system: Ubuntu VM
- Running method: Marthoc Docker container
- Firmware version: 26720700
- deCONZ version: 2.13.01
- Device: ConBee II
- Do you use an USB extension cable: yes
- Is there any other USB or serial devices connected to the host system? no
## deCONZ Logs
<!--
Debug logs can help to investigate certain problems like device pairing and communication issues.
Logging can be enabled on the command line as described in:
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/deCONZ-debug-flags
Secondly, for versions above 2.05.87: In the deCONZ GUI: click Help > debug view. Output of APS,ZDP, ZCL and INFO can be handy.
-->
5 minutes of logs: https://pastebin.com/Ex4xHhPh
During those 5 minutes, the sensor came and went 2-3 times.
## Additional context
<!--
If relevant, add any other context about the problem here, like network size, number of routers and end-devices
and what kind of devices/brands are in the network.
-->
opened 02:09PM - 19 Oct 21 UTC
closed 07:40PM - 21 Oct 21 UTC
Bug report
<!--
- Use this issue template to report a bug in the deCONZ REST-API.
- A… nything that is not clearly a bug can implicate manual closure. For support we recommend the forum: https://forum.phoscon.de
- If you want to report a bug for the Phoscon App, please head over to: https://forum.phoscon.de
- Make sure not to remove any headers and fill the template completely. If you remove the headers, the issue will be auto-closed.
- If you're unsure if the bug fits into this issue tracker, please ask for advise in our Discord chat: https://discord.gg/QFhTxqN
- Please make sure sure you're running the latest version of deCONZ: https://github.com/dresden-elektronik/deconz-rest-plugin/releases
-->
## Describe the bug
My 2 Smart Plugs from aquara (lumi.plug.maeu01) Version 09-10-2019 shows the wrong power measurment.
For few seconds it shows the correct current power consumption in "W" of the pluged device. But then it shows 0 W for many minutes.
Also the calculated "kWh" do not increasing continuasly. It always switch back to 26,902 "kWh"
I use homeassistant to use automations. On every state change homeassistant write the new value in the DB.
If i make an Query of the actual power entity you can see that the state only appears few seconds with the correct value 5 and then drops down to 0
Also if i make an Query of the "kWh" entity you can see that the state always go back to 26,902
Homeassistant throws also a Warning about that "not increasing" kWh:
That also the Deconz Application show me the weird power and total consumption behavior i dont think it is a problem from HomeAssistant.
So maybe Deconz have an Issues with the Aqara Smart Plugs EU or both Smart Plugs on exact time went broken!
I testet the Smart Plugs on different power outlets and with different devices Pluged In.
For few Week i updated deconz to the last Version at that time but i dont remember the time and from which version updatet.
Any help? Thanks
## Steps to reproduce the behavior
<!--
If the problem is reproducable, list the steps here:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. Observed error
If the problem can't be reproduced and is sporadic, please provide some details
on how often and when the issue happens.
-->
## Expected behavior
<!--
If applicable, describe what you expected to happen.
-->
## Screenshots
<!--
If applicable, add screenshots to help explain the problem.
-->
## Environment
<!--
The deCONZ and firmware versions are found in the Phoscon App: Menu -> Settings -> Gateway,
as well as in the deCONZ GUI: Menu > Help > About deCONZ.
-->
- Host system: (Raspberry Pi / PC / NAS)
- Running method: Marthoc Docker container on Synology
- Firmware version: 26720700
- deCONZ version: 2.13.01 / 6.10.2021
- Device: ConBee II
- Do you use an USB extension cable: yes
- Is there any other USB or serial devices connected to the host system? If so: Which? -> no
## deCONZ Logs
<!--
Debug logs can help to investigate certain problems like device pairing and communication issues.
Logging can be enabled on the command line as described in:
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/deCONZ-debug-flags
Secondly, for versions above 2.05.87: In the deCONZ GUI: click Help > debug view. Output of APS,ZDP, ZCL and INFO can be handy.
-->
## Additional context
<!--
If relevant, add any other context about the problem here, like network size, number of routers and end-devices
and what kind of devices/brands are in the network.
-->
On the last one you have a SwoopX comment about the used cluster, it s probably a manufacture cluster.
And some plug don’t support it https://github.com/Koenkk/zigbee2mqtt/issues/6861
1 Like
well its good to know I am not alone and not crazy. I think I’ll just pick up a wifi-based EM plug, I wonder if zigbee just doesn’t properly support this, there seems to be trouble with every EM device on every platform.
Mimiix
December 12, 2021, 5:11pm
6
I don’t have any issues with the shp13 and 15
Hello!
Mimiix
December 15, 2021, 7:22am
8
Seems like theres already a bug report open:
opened 06:18AM - 06 Nov 21 UTC
Bug report
<!--
- Use this issue template to report a bug in the deCONZ REST-API.
- A… nything that is not clearly a bug can implicate manual closure. For support we recommend the forum: https://forum.phoscon.de
- If you want to report a bug for the Phoscon App, please head over to: https://forum.phoscon.de
- Make sure not to remove any headers and fill the template completely. If you remove the headers, the issue will be auto-closed.
- If you're unsure if the bug fits into this issue tracker, please ask for advise in our Discord chat: https://discord.gg/QFhTxqN
- Please make sure sure you're running the latest version of deCONZ: https://github.com/dresden-elektronik/deconz-rest-plugin/releases
-->
## Describe the bug
Hello,
I received this plug today (lumi.plug.maeu01 / SP-EUC01) and paired it with deCONZ:
Then I went into Home Assistant and there it was showing with a lot of weird entities like Motion and Battery:
Then I went back into deCONZ and went to Sensors > Add new > Other and pressed the button on the plug. It said sensor added successfully (but no sensor actually appeared in the list of sensors).
Going back to Home Assistant, the device now fixed itself and displayed energy metering etc:
However, the problem is that the power consumption sensor becomes unavailable a few minutes after satrting deCONZ. In those few minutes, the value of the power consumption updates like it should when the power draw changes, but then the sensor becomes unavailable and stays that way.
## Steps to reproduce the behavior
## Expected behavior
<!--
If applicable, describe what you expected to happen.
-->
## Screenshots
<!--
If applicable, add screenshots to help explain the problem.
-->
## Environment
<!--
The deCONZ and firmware versions are found in the Phoscon App: Menu -> Settings -> Gateway,
as well as in the deCONZ GUI: Menu > Help > About deCONZ.
-->
- Host system: Ubuntu VM
- Running method: Marthoc Docker container
- Firmware version: 26720700
- deCONZ version: 2.13.01
- Device: ConBee II
- Do you use an USB extension cable: yes
- Is there any other USB or serial devices connected to the host system? no
## deCONZ Logs
<!--
Debug logs can help to investigate certain problems like device pairing and communication issues.
Logging can be enabled on the command line as described in:
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/deCONZ-debug-flags
Secondly, for versions above 2.05.87: In the deCONZ GUI: click Help > debug view. Output of APS,ZDP, ZCL and INFO can be handy.
-->
5 minutes of logs: https://pastebin.com/Ex4xHhPh
During those 5 minutes, the sensor came and went 2-3 times.
## Additional context
<!--
If relevant, add any other context about the problem here, like network size, number of routers and end-devices
and what kind of devices/brands are in the network.
-->
Swoop
January 29, 2022, 10:20pm
9
Can somebody please check if this has been resolved with version 2.14.0 beta?
cyrial
February 2, 2022, 8:43pm
10
Doesn’t look like it was fixed
Swoop
February 12, 2022, 9:25pm
11
Ok, so the stable 2.14.1 comes with a DDF included and on GH there’s already confirmation that it’s working with it.
1 Like
nano
February 17, 2022, 8:53am
13
Any news on this front?
some data randomly gets to HA…
12:16:28:394 0x54EF4410003145CC extract Xiaomi special attribute 0x00F7
however isnt working well for moment …
Running latest deconz and 2.14.01 firmware
Is there an update on this issue?
I have the same problem. I’m using CONBEE II v2.17.01 and when I add an AQARA SMART PLUGIN I don’t get power sensors anymore.
I have an exact same device that was connected some time ago (with older deconz sw version) which works fine.
When looking at the devices using VNC the one that works shows the following cluster info:
0702 Simple Metering
The newly added device doesn’t show these two clusters, but it shows:
FCC0 Lumi speficic
It seems deconz doesn’t identify the measurement capablities…can this be a problem with the latest software?
Any help is appreciated!
Mimiix
July 15, 2022, 8:15am
16
opened 06:18AM - 06 Nov 21 UTC
closed 03:13AM - 29 Apr 22 UTC
stale
Bug report
<!--
- Use this issue template to report a bug in the deCONZ REST-API.
- A… nything that is not clearly a bug can implicate manual closure. For support we recommend the forum: https://forum.phoscon.de
- If you want to report a bug for the Phoscon App, please head over to: https://forum.phoscon.de
- Make sure not to remove any headers and fill the template completely. If you remove the headers, the issue will be auto-closed.
- If you're unsure if the bug fits into this issue tracker, please ask for advise in our Discord chat: https://discord.gg/QFhTxqN
- Please make sure sure you're running the latest version of deCONZ: https://github.com/dresden-elektronik/deconz-rest-plugin/releases
-->
## Describe the bug
Hello,
I received this plug today (lumi.plug.maeu01 / SP-EUC01) and paired it with deCONZ:
Then I went into Home Assistant and there it was showing with a lot of weird entities like Motion and Battery:
Then I went back into deCONZ and went to Sensors > Add new > Other and pressed the button on the plug. It said sensor added successfully (but no sensor actually appeared in the list of sensors).
Going back to Home Assistant, the device now fixed itself and displayed energy metering etc:
However, the problem is that the power consumption sensor becomes unavailable a few minutes after satrting deCONZ. In those few minutes, the value of the power consumption updates like it should when the power draw changes, but then the sensor becomes unavailable and stays that way.
## Steps to reproduce the behavior
## Expected behavior
<!--
If applicable, describe what you expected to happen.
-->
## Screenshots
<!--
If applicable, add screenshots to help explain the problem.
-->
## Environment
<!--
The deCONZ and firmware versions are found in the Phoscon App: Menu -> Settings -> Gateway,
as well as in the deCONZ GUI: Menu > Help > About deCONZ.
-->
- Host system: Ubuntu VM
- Running method: Marthoc Docker container
- Firmware version: 26720700
- deCONZ version: 2.13.01
- Device: ConBee II
- Do you use an USB extension cable: yes
- Is there any other USB or serial devices connected to the host system? no
## deCONZ Logs
<!--
Debug logs can help to investigate certain problems like device pairing and communication issues.
Logging can be enabled on the command line as described in:
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/deCONZ-debug-flags
Secondly, for versions above 2.05.87: In the deCONZ GUI: click Help > debug view. Output of APS,ZDP, ZCL and INFO can be handy.
-->
5 minutes of logs: https://pastebin.com/Ex4xHhPh
During those 5 minutes, the sensor came and went 2-3 times.
## Additional context
<!--
If relevant, add any other context about the problem here, like network size, number of routers and end-devices
and what kind of devices/brands are in the network.
-->
I’ll re-open that one and continue there please. Yours is not the same as the OP’s.
I’d be happy to do that but are you sure? That one is about the sensor becoming unavailable…in my case that is not the problem, the old plug still reports fine…it’s just that a new plug doesn’t show the power monitoring data…
So to me the subject of this item “Can’t get power monitoring on Aqara smart plug” describes the problem better.
What do you think?
Or maybe report it as a new problem?
Mimiix
July 15, 2022, 10:06am
18
anon97042473:
maus01
OP has maus01
The problem is mostly that it is not reporting a lot, that’s why it probably is unavailable.
Aha…I see…I’ll add my comment from above to that call and hope it gets picked up.
The strange thing is that both devices are exactly the same type and version but deconz doesn’t see the capabilities of the last one added.
I dare not remove/add the one that works for fear of it also loosing the power-meter capability…
