-
Notifications
You must be signed in to change notification settings - Fork 675
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
Add some ts0601_motion devices (with Tuya MCU Cluster approach) #1315
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #1315 +/- ##
==========================================
+ Coverage 80.97% 81.11% +0.14%
==========================================
Files 217 217
Lines 6008 6054 +46
==========================================
+ Hits 4865 4911 +46
Misses 1143 1143
Continue to review full report at Codecov.
|
Pull Request Test Coverage Report for Build 1781218346
💛 - Coveralls |
The tamper attribute looks very OK. One way is having the "tuya battery attribute" and also doing the % converting (then USB = 100% *2) to the normal battery attribute for getting the normal ZHA battery sensor showing "somthing" and the user can getting the real sate from tuya battery attribute if they like that. |
This PR will add support for some
ts0601_motion
devices.The new devices will follow the new 'Tuya MCU Cluster' approach to update device attributes.
Fixes: #1236
Reported motion sensor 'NAS-PD07' manufactured by NEO.
Most of the code came from 'herdsman-converters'
Those DPs that have been possible are reported as a new cluster.
Those that I have not found a match for are reported as attributes of the MCU cluster.
Not sure about possible
tamper
values. Probably there are diferent values >0 with other meanings.Fixes: #1312
Unknown sensor, from unknown manufacturer.
The functionality of most DPs is unknown. They are probably used to configure device settings.
The known DPs (
occupancy
,illuminance
,target_distance
) have been implemented according to the information provided by the manufacturer.