Skip to content
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

Xiaomi Mi Smart Plug not fully usable (only switch feature offered) #4238

Closed
bcutter opened this issue Jan 19, 2021 · 9 comments
Closed

Xiaomi Mi Smart Plug not fully usable (only switch feature offered) #4238

bcutter opened this issue Jan 19, 2021 · 9 comments

Comments

@bcutter
Copy link

bcutter commented Jan 19, 2021

Describe the question or issue you are having

I paired a Xiaomi Mi Smart Plug using Phoscon with category "lights". In my smart home automation system only one entity (switch) is offered, I miss all the others for the power monitoring this device fully supports.

According to https://phoscon.de/de/conbee2/compatible the device is supported.

Do I need to pair it by another way? Did not pop up by trying to add as switch.
How to get access to the other entities?

Screenshots

grafik

Environment

  • Host system: Raspberry Pi
  • Running method: Home Assistent deCONZ Add-on
  • Firmware version: 26660700
  • deCONZ version: 2.07.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? If so: Which? - NO

deCONZ Logs

Additional context

@bcutter
Copy link
Author

bcutter commented Jan 19, 2021

Update: Grabbing the model code ZNCZ04LM from https://www.zigbee2mqtt.io/information/supported_devices.html#xiaomi and looking for this on https://phoscon.de/de/conbee2/compatible I can not find this device.

The one I find has no model number specified:
grafik

So... it´s not supported yet, really? Or unknown?

That would be a no-go - 3rd zigbee device to be integrated using Phoscon/deCONZ - and would likely force me to switch to ZigBee2MQTT :-( :-( :-(

@bcutter
Copy link
Author

bcutter commented Jan 19, 2021

@tonyawad88
Copy link

tonyawad88 commented Feb 5, 2021

@bcutter I am using Home Assistant with Phoscon/Conbee II and when I pair it as a "sensor" in Phoscon app, I get 3 entities in Home assistant, 1 switch, 1 current power consumption and 1 historical power consumption. Remove it from Phoscon and re-add it using the Sensor => Other. My model # is ZNCZ02LM.
Screen Shot 2021-02-04 at 11 53 44 PM

@bcutter
Copy link
Author

bcutter commented Feb 7, 2021

@tonyawad88 That´s the same result for me. BUT:

  • You can start pairing on the sensors page, but the plug will always be listed on the lights page.
  • I tried pairing a second Mi Smart Plug. I only get one switch entity in Home Assistant:
    grafik

So my issues still are:
1) Only switch entity offered by deCONZ to Home Assistant.

2) With a lot of luck (pairing, waiting, checking, deleting, pairing again, hope and pray, ...) I get 3 entities: switch, current and total power consumption. That´s the best I can get with this device after a dozen pairing attempts:
grafik

3) Total power consumption does not calculate (always 0.001 kWh) and it´s not constantly available (I think the first issue is the result of the unavailability):
grafik

**4) Attributes are missing (not shown at all - see current and voltage on the bottom):
grafik

5) I still miss all the other entities and sensors which are offered when using another ZigBee Gateway and ZigBee2MQTT (device temperature, overpower, link quality).
grafik

6) After deCONZ being not available (restart e. g.) the plug needs to be "awaken" by pressing the button, otherwise it will be unavailable in the ZigBee network.

So that´s HELL OF A PAIN and I´m not sure why it is that horrible. As a friend of mine runs this device just fine with other ZigBee equipment I tend to fingerpoint to the deCONZ part.

@framesetter99
Copy link

framesetter99 commented Feb 7, 2021

Worked for me. All in all I probably needed 3 pairing attempts per device to get it right.
I paired it as a Light, waited, checked the sensors with the rest API.
If I got a consumption and power sensor I was good.
If not I removed the "light" via the Phoscon GUI + the sensors via rest API and started again.
Did it step by step with two devices.
For me it was important to clean up the sensors with the Phoscon Rest API, because deleting the light does not remove the sensors.
Once I was able to see values with the rest API I added it in Home Assistant with the Deconz Integration.

image

@bcutter
Copy link
Author

bcutter commented Feb 7, 2021

After another hour of pairing / deleting / repeat I ended up in a somewhat stable total consumption entity which is acutally usable, so at least issues 1) and 3) are gone:
grafik

I think reading the basic cluster in deCONZ after starting sensor search in Phoscon made some difference (or reading the simple descriptors, don´t know exactly).

As you can see the attributes still show no values (issues 4) and 5)).
@framesetter99 do you see actual values there (check current and total consumption entities)?

grafik

So issue 6) will be the one definitely staying unfortunately - which might be the reason to kick either the Mi Smart Plugs or deCONZ, that´s a no-go and probably a deCONZ specific behaviour.

@bcutter
Copy link
Author

bcutter commented Feb 13, 2021

Update: Need to revert my word from related to issue 3: it fell back to normal behaviour, so no stable data delivery and values aren´t updated at all.

grafik

Additionally hope in latest v2.9.3 which should fix the issue 6 were not satisfied (see #4139 (comment)) so currently I need to sum all my experiences by simply stating "this device is not usable with Dresden Electronic hardware and software".

Will try to swap these plugs, just horrible experience. Same plugs with another ZigBee gateway using ZigBee2MQTT and everything´s working fine. Too bad.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 7, 2021

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.

@github-actions github-actions bot added the stale label Mar 7, 2021
@bcutter
Copy link
Author

bcutter commented Mar 7, 2021

I gave up. Great hardware but not usable with ConBee 2/deCONZ in my case.

@bcutter bcutter closed this as completed Mar 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants