New device support request: Xiaomi Mijia Zigbee 3.0 Smart Home Light Sensor #2380

sumo-89 · 2020-01-26T11:49:48Z

Hi!
Please add support for this device. :)

Completely covered "Mesured value" is "0".

SwoopX · 2020-01-26T20:25:39Z

Can you please also provide some screenshots of the basic and the power configuration cluster after the attributes have been read?

I do see we have a new manufacturer code here.

sumo-89 · 2020-01-26T21:42:56Z

Sure!
Thank you! :)

SwoopX · 2020-01-26T22:31:29Z

Thanks. Have you already checked if the sensors are available via REST API? You may check out this fur further guidance #2373 (comment)

Just to highlight this upfront, the sensor will not be visible via Phoscon as it is closed source.

sumo-89 · 2020-01-27T21:15:09Z

Hi!
Sorry, I tried to follow that thread but I don't get it... :( I use Postman, so I know how get all sensors from REST, but it just doesn't show up. I tried resetting it, restarting deconz etc. I can read the attributes.

If I can see it (like I you can see in the screenshoots above) have I managed to include it or not then? Or is that the issue?

SwoopX · 2020-01-27T21:57:49Z

I use Postman, so I know how get all sensors from REST, but it just doesn't show up.

That's fine then. It tells us that the device indeed isn't supported. Just wanted to doucle check since in the past, device integration was requested although the sensors were there.

davidclancy · 2020-02-04T21:07:23Z

When will this be supported

SwoopX · 2020-02-04T21:10:11Z

I'd expect with version .73. Not sure when DE will release it.

LukasA83 · 2020-02-17T19:46:17Z

I've tested it today with .73. I can connect the sensor and see it in REST API. If I press the button on the sensor and manually click "read" on the Illuminance measurement Cluster it is updating the Measured Value.
By forcing an update via the button without any interaction in VNC interface, I see no update of the value. Any configuration issue?

Output from docker deconz:
19:42:45:698 no button map for: lumi.sen_ill.mgl01 ep: 0x01 cl: 0x0000 cmd: 0x0A pl[0]: 005,
19:42:45:698 ZCL attribute report 0x04CF8CDF3C776202 for cluster 0x0000, ep 0x01,
19:42:45:698 0x04CF8CDF3C776202 skip Xiaomi attribute 0x0000,

Update:
I had to manually create the binding, but now it works flawless. Thanks!

davidclancy · 2020-02-17T20:12:37Z

I can now connect to the sensor but do not see in the connected sensor list. Any ideas? Regards

…

