Quick question. Since these work magnetically does the sensor just detect "a" magnetic field as opposed to "not a" magnetic field? Or is there a way to use more than one magnet to one sensor?
And if there is, is it possible to write a driver that'll accept different values of magnetic to indicate different values of closed (ie a window with 2 panels and a central bar, with a trigger magnet on the panel and the sensor on the bar)? So you'd get - all closed - one open - both open - other open options for actions.
Just a random thought.
Driver works fantastically with the ones I got in the aliexpress tat-hunters sale.
Managed to get hold of 2 tuya Wi-Fi T/H sensors, 2 tuya zigbee T/H and 3 tuya zigbee contact sensors with one that has a tamper sensor on it, that'd be good to have working (it's a little release to make switch so it trips when someone removes the sensor). They should be good to go with CR2032 upgrades over the CR2016 I think in there for a good bit of battery life help.
and I’ve been using this driver with excelent results.
My request is because I can see that the driver was not built for this specific device, and there are some adjustments that I believe are needed for it to perform accordingly to this device.
a) this Contact sensor does NOT have a temperature sensor, but still it shows some temperature value. It has to be removed for this specific model.
b) it would be very helpful if an option or button to set as Open or Closed as required is added.
Sometimes when there is a blackout, and the door physically changes state, there is no way to correct it like on other drivers, (when this has to be done remotely), only if driver on the device is changed to Device, adjusted, and changed again to the previous (this) driver. Or maybe if power is back on, and door is opened and closed again it will update properly.
@kkossev please let me know if you need specific information about this Xfinity sensor, and thank you for your hard work helping us with our toys we enjoy so much.
This doesn't look correct.... The Zigbee model and manufacturer data is missing, so from a driver perspective it is not possible to identify this device. I expect the model URC4460BC0-X-R and manufacturer 'Universal Electronics Inc'. But I will also need the inClusers list.
Please switch back to the HE inbuilt 'Device' driver and click on the 'Get Info' button, while activating/deactivating the contact sensor at the same time. I will need the fingerprint that should appear in the live logs.
Also, according to Zigbee2MQTT this device has a temperature sensor.
Yep, this is an another device ( Leedarson seems to be the actual manufacturer in China), but it also exposes the temperature cluster and most probably starts to report the temperature automatically.
Are the temperature reading inaccurate? Do you want them disabled?
Please update to the latest development version. The fingerprint is not there yet, but there is an option to sync the contact state on every battery report. Maybe this will help ?
Let me do some more testing.
That temperature valve doesn’t seem right, besides it doesn’t change very often.
Will set a thermometer next to it to see if it’s of any use.
Thanks!
Edit:
Temperature value didn’t change from 9:00 pm (last night) to 7:00 am (this morning).
It doesn’t update at all!
Would it be possible to have a switch in the driver to disable luminance? I added a few of my new Ali Express contacts with this driver and all is definitely very well with battery level and contact sensing. But one model is sensing luminance, which I don't even think is a feature it has. Number bounces around when contact is changed, but even putting it in pitch black reads a high number. I'd just like to disable it.
Agree, this device illuminance readings are very flaky! : (
You can update the driver manually :
ver. 1.2.2 2024-06-14 - (dev.branch) - added ThirdReality tilt sensor 3RDTS01056Z; new _TZE200_pay2byax fingerprint; added preference to disable illuminance @Big_Bruin
Uhhh... now I see that it is not very clear what state of the toggle means disabled and which means enabled... Do you have an idea to improve the name of the preference and the help text?
Leave the name, and maybe say "Select this option to disable the illuminace (lux) events"?
But I suppose this could hinge on what you (as the dev) want to set as the lux-reporting default (enabled or disabled)...
My suggestion above presumes it's not already selected by default... If you decide it should be, then I'd condsider "flipping" the elements accordingly -- hope that makes sense!
