This feature is quite crucial indeed, and quite simple to develop, so I moved its development forward despite it having few votes
I worked on it yesterday afternoon and this morning:
Control of a multilevel device
Control of a color device
Control of a lamp temperature
Control of a binary device
Actually, the goal of this new action is to be able to control absolutely all types of devices in the scenes. Yes, it is redundant with the « turn lights on/off » or « turn outlets on/off » actions, but these two actions are, in my opinion, « shortcuts » to go faster and turn on several lamps at once
The PR is here:
master ← new-state-action-scene
ouvert 03:02AM - 15 Jul 21 UTC
### Pull Request check-list
To ensure your Pull Request can be accepted as fa… st as possible, make sure to review and check all of these items:
- [x] If your changes affects code, did your write the tests?
- [x] Are tests passing? (`npm test` on both front/server)
- [x] Is the linter passing? (`npm run eslint` on both front/server)
- [x] Did you run prettier? (`npm run prettier` on both front/server)
- [x] If you are adding a new features/services, did you run integration comparator? (`npm run compare-translations` on front)
- [x] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code)
- [x] If you are adding a new features/services which needs explanation, did you modify the user documentation? See [the GitHub repo](https://github.com/GladysAssistant/v4-website) and the [website](https://gladysassistant.com).
- [x] 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](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
Please provide a description of the change here. It's always best with screenshots, so don't hesitate to add some!
