[Device Support Request] Xiaomi Mija ZB3.0 smart plug ZNCZ04LM (lumi.plug.mmeu01) #2583

SwoopX · 2020-03-13T21:37:57Z

Endpoint 15:

Endpoint 16:

SwoopX · 2020-03-13T22:15:53Z

The attributes from cluster FCC0:

ZigBee Cluster Library Frame, Mfr: Unknown (0x115f), Command: Discover Attributes Response, Seq: 157
    Frame Control Field: Profile-wide (0x1c)
        .... ..00 = Frame Type: Profile-wide (0x0)
        .... .1.. = Manufacturer Specific: True
        .... 1... = Direction: Server to Client
        ...1 .... = Disable Default Response: True
    Manufacturer Code: Unknown (0x115f)
    Sequence Number: 157
    Command: Discover Attributes Response (0x0d)
    Attribute Status Record
        Attribute: 0x00f3
        Data Type: 8-Bit Unsigned Integer (0x20)
    Attribute Status Record
        Attribute: 0x00f5
        Data Type: 32-Bit Unsigned Integer (0x23)
    Attribute Status Record
        Attribute: 0x00f6
        Data Type: 16-Bit Unsigned Integer (0x21)
    Attribute Status Record
        Attribute: 0x00fa
        Data Type: Boolean (0x10)
    Attribute Status Record
        Attribute: 0x00fc
        Data Type: Boolean (0x10)
    Attribute Status Record
        Attribute: 0x00fe
        Data Type: Character String (0x42)
    Attribute Status Record
        Attribute: 0x00ff
        Data Type: Octet String (0x41)
    Attribute Status Record
        Attribute: 0x0100
        Data Type: 8-Bit Unsigned Integer (0x20)
    Attribute Status Record
        Attribute: 0x0200
        Data Type: 8-Bit Unsigned Integer (0x20)
    Attribute Status Record
        Attribute: 0x0201
        Data Type: Boolean (0x10)
    Attribute Status Record
        Attribute: 0x0202
        Data Type: Boolean (0x10)
    Attribute Status Record
        Attribute: 0x0203
        Data Type: Boolean (0x10)
    Attribute Status Record
        Attribute: 0x0204
        Data Type: Single Precision Floating Point (0x39)
    Attribute Status Record
        Attribute: 0x0205
        Data Type: 8-Bit Unsigned Integer (0x20)
    Attribute Status Record
        Attribute: 0x0206
        Data Type: Single Precision Floating Point (0x39)
    Attribute Status Record
        Attribute: 0x0207
        Data Type: Boolean (0x10)
    Attribute Status Record
        Attribute: 0x020b
        Data Type: Single Precision Floating Point (0x39)
    Attribute Status Record
        Attribute: 0xf000
        Data Type: 8-Bit Unsigned Integer (0x20)
    Attribute Status Record
        Attribute: 0xfffd
        Data Type: 16-Bit Unsigned Integer (0x21)

0000   1c 5f 11 9d 0d 01 f3 00 20 f5 00 23 f6 00 21 fa   ._...... ..#..!.
0010   00 10 fc 00 10 fe 00 42 ff 00 41 00 01 20 00 02   .......B..A.. ..
0020   20 01 02 10 02 02 10 03 02 10 04 02 39 05 02 20    ...........9.. 
0030   06 02 39 07 02 10 0b 02 39 00 f0 20 fd ff 21      ..9.....9.. ..!

And some investigation to find out what they are for:

<attribute id="0x00f3" name="Unknown" type="u8" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0x00f5" name="Unknown" type="u32" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0x00f6" name="Reporting Interval" type="u16" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0x00fa" name="Unknown" type="bool" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0x00fc" name="Unknown" type="bool" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0x00fe" name="Serial Number" type="cstring" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0x00ff" name="Unknown (write only)" type="ostring" mfcode="0x115f" access="w" required="m"> </attribute>
<attribute id="0x0100" name="Unknown" type="u8" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0x0200" name="Unknown" type="u8" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0x0201" name="Restore Power on Outage" type="bool" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0x0202" name="Auto-off after 20m below 2W" type="bool" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0x0203" name="Device LED off" type="bool" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0x0204" name="Unknown" type="float" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0x0205" name="Unknown" type="u8" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0x0206" name="Unknown" type="float" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0x0207" name="Consumer connected" type="bool" mfcode="0x115f" access="r" required="m"> </attribute>
<attribute id="0x020b" name="Max. Load exceeded at (in W)???" type="float" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0xf000" name="Unknown" type="u8" mfcode="0x115f" access="rw" required="m"> </attribute>
<attribute id="0xfffd" name="Unknown" type="u16" mfcode="0x115f" access="rw" required="m"> </attribute>

