Keep dropping Visonic XHS2-TY MCT-350 SMA ZigBee Door Window Sensor

I have successfully paired 2 contact sensors. Both temp and contact read out. Units are paired about 20ft from HE hub. Contact response has<1s latency. Then the next day, I'll check status and note that device>status shows that it hasn't updated since the night before.

I reset the contact sensors and re-pair no problems. Next day I lose it again.

-I do have Ecobee paired to HE. Constant updates still going
-I have 4 sonoff temp sensors. hourly updates still going
-Single Sonoff S31Lite. It doesn't poll often, but I can toggle the switch (lamp is plugged in) at any time; this is a supposed repeater. I suppose if it's ineffective it can be dropping the Visonic?

I've seen old references to be able to check child log, etc for signal strength, communication time out.. but those posts are old and references to log locations aren't relevant anymore.

Anyone have suggestions on fix, pointers to properly log/access said log?

My newbie approach is probably next going to be using new batteries.
As of now my visonic readouts are at 100%. Device came with name brand batteries.
MY sonoff temp sensors previously dropped due to bad batteries, but the battery feedback also made that abundantly clear.

Welcome to our community!

Try ->

And also->

Check the zigbee channel your hubitat is set to: http://hub-ip/hub/zigbeeinfo

Then look at this;

Try to keep wifi and zigbee far apart, you'll have to log into your wifi router to check what channel its on or use a wifi scanner app on a smartphone. If you use a wifi scanner ap, you'll see your neighbors wifi and they maybe on wifi channels 6 or 11 but should be weak enough to not interfere. This is a wifi analyzer I use (Android)

I run my wifi on channel 1 and hubitat on channel 25.

Zigbee channels 15, 20 & 25 are the recommended channels as they fall in the sidebands of the 3 wifi channels. You could use zigbee channel 26 ( i did for a while without any issues, only had ~12 zigbee devices) but others on the forum have said some zigbee devices won't work on 26, No device examples were given.

I use several visonic ct-340's and they're rock solid and the battery readings are "accurate" for the most part.

Thanks for the pointer to the new pointers to those router logs.
Is there an official resource detailing the outputs? Worst case I do know I saw in passing some details in old posts.

Thanks for the feedback.
I did see this when manually clicking thru settings. I'm currently set to 20 for HE and 6 for my WIFI. I think that may be as far apart as I'm willing to put it ATM given your anecdotal experience.

Regarding distance/interference I've tried to decouple that from the equation simply by moving the troubled contact sensors closer. What's weird is that even far away 100'+ I can easily pair in 15secs consistently. At this range I can demonstrate low latency opening and closing of the contact switch. The problem is that if I check the next day, it'll show that the sensor has not refreshed since the day prior when I originally set up. Checking HE>Devices the latest event was from previous day.

Yet if I go to Logs>DeviceStats after a fresh reboot to HE when I've found that I lost comms with contact sensor, the contact sensors have logged upwards of ~3s of what I imagine to to process time on the HE. This number is far smaller than time I have on my Ecobee thermostats for example, but larger than my other working temp sensors and comparable to the sonoff outlet.
So it seems to be doing something with HE?

The Ecobee thermostats (at least the ones I know about) use a cloud-based IP integration, so they're probably not a great comparison.

As others have suggested, this sounds like a zigbee mesh issue or a device issue. Can you post a screen shot of your child & routes info? And does it affect both contact sensors or just one?

Your still overlapping between the wifi (green area is wifi ch 6) and zigbee. Ideally you don't want any overlap.

Regarding the distance between hub and sensor; that's not really a good measure as AC powered wifi transmits at a much high power level and can drown out a coin cell powered zigbee sensor. The 2.4ghz frequency band is also shared by cordless phones, your microwave oven, bluetooth and the endless variety of wireless devices, keyboards, mice, baby monitors, smart utility meters etc.

Moving your wifi and zigbee networks to other channels won't cause any issues as devices will follow, it's worth a try. And ideally your wifi router should be several feet away from the hub.

