Hello,
Would it be possible to create a new box for activating or deactivating a scene from the Dashboard?
Given that the integration of sirens and various gas sensors is underway in the Z2M integration, it would be interesting to be able to activate an « Alarm » scene directly from the dashboard.
guim31
March 17, 2022, 5:11pm
2
You don’t really need a box for this.
You create a fake MQTT device of the switch type (which you will display on your dashboard) and you create a scene whose scenario is:
When the state of my MQTT device changes
Trigger scene X
And that’s it!
1 Like
Indeed, I agree with @guim31 for the hack!
But I think this request is still useful, we’ll keep it!
1 Like
I removed the « Solution » then, thanks to both of you!
Lokkye
April 18, 2022, 4:19pm
6
Hello everyone,
I made a small proposal for this request:
master ← callemand:DashboardScene
ouvert 04:15PM - 18 Apr 22 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)
- [ ] If you are adding a new features/services, did you run integration comparator? (`npm run compare-translations` on front)
- [ ] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to [the community](https://community.gladysassistant.com/) for testing before merging.
- [ ] 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](https://github.com/GladysAssistant/v4-website) and the [website](https://gladysassistant.com).
- [ ] 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](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
Proposal for this feature request : https://community.gladysassistant.com/t/dashboard-activer-ou-desactiver-une-scene/7072/3
Add new boxes to display scene. We can activate or deactivate scene from this new box
<img width="559" alt="Screenshot 2022-04-18 at 18 08 37" src="https://user-images.githubusercontent.com/11317212/163838161-95a0a61c-224d-4d08-8b70-1743a2464cef.png">
<img width="549" alt="Screenshot 2022-04-18 at 18 21 20" src="https://user-images.githubusercontent.com/11317212/163838942-af770f42-a5ec-4583-9abd-c87e7bd1c13a.png">
I wondered if we shouldn’t choose a list of scenes instead of a single scene, what do you think?
All feedback is welcome
1 Like
Top thanks for the proposal @Lokkye !
Just a question about the purpose of this feature, was the idea to add a button to « enable/disable » a scene, or « trigger » a scene?
Because the title doesn’t match the messages below
Lokkye
April 26, 2022, 5:20pm
8
@pierre-gilles from what I understood from the messages, it was just to activate or deactivate a scene, but I can add a button to trigger it in the same box if needed.
This message made me think the opposite, it clearly talked about triggering:
After that, the two features are interesting, I agree!
To be tested if everything should be in the same box, or two different boxes, it shouldn’t be too loaded for mobile use
3 Likes
I reviewed your PR, and indeed the current implementation is not clear.
The box displays the date of the last execution, so you’d expect that clicking the button executes the scene, but that’s not the case!
All my comments are available here:
master ← callemand:DashboardScene
ouvert 04:15PM - 18 Apr 22 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)
- [ ] If you are adding a new features/services, did you run integration comparator? (`npm run compare-translations` on front)
- [ ] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to [the community](https://community.gladysassistant.com/) for testing before merging.
- [ ] 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](https://github.com/GladysAssistant/v4-website) and the [website](https://gladysassistant.com).
- [ ] 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](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
Proposal for this feature request : https://community.gladysassistant.com/t/dashboard-activer-ou-desactiver-une-scene/7072/3
Add new boxes to display scene. We can activate or deactivate scene from this new box
<img width="559" alt="Screenshot 2022-04-18 at 18 08 37" src="https://user-images.githubusercontent.com/11317212/163838161-95a0a61c-224d-4d08-8b70-1743a2464cef.png">
<img width="549" alt="Screenshot 2022-04-18 at 18 21 20" src="https://user-images.githubusercontent.com/11317212/163838942-af770f42-a5ec-4583-9abd-c87e7bd1c13a.png">
I’m closing this thread because this feature was implemented a long time ago