New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Device Support Request] linptech Human Presence Sensor #2599
Comments
Same need here, can anyone help? |
This seems to be working in z2mqtt, I believe. I've had a play with trying to write a custom quirk but I'm not really sure what I'm doing! If anyone is willing/able to help I'd appreciate it! |
I have only today learned about ZHA quirks. If you would like someone to test it let me know. Thanks |
Got mine today, and I only have the occupancy working. Can someone help me to write an ZHA quirk ? |
I tried to use a different quirk that is similar and change it to accept this model. That did not work for me. I am going to look into Zigbee2MQTT but not sure if it works with SkyConnect. |
Picked one of these up. If I can help in some way to get it working with zha let me know |
I would say that writing a quirk for it would be great. |
@felafel can you open a PR with that code? Opening that may show what code did you add to get some advice |
I am not sure if this is helpful but here is what I have. I do not know why it is not being picked up and I have not found a way to see if the quirk is being attempted. I set up the settings I have seen in the YAML file but whether it is being used is a mystery. It would be helpful if ZHA could confirm that it is looking for quirks in my folder, and also, whether it cannot use files that are there for whatever reason. If there is a file there then ZHA should assume I want to use it, I think. `"""Device handler for Tuya ZG-205Z-A Mini 24Ghz human presence sensor.""" import math from zigpy.zcl.clusters.general import Basic, Identify, Ota, GreenPowerProxy, AnalogOutput from zhaquirks import MotionWithReset class MotionCluster(MotionWithReset):
class TuyaOccupancySensing(OccupancySensing, TuyaLocalCluster): class TuyaMmwRadarFadingTime(TuyaAttributesCluster, AnalogOutput):
class TuyaMmwRadarLargeMotionDetectionSensitivity(TuyaAttributesCluster, AnalogOutput):
class TuyaMmwRadarLargeMotionDetectionDistance(TuyaAttributesCluster, AnalogOutput):
class TuyaMmwRadarSmallMotionDetectionSensitivity(TuyaAttributesCluster, AnalogOutput):
class TuyaMmwRadarSmallMotionDetectionDistance(TuyaAttributesCluster, AnalogOutput):
class TuyaMmwRadarStaticMotionDetectionSensitivity(TuyaAttributesCluster, AnalogOutput):
class TuyaMmwRadarStaticMotionDetectionDistance(TuyaAttributesCluster, AnalogOutput):
class MmwRadarManufCluster(TuyaMCUCluster):
class TS0225Radar(CustomDevice): #note: Changed _TZE200_2aaelwxk to _TZ3218_awarhusb. Both appear to be model TS0225
|
Does @danielgomezrico or anyone else have constructive help with the code above? |
I was a bit out of clues about how to build this one, but I want to try |
Bought some of these because they were recommended. Sadly the person that recommended it didn't know about ZHA support (he said it works out of the box, but he meant Z2MQTT. Any news on this? |
I did the same and too have no clue on how to make it better. |
According to blakkadder the device seems to work already. I don't have the opportunity to test it right now, so any updates on this? |
There is an attempted ZHA Quirk above to get the other features to work. Presence itself appears to be in ZHA but the other features do not. Do you have any suggestions on getting the quirk to work? |
I sadly have no experience in Python or ZHA quirks. So I'm just here to ask. 😅 When I use it the way it works now and someone writes a quirk does it automatically work or do I have to re-pair it? |
This comment was marked as off-topic.
This comment was marked as off-topic.
@felafel i understand you may be frustrated but everyone working on these things are volunteers. This isn’t the appropriate place to vent. |
I think it's fair to point out that the official implementation is much worse in many points than a community alternative. The wrong place to vent? Definitely. But he is right in my opinion. I'm really frustrated too. Tried to switch ti Zigbee2MQTT, failed and now are trapped in this. I really wish that ZHA would get much more attention. Not only for Device support. |
What am I missing? All of this is FREE and done by folks in their spare time… ZHA came from the community and is largely maintained by community members… no one forces anyone to use it. everything here in this repo is from the community. The problem is with device manufacturers… they basically do what they want. Tbh, being frustrated is perfectly normal and acceptable but dumping it on folks who put a lot of effort into this in their free time is just not right. Try to look at the situation from the opposite perspective and imagine how you would feel. |
I think my frustration is certainly less about the work of the volunteers, which as you say is entirely supported by the community, and more that I listened to Home Assistant when they announced ZHA as the native support for Zigbee. I was at the time on Zigbee2MQTT and changed over thinking that I was moving to the more stable / supported platform. Since then it's consistently lagged in features and support. For example, at the time I already had OTA updates presented nicely in the UI for Z2M, years late ZHA still handles OTA update incredibly unintuitively. I kept expecting that such basic things were only around the corner, but like the experience of this presence sensor, there's no predictable outcome for ZHA based on what Z2M is managing to do. Expressing frustration at the countless hours spent by volunteers on ZHA is definitely missing the point, and they don't owe anyone anything, but to someone starting a Home Assistant build afresh, they're still encouraged that ZHA is best option for them to set up their Zigbee network, and I just don't think that's proven to be accurate. |
To come back to the initial topic: Has someone already implemented a custom quirk that we could test to get this running? I really would like to use the luminance sensor in this thing instead of trying to guess the current light based on time and weather. 😅 |
I have 5 of these and they work pretty well, however, there is a lag from some of them some time, not sure if this is because of some interference or due to the sensors flooding the zigbee log. Some good news of the LED indicator front, I found to that when pairing these sensors with a TUYA hub, instead of my Z2M network, it pops up saying there’s an update, specifically to allow you to turn off the indicator LED. This does posisble mean that there is now a cluster exposed to be able to configure the LED state over zigbee so anyone that can, please look into whether the LED cluster is exposed and add it to the device configuration. |
Hello everyone, The _TZ3218_awarhusb module uses different clusters than those used by _TZE200_2aaelwxk so we cannot simply add the device, despite the fact that they are both TS0225 models. I tried to implement a quirk that takes into account the signature of the _TZ3218_awarhusb module, without success so far. I'll give you the code I use, if someone has better knowledge than me (first time I'm getting into this), I'm interested :-) I am blocked in particular on two points:
source from which I took inspiration: https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Tuya%20Multi%20Sensor%204%20In%201/Tuya%20Multi%20Sensor%204%20In%201.groovy search TS0225_LINPTECH_RADAR inside the file. "// LINPTECH / MOES are using a custom cluster 0xE002 for the settings (except for the fadingTime), ZCL cluster 0x0400 for illuminance (malformed reports!) and the IAS cluster 0x0500 for motion detection" and of course zigbee2mqtt: Koenkk/zigbee2mqtt#18637 I Hope someone could help with this start : |
Hi, I don't have any experience writing zigpy quirks and at the beginning it seemed to be way above my head but as a complete beginner I was able to write a partially working quirk for TZ3218/TS0225. What is working:
What is not working:
When setting sensitivity or detection distance I get UNSUPPORTED_ATTRIBUTE I would be grateful for any help/feedback |
Hi, I'm also totally new with quirks but yesterday I was able to get this kind of working.... at least I was able to set the https://gist.github.com/mool/d4fb96eaed3d04b9bdbf1d7c1517141c |
Problem description
Request to add support for the linptech Human Presence Sensor ( aka Moes Human Presence Sensor -- might be a rebrand of the linptech )
It looks like folks in this thread are getting close to having it working in zigbee2mqtt.
Solution description
Integration into ZHA or zha_quirk to get the device working in HA.
Screenshots/Video
No response
Device signature
Device signature
Diagnostic information
Diagnostic information
Logs
No response
Custom quirk
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: