My Linptech connected fine and stayed connected on my C8, but I had repeated instances of several Aqara contact sensors falling off when it was attached. (Attached Linptech, devices fell off. Remove Linptech, devices rejoined and stayed. Re-attached Linptech and devices fell off again.)
So I have all five of my Linptechs on my C7. I also have a lot of Aqara contact sensors on the C7, so it's not like the Linptech is anti-Aqara, just something about my C8 Zigbee connections/repeaters/devices. Other than the issue w/the Linptech my Aqara contacts are rock-solid on my C8.
Looks like the Linptech that was going nutty w/repeated active/inactive events may have calmed down after the reset/re-join. Only been a day, but it's behaving normally again.
I think that changing the sensitivity parameters also performs some kind of re-calibration in background…’At least this is what I have observed with some other mmWave sensors.
If a RM rule is setup to change some of the sensitivity parameters every day or night, will this prevent these random issues?
After the fact, I did try changing sensitivity parameters while I was away for the weekend (via VPN connection to hub) and I didn't seem to get any improvement in the existing bad behavior. Only the reset seems to have fixed the particular issues I was having.
Now whether doing the sensitivity changes proactively before there is a problem would make a difference is another question.
I'm going to let the sensor ride as-is for now, but if it falls back into issues I'll reset it again, and then try setting up a rule as you suggest.
All 3 of mine have been working really well with no problems at all for a while now and all in all any issues have been minor. I am missing some info on this one in the state variables section and dont know how to get it back even tho it does not appear to cause problems I was used to seeing it and it is on the other sensors device pages. Also this one has more info in the data section than at least one of my other ones. Maybe Im to OCD
You can try the following. Change the Linptech to the "Device" driver, clear all states/settings, etc., then re-apply the Linptech driver and do the Configure/Initialize/Refresh dance.
Device driver:
Then: Configure, run all the "Delete" commands, then Get Info.
Well I did the device driver and cleared everything, then back to the Linptech. Put all my settings back, flipped on and off all things including config, refresh, etc. Here is what the states has. Still missing 3 lines?
If you have never enabled Distance Reporting, you'd expect that value to be empty and not displayed. In my case, it might have been days ago that I turned that on for 2 mins and then back to Off. The last value would be reported forever, or to the next reboot. Equally, if you've never changed the sensitivities, they might be blank as well and not displayed.
Interestingly:
The two sensitivity values don't match. Medium, Medium for State Variables, High, Medium for Current States.
If you use the buttons to change those values, when you refresh the page, they revert to High, High:
Well I have set every setting and turned on and off every switch in the driver. My motion and static change with a rule every time the AC comes on and turns off and nothing has been added to this kitchen sensor. Other 2 look like this.
State Variables
packetID : 8
static : high
DriverVersion : 2.0
distance : 4.5 m
motion : medium-high
healthCheck : false
Every thing is working so maybe I should quit dwelling on it
Starting to think that this is how they all should be. I reset and rejoined my device that was only showing 3 state variables, and there is no change in that regard. Perhaps the ones showing 6 are the ones that need to be fixed.
I meant that I was going to fix it till it didn’t work
i am running the full driver and it shows maxiumum distance setting, but is there an attribute that can be exposed to show the distance that the last motion was sensed? or does it not know that?
thanks
i do have ignore distance reports on.. i assume turning that off will do that.. but every second seems like it might be much for the hub?
maybe add an option to only report the distance whenever a motion active report comes in.. and ignore the others?
