I want to check if one of my devices has less than 25% battery
Currently, I have to create a scene with x20 « Retrieve the last state » boxes, followed by x20 tests on these states (I was too lazy, there are only 9):
What I propose as a new feature is the ability to retrieve all values of a certain type.
So here, all the battery levels of all the sensors and check if one of them is below 25%. In this specific case, a message can be sent to me with the name and room of the sensor.
One can imagine a multitude of applications: all temperature values, battery levels, brightness, power consumption of outlets, etc.
Mmmm not stupid, I agree on the problem then I’m not sure if the solution is to do this in the scenes
For the battery story, I think it would be something we might want « natively » in Gladys. Like Gladys warning you, without your intervention, that some of your devices have less than 25% battery
Same for devices that are turned off, receiving an alert in « sensor XX has not sent data for 24 hours » mode
First, a device is not linked to a user (maybe we’re not talking about the same thing?), and moreover, I think presence management is a specific case for each individual and is difficult to generalize.
For example, you might want to manage presence through multiple factors: Wi-Fi presence + Bluetooth presence + OwnTracks (GPS smartphone) + who knows what!
And doing it via scenes allows you to be infinitely flexible, and above all, it’s more understandable/transparent for the user; it’s not something magical.
I understand your point of view, and perhaps it is not the right solution after all.
However, I find that it is still not intuitive when using the presence detection service via Bluetooth.
At a minimum, it would be necessary to explain that you need to create the scene, or even provide an example of a scene?
This way, the basic need is covered (detecting my presence with Bluetooth), but the scene can be modified for advanced users or needs.
Thanks for your support
The more of us who vote, the more important this feature request will be and the more likely it is to be developed by @pierre-gilles or one of the community developers!
I just realized that I made the same scene @lmilcent.
I just integrated 6 sensors and this can be really tedious if there are many more sensors/actuators.
Has anyone started developing this feature?
I took the liberty of putting it in a separate « box ».
What do you think?
What would you say about putting the settings in separate « boxes » to distribute them across the 2 columns?
For now, I set it to every hour; I can change it to 1 or 2 times per week or even make it configurable (I don’t know if that’s possible)
That’s a good idea, but I don’t know if that’s possible. For the moment, I went with a system that « checks » the battery level every day. But if I take your idea, I’d need to notify when the device changes level and therefore « listen » to each change in battery level to check whether it has dropped below 30% for example. I’m not sure if I’m being clear
That works very well for me, we’ll see how it looks in practice but in principle I agree!
I think we can keep it simple for now: once a week at a fixed date/time, like Saturday at 9am for example? (that allows for a notification at the start of the weekend when the user is potentially available to take care of it?)
We should just specify that in the feature description so it’s clear
I like the idea of doing it at a fixed interval, so if we have 5 sensors that start to weaken, we don’t get 5 random notifications during the week but a batch of notifications on a day that makes sense, so the user can tell themselves « Ah, there are 5 devices that are almost dead, I’ll place an order for 5 batteries »
, this could be useful when you have many sensors that run on batteries!
)
