search

Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
12.29k stars 1.69k forks source link

Visonic MCT-340 E Door Sensor #66

Closed oakbrad closed 5 years ago

oakbrad commented 6 years ago

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 []
``
Koenkk commented 6 years ago

Did you factory reset the device?

oakbrad commented 6 years ago

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

Koenkk commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

@oakbrad you can try https://github.com/Koenkk/zigbee2mqtt/issues/90 details to see if it helps on how things should look when pairing difficult devices.

oakbrad commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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

ciotlosm commented 6 years ago

@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 commented 6 years ago

@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 commented 6 years ago

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

ciotlosm commented 6 years ago

@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 commented 6 years ago

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

stale[bot] commented 6 years ago

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 commented 6 years ago

@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
> zigbee2mqtt@0.1.3 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 commented 6 years ago

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

ajayjohn commented 6 years ago

@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 commented 6 years ago

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 commented 6 years ago

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

Koenkk commented 6 years ago

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

ajayjohn commented 6 years ago

Procedure 1) I turn on the 'permit_join' option in the official hassio add-on you have provided 2) I initiate the pairing sequence on the sensor (MCT-340 E). The sensor is now in pairing mode. 3) 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)' 4) 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. 5) 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 commented 6 years ago

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

stale[bot] commented 5 years ago

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.

henworth commented 5 years ago

I found this issue after having this very same problem pairing a couple sensors. One sensor paired seemingly without issue (ie. it left pairing mode) but the second has not. They both have been added to configuration.yaml correctly and I've created a stub entry in devices.js for the Visonic devices.

I've captured the extent of the debug logs, I hope they are helpful: https://hastebin.com/esayotayoz.apache

henworth commented 5 years ago

I realized that the logs didn't capture the shepherd debug even though that was enabled as well, maybe a quirk with hassio? Anyway, I wasn't able to capture the full set of missed debug messages due to the limited window size of the hassio addon logs in the gui, but I was able to get these blocks

This gets repeated a few times:

2018-12-21 18:20:26 - debug: Received zigbee message of type 'devInterview' with data '"0x000d6f000b3dfe2f"'
2018-12-21 18:20:26 - info: Connecting with device...
2018-12-21 18:20:26 - info: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"connecting with device"}'
2018-12-21 18:20:26 - warn: Message without device!
2018-12-21 18:20:26 - zigbee-shepherd:request REQ --> AF:dataRequest, transId: 16
2018-12-21 18:20:26 - zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object]
2018-12-21 18:20:26 - zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0
2018-12-21 18:20:26 - zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0
2018-12-21 18:20:26 - zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object]
2018-12-21 18:20:27 - zigbee-shepherd:af dispatchIncomingMsg(): type: dataConfirm, msg: [object Object]
2018-12-21 18:20:27 - zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 16
2018-12-21 18:20:27 - zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object]
2018-12-21 18:20:27 - zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0
2018-12-21 18:20:27 - zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object]
2018-12-21 18:20:27 - zigbee-shepherd:request REQ --> AF:dataRequest, transId: 17
2018-12-21 18:20:27 - zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0
2018-12-21 18:20:28 - zigbee-shepherd:af dispatchIncomingMsg(): type: dataConfirm, msg: [object Object]
2018-12-21 18:20:28 - zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 17
2018-12-21 18:20:28 - zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object]
2018-12-21 18:20:28 - zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0
2018-12-21 18:20:28 - zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object]

This also happens towards the end:

2018-12-21 18:21:20 zigbee-shepherd Device: 0x000d6f000b3dfe2f already in network
2018-12-21 18:21:20 zigbee-shepherd:msgHdlr IND <-- ZDO:tcDeviceInd
2018-12-21 18:21:20 zigbee-shepherd spinlock: false []
2018-12-21 18:21:20 zigbee-shepherd Device: 0x000d6f000b3dfe2f already in network
2018-12-21 18:21:20 zigbee-shepherd:msgHdlr IND <-- ZDO:endDeviceAnnceInd
2018-12-21 18:21:30 zigbee-shepherd Device: 0x000d6f000b3dfe2f already in network
2018-12-21 18:21:30 zigbee-shepherd:msgHdlr IND <-- ZDO:tcDeviceInd
2018-12-21 18:21:31 zigbee-shepherd spinlock: false []
2018-12-21 18:21:31 zigbee-shepherd Device: 0x000d6f000b3dfe2f already in network
2018-12-21 18:21:31 zigbee-shepherd:msgHdlr IND <-- ZDO:endDeviceAnnceInd
Koenkk commented 5 years ago

If I understand correctly, you are able to pair it now but dont receive any messages from the device, is that right?

henworth commented 5 years ago

Essentially, yes. The first sensor I paired looked like it worked successfully and it shows as online in the database. The second two seemed to work, but don’t leave the pairing the stage based on the device’s led blink pattern. Those two show up as offline in the database.

However, there are no messages from either set of sensors.

Koenkk commented 5 years ago

Try with the following in devices.js

