Visonic MCT-340 E Door Sensor #66

oakbrad · 2018-05-26T20:47:39Z

I have a couple of these
https://www.amazon.com/Visonic-MCT-340-Wireless-Samsung-SmartThings/dp/B06XDJ3KYC

When trying to pair:

6 20:25:02 INFO New device joined the network!
6 20:25:26 ERROR Cannot get the Node Descriptor of the Device: 0x000d6f000af05332 (Error: Timed out after 10000 ms)
: true [ { func: [Function: func], ieeeAddr: '0x000d6f000af05332' } ]
in joinqueue
6 20:26:46 ERROR Cannot get the Node Descriptor of the Device: 0x000d6f000af05332 (Error: Timed out after 10000 ms)
6 20:27:06 ERROR Cannot get the Node Descriptor of the Device: 0x000d6f000af05332 (Error: Timed out after 10000 ms)
: true []
``

The text was updated successfully, but these errors were encountered:

Koenkk · 2018-05-27T11:30:08Z

Did you factory reset the device?

oakbrad · 2018-05-27T22:31:17Z

I've tried resetting it many times, it will start the pairing process over again but gives the same error.

Koenkk · 2018-05-28T16:29:06Z

I get this error when I keep pressing the reset button on Xiaomi Aqara devices after holding the reset button for 5 seconds. Can you check different combinations of button hold/press when pairing?

oakbrad · 2018-06-03T17:51:39Z

I will keep trying, the documentation I have for it says hold down for 2 seconds to reset but I am having no luck - I have a few of these and can't get any of them to pair.

ciotlosm · 2018-06-03T18:06:34Z

@oakbrad you can try #90 details to see if it helps on how things should look when pairing difficult devices.

oakbrad · 2018-06-03T18:39:10Z

I think I got one to connect. It appears the magic combo might be fresh zigbee2mqtt start, and holding down the button while inserting the battery.

I am still getting the time out error though

 18:34:19 INFO Connecting with device, please wait...
 18:34:19 INFO New device joined the network!
 18:34:19 INFO New device with address 0x000d6f000b02ceca connected!
 18:34:19 INFO MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"device_connected","message":"0x000d6f000b02ceca"}'
: false []
: true []
 18:34:43 ERROR Cannot get the Node Descriptor of the Device: 0x000d6f000b02ceca (Error: Timed out after 10000 ms)
in joinqueue
: true []
 18:35:23 ERROR Cannot get the Node Descriptor of the Device: 0x000d6f000b02ceca (Error: Timed out after 10000 ms)

It does end up in my configuration.yaml

  '0x000d6f000b02ceca':
    friendly_name: '0x000d6f000b02ceca'
    retain: false

And the pairing light on the device stops blinking.

Let me see if I can replicate pairing with another one..

oakbrad · 2018-06-03T18:47:30Z

Hold the button for 2 seconds while inserting the battery is definitely the pairing mechanism. Got 3/4 devices paired all with the same result:

 18:44:36 INFO New device joined the network!
 18:44:36 INFO New device with address 0x000d6f000b3e43d1 connected!
 18:44:36 INFO MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"device_connected","message":"0x000d6f000b3e43d1"}'
: false []
: true []
 18:45:03 ERROR Cannot get the Node Descriptor of the Device: 0x000d6f000b3e43d1 (Error: Timed out after 10000 ms)

All of them in the YAML

  '0x000d6f000b02ceca':
    friendly_name: '0x000d6f000b02ceca'
    retain: false
  '0x000d6f000af05332':
    friendly_name: '0x000d6f000af05332'
    retain: false
  '0x000d6f000b3e43d1':
    friendly_name: '0x000d6f000b3e43d1'
    retain: false

ciotlosm · 2018-06-03T18:59:44Z

@oakbrad try to document your setup for wiki to help other users with similar devices.

ciotlosm · 2018-06-15T05:29:20Z

@oakbrad Are you happy to close this issue?

To get more information when trying to pair you can always use the documentation.

I had similar problems when trying to pair a cube that was previously paired and the solution was to start over by removing batter, reset it and start over. Always had to press link button every second after spinlock to make sure it sends needed information.

oakbrad · 2018-06-18T18:31:43Z