You say that your Zigbee devices are 20 ft from your hub. Normally that would be great. However, unless they devices are line-of-sight with nothing intervening, that might not be adequate. For example, I have an outdoor motion detector that is 20 ft from my hub, but there is a brick chimney between it and the hub, so I need a repeater to bypass the chimney obstruction. The repeater is further away from the hub than the sensor is, but the repeater is line of sight to both the hub and the device.

Normally standard gypsum wallboard over wooden studs is not a problem, but if the walls contain HVAC ducts, water piping, etc. that can be an issue. Metal studs used in some newer construction might be an issue. I have an HVAC return duct between my hub and front door lock, so I need a repeater to get around the obstruction. Also things like flat panel TVs, mirrors, aquariums and large appliances can block signals.

Adding Zigbee repeaters to your mesh is not expensive. Many people use the Tradfri repeaters from Ikea. I have had success with the Zigbee 3.0 smart plugs using eWeLink technology. Mine were produced by LUNTAK, but there are several others featuring similar design. Some others on the forum are using these same plugs successfully as repeaters. The nice thing about both the Tradfri and eWeLink devices is that they also repeat for Xiaomi/Aqara devices which many repeaters won't do.

1 Like

I changed my WIFI to channel 1 and changed the zigbee channel to 25.
This seemed to help.
I can now see that >Devices>LastActivity has updated to a recent time for the contact sensors.
I can also actively open and close the contact sensors and see HE recognize this.

What I don't understand is why the furthest most room, with poor line of sight, where I had originally paired the contact sensors and reliably reflected open and close status simply stopped working over night?
Now I can walk the working contact sensors a few feet right in front of the Sonoff Outlet (bookshelf) and I cease to be able get live updates from opening/closing contact sensors.
Is the Sonoff outlet an unreliable repeater? It's the S31LIte Zigbee version and can reliably turn switch on and off.
Is there another way to get live feedback about quality of connection? The Child/Route seems to kind of not really try to do this.

"Parent child parameters
EzspGetParentChildParametersResponse [childCount=1, parentEui64=0000000000000000, parentNodeId=65535]

Child Data
child:[snzb4, BC7B, type:EMBER_SLEEPY_END_DEVICE]

Neighbor Table Entry
[Outlet_1-Bookshelf, 3105], LQI:254, age:4, inCost:1, outCost:1

Route Table Entry
status:Active, age:64, routeRecordState:0, concentratorType:None, [Contact_2, 9F32] via [Outlet_1-Bookshelf, 3105]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Contact_1, D400] via [Outlet_1-Bookshelf, 3105]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Outlet_1-Bookshelf, 3105] via [Outlet_1-Bookshelf, 3105]

Seems to indicate the contact sensors are routing thru the outlet repeater?

I should have SNZB1/2/3/4 for the sonoff temp sensors, contact1/2 for 2 visonic contacts, and 1 bookshelf for sonoff outlet.
I don't see any mention of the SNZB sensors.

Is there a primer for the child/route output available? Weird that the bookshelf self references and that most of the temp sensors aren't displayed, that the age is so old, etc.

Thanks for the help

Now my contact sensors have dramatically increased range. IE I can now walk way beyond my bookshelf outlet and the open/close state is registered on HE.

IS there a smarter way to get live feedback? IE open/close won't work with basic temp sensors.

Refreshing child and route gave identical results except for age4 for neighbor...

The only thing I can think of is that the Zigbee channel change to 25 took awhile to update ?

Yes it can definitely take a while for the mesh to settle back down after a channel change.

1 Like

Regarding your "missing" sensors. From info I gathered, the hub routing is a snapshot in time of the current routes and devices. Perhaps for a certain period of time like the last 15 minutes.

Also zigbee does not maintain active, constant communications channels. Sensors wake up and communicate when they have something to report then they go back to sleep. So routers and coordinators (hubs) may see sleepy end devices (battery powered) sensors drop off.

And routes devices take aren't always logical in terms of distance or line of sight. I've had sensors in my detached garage use routers that were further away then the hub itself.

