Yes, that’s correct. Just tested it and it works. The sensitivity change is also confirmed in the device current states and in the live logs.
Yeah this is a really frustrating, perhaps deal-breaker. If it was only me in the house, having to unplug / replug once in awhile is not a huge deal. But now that I have 5 of these, it's a weekly occurrence and my family doesn't appreciate stuff randomly not working. My advice to those considering these for non-enthusiast applications, they may not be ready for prime-time / mainstream use.
I have 3 of the Linptech sensors running for a couple months now and have only had this happen to one of the sensors one time. Since they don't come with a power supply, I wonder if voltage fluctuation has something to do with it. I am using old Echo Dot power supplies on 2 of them, and a power supply from a C-5 hub on the third. I also have taped over the lux sensor since I use outdoor Hue sensors for that.
I'm curious about the inconsistency, as the Linptechs have been great for me. I have 7 running for 2-3 weeks without any power recycling. Some plug into power strips with dedicated USB-A ports, while others use their own 5V power supplies. Most do not have surge protection.
What are your devices sensitivity and distance settings?
Avoid maximum sensitivity and maximum distances except it is absolutely necessary.
1 Like
I've tuned them all differently, they are all over the map. I wouldn't expect this is an issue as it's not an issue of them firing or not firing, it's an issue of them stopping sending motion events altogether.
Yeah, I may be overstating the rate of issues, but it's at least one every couple weeks. It has happened to all of them at least once at this point ~3 months into my journey. I can recall ~5 times I've had to power cycle one. I just came home from a 4 day trip to find the one in my office not sending events and that was the last one to never have an issue (and the first one I installed).
So here's something interesting. While I was out of town for 4 days, the following appeared in my event logs. Don't usually see these healthStatus messages. What's really curious is the offline came at roughly the exact same time on 3 separate days. Not seeing anything else in my logs at that time.
The lux entry at the bottom is right when I left town. It stopped reporting lux and started doing the online offline thing until I got back on 3/6 and rebooted it. 4am is when my Hubitat reboots so it seems to report "online" after the reboot each morning, then went offline again at 4:58pm. Didn't report anything in between. There wouldn't have been motion, but no lux reports either.
I went for like 6 months before one of mine disconnected. Then it did it like 8 times over the next week. So I put it on a little Kasa smart plug with a rule Machine rule that automatically power cycles the sensors when it disconnects. So far it's gone a month again without disconnecting and the rule has never been triggered, so I really have no idea what's up.
1 Like
I had two of five get into limbo state (not reporting motion, but reporting everything else) the same day my hub rebooted due to a platform update last week. Nothing before that for months, and nothing since. My sensitivity settings are also all over the map, and the two that went quiet were on lower settings.
My over-engineered response to this very infrequent issue (that's what we do here, right? 
) was to add the tiny SonOff wi-fi plugs to the two sensors that I'm most concerned about not getting stuck (WAF-based concern). I have set the plugs to turn off/on every few days at 3am. Not trying sense any issues, just brute-force off/pause/on "just in case." The plugs have their own built-in scheduling capability, or you can add them to Google Home or Alexa, and set it up to turn off/turn on there, or use virtual switches to trigger it from HE if you wanted to. Only issue w/the plugs is they complicate the connection of the sensor to power a little (USB adapter fun). 
I just replaced the power supply on the one off mine that stops reporting motion lately about every day, see if that makes a difference. The other 2 rarely stop working. About got the false activity from air conditioner under control by lowering sensitivity with RM rule when it comes on.
1 Like
my one is working well .. but i have it on a apc smart ups.. no drops so far.
The ability to do that (modify sensitivity settings on the fly) in @gassgs updated driver is very cool.
For reference this came a couple months back
Wow, I whiffed on that. Haha.
1 Like
I appear to have one Linptech that has gone south - it's reporting mostion constantly, almost never goes inactive for more than a few minutes. It was constantly active over the weekend when we and the dogs were away for three days. I remotely reduced static sensitivity a few times but that didn't help.
It had worked fine for quite a while. I'm going to reset-rejoin it, but thinking this one may be a return...
No harm, no foul. Been there, whiffed a few myself.
I had one I feared had gone south as well. Had been working fine for quite sometime and then every morning it was stuck active. I would unplug it but still acted funny. Static was set at medium high for a long time and had been working well. Set it to medium and it has been fine now for several days.
1 Like
I only recently bought one of these Linptech zigbee sensors and it worked well on my C7. I just migrated to a C8 Pro this past weekend and this is the only device that has dropped off the network. Everything else has stayed connected.
Anyone else having issues with these devices on a C8?
Cant remember for sure but I may have had problems getting them to connect to my C8. Could be the reason I decided to pull out the C7 after migrating. My 3 Linptechs and one other zigbee device are the only ones on the C7.
1 Like
I have 3 of them connected to one of my C-8's and have had no trouble with long term connectivity, OTHER than their 'stalling' (failing to send motion reports, solved with an unplug, plug, roughly monthly.) They have never dropped in the sense that I have to button click to get them back into pairing mode.
2 Likes
