Core: Visonic MCT-340 E zigbee door sensor temperature reading not working

[admun]

Many of us been seeing issue on this sensor

https://community.home-assistant.io/t/visonic-mct-340-e-window-door-sensor/20966/19

Currently, running on latest 0.77.3, seeing temperature @ 32.0F all the time.

How can we debug and get this to work?

[MartinHjelmare]

Please fill in the issue template completely.

[admun]

Sorry, hope this is the info we can started.

Home Assistant release with the issue:
0.77.3

Last working Home Assistant release (if known):
not known

Operating environment (Hass.io/Docker/Windows/etc.):
Pi 3, HassOS 1.10

Component/platform:
https://www.home-assistant.io/components/zigbee/

Description of problem:
After adding the MCT-340 E device, the temperature (in F) shows in overview and history, but constantly at 32.0

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
zha:
usb_path: /dev/ttyUSB1
database_path: /config/zigbee.db

Traceback (if applicable):
Please let me know where I can provide log...

Additional information:

[admun]

forgot to mention, using Linear HUSBZB-1

[ajayjohn]

Thanks for opening this issue admun!
@MartinHjelmare I can confirm that this issue exists for me too, for the same device and Zigbee stick combination.

Other details at my end include...
Home Assistant release with the issue:
0.78.3

Last working Home Assistant release (if known):
not known

Operating environment (Hass.io/Docker/Windows/etc.):
Intel NUC with Hass.io running on Docker

[WedHumpDay]

Confirmed in 0.79.3 as well. However in this case, not reporting temperature what so ever.
Have tried repairing, resetting, restarting HA multiple times without any success.

These devices are very responsive. Would be wonderful to have the temperature working.

Asking developers to acknowledge they will work to support the temperature portion of these devices.

[WedHumpDay]

What is it going to take to have this resolve?
Seems to me this issue is being ignored.

2018-10-13 07:35:59 INFO (MainThread) [homeassistant.components.zha] Permitting joins for 60s
2018-10-13 07:36:03 INFO (MainThread) [zigpy.application] Device 0x2143 (00:0d:6f:00:0b:3b:85:59) joined the network
2018-10-13 07:36:03 INFO (MainThread) [zigpy.device] [0x2143] Discovering endpoints
Tries remaining: 3
2018-10-13 07:36:04 INFO (MainThread) [zigpy.device] [0x2143] Discovered endpoints: [1]
2018-10-13 07:36:04 INFO (MainThread) [zigpy.endpoint] [0x2143:1] Discovering endpoint information
Tries remaining: 3
2018-10-13 07:36:04 INFO (MainThread) [zigpy.endpoint] [0x2143:1] Discovered endpoint information: 2018-10-13 07:36:05 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.zha
2018-10-13 07:36:05 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.zha
2018-10-13 07:37:24 INFO (MainThread) [homeassistant.components.http.view] Serving /api/ to 172.30.32.2 (auth: True)

2018-10-13 07:39:09 WARNING (MainThread) [zigpy.zcl] Data remains after deserializing ZCL frame
2018-10-13 07:39:09 WARNING (MainThread) [zigpy.zcl] Data remains after deserializing ZCL frame
2018-10-13 07:39:09 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=2 command=11 args=[0, ]
2018-10-13 07:39:19 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/zigpy/device.py", line 89, in request
expect_reply=expect_reply,
File "/usr/local/lib/python3.6/site-packages/bellows/zigbee/application.py", line 245, in request
v = await asyncio.wait_for(reply_fut, timeout)
File "/usr/local/lib/python3.6/asyncio/tasks.py", line 362, in wait_for
raise futures.TimeoutError()
concurrent.futures._base.TimeoutError
2018-10-13 07:39:19 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/zigpy/device.py", line 89, in request
expect_reply=expect_reply,
File "/usr/local/lib/python3.6/site-packages/bellows/zigbee/application.py", line 245, in request
v = await asyncio.wait_for(reply_fut, timeout)
File "/usr/local/lib/python3.6/asyncio/tasks.py", line 362, in wait_for
raise futures.TimeoutError()
concurrent.futures._base.TimeoutError

[dmulcahey]

Just bought one to investigate... should arrive tomorrow. I'll report back when I have an idea as to what is going on.

[dmulcahey]

So, I paired this and it just works. My guess is that there was an error during the configure reporting stage when you paired the sensor. I suggest unpairing the sensor and repairing it.