SwoopX · 2020-03-14T00:14:28Z

Decoding of manufacturer specific attribute reporting (attribute 0x00F7. cluster FCC0, Endpoint 1, first byte is always the length)

ZigBee Cluster Library Frame, Mfr: Unknown (0x115f), Command: Report Attributes, Seq: 45
    Frame Control Field: Profile-wide (0x1c)
        .... ..00 = Frame Type: Profile-wide (0x0)
        .... .1.. = Manufacturer Specific: True
        .... 1... = Direction: Server to Client
        ...1 .... = Disable Default Response: True
    Manufacturer Code: Unknown (0x115f)
    Sequence Number: 45
    Command: Report Attributes (0x0a)
    Attribute Field, Octets: 64:10:00:03:28:17:98:39:00:00:00:00:95:39:1a:a4:…
        Attribute: 0x00f7
        Data Type: Octet String (0x41)
        Octet String: 64:10:00:03:28:17:98:39:00:00:00:00:95:39:1a:a4:…

0000   3d 64 10 00 03 28 17 98 39 00 00 00 00 95 39 1a
0010   a4 ec 3d 96 39 00 60 0b 45 97 39 00 00 00 00 05
0020   21 02 00 9a 20 00 08 21 16 01 07 27 00 00 00 00
0030   00 00 00 00 09 21 00 01 0b 20 00 9b 10 01

03 28 18				(Zcl8BitInt)     Device temperature
05 21 02 00				(Zcl16BitUint)   Unknown
07 27 00 00 00 00 00 00 00 00		(Zcl64BitUint)   Unknown
08 21 16 01				(Zcl16BitUint)   Unknown
09 21 00 01				(Zcl16BitUint)   Unknown
0b 20 00				(Zcl8BitUint)    Unknown
64 10 01				(ZclBoolean)     on/off
95 39 e0 7c e5 3d			(ZclSingleFloat) Consumption
96 39 00 60 0b 45			(ZclSingleFloat) Voltage
97 39 49 5f 53 41			(ZclSingleFloat) Current
98 39 44 8b 3c 40			(ZclSingleFloat) Power
9a 20 00				(Zcl8BitUint)    Unknown
9b 10 01				(ZclBoolean)     Unknown

Smlooc · 2020-03-14T14:13:42Z

How to read ENERGY and POWER(endpoint 15 and 16) from API ?
Are only visible from GUI?

SwoopX · 2020-03-14T18:28:38Z

As of now, you can't since the device is not supported yet. However, I'm almost done and I just need to amend some data types...

Kristian8606 · 2020-03-24T11:22:22Z

I have lumi.plug.mmeu01 I was disappointed to find that consumption and history were not working, my question soon be included and maintained?

SwoopX · 2020-03-24T14:33:54Z

I have an open pull request pending for the device. Locally, with the changes I made, it works perfectly from a deconz perspective. How middleware handles the sensor and data is a different question not to be discussed here then.

Once integrated, you will see a consumption and a power sensor, providing corresponding data. If you cannot wait, you may want to compile the version from my repo manually.

Kristian8606 · 2020-03-24T17:48:31Z

Sorry for the stupid question but can you help me because I don't know how to install your code, some instruction would be helpful

SwoopX · 2020-03-24T19:43:04Z

Have a look at the readme of the repo, the steps and requirements are mentioned there. To be abe to get the deconz dev package, check out phoscon.de to see how to add the deconz repository.

For compilation, there might be further packages required which you need to install first.

Kristian8606 · 2020-03-24T19:50:14Z

if i wait will it be integrated into the next official update?

SwoopX · 2020-03-24T21:01:33Z

That's my current assumption.

Kristian8606 · 2020-04-05T10:37:21Z

One thing I noticed quite by accident is that when I unplugged the device and plugged it back in, eve showed historical data.

SwoopX · 2020-04-05T11:46:22Z

Not sure what exactly you mean. Can you elaborate a bit? Consumption is historical data, power is not.

Kristian8606 · 2020-04-05T12:01:18Z

Sorry about my bad English. when I plug the plug into the mains and then plug in the heater in the app it records neither amps nor power consumption. After 15 minutes I unplug it and plug it back in and eve reads the story.

Kristian8606 · 2020-04-05T12:08:47Z