{
        zigbeeModel: ['MCT-340 E'],
        model: 'MCT-340 E',
        vendor: 'Visonic',
        description: 'Wireless door window temperature sensor',
        supports: 'contact and temperature',
        fromZigbee: [],
        toZigbee: [],
        configure: (ieeeAddr, shepherd, coordinator, callback) => {
            const device = shepherd.find(ieeeAddr, 1);
            const actions = [
                (cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb),
                (cb) => device.functional('ssIasZone', 'enrollRsp', {enrollrspcode: 0, zoneid: 23}, cb),
                (cb) => device.bind('msTemperatureMeasurement', coordinator, cb),
                (cb) => device.report('msTemperatureMeasurement', 'measuredValue', 30, 600, 1, cb),
            ];
            execute(device, actions, callback);
        },
    },
henworth commented 5 years ago

Looks like the only sensor that showed online is now not. I think I captured the relevant section of the logs. If not it shows up on every restart so I can get more context if needed. 


Tue, 01 Jan 2019 19:52:54 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: dataConfirm, msg: [object Object]
Tue, 01 Jan 2019 19:52:54 GMT zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 1
2019-01-01T19:52:54.902Z zigbee-shepherd-converters:devices Configured '(cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb)' with result 'Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.'
  zigbee2mqtt:error 2019-1-1 14:52:54 Failed to configure 0x000d6f000b3e0242 0x000d6f000b3e0242