________________________________ From: LukasA83 <notifications@github.com> Sent: Tuesday, February 18, 2020 8:46:17 AM To: dresden-elektronik/deconz-rest-plugin <deconz-rest-plugin@noreply.github.com> Cc: davidclancy <clancy666@hotmail.co.uk>; Comment <comment@noreply.github.com> Subject: Re: [dresden-elektronik/deconz-rest-plugin] New device support request: Xiaomi Mijia Zigbee 3.0 Smart Home Light Sensor (#2380) I've tested it today with .73. I can connect the sensor and see it in REST API. If I press the button on the sensor and manually click "read" on the Illuminance measurement Cluster it is updating the Measured Value. By forcing an update via the button via any interaction in VNC interface, I see no update of the value. Any configuration issue? — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#2380?email_source=notifications&email_token=AC5TXC6YKXCFKXYCZC6MTFLRDLSQTA5CNFSM4KLWODV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL7PSHA#issuecomment-587135260>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC5TXCYGPUAWYNCA3F2IQ5TRDLSQTANCNFSM4KLWODVQ>.

SwoopX · 2020-02-18T09:48:56Z

Phoscon? If yes, this will probably not happen any time soon since Phoscon is closed source and devices need to be integrated seperately.

@LukasA83 Thanks for your feedback. It then looks like the code with regard to binding requires some more tweaking. I'll have a look at it.

davidclancy · 2020-02-18T20:06:10Z

Yes this is using Phoscon via Home Assistant. HA seems to see the sensor but as unknown. although it does not show in the Phoscon list.

eserero · 2020-02-18T23:26:56Z

@LukasA83 can you explain more what you did?
how did you get the button press to refresh the data?
my sensor never refresh the data unless I pressed it and click "read", but shouldn't the sensor report light changes every few seconds without any need for user intervention?

SwoopX · 2020-02-19T12:55:31Z

@eserero You need to add the binding in deconz GUI manually. Bind cluster illuminance with the level control cluster of the conbee. You can check #2445 for details.

LukasA83 · 2020-02-20T01:19:40Z

Battery is no reported into rest api, always indicates "null":

{
  "config": {
    "battery": null,
    "on": true,
    "reachable": true,
    "temperature": null,
    "tholddark": 12000,
    "tholdoffset": 7000
  },
  "ep": 1,
  "etag": "20307667724a20efdd08ead6e29bb8b3",
  "manufacturername": "LUMI",
  "modelid": "lumi.sen_ill.mgl01",
  "name": "Lightsensor outside garage",
  "state": {
    "dark": true,
    "daylight": false,
    "lastupdated": "2020-02-20T01:09:32",
    "lightlevel": 0,
    "lux": 0
  },
  "swversion": "20191118",
  "type": "ZHALightLevel",
  "uniqueid": "04:cf:8c:df:3c:77:62:02-01-0400"
}

SwoopX · 2020-02-20T19:49:47Z

Already included automatic binding and battery status in a new pull request.

davidclancy · 2020-02-20T22:00:56Z

Still can not see it in Phoscon via Home Assistant

SwoopX · 2020-02-20T23:28:28Z

Have you compiled my repo to check it, or...?

And by the way, Phoscon is not deconz. I don't expect the device to show up in Phoscon as it is closed source and we cannot implement anything there.

zladukas · 2020-02-26T20:47:16Z

I can confirm, that device is working fine:

{
"config": {
"battery": 100,
"on": true,
"reachable": true,
"temperature": null,
"tholddark": 12000,
"tholdoffset": 7000
},
"ep": 1,
"etag": "a3264bada36855929d175008da7344be",
"manufacturername": "LUMI",
"modelid": "lumi.sen_ill.mgl01",
"name": "Light sensor",
"state": {
"dark": true,
"daylight": false,
"lastupdated": "2020-02-26T20:45:50",
"lightlevel": 6021,
"lux": 4
},
"swversion": "20191118",
"type": "ZHALightLevel",
"uniqueid": "04:cf:8c:df:3c:77:xx:xx-01-0400"
}

SwoopX · 2020-02-26T22:48:07Z

Sounds great, then I guess we're done here.

davidclancy · 2020-02-28T06:47:55Z

works in HA now but still not seen in the Deconz interface in Sensors On 27/02/2020, at 11:48, SwoopX <notifications@github.com<mailto:notifications@github.com>> wrote: Sounds great, then I guess we're done here. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#2380?email_source=notifications&email_token=AC5TXC63ROB4D4LQRFB4K7TRE3WSRA5CNFSM4KLWODV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENCGFLY#issuecomment-591684271>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC5TXCYNP6PGRXCQMU7PFP3RE3WSRANCNFSM4KLWODVQ>.

SwoopX · 2020-02-28T09:25:51Z

works in HA now but still not seen in the Deconz interface in Sensors

This will not happen unless DE integrates it. Phoscon is closed source.

drthanwho · 2020-03-21T23:17:51Z

If it helps I can also confirm that the device works with HA. I can see it as a device (sensor.lightlevel_4) on HA and doesn't show up on deconz integration as expected, which isn't really a problem anyway.

Thanks for adding support :)

jensflorian · 2020-04-21T16:28:57Z

I can also confirm this device works with Openhab 2.4.5 and can be accessed via the Deconz REST API. @SwoopX thanks for adding the support!

I don't understand why Dresden won't add this into phoscon. Real values are much better than the built in virtual daylight sensor.

drthanwho · 2020-04-30T18:46:25Z

I've been having some issue with the sensor the last two days. I was working for weeks until two days ago where it stopped syncing with HA. Weirdly however looking at the mesh network it still showed up as connected and with last seen status updating frequently.

After attempting to pair again (holding down button) it updated in HA once and hasn't since.

callebridholm · 2020-05-31T20:14:50Z

Anyone got this sensor working in deCONZ? I have tried adding my sensor several times now and that went fine but no data is sent. I am running deCONZ 2.05.77

"98": {
    "config": {
        "battery": null,
        "on": true,
        "reachable": true,
        "temperature": 0,
        "tholddark": 12000,
        "tholdoffset": 7000
    },
    "ep": 1,
    "etag": "0761fcf84eeb0e6ec003343dd44623f8",
    "lastseen": "2020-05-31T20:12:25.285",
    "manufacturername": "LUMI",
    "modelid": "lumi.sen_ill.mgl01",
    "name": "Light Sensor",
    "state": {
        "dark": null,
        "daylight": null,
        "lastupdated": "none",
        "lightlevel": null,
        "lux": null
    },
    "swversion": "20191118",
    "type": "ZHALightLevel",
    "uniqueid": "04:cf:8c:df:3c:77:3c:74-01-0400"
},

drthanwho · 2020-05-31T22:04:46Z

@callebridholm yeah I've had mine working just fine with deCONZ in Home Assistant. Only once it dropped off and had to pair it again. Apart from that it's working fine.

SwoopX · 2020-05-31T22:26:39Z

@callebridholm the binding got probably MIA. You can set it manually, use the illuminance measurement cluster for 1) and the measured value for 2) (values have been mentioned below as they would have been set by default for your device).