The thought is that the unit show nothing, amper nor power consumption, but still records a story only when I turn it off and plug it in the electrical

ebaauw · 2020-04-05T12:13:32Z

The Simple Metering cluster, 0x0702, exposes life-time consumption (Current Summation Delivered attribute, 0x0000), and current power (Instantaneous Demand attribute, 0x0400). The REST API plugin exposes these as state.consumption and state.power in a ZHAConsumption /sensors resource.

The Electrical Measurement cluster, 0x0B04, exposes current power (Active Power attribute, 0x050B). The REST API plugin exposes this as state.power in a ZHAPower /sensors resource.

The wired Xiaomi switches I've seen report power through the Analog Input cluster on the lower endpoint, and consumption through the Analog Input cluster on the higher endpoint. The lower endpoint should be exposed as ZHAPower, the higher as ZHAConsumption.

Eve needs both consumption and power to show history, so Homebridge Hue will compute any missing value from the other. For devices with a ZHAConsumption resource, Homebridge Hue creates the history based on state.consumption. For devices with only a ZHAPower resource, Homebridge Hue creates history based on state.power, approximating consumption by applying power over time.

Kristian8606 · 2020-04-05T12:20:59Z

Thanks for the explanation. Also i would like to know where in the app i can adjust the price for kwh.

SwoopX · 2020-04-05T12:22:39Z

@Kristian8606 that was not really a language problem ;) The code just got merged.

@ebaauw Very true. I've provided an updated code to handle the analog input clusters and consumption and power values are exposed now. Works like a charm locally.

ebaauw · 2020-04-05T12:48:25Z

Also i would like to know where in the app i can adjust the price for kwh.

Settings | General | Energy Cost

Kristian8606 · 2020-04-09T15:16:39Z

@SwoopX would you view this problem about Xiaomi lumi.plug.mmeu01

ebaauw/homebridge-hue#664

SwoopX · 2020-04-09T19:27:17Z

Thanks. There's indeed some more work required to expose V and A as well. I'll check it out.

SwoopX · 2020-04-09T21:32:00Z

Updated it. If you want, you can compile my repo to test it.

Kristian8606 · 2020-04-10T11:52:22Z

Great after work, I'll test it immediately.

Kristian8606 · 2020-04-11T07:14:42Z

Thanks for the lightning reaction! Now this outlet is working as expected. I'll watch it for bugs and report if any. Once again thank you.

thikade · 2020-07-27T09:13:18Z

@Kristian8606
Hi,
researching a phoscon issue I stumbled over your beautiful app screenshots displaying power metering stats.
I was wondering what the app name / system are you using for that is?
Thanks, Thomas

Link to your screenshot comment: #2583 (comment)

ebaauw · 2020-07-27T17:25:13Z

That’s the Eve app for Apple’s HomeKit, see https://www.evehome.com/en/eve-app. Use Homebridge and Homebridge Hue to expose the devices connected to deCONZ to HomeKit, see https://github.com/ebaauw/homebridge-hue.

thikade · 2020-07-27T22:51:35Z

Thanks, Erik!

…

On Mon, Jul 27, 2020 at 7:25 PM Erik Baauw ***@***.***> wrote: That’s the Eve app for Apple’s HomeKit, see https://www.evehome.com/en/eve-app. Use Homebridge and Homebridge Hue to expose the devices connected to deCONZ to HomeKit, see https://github.com/ebaauw/homebridge-hue. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2583 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACDHIHYOLOHHNVYE5EJEGOLR5W2ATANCNFSM4LHM3MOA> .

archiespb · 2020-12-16T18:05:42Z

Hi!

There is a bit of a problem with my ZNCZ04LM.
It works fine but after raspberry pi reboot phoscon/deconz (and home assistant) cannot control smart plug until I press button on it.

Is there any solution to this?

leonardpitzu · 2021-01-08T19:37:00Z

Exactly the same for me

net1957 · 2021-01-08T21:05:19Z

same for me. I use deconz/phoscon ConBeeII with Jeedom on Raspberry 4

version 2.07.01
firmware 26680700

as they are new, I don't know if this was working in previous releases.

