Problem with data reporting to DBs

[pierre-gilles]

@Kevin

12 hours? I have a sensor that was disconnected for more than a week and the displayed information stayed the same. Should we normally see something else displayed?

Yes you should see this:

Is that not the case?

@Kevin

But for me, a door sensor is the same principle. If the sensor has been disconnected for more than a week, it can prevent some scenes from working, for example. Especially if we don’t know that the sensor is disconnected from the system.

I think we’re talking about two different things.

As things currently stand, the Gladys interface has no notion of a « connection » with devices, it just sees when the last value report occurred. For a temperature sensor that sends a value every hour, for example, you can deduce after 12 hours that there is an issue. For a door open sensor, after 3 days that doesn’t mean anything — the sensor may be fully functional, the door just hasn’t been touched in 3 days…

Edit: There is already a feature request for that, feel free to vote for it!

Alerter et créer un statut "Indisponible" d'un équipement (plus de batterie, connexion, etc.)

Feature description Gladys m’avertit lorsqu’un capteur ne fonctionne plus, ne capte plus ou ne renvoie plus de données. Contexte J’ai une domotique 100% Zigbee, avec une majorité de Xiaomi en direct sur Gladys. Actuellement, la dernière valeur connue est toujours utilisée dans les scènes, comme si le capteur fonctionnait toujours. Je m’en suis aussi rendu compte parce que la scène qui m’averti lorsqu’une pièce est trop humide depuis plusieurs heures me renvoyait toujours la mê…