Don't get too hung up on the routing. If a device pairs and does what it supposed to do reliably, that's all that matters.

You could look into The Device Watchdog app, It monitors device activity and battery levels and produces a report if a device fails to report after a period of time that you designate.

Here's mine on a dashboard, With several obvious test sensors.


Not to your problem but I found the MCT-350 sensor was stable on my network (with a repeater nearby) but the battery life was horrible. I replaced it with an Aqara sensor.

Thank you all for your thoughtful replies.

I guess I came into this expecting the process to be a little more deterministic given that HE is a COTS product.
Even the official guide is suggesting how days are required for the mesh to 'settle'. This implies a lot more magic (stuff out of my control) than I'd like.

This seems to be supported by the fact that I can have high accuracy, low latency, high responsiveness feedback from a contact sensor during install one evening- i purposely chose a location bridged by a repeater, furthest location and highest physical barriers in the house. Zero responsivity from the same location the next day.
I can re pair in a much more benign location , much closer with LOS and stuff works. Next day feedback is intermittent.

I've since installed the watchdog APP and it provides some useful info.
I think that the child/route output is the most useful in troubleshooting variables that impact comms.. this would have been infinitely more useful if ALL devices regardless of how stale the data was retained in this log..

Right now I'm stuck with brute force feedback (contact sensor open/close).

Luckily the mains installed Sonoff31 Lite zigbee outlet is the only robust item on my network that consistently responds.
Maybe I just need to buy a slew of repeaters and scatter them around the house? I'm not convinced this is the solution since I can spend hours with reliable contact sensor feedback. If this were a mesh connectivity issue, I'd expect that symptoms would be that I have intermittent connection over the course of days rather than the small windows of great responsivity.

Folks have mentioned the IKEA repeater. Just looking at $$ the Sonoff31Lite is only $10 @qty4. Any reason I wouldn't have this be my backbone given the value?

So far the stock batteries on the visonics are reading 100; Will keep an eye on it. IT seemed like a great solution given cost and included temp sensor. I like that they paired with no drama.
Too bad they don't seem to stay connected for unknown reasons.


This may not apply to you but folks have complained that Smart Water meters (from the water company, not an HA product) have caused issues with other wireless devices in the home. Just a thought.

Just a comment on this scenario-- when you take a child 'sleepy end device' out of range of its parent, it's a disruptive change... meaning that the device isn't capable of forwarding its messages immediately through another in-range repeater when it loses contact with its original parent.

First it must recognize that it has been orphaned (a Zigbee child device relies on dedicated send/receive buffers that have been allocated by its parent to store/retrieve its messages)-- this involves scanning all available Zigbee channels to account for a possible network channel change. It then must go through a process of finding a new parent router and rejoining the network.

When it works as intended (not all Zigbee stacks seem to be equally good at doing this) it may only take several seconds, but until the rejoin happens you'll notice the device fail to respond properly until the child/new parent link gets established. Ultimately the device should begin to work again with a new parent without manual intervention (at least when things are working as intended).

It's likely your network would benefit from a few more repeaters, though the one you have does seem to show a good link to the hub. The 'free air' range you may see quoted for Zigbee is reduced to a fraction of that indoors (Control4 recommends no more than 15'-30' between repeaters, and sometimes as little as 6'-9' due to attenuation/reflections of building materials and furniture).

I understand your comments regarding 'real life' range LOS perfect conditions vs various obstacles that attenuate signal to various amounts, interference from WIFI, etc.
I also hear you regarding how slow the mesh repair/redirecting traffic may be. How long would you expect the zigbee mesh to heal after it breaks?

I try to mitigate these unknown variables simply by picking a static worst case scenario, successfully pairing and demonstrating a robust feedback loop (open/close contact) of more than one sensor. I can open and close over a chunk of time (~3 hours in this case) with 100% hit rate on HE status recognition. I can now try the same the next day, same spot, no moving setup and breaking zigbee routings, and not have connection or status is stuck open, etc.

