New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aqara Smart Plug - power sensor becomes unreachable #5454
Comments
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs. |
Anyone? |
@SwoopX Perhaps you have some time to check? |
I'm afraid there is nothing to be checked. I don't have even the slightest clue how such a condition can happen. |
I also have the same issue with the sensor being unavailable. I did some quick debugging where A newly reset and added plug has After power cycling the plug, the fingerprint now contains Tested a hack fix in But I hope someone else knows what a proper fix is. Since I know neither the code nor the zigbee protocol. |
Looks like the change I did partially revert commit 36b9fc1. |
Can somebody please check if this has been resolved with version 2.14.0 beta? |
Tried the beta (unmodified) and the issue remains, for me at least. Still creates a dotted history graph in HA while unavailable (like the one in torkel's image). |
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 |
same over here... so it looks to me, that the new plugs don't use the "electrical measurement" descriptors anymore as these are always 0, but with the xiaomi specific values the real power value is being read. I'm on: |
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs. |
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs. |
As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again. |
Is there an update on this issue? |
I have the same plugs with a similar problem. The device becomes temporarily unavailable in Home Assistant every time the power consumption changes more than the value set in: FCC0 Lumi specific -> 0x0204 (min. power change for report(W)) It also happens when I manually read the value from 000C Analog Input -> 0X0055 Present value. As a workaround I could fabricate a template sensor that updates only when the value changes to a numeric value. It would clean up the sensor data nicely, but it's undesirable |
Used another workaround for Home Assistant: I used the deCONZ API instead. I set the reporting interval (0X00F6) to 3 seconds (I'll see how that goes), and configured a REST sensor that checks the sensor value. The resulting data is picked up by a template sensor. The API GET method: http://XX.XX.XX.XX:40850/api/YOUR_API_TOKEN/sensors/YOUR_SENSOR_ID REST Sensor configuration - platform: rest
name: lumi_power_1
resource: http://XX.XX.XX.XX:40850/api/YOUR_API_TOKEN/sensors/YOUR_SENSOR_ID
scan_interval: 3
json_attributes_path: '$.state'
json_attributes:
- power
value_template: 'OK' Template sensor configuration - platform: template
sensors:
lumi_power_1_wattage:
value_template: '{{ state_attr("sensor.lumi_power_1", "power") }}'
device_class: power
unit_of_measurement: 'W' The only downside I found so far is that when the plug is removed from the wall socket without switching it off first, the last known value is retained in the sensor. If you shut it down first, it will be 0. |
@silcotm Do you mind re-opening the issue please? It's still not fixed. |
One problem is, that there are different firmware versions for that smartplug that cannot be identified with deconz yet. You might want to comment there as its about the smartplug issue. https://forum.phoscon.de/t/feature-request-ddf-optional-basic-cluster-identifications/2092 I have 2 Aqara smart plugs with different firmware versions and can only use one at a time due to that issue |
REopening as it probably isn't solved. @SwoopX can you check along? |
I have a similar 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 capabilities…can this be a problem with the latest software? Any help is appreciated! |
@phlexss Can you share screens of the basic cluster for both devices? https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/How-to-read-Clusters |
@phlexss I think you need to re-pair the faulty one a few times. They are the same devices but probably haven't paired fully. |
This is a bit embarassing....I have deleted/paired this device at least 5 times and it never showed the measurement capabilities......and now I delete/pair again and it works! So no more issue for me....I'll keep this "trick" in mind! |
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs. |
@silcotm Do you mind re-opening the issue please? Issue still not fixed. |
Should be settled with #6216 |
I pulled in the latest commit (0e2f15e) earlier today and tried the new DDF with lumi.plug.maeu01, conbee II fw 26720700. Can confirm that both power and consumption sensors are working without becoming unreachable. |
After upgrading today to latest docker release, I didn't get the power and consumtion measurments from Aqara Smart Plugs. But not from all devices i used, only for these with firmware |
you have to re-pair the devices that are not working anymore. |
@SwoopX can you tell me why you read the power via zcl and not via xiaomi:special directly? via zcl i see random drops to 0W while not with xiaomi:special. of course i have to lower the reporting interval of the device to get more fresher data. |
@nhulsch please keep the discussion on topic. I haven't observed anything like you describe within 1h runtime, confirmed by deconz logs and the sniffer. If you still feel there's something wrong, you can raise a seperate issue with supporting debug log data. |
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
Screenshots
Environment
deCONZ Logs
5 minutes of logs: https://pastebin.com/Ex4xHhPh
During those 5 minutes, the sensor came and went 2-3 times.
Additional context
The text was updated successfully, but these errors were encountered: