I really like the visual and the idea, especially. I try to do this kind of thing as best I can, but it will clearly be more functional through a dedicated interface.
A mini tablet in the entrance for the Gladys interface and that’s it!
Wow, I came across this topic and guess what… I made a mockup for managing something similar!
@pierre-gilles I wouldn’t take on all the projects but when I have ideas, I note them down and it can help advance the idea for others… (more skilled developers than me)
@syper Don’t worry, I always say the same thing: code is only 10% of development.
The hardest part is agreeing on specifications (both functional and technical)
I’ve actually had quite a bit of feedback on your proposal!
First, I get the impression that you’re reinventing the wheel in terms of many mechanisms that we already have in Gladys.
Typically, all the programming/what happens when an intrusion is detected/etc., should, in my opinion, be entirely managed in the scenes, rather than recoding a similar mechanism outside. This allows the user to create very rich scenes, with the alarm that can be activated automatically when certain criteria are met, that kind of thing.
Then, in my opinion, the alarm management should be done at the « house » level and not at the « global » level in Gladys, because you can manage multiple houses in Gladys.
If you have 2 houses: a main residence and a secondary residence, you won’t activate the alarm globally, you want to set the alarm on your main residence when you are on vacation in the secondary residence, and vice versa.
After that, I think there are some very good ideas in your proposal too, and I think we need a hybrid approach between something « super generic » as I propose, and something « too specific » as you propose. It needs to be powerful, but simple to understand and implement
Typically, all programming/what happens when an intrusion is detected/etc., should, in my opinion, be entirely managed within the scenes, rather than re-coding a similar mechanism outside. This allows the user to create very rich scenes, with the alarm that can be automatically activated when certain criteria are met, that kind of thing.
Indeed, but for beginners, scenes are not the best. So I’m torn because indeed, scenes fulfill their function …
Next, alarm management should be done at the « house » level in my opinion, and not at the « global » level in Gladys, because you can manage several houses in Gladys.
I hadn’t thought of that
After that, I think there are very good ideas in your proposal too, and I think we need a hybrid approach between something « super generic » as I propose, and something « too specific » as you propose. It needs to be powerful, but simple to understand and implement
Hello @pierre-gilles,
I wanted to know if you were able to make progress on this kind of change?
Is this 100% core?
Or will this change be part of an alarm-type module?
I haven’t touched this subject! It’s 100% core, yes.
Depending on the other topics (everything is constantly evolving), I could work on it in Q3 2023, but to be honest, despite the number of votes it’s really not at all my priority, I have many many many other topics that I see as more of a priority for the life
I think it would be useful to distinguish Gladys devices that are « wall-mounted tablets with open access » from devices like « my phone/personal computer ».
For that, I propose adding a button on the dashboard:
I find the whole setup rather good!!
It reproduces almost the same functionality as what I have at home, with the added « screen lock », which I think would be a big plus!!
I have a quick question, to come back to the request to make Gladys « speak ».
Is it possible, in the development of this feature, to include a few short phrases / a few sounds to play on the tablet in question?
Like: