I purchsed this item ZigBee Human Presence Sensor and added to my Home Assistance with SkyConnect cordinator without issues. However, when I open it there is no information what so ever. Does not have any sensor data. Check the image to see.
I tried it with the normal Smart Life app and it worked, but not under Home assistant. Please help? i dont want to use Tuya integration, I want it local. Thank you.
P.S. I am newbie into HA so please be patience and speak plain English :))
Unfortunately you canât assume that a device with the ZigBee logo will be supported. It can take a while for new devices to be supported because developers need to invest time to create the compatibility within ZHA.
A good resource for checking compatibility is here
Hopefully your device will be supported at some time soon.
Thank you very much for the replay and the explanation. As I explained I am brand new into HA but big enthusiast so, I will try to follow this forum and get more experienced. I guess I will use the Tuya integration for now, and hopefully later on it can natively be applied into ZHA.
Can anyone suggest a good native ZHA Human Presence or Occupancy sensor that is also widely available and on budget? I live in eastern Europe where there is no amazon, and such gadgets can only be purchase on AliExpress and eBay most of the time. Thanks again.
Zigbee devices that do not use standard configuration and parameters (standard ZCL clusters and attributes) will need a custom handler/converter/translator as Python script code in âZHA Device Handlersâ repository to extend custom support for specific non-standard devices (which the ZHA integration then makes use of).
If you can not code that Python script code yourself to write the needed custom handler/converter/translator for adding that specific device to the âZHA Device Handlersâ repository/library then suggest submitting a âdevice support requestâ as new issues â https://github.com/zigpy/zha-device-handlers/issues
Without a âdevice support requestâ as a new issue posted to the âZHA Device Handlersâ repository/library requesting support for an unsupported device or device feature with Device signature and Diagnostic information the ZHA integration developers will not even know about the device unless they by random chance happened to have bought it themselves.
I have this device and have it commented to ZigBee2MQTT
I will say that Iâm really struggling to have it working reliably. It will happily sit there and detect if there is activity but it is very erratic. It will drop back to âawayâ when there is clearly activity and on the flip side will stay in âhomeâ state when there is clearly no activityâŚ
Iâve tried fiddling with the settings but havenât managed to find a setting which is reliable
Would love to know if others have similar experience
Jumping into this conversation as Iâve just bought some of these sensors from AliExpress and have mixed results. Iâm using ZHA as the integration but had to do a little hacking to get it to show all the settings that you get by default using ZigBee2MQTT. I have two, one in the kitchen which works pretty flawlessly and one in the lounge that currently wonât revert to âclearedâ after the idle time. I have the exact same settings on both so currently testing using different power bricks or usb cables. Very promising though and easier to automate than the Xiaomi presence sensors that have a two minute cooldown detection and battery powered. As Iâm typing this the Lounge sensor has cleared so potentially it was the power adapter I was initially using - will report back on success or failure!
I have this device and use it with ZigBee2MQTT. I have the same experience as you, except for the false positives. I noticed that the distance measurements are erratic, so tweaking the max distance is essential.
I have not been able to fix the false negatives (incorrecting reporting âawayâ). I noticed this mostly happens when I dont move at certain angles. It also happens when I lie flat and dont move. What I do now is fading time to 15 min or so. But of course this is not always ideal.
Sadly not yet, Iâve fiddled to make it workable but I still find myself on the toilet in the dark on occasion
I actually intend to try it in a new position (thankfully I didnât go straight in and mount it in the roof as I intended, instead 3d printed a temporary enclosure!!)
Agree that dialling in is needed. My false positives donât really happen now I reduced the max distance, but it will regularly switch to away when Iâm sitting there
Honestly, itâs no better than the PIR I was using before and slower to react (I still use the PIR for this reason)
Got this working on ZHA with a custom quirk, but only the basics. Sensitivity/Detection Distance leaves a lot to be desired. If that can be rectified it might be viable. As is, itâs good for about 4-5ft.
I too find inconsistent behaviour. Sitting side by side, they report different values for presence and lux.
I purchased 2 with one powered by DC and the other AC. No amount of fiddling with settings makes these reliable Iâm afraid.
For those talking about the ZY-M100, thereâs an active thread here about ZHA support that I think can now expose all the other features of the device so you can finally tweak the settings:
I pretty much followed the link posted earlier by @Rofo. The latest update 2023.03.0 broke it but there has already been an update on the git page to fix it (I can confirm it works). https://github.com/zigpy/zha-device-handlers/pull/1928
In short, you need to create a new folder called custom_zha_configs in your main HA config folder using something like Studio Code Server. Then create a new file called ts601_motion.py and copy and paste the latest code from the above link (use the copy button when you hover over the code in the top right).
Then in your config file in HA, you need to add the below (âzha:â should already be there if youâre using it so just an indented line after that bit)
I was having issues and I think I narrowed it down to using an old phone charger that was adaptive voltage. Once I switched to a standard 5v 1A charger, itâs worked perfectly
