Hey @muxa Thanks for creating the driver. I got new/first Konke Temp/Humidity sensor, but have problem to install/pair the sensor.
I download and install driver.
By using the Zigbee button at "add devices manual": I can start pairing with channel 15,
but it stop halve way, with a message.
"Found Zigbee device with id 086BD7FFFE9159F6, initializing..."
When I check the log:
[sys:1]2022-01-03 20:41:14.406 Created Unknown Zigbee Device
[sys:1]2022-01-03 20:41:12.058 Zigbee Discovery Running
[sys:1]2022-01-03 20:41:11.056 Zigbee Discovery Stopped
[sys:1]2022-01-03 20:40:11.348 Initializing Zigbee Device 086BD7FFFE9159F6, 12E7
[sys:1]2022-01-03 20:40:11.050 Zigbee Discovery Running
But when I checked devices tab, there is no new device created.
Backside of sensor has the following code.
Konke FCC ID: 2AJZ4-KPFT IC:23777-KPFT
May I have to change model number or have to do something extra, after installing the driver code?
Hey @bkehv and @henrik - Did either of you ever have success with getting your Konke units to pair? I posted Konke pairing issues here. My theory on the Konke Temperature sensor, given my observations, is that there is more than one version of HW/FW for this device. And one of the versions is not compatible with Hubitat. I purchased four units from AliExpress and one works great, but three fail with the same symptoms that you have described. Upon close examination, even though all four have the same model #, there are differences between the working unit and the non-working units. There are differences in the markings on the battery cover, and differences in how the LED flashes when I press the button.
I have the Konke humidity sensor, and this driver. It seems that some times the report of humidity is irregular...every 5 minutes sometimes, 20 mins sometimes and 30 mins sometimes. Is there some internal logic driving this irregularity?
In that series of event, my concern is with the latest one - 52.7%. This was almost 25 mins later. This sensor is used to turn of bathroom exhaust fan, but because of this delay in last few readings, the fan may keep running for more than an hour of extra time simply because the reading got reported later.
Here are the latest readings post 10:23 PM from my previous post:
I integrate these sensors into Hubitat via zigbee2mqtt. They report both temperature and humidity events very frequently. For example, these are the temp and humidity events recorded over the last 5 hours.
But if the sensor hasn't changed enough to report a new value, do you want the bathroom fan turning off (as by definition the humidity hasn't gone down enough yet)? The frequency of reports doesn't really matter, the delta change when it decides to report does. If it doesn't report that just means that the humidity didn't drop enough.
In other words, maybe it takes a lot longer than you think to actually drop the humidity in your bathroom?
For example, in my bathroom the vent has to run for 50+ minutes to get humidity below my off thresh hold.
If both my wife and I shower back to back it takes more like an hour and a half. Graph below shows my exhaust fan, my bathroom humidity sensor (blue line), and the reference humidity reading (purple line).
on those.