How to manually bind and enable attribute reporting on the example of the current position for windows covering devices

Manually bind a cluster
In deconz GUI, select Panels and then Bind dropbox.
For your device as well as the coordinator (blue node), press the most right bullet to expand the available clusters.
For the coordinator: Drag&drop 01 Home Automation Endpoint as destination.
For the device: Select the windows covering cluster as source, also drag&drop it. Take note that this must be a server cluster (colored blue).
Press bind.
Manually set up attribute reporting
Then you need to set up attribute reporting. In most cases, there are default settings already defined and should be placed into action either after a deconz restart or power-cycling the device. However, if values do not get updated upon the taken action or not at all, attributes reporting has presumably not been set up properly.
Select windows covering cluster of your device, double click on 0x0008 (current position).
On the lower end of the dialog, enter the values
Min. report interval: 5
Max. report interval: 300
Reportable change: 2000
then press write config.

callebridholm · 2020-06-01T10:25:43Z

@callebridholm the binding got probably MIA. You can set it manually, use the illuminance measurement cluster for 1) and the measured value for 2) (values have been mentioned below as they would have been set by default for your device).

How to manually bind and enable attribute reporting on the example of the current position for windows covering devices

Manually bind a cluster
In deconz GUI, select Panels and then Bind dropbox.
For your device as well as the coordinator (blue node), press the most right bullet to expand the available clusters.
For the coordinator: Drag&drop 01 Home Automation Endpoint as destination.
For the device: Select the windows covering cluster as source, also drag&drop it. Take note that this must be a server cluster (colored blue).
Press bind.

Manually set up attribute reporting
Then you need to set up attribute reporting. In most cases, there are default settings already defined and should be placed into action either after a deconz restart or power-cycling the device. However, if values do not get updated upon the taken action or not at all, attributes reporting has presumably not been set up properly.
Select windows covering cluster of your device, double click on 0x0008 (current position).
On the lower end of the dialog, enter the values
Min. report interval: 5
Max. report interval: 300
Reportable change: 2000
then press write config.

Hi,
I tried with the first step 1 but have problem to bind them, think I did the correct thing. Tried all four different lines with blue numbers but same problem with timeout.

SwoopX · 2020-06-01T11:43:47Z

Wake the device by exposing it to a light source and then darken it.

callebridholm · 2020-06-01T20:31:24Z

Wake the device by exposing it to a light source and then darken it.

Exposed to flash light 5 minutes and then in black box 8 hours but still same problems with binding

SwoopX · 2020-06-02T18:58:10Z

That is indeed strange. Have you also tried to reset and re-pair already?

callebridholm · 2020-06-03T10:33:15Z

That is indeed strange. Have you also tried to reset and re-pair already?

Yes! Now I tried to via VNC mark it and then choose "Delete selected nodes". The device is then remove but still visible when executing this command in postman:
http://localhost:40850/api/56478788EA/sensors/98

I then restarted deCONZ plugin but then the Light sensor is back. Is it a better way to completely remove a device in deCONZ?

SwoopX · 2020-06-03T21:54:05Z

Just physically reset the device. There should be a button somewhere which has to be held for like 5 - 15 secs.

callebridholm · 2020-06-05T20:25:43Z

Just physically reset the device. There should be a button somewhere which has to be held for like 5 - 15 secs.

Tried that several times without luck. Today I tried it at our summer house with a Conbee 1 and fw 26330500 and it work directly and updates lux values rapidly. So my problems is probably very old firmware at my Conbee stick at home, It has fw 260B0500 :)

SwoopX · 2020-06-05T21:31:32Z

That might be indeed a valid reason ;) But as you can see, it uses to work.

Mimiix · 2020-06-06T16:01:35Z

As OP's original question has been answered, please open a new issue.

slurpey · 2021-06-17T16:21:25Z

@callebridholm hi, I've tried your newbie instructions and somewhat got things going but nothing ends up showing in Home Assistant or in Node-Red Deconz integration. I seem to fail to follow your "Select windows covering cluster of your device, double click on 0x0008 (current position)."

Is this what you mean? In select windows, it's actually the 0000 box I need to click on? If so, I did try to "write" the interval times etc but it would end up in error.
I've tried this many times, restarted, even updated firmware and it seems it reacts (if I press the physical button, the little node blinks blue)

Apologies, this interface is very scary for a casual user. Thanks.

callebridholm · 2021-06-17T18:43:02Z

@callebridholm hi, I've tried your newbie instructions and somewhat got things going but nothing ends up showing in Home Assistant or in Node-Red Deconz integration. I seem to fail to follow your "Select windows covering cluster of your device, double click on 0x0008 (current position)."

