-
-
Notifications
You must be signed in to change notification settings - Fork 288
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
Z2m cover feature #1577
Z2m cover feature #1577
Conversation
Codecov ReportBase: 96.77% // Head: 96.77% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #1577 +/- ##
=======================================
Coverage 96.77% 96.77%
=======================================
Files 654 654
Lines 9662 9664 +2
=======================================
+ Hits 9350 9352 +2
Misses 312 312
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Patched my production server to test with my device discover json {
"name": "Volet chambre Sasha",
"model": "CCT5015-0001",
"external_id": "zigbee2mqtt:Volet chambre Sasha",
"features": [
{
"name": "State",
"min": -1,
"read_only": false,
"has_feedback": true,
"category": "shutter",
"type": "state",
"max": 1,
"unit": null,
"external_id": "zigbee2mqtt:Volet chambre Sasha:shutter:state:state",
"selector": "zigbee2mqtt-volet-chambre-sasha-shutter-state-state"
},
{
"name": "Position",
"min": 0,
"read_only": false,
"has_feedback": true,
"category": "shutter",
"type": "position",
"unit": "percent",
"max": 100,
"external_id": "zigbee2mqtt:Volet chambre Sasha:shutter:position:position",
"selector": "zigbee2mqtt-volet-chambre-sasha-shutter-position-position"
}
],
"should_poll": false,
"service_id": "0fccf6a6-0377-4678-b244-30d650619a42"
} Not sure how I can help ( no log in server and no log in front ) I'va added the device manually in db Button not working, level feature does. |
@atrovato If it help
|
@VonOx don't you miss a commit? I think you forgot both 8dc7103 and 8f81ccc commits (https://github.com/GladysAssistant/Gladys/pull/1576/commits). |
Read again, softly, I agree there is another problem. |
I don't think so, I used a patch file. 🤔 I will manually check every file tomorrow. |
I pushed a new commit on z2m part, for the "readValue" error. |
I've applied commit Not working, and no error in logs for button. But position throw error. ( the slider is working )
|
44c105d
to
e32a6ad
Compare
This constant is in a server file I just rebase from #1576 branch (which was just rebased from latest merged changes on master branch). |
9464a4b
to
19e5aa3
Compare
Tests in progress (I hope): https://community.gladysassistant.com/t/gestion-des-volets-roulants/5693/54?u=alextrovato |
Nice ! Can I merge ? |
Yes no error with my device |
19e5aa3
to
af30069
Compare
I just rebase on master. Thanks @VonOx |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing work, thanks @atrovato 🙏
Job #516: Bundle Size — 7.02MB (+0.01%).Changed metrics (2/10)
|
Pull Request check-list
To ensure your Pull Request can be accepted as fast as possible, make sure to review and check all of these items:
npm test
on both front/server)npm run eslint
on both front/server)npm run prettier
on both front/server)npm run compare-translations
on front)[ ] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code)[ ] If you are adding a new features/services which needs explanation, did you modify the user documentation? See the GitHub repo and the website.[ ] Did you add fake requests data for the demo mode (front/src/config/demo.js
) so that the demo website is working without a backend? (if needed) See https://demo.gladysassistant.com.NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.
Description of change
Linked to
Manage cover with z2m.