I definitely don't have a complex, dynamic operating environment. As stated above, if I were limited by spotty connectivity, I imagine the first night of testing would yield intermittent results as would the second night. I'd get consistently intermittent results if you will. Right now I'm seeing bursts of clarity which I don't understand.

unless I'm mistaken, I don't have the tools to truly trouble shoot this opaque system.

And I'm relegated to blindly dumping more repeaters on the issue... anyone have thoughts on Sonoff s31Lite outlet repeaters?

Updated :
Parent child parameters
EzspGetParentChildParametersResponse [childCount=0, parentEui64=0000000000000000, parentNodeId=65535]

Child Data

Neighbor Table Entry
[Outlet_1-Bookshelf, 3105], LQI:255, age:3, inCost:1, outCost:1

Route Table Entry
status:Active, age:64, routeRecordState:0, concentratorType:None, [Snzb2, 844E] via [Outlet_1-Bookshelf, 3105]
status:In Discovery, age:0, routeRecordState:2, concentratorType:High Ram, [null, 0000] via [Outlet_1-Bookshelf, 3105]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Outlet_1-Bookshelf, 3105] via [Outlet_1-Bookshelf, 3105]
status:In Discovery, age:0, routeRecordState:0, concentratorType:None, [Contact_2_Garage1Door, 9F32] via [Outlet_1-Bookshelf, 3105]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Contact_3, 1DF9] via [Outlet_1-Bookshelf, 3105]

It's hard to generalize but a small change can be pretty quick. I've experimented, watching a Zigbee sniffer trace (CC2530 and the free TI software). While watching packets from a Kwikset Zigbee lock (checking in every 3 seconds with its Iris V2 plug parent) I'd unplug the Iris and by the time I got back to view the trace, the Kwikset had already aquired a new parent (it had lots of repeaters in range to choose from). It probably happened within 20 seconds.

I mentioned it because if you're testing with a sensor while moving it around, you would notice a disruption during the process as the device gets orphaned until the point that it negotiates with the new parent and rejoined-- messages from the sensor won't be relayed by any repeater that happens to be in range, just the bonafide current parent of the device.

Troubleshooting issues like these can be tricky without visibility into what's going on. I was helping a friend troubleshoot his SmartThings Zigbee network last week-- it handled his collection of Cree bulbs, outlets and motion sensors flawlessly for years with the exception of cloud issues. But suddenly things stopped working well; timed lighting events became flaky and devices weren't responding to the app.

Ultimately it turned out that his wifi router was located very close to his ST hub-- within a couple of feet. This is bad; regardless of what wifi channel you are using, the sidelobe interference (within roughly 3 feet or so of the router) can swamp the Zigbee radio. It always had been located there and had apparently never caused any issues-- Zigbee can be pretty resilient and his stuff had been working.

Recently (coinciding with the start of the problems) he had rearranged the antenna orientations on the router trying to optimize wifi range. This was enough to tip things over the edge and caused his Zigbee issues-- when he had all four of the router's antennas pointed straight up, Zigbee worked. Moving them in different angles (better for wifi coverage) effectively swamped his nearby ST hub. Relocating it a few feet farther away solved his problems.

You don't have to go hog wild with repeaters but having two or three even in a small setup is reasonable.

1 Like

Ironic... I had 2 of my Vision MT-340's drop off the mesh in my shed this week. I have never had any issues before with them. I had to re-pair them to get them to work again. I was using channel 20. I thought that maybe a neighbor was causing interference so I relocated them to channel 25 but they wouldn't work. I dropped back to 20 and keeping my fingers crossed. Weird coincidence that you are having issues all of a sudden as well.

I'd actually say I never got off the ground.
Only my sonoff zigbee outlets and ecobee are reliable. Sonoff Temps and Visonic Contacts are a crap shoot.

I have 13 other Visionic MT-340s that work flawlessly. The ones in my shed are the only ones that seem to have failed. I can only assume that there is some interference on that Zigbee channel on that hub. Unfortunately I have run out of unique Zigbee channels because of the number of zigbee networks that I have, so moving the channel is a problem.

Download the Hubitat app