Is this what you mean? In select windows, it's actually the 0000 box I need to click on? If so, I did try to "write" the interval times etc but it would end up in error.
I've tried this many times, restarted, even updated firmware and it seems it reacts (if I press the physical button, the little node blinks blue)

Apologies, this interface is very scary for a casual user. Thanks.

Last months when I added some of these sensors it work perfect automatically and you can now see the sensors in Phoscon UI

slurpey · 2021-06-17T20:24:32Z

Hmmm. I'll give it another try tomorrow. I have 40 various devices and I only got it to show in the deconz after pairing in phoscon (while it said phoscon couldn't pair). Strange

slurpey · 2021-06-18T08:16:25Z

I confirm, this works now in Phoscon. Thanks @callebridholm
version: 2.11.05 / 5/9/2021
Firmware: 26660700

If using from HASSIO addon - in Home Assistant, go to Supervisor > Deconz
Look at top of page if you need to upgrade. This started working after I upgraded to version: 6.9.0

SwoopX mentioned this issue Jan 28, 2020

Integration of various devices #2375

Merged

Sjonnie2018 mentioned this issue Jan 29, 2020

New device support request: Heiman HS1SA-N Smoke sensor #2373

Closed

SwoopX mentioned this issue Feb 4, 2020

light sensor not pairing #2412

Closed

tjaena mentioned this issue Feb 11, 2020

Add support for Xiaomi Mijia Smart Light Sensor (GZCGQ01LM) #2300

Closed

Smanar mentioned this issue Feb 27, 2020

Zigbee 3.0 with Conbee 1/Conbee 2 #2057

Closed

This was referenced Feb 29, 2020

deConz GUI over remote PC #800

Closed

Remote access to deConz GUI #2512

Closed

sedony23 mentioned this issue Apr 29, 2020

Support for the Xiaomi Mijia Smart Light Sensor Zigbee 3.0? ebaauw/homebridge-hue#685

Closed

Mimiix closed this as completed Jun 6, 2020

pattyland mentioned this issue Aug 3, 2020

Support for Xiaomi Mijia Zigbee 3.0 Smart Home Light Sensor dresden-elektronik/phoscon-app-beta#166

Closed

This was referenced Mar 24, 2021

Xiaomi Mijia Zigbee 3.0 Smart Home Light Sensor parring fails in phoscon dresden-elektronik/phoscon-app-beta#361

Closed

Mi Light Detection Sensor #4648

Closed

New device support request: Xiaomi Mijia Zigbee 3.0 Smart Home Light Sensor #2380

New device support request: Xiaomi Mijia Zigbee 3.0 Smart Home Light Sensor #2380

Comments

sumo-89 commented Jan 26, 2020

SwoopX commented Jan 26, 2020

sumo-89 commented Jan 26, 2020

SwoopX commented Jan 26, 2020

sumo-89 commented Jan 27, 2020

SwoopX commented Jan 27, 2020

davidclancy commented Feb 4, 2020

SwoopX commented Feb 4, 2020

LukasA83 commented Feb 17, 2020 • edited Loading

davidclancy commented Feb 17, 2020 via email

SwoopX commented Feb 18, 2020 • edited Loading

davidclancy commented Feb 18, 2020

eserero commented Feb 18, 2020

SwoopX commented Feb 19, 2020 • edited Loading

LukasA83 commented Feb 20, 2020

SwoopX commented Feb 20, 2020

davidclancy commented Feb 20, 2020

SwoopX commented Feb 20, 2020 • edited Loading

zladukas commented Feb 26, 2020

SwoopX commented Feb 26, 2020

davidclancy commented Feb 28, 2020 via email

SwoopX commented Feb 28, 2020

drthanwho commented Mar 21, 2020

jensflorian commented Apr 21, 2020

drthanwho commented Apr 30, 2020

callebridholm commented May 31, 2020 • edited Loading

drthanwho commented May 31, 2020

SwoopX commented May 31, 2020

callebridholm commented Jun 1, 2020

SwoopX commented Jun 1, 2020

callebridholm commented Jun 1, 2020

SwoopX commented Jun 2, 2020

callebridholm commented Jun 3, 2020

SwoopX commented Jun 3, 2020

callebridholm commented Jun 5, 2020

SwoopX commented Jun 5, 2020

Mimiix commented Jun 6, 2020

slurpey commented Jun 17, 2021 • edited Loading

callebridholm commented Jun 17, 2021

slurpey commented Jun 17, 2021

slurpey commented Jun 18, 2021

LukasA83 commented Feb 17, 2020 •

edited

Loading

SwoopX commented Feb 18, 2020 •

edited

Loading

SwoopX commented Feb 19, 2020 •

edited

Loading

SwoopX commented Feb 20, 2020 •

edited

Loading

callebridholm commented May 31, 2020 •

edited

Loading

slurpey commented Jun 17, 2021 •

edited

Loading