Tue, 01 Jan 2019 19:52:54 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: dataConfirm, msg: [object Object]
Tue, 01 Jan 2019 19:52:54 GMT zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 2
2019-01-01T19:52:55.001Z zigbee-shepherd-converters:devices Configured '(cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb)' with result 'Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.'```
Koenkk commented 5 years ago

Configuring probably fails because the device is offline, could you press a button on the startup, this makes sure the device is awake and ready to be configured.

starbuck93 commented 5 years ago

Related to the Visonic MCT-340 E... Let me know if I need to open a new issue versus tagging along with this one.

I just got zigbee2mqtt up and running on my Raspberry Pi with the CC2531 after a few hours of messing around. I got the SmartThings Motion Sensor (2016) working first after messing with devices.js and fromZigbee.js, then paired the Visonic door sensor. I've seen a lot of strange things with this door sensor.

Firstly, when it pairs, the log outputs around 10 Message without device! ... Connecting with device... messages. Now it is paired as it shows up in the log, as well as in the database.db and configuration.yaml. The weird thing about the pairing is that two devices show up in all 3 locations. 

Device with modelID 'MCT-340 E' is not supported.
Device with modelID 'undefined' is not supported.

They both have unique 0x addresses. The database shows the MCT-340 E (excerpt from database.db and the undefined device. You might notice the undefined device is registered as a Coordinator ..."type":"Coordinator"... Why does zigbee2mqtt think it's the coordinator? ~How do I see the actual coordinator's 0x address?~ Edit: The coordinator's actual 0x address is the same as the undefined device.

When I open and close the door (triggering zigbee traffic) the logs show the undefined device is the one sending the messages. Turning on debug mode, the traffic is accurate by sending zoneStatus 32 and 33 for open and closed. But it's not the right device sending that data.

Received zigbee message of type 'statusChange' with data '{"cid":"ssIasZone","zoneStatus":32}' of device 'undefined' (0x00124b0019366619)

801 seems relevant but after reading that a lot of their log files are quite different than what I'm seeing over here. I've also read a lot of #176 but I don't entirely remember how I got there anymore.

Koenkk commented 5 years ago

@starbuck93 your experiencing the same as in #176.

When setting https://github.com/Koenkk/zigbee2mqtt/blob/master/lib/zapp/cie.js#L12 to cieClusters.init('ssIasZone', 'dir', {value: 1}); does it work?

starbuck93 commented 5 years ago

@starbuck93 your experiencing the same as in #176.

When setting https://github.com/Koenkk/zigbee2mqtt/blob/master/lib/zapp/cie.js#L12 to cieClusters.init('ssIasZone', 'dir', {value: 1}); does it work?

No, it didn't work. Here's the log https://hastebin.com/exuyudowik.js

I stopped zigbee2mqtt, reset the MCT-340 and removed all instances of both 0x addresses in database.db and configuration.yaml, started zigbee2mqtt back up, paired the device and it still happened.

Koenkk commented 5 years ago

@starbuck93 can you try with (please re-pair the device afterwards)

{
        zigbeeModel: ['MCT-340 E'],
        model: 'MCT-340 E',
        vendor: 'Visonic',
        description: 'Wireless door window temperature sensor',
        supports: 'contact and temperature',
        fromZigbee: [],
        toZigbee: [],
        configure: (ieeeAddr, shepherd, coordinator, callback) => {
            const device = shepherd.find(ieeeAddr, 1);
            const actions = [
                (cb) => device.functional('ssIasZone', 'enrollRsp', {enrollrspcode: 0, zoneid: 23}, cb),
                (cb) => device.bind('msTemperatureMeasurement', coordinator, cb),
                (cb) => device.report('msTemperatureMeasurement', 'measuredValue', 30, 600, 1, cb),
            ];
            execute(device, actions, callback);
        },
    },
starbuck93 commented 5 years ago

@Koenkk Same thing happened again. Stopped zigbee2mqtt, deleted from db and yaml, changed the devices.js and repaired the MCT-340.

https://hastebin.com/baxomijuno.makefile

(you'll see some other zigbee traffic here too)

Koenkk commented 5 years ago

@starbuck93 could you add to https://github.com/Koenkk/zigbee-shepherd/blob/master/lib/components/af.js#L591 

console.log('MYTAG', type, JSON.stringify(msg));

and provide the logging?

starbuck93 commented 5 years ago

Here's the output of the log: https://hastebin.com/oyevulobul.sql

Koenkk commented 5 years ago

@starbuck93 somehow the hastebin is now empty (I checked earlier today and saw the log). Could you repost it?

starbuck93 commented 5 years ago

I can still see https://hastebin.com/oyevulobul.sql. But here it is again https://pastebin.com/K9K9GHNP

Koenkk commented 5 years ago

Can you try replacing https://github.com/Koenkk/zigbee-shepherd/blob/master/lib/components/af.js#L596 till 597 with

if(!coord) return;
if (msg.dstendpoint == 11) {
  msg.dstendpoint = 1;
}
targetEp = coord.getEndpoint(msg.dstendpoint);               //  => find local ep
starbuck93 commented 5 years ago

Here's what happens with the new edit in af.js https://hastebin.com/heloyefocu.apache

  1. stop zigbee2mqtt
  2. remove entries from db and config
  3. take battery out of MCT-340 E
  4. start zigbee2mqtt, wait for setup to finish in logs
  5. factory reset MCT-340 E
  6. pasted logs starting after zigbee2mqtt setup is finished

full logs with zigbee2mqtt debug https://hastebin.com/ulimijubep.sql

Koenkk commented 5 years ago

@starbuck93 what happens when you trigger the MCT-340 E?

starbuck93 commented 5 years ago

Line 1 is door closed and line 2 is door open https://hastebin.com/kofeyuzizu.pl

Koenkk commented 5 years ago

Can you try with

https://github.com/Koenkk/zigbee-shepherd/blob/master/lib/components/af.js#L596 till 597 with

if(!coord) return;
if (msg.dstendpoint == 11) {
  msg.dstendpoint = 1;
  type = 'zclIncomingMsg';
}
targetEp = coord.getEndpoint(msg.dstendpoint);               //  => find local ep
starbuck93 commented 5 years ago

Steps taken:

  1. stop zigbee2mqtt
  2. edit af.js, remove entries from db and config
  3. take battery out of MCT-340 E
  4. start zigbee2mqtt, wait for setup to finish in logs
  5. factory reset MCT-340 E
  6. pasted logs starting after zigbee2mqtt setup is finished

https://hastebin.com/goxoxobuke.apache

The last few lines are triggering the MCT-340

Koenkk commented 5 years ago

@starbuck93 sorry for the delay.

Please try with the following af.js: https://raw.githubusercontent.com/Koenkk/zigbee-shepherd/fix/lib/components/af.js

You don't need to repair the device, just update af.js and trigger the contact sensor a few times.

starbuck93 commented 5 years ago

@Koenkk no problem! I appreciate all the help you're providing here.

I had to add ../model/group to the right directory to get it to run after an error, now I'm getting a new error.

/opt/zigbee2mqtt/node_modules/zigbee-shepherd/lib/components/af.js:608
        console.log("Checkpoint 3", JSON.stringify(targetEp));
                                         ^

TypeError: Converting circular structure to JSON
    at JSON.stringify (<anonymous>)
    at dispatchIncomingMsg (/opt/zigbee2mqtt/node_modules/zigbee-shepherd/lib/components/af.js:608:42)
    at Controller.incomingMsgHandler (/opt/zigbee2mqtt/node_modules/zigbee-shepherd/lib/components/af.js:754:12)
    at Controller.emit (events.js:197:13)
    at Object.bridge._areqEventBridge (/opt/zigbee2mqtt/node_modules/zigbee-shepherd/lib/components/event_bridge.js:15:16)
    at CcZnp.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-shepherd/lib/components/controller.js:105:16)
    at CcZnp.emit (events.js:197:13)
    at CcZnp._mtIncomingDataHdlr (/opt/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:370:14)
    at Immediate.<anonymous> (/opt/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:336:22)
    at processImmediate (timers.js:632:19)
Koenkk commented 5 years ago

@starbuck93 can you try with: https://raw.githubusercontent.com/Koenkk/zigbee-shepherd/fix/lib/components/af.js (updated it)

starbuck93 commented 5 years ago

@Koenkk Another circular structure error, and here's the output https://hastebin.com/ovitoyevit.coffeescript

Koenkk commented 5 years ago

Updated again: https://raw.githubusercontent.com/Koenkk/zigbee-shepherd/fix/lib/components/af.js