Skip to content
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

Sonoff: improve device compliance #627

Merged
merged 34 commits into from Mar 28, 2020

Conversation

atrovato
Copy link
Contributor

@atrovato atrovato commented Dec 8, 2019

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:

  • If your changes affects code, did your write the tests?
  • Are tests passing? (npm test on both front/server)
  • Is the linter passing? (npm run eslint on both front/server)
  • Did you run prettier? (npm run prettier on both front/server)
    - [ ] 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.json) 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

Complete the device compatibility.
Remove manual creation.
Rename to Tasmota.

@atrovato atrovato force-pushed the sonoff-missing-devices branch 2 times, most recently from 72417ec to b283721 Compare December 14, 2019 11:01
@atrovato atrovato force-pushed the sonoff-missing-devices branch 2 times, most recently from a3d3af7 to e9b14a3 Compare December 24, 2019 09:00
@Pierre-Gilles Pierre-Gilles moved this from To do to In progress in Gladys 4 Development Dec 28, 2019
@atrovato atrovato marked this pull request as ready for review January 19, 2020 13:24
@atrovato
Copy link
Contributor Author

atrovato commented Mar 2, 2020

Please @Pierre-Gilles don't forgot this PR, it a great refactor :)

@Pierre-Gilles
Copy link
Contributor

@atrovato Don't worry, but the PR is really huge so it'll take a lot of time to review it.

For now all my time is dedicated to the scene feature, hope you'll understand! 😄

@atrovato
Copy link
Contributor Author

atrovato commented Mar 7, 2020

I understand, please don't forget it :)

@Pierre-Gilles
Copy link
Contributor

Hi ! I'm reviewing your PR and wanted to see the code coverage, I don't understand why the coverage is never reported on this PR specifically (works with other PR...)

I think it's because tests are passing on your CircleCI, not Gladys Assistant CircleCI ! Any idea ?

@atrovato
Copy link
Contributor Author

atrovato commented Mar 9, 2020

It don't work all the time, on other PR too.
I try a rebase too force it.

Copy link
Contributor

@Pierre-Gilles Pierre-Gilles left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi !

First, thanks for this really great PR ! 🙂

There is lots of work here, and quality work, no doubt =)

I noted a few feedbacks, most of them are just question, no change required.

There is just 2-3 comments with minor changes asked, but otherwise the rest of the code is perfect !

I'm looking forward to your answers to integrate this into Gladys !

server/utils/constants.js Show resolved Hide resolved
server/utils/constants.js Show resolved Hide resolved
server/services/tasmota/lib/setValue.js Show resolved Hide resolved
server/services/tasmota/lib/setValue.js Show resolved Hide resolved
Gladys 4 Development automation moved this from In progress to Review in progress Mar 9, 2020
@atrovato
Copy link
Contributor Author

atrovato commented Mar 9, 2020

I have following URL on push coverage step:
https://codecov.io/github/********/Gladys/commit/a040e91670c8c62d985f8718e1ca0089575db03f

But ****** should be GladysAssistant or atrovato.

@Pierre-Gilles
Copy link
Contributor

I have following URL on push coverage step:
https://codecov.io/github/********/Gladys/commit/a040e91670c8c62d985f8718e1ca0089575db03f

But ****** should be GladysAssistant or atrovato.

When I think about it I'm not sure this can work... Does codecov allow a forked repo to push data on my Codecov account ? I think it would be a security issue and I don't know if they allow that

No worries, I can push your branch on Gladys main repo before merging to have a full build in any case.

@Pierre-Gilles
Copy link
Contributor

Pierre-Gilles commented Mar 9, 2020

In fact, it works on other PR from fork!

Example:

https://codecov.io/gh/GladysAssistant/Gladys/pull/675

Maybe you are doing something differently? Did it work in the past for others PR you did?

@atrovato
Copy link
Contributor Author

atrovato commented Mar 9, 2020

Ok, for test coverage, I unfollow my own GitHub repository, URL looks good for now.

@codecov
Copy link

codecov bot commented Mar 9, 2020

Codecov Report

Merging #627 into master will increase coverage by 0.16%.
The diff coverage is 98.09%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #627      +/-   ##
==========================================
+ Coverage   91.88%   92.05%   +0.16%     
==========================================
  Files         393      410      +17     
  Lines        4967     5134     +167     
==========================================
+ Hits         4564     4726     +162     
- Misses        403      408       +5
Flag Coverage Δ
#server 92.05% <98.09%> (+0.16%) ⬆️
Impacted Files Coverage Δ
server/services/tasmota/lib/disconnect.js 100% <ø> (ø)
server/utils/constants.js 100% <ø> (ø) ⬆️
server/services/tasmota/lib/connect.js 100% <ø> (ø)
server/services/tasmota/index.js 100% <100%> (ø)
server/services/tasmota/lib/notifyNewDevice.js 100% <100%> (ø)
.../services/tasmota/lib/features/colorTemperature.js 100% <100%> (ø)
server/services/index.js 100% <100%> (ø) ⬆️
...rver/services/tasmota/lib/features/energy.power.js 100% <100%> (ø)
server/services/tasmota/lib/features/power.js 100% <100%> (ø)
server/services/tasmota/lib/mqtt/status.js 100% <100%> (ø)
... and 47 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 65624b6...32ff778. Read the comment docs.

Gladys 4 Development automation moved this from Review in progress to Reviewer approved Mar 28, 2020
@Pierre-Gilles Pierre-Gilles merged commit fd658f7 into GladysAssistant:master Mar 28, 2020
Gladys 4 Development automation moved this from Reviewer approved to Done Mar 28, 2020
R6n0 pushed a commit to R6n0/Gladys that referenced this pull request Dec 2, 2020
…#627)

* Sonoff: improve pow device and mqtt topics

* Sonoff: manage Dual R2

* Sonoff: dual R2 setValue Power1/2

* Sonoff: add arilux-lc01 device

* Sonoff: split methods

* Sonoff: improve test coverage

* Sonoff: refactor device list

* Sonoff: manage Sonoff SV device

* Sonoff: manage Sonoff Dual device

* Sonoff: manage 4CH device

* Sonoff: rename device files

* Sonoff: manage Slampher device

* Sonoff: manage Sonoff Touch device

* Sonoff: manage Sonoff LED device

* Sonoff: manage 1/4 Channel devices

* Sonoff: fix device discover

* Sonoff: edit device features

* Sonoff: delete manual creation

* Sonoff: refactor device box

* Sonoff: fix typo

* Sonoff: refactor device and handle updates

* Sonoff: fix refactor impacts

* Sonoff: manage not managed device

* Sonoff: oops - fix tests

* Sonoff to Tasmota

* Tasmota: add more devices

* Tasmota: refactor feature discovering

* Tasmota: dynamic discover

* Tasmota: add components

* Tasmota: improve UI

* Tasmota: fix feature label and icon

* Tasmota: display featuren name

* Tasmota: remove front pagination

* Tasmota: rollback dashboard display
@atrovato atrovato deleted the sonoff-missing-devices branch November 28, 2021 20:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

None yet

2 participants