information for the plugs (all are on same sw version):
{
"8": {
"etag": "0cc603de166f4750f23e32d2adf62130",
"hascolor": false,
"lastannounced": "2020-12-20T11:57:27Z",
"lastseen": "2021-01-08T19:45Z",
"manufacturername": "LUMI",
"modelid": "lumi.plug.mmeu01",
"name": "Prise_4",
"state": {
"alert": "none",
"on": true,
"reachable": true
},
"swversion": "09-06-2019",
"type": "Smart plug",
"uniqueid": "04:cf:8c:df:3c:86:77:ce-01"
}, ....

sieren · 2021-01-08T23:22:52Z

Sadly, it's always been like that. I vaguely recall there were some discussions around it but nobody knew a good approach on how to fix this.

bcutter · 2021-01-19T21:12:02Z

What is the right way to pair this device using Phoscon? I only get the switch entity, no power consumption measurements at all (paired as light)...

#4238

(using latest stable firmware 26660700, Version 2.07.01 / 8.12.2020)

bcutter · 2021-01-21T08:09:46Z

Can someone please explain what is the right way to pair this smart plug using Phoscon?

Pairing as light it only provides the power switch, no other sensors (power, consumption, temperature etc. missing https://www.zigbee2mqtt.io/devices/ZNCZ04LM.html#xiaomi-zncz04lm / https://zigbee.blakadder.com/Xiaomi_ZNCZ04LM.html) :-(

@jsconstantelos @kt666 @ebaauw @SwoopX

archiespb · 2021-01-21T08:53:22Z

Try unpair and pair again. Sometimes my devices have the same bug.

net1957 · 2021-01-21T09:07:02Z

some time it need some hours to get all informations

bcutter · 2021-01-21T09:08:25Z

So it doesn't matter how to pair it or is using the search for lights definitely the right way?

archiespb · 2021-01-21T09:10:57Z

Yes, it is light from Phoscon view point.

net1957 · 2021-01-21T09:15:00Z

on deconz it look like:

and in jeedom the information is
{
"8": {
"etag": "ce3f5965ecfeda6fda07f3d0e8c5eef8",
"hascolor": false,
"lastannounced": "2021-01-16T14:36:19Z",
"lastseen": "2021-01-17T22:09Z",
"manufacturername": "LUMI",
"modelid": "lumi.plug.mmeu01",
"name": "Prise_4",
"state": {
"alert": "none",
"on": false,
"reachable": true
},
"swversion": "09-06-2019",
"type": "Smart plug",
"uniqueid": "04:cf:8c:df:3c:86:77:ce-01"
},
"54": {
"config": {
"on": true,
"reachable": true,
"temperature": 2000
},
"ep": 21,
"etag": "d3daec152e685926d3f0d61288745ff2",
"lastseen": "2021-01-21T09:11Z",
"manufacturername": "LUMI",
"modelid": "lumi.plug.mmeu01",
"name": "Power 54",
"state": {
"current": 0,
"lastupdated": "2021-01-21T09:11:06.952",
"power": 0,
"voltage": 236
},
"swversion": "09-06-2019",
"type": "ZHAPower",
"uniqueid": "04:cf:8c:df:3c:86:77:ce-15-000c"
},
"92": {
"config": {
"on": true,
"reachable": true,
"temperature": 2000
},
"ep": 1,
"etag": "3a182b8cd83b746c86237b21a29a1394",
"lastseen": "2021-01-21T09:11Z",
"manufacturername": "LUMI",
"modelid": "lumi.plug.mmeu01",
"name": "Consumption 92",
"state": {
"consumption": 5588,
"lastupdated": "2021-01-21T09:11:31.369",
"power": 0
},
"swversion": "09-06-2019",
"type": "ZHAConsumption",
"uniqueid": "04:cf:8c:df:3c:86:77:ce-01-0702"
},
"93": {
"config": {
"on": true,
"reachable": true,
"temperature": 2000
},
"ep": 1,
"etag": "1aee1ac42531e4bb4b0e9e0c92bc5ff5",
"lastseen": "2021-01-21T09:11Z",
"manufacturername": "LUMI",
"modelid": "lumi.plug.mmeu01",
"name": "Power 93",
"state": {
"current": 0,
"lastupdated": "2021-01-21T09:11:32.263",
"power": 0,
"voltage": 236
},
"swversion": "09-06-2019",
"type": "ZHAPower",
"uniqueid": "04:cf:8c:df:3c:86:77:ce-01-0b04"
},
"94": {
"config": {
"on": true,
"reachable": true,
"temperature": 2000
},
"ep": 22,
"etag": "d3daec152e685926d3f0d61288745ff2",
"lastseen": "2021-01-21T09:11Z",
"manufacturername": "LUMI",
"modelid": "lumi.plug.mmeu01",
"name": "Consumption 94",
"state": {
"consumption": 5588,
"lastupdated": "2021-01-21T09:11:06.952"
},
"swversion": "09-06-2019",
"type": "ZHAConsumption",
"uniqueid": "04:cf:8c:df:3c:86:77:ce-16-000c"
}
}

framesetter99 · 2021-01-21T21:25:37Z

Actually had the same problem. Unwrapped from box, paired and only the light entity showed up with the rest API.
Repaired it back then, same issue.
One day later plugged in the unit again, added an active consumer (my laptop), repaired and I got the sensor.

It might be that having it on and having an actual consumer while pairing did the trick.
So just try to get it with the API, check if the additional sensors show up and repair if needed.

bcutter · 2021-01-21T22:11:20Z

@framesetter99 Thanks for that great advice, I will test this at the next opportunity. Sounds quite promising! ✌🏼

bcutter · 2021-01-23T14:41:45Z

I tested another two hours (!) and paired several times.

With active consumer connected
Tried to pair as sensor (it showed a green banner and it was added - as light)
Completely restarted deCONZ

This is the best I could get so far - and it´s just CRAP, still almost useless:

Update:

Updated summary:

Total consumption (kWh) only appears every few seconds, being "not available" most of the time
Power and current consumption entities (3 times?!) are bullshit - they don´t change depending on actual consumption
--> Update: Current consumption seems to work now (it changes depending on the power usage)
I see no option to disable the LED according to https://www.zigbee2mqtt.io/devices/ZNCZ04LM.html#led_disabled_night-binary
Information not being available (not at all or not reliably (1)):

Total power consumption (important)
Temperature (nice)
Voltage (I don´t care)
Link quality (I don´t care)
Not able to set LED state

+++ Can anyone who managed to successfully pair and integrate this device with deCONZ please post what it SHOULD offer when working fine? +++
@sieren @archiespb @net1957 @framesetter99

I experience some kind of strong limitations and multiple entities for current consumption as shown.

As a reference - this is what I expect (another user with a ZNCZ0**2**LM) not using deCONZ:

bcutter · 2021-02-07T13:47:20Z

Still no progress. Is it me or - sorry for that kind of formulation - is the deCONZ integration of lumi.plug.mmeu01 just crap? I mean I meanwhile spent 5 hours to get two of those devices to work and it´s still impossible (see #4238 (comment)).

It really is horrible. What else can I try? Any ideas (@SwoopX)?

bcutter · 2021-02-07T17:12:52Z

The sensor as such presented above looks perfectly fine. In it's default settings, you only get a consumption update every 10 mins. If the value doesn't change, then there's no update.

I have a 66 W consumer attached to the plug for one hour. Total consumption entity does not change (anymore):

deCONZ 0702 Simple metering cluster contains:

So... what about that 10 minutes update interval?!?

poughkeepsee · 2022-04-12T19:00:12Z

Actually had the same problem. Unwrapped from box, paired and only the light entity showed up with the rest API. Repaired it back then, same issue. One day later plugged in the unit again, added an active consumer (my laptop), repaired and I got the sensor.

It might be that having it on and having an actual consumer while pairing did the trick. So just try to get it with the API, check if the additional sensors show up and repair if needed.

This did the trick for me. Steps the reproduce:

Reset the plug (press the on/off button for 5 seconds until the led flashes blue and red)
Remove the plug from deconz
Unplug from socket and plug again
Press on/off for pair (light flashes blue)
Press on again and have any device connected to the plug - THIS DID THE TRICK for me after trying 10 times with no device. Plug needs to be on and pulling power to any connected device, I just used my laptop charger
Search (as light) in deconz
Hopefully FCC0 is now showing Lumi specific and not unknown

This is anecdotal evidence, worked for me but I really hope it works for anyone else.

Smanar · 2022-04-13T10:26:50Z

Ha yes, not stupid, make the device make report with the problematic cluster using it, for deconz detect it better.

SwoopX changed the title ~~[Device Support Request] Xiaomi Mija ZB3.0 smart plug lumi.plug.mmeu01~~ [Device Support Request] Xiaomi Mija ZB3.0 smart plug ZNCZ04LM (lumi.plug.mmeu01) Mar 13, 2020

This was referenced Mar 14, 2020

Device updates #2572

Merged

Unknown entity when using Xiaomi Smart Plug #2533

Closed

ebaauw mentioned this issue Mar 24, 2020

Xiaomi smart plugs ebaauw/homebridge-hue#664

Closed

SwoopX mentioned this issue Apr 4, 2020

[Device Support Request] Mi Smart Plug (add Wattmeter) #2653

Closed

SwoopX closed this as completed Apr 5, 2020

SwoopX mentioned this issue Apr 10, 2020

Enhancements and addition of various devices #2668

Merged

Draluak mentioned this issue Oct 6, 2020

[Device Support Request] Total Consumption Xiaomi Plug EU [lumi.plug.mmeu01] zigpy/zha-device-handlers#516

Closed

digitalsteezdesign mentioned this issue Oct 21, 2020

Smart Socket ZNCZ04LM - Integrate Power Outage - Restore previous state AlexxIT/XiaomiGateway3#76

Closed

dbanyos mentioned this issue Nov 18, 2020

ZHA - lumi.plug.mmeu01 not showing power monitor measures home-assistant/core#42840

Closed

KiwiHC16 mentioned this issue Dec 10, 2020

Support de la prise EU Xiaomi ZNCZ04LM (lumi.plug.mmeu01) KiwiHC16/Abeille#1344

Closed

This was referenced Jan 8, 2021

ZNCZ04LM (lumi.plug.mmeu01) fail after deconz reboot #4138

Closed

ZNCZ04LM (lumi.plug.mmeu01) fail after deconz reboot #4139

Closed

bcutter mentioned this issue Jan 19, 2021

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

Closed

SwoopX mentioned this issue Feb 8, 2021

Fix for Xiaomi lightnodes not getting a proper rx() #4371

Merged

alextud mentioned this issue Mar 4, 2021

Aqara Smart Wall Plug: Power measurement #2302

Closed

[Device Support Request] Xiaomi Mija ZB3.0 smart plug ZNCZ04LM (lumi.plug.mmeu01) #2583

[Device Support Request] Xiaomi Mija ZB3.0 smart plug ZNCZ04LM (lumi.plug.mmeu01) #2583

Comments

SwoopX commented Mar 13, 2020 • edited

SwoopX commented Mar 13, 2020 • edited

SwoopX commented Mar 14, 2020 • edited

Smlooc commented Mar 14, 2020 • edited

SwoopX commented Mar 14, 2020

Kristian8606 commented Mar 24, 2020

SwoopX commented Mar 24, 2020 • edited

Kristian8606 commented Mar 24, 2020

SwoopX commented Mar 24, 2020

Kristian8606 commented Mar 24, 2020

SwoopX commented Mar 24, 2020

Kristian8606 commented Apr 5, 2020 • edited

SwoopX commented Apr 5, 2020

Kristian8606 commented Apr 5, 2020

Kristian8606 commented Apr 5, 2020

ebaauw commented Apr 5, 2020 • edited

Kristian8606 commented Apr 5, 2020

SwoopX commented Apr 5, 2020

ebaauw commented Apr 5, 2020

Kristian8606 commented Apr 9, 2020

SwoopX commented Apr 9, 2020

SwoopX commented Apr 9, 2020

Kristian8606 commented Apr 10, 2020

Kristian8606 commented Apr 11, 2020

thikade commented Jul 27, 2020

ebaauw commented Jul 27, 2020

thikade commented Jul 27, 2020 via email

archiespb commented Dec 16, 2020

leonardpitzu commented Jan 8, 2021

net1957 commented Jan 8, 2021

sieren commented Jan 8, 2021

bcutter commented Jan 19, 2021 • edited

bcutter commented Jan 21, 2021 • edited

archiespb commented Jan 21, 2021

net1957 commented Jan 21, 2021

bcutter commented Jan 21, 2021

archiespb commented Jan 21, 2021

net1957 commented Jan 21, 2021

framesetter99 commented Jan 21, 2021

bcutter commented Jan 21, 2021

bcutter commented Jan 23, 2021 • edited

bcutter commented Feb 7, 2021 • edited

bcutter commented Feb 7, 2021

poughkeepsee commented Apr 12, 2022

Smanar commented Apr 13, 2022 • edited

SwoopX commented Mar 13, 2020 •

edited

SwoopX commented Mar 13, 2020 •

edited

SwoopX commented Mar 14, 2020 •

edited

Smlooc commented Mar 14, 2020 •

edited

SwoopX commented Mar 24, 2020 •

edited

Kristian8606 commented Apr 5, 2020 •

edited

ebaauw commented Apr 5, 2020 •

edited

bcutter commented Jan 19, 2021 •

edited

bcutter commented Jan 21, 2021 •

edited

bcutter commented Jan 23, 2021 •

edited

bcutter commented Feb 7, 2021 •

edited

Smanar commented Apr 13, 2022 •

edited