I have installed 2 x NUE 4 gang ZigBee switches. they connect directly to the Hubitat hub and work perfectly for say 30 minutes maybe 1 hour. They are set up to the NUE Zigbee Switch, they are close to the Hub and other devices around work perfectly.
After 30 minutes or so they become unresponsive through habitat, still, work locally. but cannot work through hubtitat.
I have looked at logs and no errors, I have soft reset and re loaded back up the same problem.
The kicker here is that the switch is talking to HE because I can see the status change on the switch if I manually press the switch at the switch but cannot turn on or off from Hubitat.
I have tried changing the driver to generic.
Also to note, when this happens if I put the switch back in pairing mode it will re-save perfectly and then do the same thing again in 30 minis or so.
NUE-ZB404B driving me crazy as I have tried everything. both units I am testing do exactly the same thing. but only last 30 minutes then disconnect. funny however I have just noticed that I can monitor status on or off if the stitch is operated manually but cannot drive the switch from habitat. so there is connectivity.
That particular one isn't on the compatibility list. That said it makes me think of a couple of things.
1st It may not be fully zigbee compliant (and crashing with HE)
2nd Perhaps contacting NUE support to see if there is a firmware update that could resolve the issue.
Your description reminds me of Aqara behavior in the way it drops off the mesh. I also wonder for shites and giggles if it would be worth trying to put a trafardi (ikea) repeater next to the switch (to get it to route through it. They seem to handle non compliant zigbee stuff better)
Mate, firstly thanks for your support I am new to Hubitat but not to the concept and find it very hard to get a straight answer.
I will follow up on your suggestions by firstly chasing NUE for a firmware update. so you don't believe it is driver related? and also I have read on this forum many similar examples of NUE and what I am suffering that there was a suggestion that the driver provided by HE has a scheduled job that may be accidentally left in the code. thoughts on this?
finally, I have an Ikea repeater I will set it up adjacent.
The fact that the driver works for 30 mins shows that the driver works. So no it's not a driver. It's the switch itself dropping off the mesh. Look up aqara problems. Exact same behavior. It's the switch crashing against the hub. Likely the switch is not following proper zigbee protocol
I would second what rlithgow1 says, it sounds like a weak mesh, or this device is just falling off the mesh because it is a defective, poorly designed, or non-standard Zigbee.
I don't think it is a driver issue either, as it pairs and works for a bit. It is no different than a mouse or keyboard pairing, then they stop working later on. That points toward hardware rather than software in most cases.
I would try the repeater, and see if that makes any difference.
Guys I spoke with the NUE supplier and they sounded a bit suss but helpful. Apparently, they have a new update out next week which may mean next month or next year. we will see. it is a shame as the device itself is well made and when working is perfect. in the meantime, I will try repeater but struggle to think of this as devices adjacent and further from Hub work perfectly.
I am also confused at why I can see staus change once it has dropped off. this means there MUST be connectivity. which makes me think it I not dropping of. doesn't explain why I cant drive through HE.
I know these are 3rd world problems but so fristrating.
I'm surprised given the amount of NUE stuff that is compatible. Maybe you can convince them to send a couple of samples of their newer stuff to @mike.maxwell