@ciotlosm I got the 4 of them paired, they appear in my configuration.yaml as I posted above, but they do not actually do anything or initialize as devices. All I see in the logs related to them is timeout errors.

Not sure where to go from here?

ciotlosm · 2018-06-19T06:37:20Z

@oakbrad can you try and start in DEBUG mode? DEBUG=* npm start
Use hastebin to post results.

ciotlosm · 2018-06-29T18:39:31Z

@oakbrad when pairing if you get timeout it's usually because you didn't keep pressing a button or something to keep them sending zigbee packages to make them complete pairing.

Koenkk · 2018-06-29T19:13:13Z

Can you post the database.db entry of this device?

stale · 2018-08-28T19:25:29Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

ajayjohn · 2018-09-09T03:03:37Z

@oakbrad @Koenkk @ciotlosm
Was this issue ever resolved? I tried to use the same device and encountered identical errors to what has been reported here.

Is there anything I can provide here, to help troubleshoot the issue? I tried to open the database.db file using an SQLite browser, but it asks me for an SQLCipher encryption password.
Given below are by logs from the Hassio Addon I use.

[Info] Configuration written to /share/zigbee2mqtt/configuration.yaml
[2018-09-08T21:59:14.389Z] PM2 log: Launching in no daemon mode
[2018-09-08T21:59:14.459Z] PM2 log: Starting execution sequence in -fork mode- for app name:npm id:0
[2018-09-08T21:59:14.468Z] PM2 log: App name:npm id:0 online
> [email protected] start /app
> node index.js
  zigbee2mqtt:info 2018-9-8 21:59:15 Logging to directory: '/share/zigbee2mqtt/log/2018-09-08.21:59:15'
  zigbee2mqtt:info 2018-9-8 21:59:15 Starting zigbee2mqtt version 0.1.3 (commit #c05b70b)
  zigbee2mqtt:info 2018-9-8 21:59:15 Starting zigbee-shepherd
  zigbee2mqtt:info 2018-9-8 21:59:15 zigbee-shepherd started
  zigbee2mqtt:info 2018-9-8 21:59:15 Coordinator firmware version: '20180507'
  zigbee2mqtt:info 2018-9-8 21:59:15 Currently 2 devices are joined:
  zigbee2mqtt:info 2018-9-8 21:59:15 0x8418260000037707 (0x8418260000037707): 73740 - Sylvania LIGHTIFY LED adjustable white BR30 (Router)
  zigbee2mqtt:info 2018-9-8 21:59:15 0x00158d0002136055 (0x00158d0002136055): WXKG11LM - Xiaomi Aqara wireless switch (EndDevice)
  zigbee2mqtt:warn 2018-9-8 21:59:15 `permit_join` set to  `true` in configuration.yaml.
  zigbee2mqtt:warn 2018-9-8 21:59:15 Allowing new devices to join.
  zigbee2mqtt:warn 2018-9-8 21:59:15 Set `permit_join` to `false` once you joined all devices.
  zigbee2mqtt:info 2018-9-8 21:59:15 Zigbee: allowing new devices to join.
  zigbee2mqtt:info 2018-9-8 21:59:15 Connecting to MQTT server at mqtt://homeassistant
  zigbee2mqtt:info 2018-9-8 21:59:15 zigbee-shepherd ready
  zigbee2mqtt:info 2018-9-8 21:59:15 Connected to MQTT server
  zigbee2mqtt:info 2018-9-8 21:59:15 MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'online'
  zigbee2mqtt:info 2018-9-8 21:59:15 MQTT publish, topic: 'homeassistant/light/0x8418260000037707/light/config', payload: '{"brightness":true,"color_temp":true,"platform":"mqtt_json","command_topic":"zigbee2mqtt/0x8418260000037707/set","state_topic":"zigbee2mqtt/0x8418260000037707","availability_topic":"zigbee2mqtt/bridge/state","name":"0x8418260000037707","unique_id":"0x8418260000037707_light_zigbee2mqtt"}'
  zigbee2mqtt:info 2018-9-8 21:59:15 MQTT publish, topic: 'homeassistant/sensor/0x00158d0002136055/click/config', payload: '{"icon":"mdi:toggle-switch","value_template":"{{ value_json.click }}","json_attributes":["battery","voltage","action","duration"],"force_update":true,"state_topic":"zigbee2mqtt/0x00158d0002136055","availability_topic":"zigbee2mqtt/bridge/state","name":"0x00158d0002136055","unique_id":"0x00158d0002136055_click_zigbee2mqtt"}'
  zigbee2mqtt:info 2018-9-8 21:59:15 MQTT publish, topic: 'zigbee2mqtt/0x8418260000037707', payload: '{"state":"OFF","brightness":255,"color_temp":370}'
  zigbee2mqtt:info 2018-9-8 21:59:15 MQTT publish, topic: 'zigbee2mqtt/0x00158d0002136055', payload: '{"battery":"100.00","voltage":3045,"linkquality":97}'
  zigbee2mqtt:info 2018-9-8 21:55:17 Device incoming...
  zigbee2mqtt:info 2018-9-8 21:55:17 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}'
  zigbee2mqtt:warn 2018-9-8 21:56:01 Message without device!
  zigbee2mqtt:info 2018-9-8 21:56:01 Connecting with device...
  zigbee2mqtt:info 2018-9-8 21:56:01 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
  zigbee2mqtt:info 2018-9-8 21:56:02 Connecting with device...
  zigbee2mqtt:info 2018-9-8 21:56:02 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
  zigbee2mqtt:info 2018-9-8 21:56:03 Connecting with device...
  zigbee2mqtt:info 2018-9-8 21:56:03 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
  zigbee2mqtt:info 2018-9-8 21:56:03 Connecting with device...
  zigbee2mqtt:info 2018-9-8 21:56:03 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
  zigbee2mqtt:info 2018-9-8 21:56:04 Connecting with device...
  zigbee2mqtt:info 2018-9-8 21:56:04 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
  zigbee2mqtt:info 2018-9-8 21:56:04 Connecting with device...
  zigbee2mqtt:info 2018-9-8 21:56:04 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
  zigbee2mqtt:info 2018-9-8 21:56:05 Connecting with device...
  zigbee2mqtt:info 2018-9-8 21:56:05 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
  zigbee2mqtt:info 2018-9-8 21:56:05 Connecting with device...
  zigbee2mqtt:info 2018-9-8 21:56:05 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
  zigbee2mqtt:info 2018-9-8 21:56:05 Device incoming...
  zigbee2mqtt:info 2018-9-8 21:56:05 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}'
  zigbee2mqtt:info 2018-9-8 21:56:05 New device with address 0x000d6f000b11d7bb connected!
  zigbee2mqtt:info 2018-9-8 21:56:05 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"device_connected","message":"0x000d6f000b11d7bb"}'
  zigbee2mqtt:warn 2018-9-8 21:56:09 Message without device!
  zigbee2mqtt:info 2018-9-8 21:56:14 Device incoming...
  zigbee2mqtt:info 2018-9-8 21:56:14 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}'
  zigbee2mqtt:warn 2018-9-8 21:56:17 Message without device!
  zigbee2mqtt:info 2018-9-8 21:56:22 Device incoming...
  zigbee2mqtt:info 2018-9-8 21:56:22 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}'
  zigbee2mqtt:warn 2018-9-8 21:56:25 Message without device!
  zigbee2mqtt:info 2018-9-8 21:56:30 Device incoming...
  zigbee2mqtt:info 2018-9-8 21:56:30 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}'
  zigbee2mqtt:warn 2018-9-8 21:56:33 Message without device!
  zigbee2mqtt:info 2018-9-8 21:56:39 Device incoming...
  zigbee2mqtt:info 2018-9-8 21:56:39 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}'
  zigbee2mqtt:warn 2018-9-8 21:56:41 Message without device!
  zigbee2mqtt:info 2018-9-8 21:56:47 Device incoming...
  zigbee2mqtt:info 2018-9-8 21:56:47 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}'
  zigbee2mqtt:warn 2018-9-8 21:56:50 Message without device!
  zigbee2mqtt:info 2018-9-8 21:56:55 Device incoming...
  zigbee2mqtt:info 2018-9-8 21:56:55 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}'
  zigbee2mqtt:error 2018-9-8 21:57:21 Cannot get the Node Descriptor of the Device: 0x000d6f000b11d7bb (Error: Timed out after 10000 ms)
  zigbee2mqtt:error 2018-9-8 21:57:41 Cannot get the Node Descriptor of the Device: 0x000d6f000b11d7bb (Error: Timed out after 10000 ms)
  zigbee2mqtt:error 2018-9-8 21:58:01 Cannot get the Node Descriptor of the Device: 0x000d6f000b11d7bb (Error: Timed out after 10000 ms)
  zigbee2mqtt:error 2018-9-8 21:58:21 Cannot get the Node Descriptor of the Device: 0x000d6f000b11d7bb (Error: Timed out after 10000 ms)`

Koenkk · 2018-09-10T06:13:31Z

The database.db can be opened with a text editor.

ajayjohn · 2018-09-10T22:08:04Z

@Koenkk Thanks! I checked and it seems this device has not created any db entry yet. All my other successfully paired devices are shown correctly, including the USB coordinator itself.

oakbrad · 2018-09-12T03:37:34Z

Sorry all I never got these working and ended up giving them to a friend.

When I was troubleshooting it I never saw it create a database.db entry either like @ajayjohn said.

ajayjohn · 2018-10-08T23:00:39Z

@Koenkk Just checking to see if you need anything else to debug this issue.
Also, can this issue status be updated to open?

Koenkk · 2018-10-09T09:25:02Z

If it is not in the database.db it has not been paired correctly, what is the current procedure you follow?

ajayjohn · 2018-10-12T06:36:47Z

Procedure

I turn on the 'permit_join' option in the official hassio add-on you have provided
I initiate the pairing sequence on the sensor (MCT-340 E). The sensor is now in pairing mode.
On checking the hassio add-on logs, I find that the device has been detected and the following message keeps repeating every few seconds, in the logs,
'zigbee2mqtt:error 2018-10-12 01:28:40 Cannot get the Node Descriptor of the Device: 0x000d6f000b3b89ae (Error: Timed out after 10000 ms)'
Nothing further appears in the log, related to this device. On checking the configuration.yaml as well as the database.db, this device does not have any entries.
The sensor continues to be in pairing mode and does not show any signs of being successfully paired (based on its LED blinking pattern).

Footnotes
This device is currently supported by native zigbee on HA (bellows). The device is also supported natively by other platforms like SmartThings. Finally, the device and all its details can be viewed in deCONZ too.

Koenkk · 2018-10-15T13:30:20Z

When pairing, could you provide your log when running with DEBUG=* npm start

stale · 2018-12-14T13:41:34Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

starbuck93 · 2019-02-06T17:46:56Z

@Koenkk https://hastebin.com/qezotatuxo.js

everything started up just fine! I let the setup finish outputting a ton of log files and then triggered the MCT-340 and that's the output.

Koenkk · 2019-02-06T18:23:51Z

@starbuck93 updated https://raw.githubusercontent.com/Koenkk/zigbee-shepherd/fix/lib/components/af.js again (made a typo). Please do the same, previous log is what I need :)

starbuck93 · 2019-02-06T18:59:41Z

Here it is! https://hastebin.com/ijehuluwew.js with two triggers of the MCT-340

Koenkk · 2019-02-06T19:13:14Z

@starbuck93 can you post your complete database.db?

starbuck93 · 2019-02-06T19:17:50Z

Here is database.db https://hastebin.com/janipohici.json
with configuration.yaml https://hastebin.com/fomucuceku.js just in case

Koenkk · 2019-02-06T19:49:29Z

In a log which you provided earlier (#66 (comment), https://hastebin.com/obilotorux.json) the MCT-340 E (0x000d6f000b02c95d) had a modelId in database.db. I'm missing this from your latest database.db, probably the pairing did not complete correctly? We first need to have this modelId back before we can continue.

starbuck93 · 2019-02-06T20:00:39Z

It looks like it is in database.db as "id":11 now versus being "id":3 before

Koenkk · 2019-02-06T20:14:29Z

It's is, but it's missing the modelId. When searching the old database.db for MCT-340 you will find it, in the new one not.

starbuck93 · 2019-02-06T20:58:06Z

@Koenkk I'm getting an error, Failed to mount the cieApp, now and I'm unsure why. I finally managed to get the MCT-340 E into pairing mode though so that's good (the mfg's instructions are almost correct, I thought I was doing it the whole time!)

Logs: https://hastebin.com/umaluveked.apache and https://hastebin.com/gufixomaxe.coffeescript

Update 30 minutes later: ignore the above error, I think I got it to work.

Update 2: Got it to pair, here's the logs: https://hastebin.com/uyezivizah.coffeescript (around line 352)
database.db https://hastebin.com/widujojawa.json
configuration.yaml https://hastebin.com/atehepatot.js

I'm not sure if it worked

jjlawren · 2019-02-07T05:35:20Z

@starbuck93 what were the actual steps you took to pair the device if the instructions were incomplete?

Koenkk · 2019-02-07T07:07:50Z

@starbuck93 I still don't see MCT-340 in the database.db, which I did in: (#66 (comment), https://hastebin.com/obilotorux.json) .

Please

Stop zigbee2mqtt
Remove all entries of 0x000d6f000b02c95d from database.db
Start zigbee2mqtt
Pair device
Trigger contact a few times
Post log here

starbuck93 · 2019-02-07T19:35:28Z

@jjlawren The docs say to hold the trigger switch down for 4 seconds while inserting the battery but you have to hold it slightly shorter than that to successfully get it to go into pairing.

@Koenkk I'm working on pairing the device again, it's not working as expected. I'm getting Cannot get the Node Descriptor of the Device errors.

Update: Here's some logs of an attempted pairing. Hastebin is having trouble apparently https://pastebin.com/RfGCWdtd

Update 2: I got it to output the name of the device in the logs, and it appeared to be paired as shown in configuration.yaml and the database, but the red LED is still blinking on the MCT-340 E indicating it is still in pairing mode and the logs reflect that it is still trying to pair. https://ghostbin.com/paste/t73un#L1830

Koenkk · 2019-02-08T22:47:30Z

@starbuck93 is the device in database.db now? (hopefully together with modelId: MCT-340 E)

starbuck93 · 2019-02-09T18:25:23Z

@Koenkk it is in database.db now https://hastebin.com/nukisupozi.json (there are two unique MCT-340 Es in there now because I wanted to test if the pairing issue was a device specific thing or not.)

Also I have not solved the pairing issue. The device(s) are still in pairing mode for some reason. Triggering the device(s) only turns them back on pairing mode like this: https://hastebin.com/sigarefici.js

jjlawren · 2019-02-09T18:34:14Z

FYI, a similar pairing issue for this device is being investigated over with Deconz, too: dresden-elektronik/deconz-rest-plugin#978

starbuck93 · 2019-02-09T18:48:55Z

@jjlawren just finished reading the Deconz issue thread. did you manage to factory reset the MCT-340 E after they appear to be stuck in pairing mode? Each of my two devices blink their red LED 3 times every 5 seconds (to show they are in pairing mode) when I do any one of the following:

open the battery cover
push the trigger button once
bring the magnet close to close the sensor/door
take the battery out and put it back in
close the battery cover.

And zigbee2mqtt will try to pair with the device(s) again every time I do any of those things.

jjlawren · 2019-02-09T18:55:12Z

@starbuck93 same for me. It seems like the pairing process half-completes, where the controller thinks it's paired but the MCR-340 does not. Factory reset doesn't change the behavior.

There's a change pending over there that I'll test when available.

wixoff · 2019-02-12T19:51:24Z

@jjlawren I agree. I have a dotted-outline MCT-340 E showing up in my zigbee network map, connected to nothing, just floating out there. The device has no idea it's paired to anything.

These sensors worked perfectly and very reliably for me in that home-assistant zha component, so they may have a solution somewhere too.

wixoff · 2019-02-21T20:56:24Z

Is there anything I can do to help move this forward? It looks like the Deconz folks have it working as of about a week ago, as noted in the thread @jjlawren linked.

Also, I misspoke in my post above -- the MCT-340 E that I tried to pair does have a link to the controller in the zigbee map, but all else is true: it's a dotted-line box and the device doesn't know it's paired.

wixoff · 2019-03-08T14:48:40Z

@Koenkk @ciotlosm I have five of these things so I'd like to contribute if I can. Please let me know if I can -- just let me know what is needed.

stale · 2019-05-07T15:18:40Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

wixoff · 2019-05-13T15:16:22Z

Let's not close this, please. I'm still holding out hope for this device.

Koenkk · 2019-05-13T18:25:15Z

@wixoff that will happen soon: Koenkk/zigbee-herdsman-converters#434

wixoff · 2019-05-13T19:52:33Z

Fantastic!

Koenkk · 2019-05-14T16:05:31Z

Thanks to @imortkz Supported in the dev branch now! (http://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html)

wixoff · 2019-08-12T19:01:24Z

Has anyone managed to solve the pairing issue for this device? I'm having the same problem as described in #66 (comment).

Namely: device can be put into pairing mode. Putting the controller into join mode results in an entry being added to database.db, but nothing else happens. Device remains in pairing mode (blinking red light) until it times out, and after that any trigger will wake it up and cause it to try pairing again.

No amount of triggering or tamper-button-pushing during the pairing process seems to result in a completed pairing. But others have had luck! No success for me, and I have tried it many times.

wixoff · 2019-08-13T12:28:15Z

Ah, never mind. Wouldn't you know: after trying this literally dozens of times over the last few months, all it took was a post to this thread and then they all started successfully pairing. I didn't change anything!

Koenkk added the help wanted label May 27, 2018

ciotlosm added new device support New device support request and removed help wanted labels Jun 29, 2018

stale bot added the stale Stale issues label Aug 28, 2018

stale bot closed this as completed Sep 4, 2018

Koenkk reopened this Oct 9, 2018

stale bot removed the stale Stale issues label Oct 9, 2018

stale bot added the stale Stale issues label May 7, 2019

stale bot removed the stale Stale issues label May 13, 2019

Koenkk closed this as completed May 14, 2019

Visonic MCT-340 E Door Sensor #66

Visonic MCT-340 E Door Sensor #66

Comments

oakbrad commented May 26, 2018

Koenkk commented May 27, 2018

oakbrad commented May 27, 2018

Koenkk commented May 28, 2018

oakbrad commented Jun 3, 2018

ciotlosm commented Jun 3, 2018

oakbrad commented Jun 3, 2018

oakbrad commented Jun 3, 2018 • edited Loading

ciotlosm commented Jun 3, 2018

ciotlosm commented Jun 15, 2018

oakbrad commented Jun 18, 2018

ciotlosm commented Jun 19, 2018

ciotlosm commented Jun 29, 2018

Koenkk commented Jun 29, 2018

stale bot commented Aug 28, 2018

ajayjohn commented Sep 9, 2018 • edited Loading

Koenkk commented Sep 10, 2018

ajayjohn commented Sep 10, 2018

oakbrad commented Sep 12, 2018

ajayjohn commented Oct 8, 2018 • edited Loading

Koenkk commented Oct 9, 2018

ajayjohn commented Oct 12, 2018

Koenkk commented Oct 15, 2018

stale bot commented Dec 14, 2018

starbuck93 commented Feb 6, 2019

Koenkk commented Feb 6, 2019

starbuck93 commented Feb 6, 2019

Koenkk commented Feb 6, 2019

starbuck93 commented Feb 6, 2019

Koenkk commented Feb 6, 2019

starbuck93 commented Feb 6, 2019

Koenkk commented Feb 6, 2019

starbuck93 commented Feb 6, 2019 • edited Loading

jjlawren commented Feb 7, 2019

Koenkk commented Feb 7, 2019

starbuck93 commented Feb 7, 2019 • edited Loading

Koenkk commented Feb 8, 2019 • edited Loading

starbuck93 commented Feb 9, 2019

jjlawren commented Feb 9, 2019

starbuck93 commented Feb 9, 2019

jjlawren commented Feb 9, 2019

wixoff commented Feb 12, 2019

wixoff commented Feb 21, 2019

wixoff commented Mar 8, 2019

stale bot commented May 7, 2019

wixoff commented May 13, 2019

Koenkk commented May 13, 2019

wixoff commented May 13, 2019

Koenkk commented May 14, 2019

wixoff commented Aug 12, 2019

wixoff commented Aug 13, 2019

oakbrad commented Jun 3, 2018 •

edited

Loading

ajayjohn commented Sep 9, 2018 •

edited

Loading

ajayjohn commented Oct 8, 2018 •

edited

Loading

starbuck93 commented Feb 6, 2019 •

edited

Loading

starbuck93 commented Feb 7, 2019 •

edited

Loading

Koenkk commented Feb 8, 2019 •

edited

Loading