[edif30]

@dmulcahey how long have you had it paired? And have you done an HA restart? I have experience this sensor will just stop updating its state after a bit and 1 or a few restarts.

[dmulcahey]

@edif30 several restarts and about 90 minutes on my dev system. Zigbee is very sensitive to mesh design issues and potentially 2.4ghz interference. Adding smart plugs to the network is the best way to help prevent devices dropping off.

[edif30]

I'm curious to see how long it lasts. I have tried several times in the past and after the initial temp updates, it doesnt after some time and restarts. Also, the open/close stops updating too. I also have plugs which should repeat as well. The stick and sensor have been no more than 10 ft apart, isolated 2.4, etc. Same issue. I even have Iris sensors that I tested with and they are fine.

[dmulcahey]

@edif30 I'll keep an eye on it while I am developing the device handler for the keen smart vent... that should take me a couple hours... another question: what hardware is running the system? Are you using an rpi?

[edif30]

NUC i5 v7 16g RAM 500G SSD

[dmulcahey]

@edif30 whelp... that def isn't it lol. are you up to date on HA? if so, in the zha device entity for it, what are your radio readings:

[edif30]

0.82 and -64

[dmulcahey]

dumb question... are u sure it isn't reporting? the time on the card will not update if it is reporting consistent temperature...

[edif30]

Very sure. I held the sensor in my hand which should have raised the temp easily. I also put an ice pack on it. Same result.

[dmulcahey]

ok, at this point your setup is beyond perfect and everything you're describing is as well. Can you do me a favor? Remove (unpair) the sensor from your setup and set zigpy, bellows and zha logging to debug. then restart HA and repair the sensor. Let the system run for about 45 mins and then send me the entire unedited log.

[edif30]

Will have to get you this tomorrow. But happy to help.

On Thu, Nov 29, 2018, 8:50 PM David F. Mulcahey <[email protected]
wrote:

ok, at this point your setup is beyond perfect and everything you're
describing is as well. Can you do me a favor? Remove (unpair) the sensor
from your setup and set zigpy, bellows and zha logging to debug. then
restart HA and repair the sensor. Let the system run for about 45 mins and
then send me the entire unedited log.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/16632#issuecomment-443061454,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQgbt1zQgIgEF48yafEH2pO-2lPXjlgKks5u0I7SgaJpZM4WqRzE
.

[dmulcahey]

So, my this is still reporting on my dev setup just fine. Not sure what the issue is here and I am going to suggest closing as not reproducible unless someone can provide additional details.

[admun]

@dmulcahey how to do the debugging, sorry I am not familiar with testing zha device.

If there is an instruction, I can try to follow and gather info on the problem

[dmulcahey]

@admun start by removing and rejoining the device to ensure its paired correctly. If there are any tracebacks post them here. If not, let me know if the device is working as expected.

[admun]

stupid question; how do I find a device address? zha.remove takes a json w/ ieee_address

[Adminiuga]

@admun got to hass Dev tools -> entities and filter by zha., it would/should display all ZHA device entities, now you just need to pick the right entity.
Unless you've updated entity_id for the temp sensor, it would like somewhat similar to zha device entity id, eg: zha.zha_osram_lightify_a19_rgbw_00a45595 vs light entity id: light.osram_lightify_a19_rgbw_00a45595_3 the block of hex digits in entity-id is derived from IEEE (last digits) so you could match temp sensor entity_id -> zha entity id and find the IEEE

[admun]

@Adminiuga Thx.

Ok, I removed all MCT-340 E in my HA.

After I added them, the temp for one is showing Unknown, the other one now work.

For the one reported unknown, I tried to remove/add again but still seeing unknown

I check Dev info -> About -> log and hass.io -> System -> system log but saw no error. Do I need to turn on some debug log or maybe i am looking at the wrong place?

[admun]

actually... the unknown one reporting temp after a few min.....

I guess the problem is one might need to remove/add again to fix the issue.

[dmulcahey]

Glad it’s working...

[HyperEscape]

Joining the conversation for possible guidance for my similar situation. I am trying to use it with Nortek HUSBZB-1,

Please have a look at my thread here for details and any possible guidance clue to make it work.

https://community.home-assistant.io/t/visonic-mct-340-e-window-door-sensor/20966/25?u=sfhasan

Thanks.

[dmulcahey]

closing as @admun has confirmed that rejoining the device corrected his issue and that aligns with what I am seeing.