Ability to stop keeping the history of certain features to save DB storage and improve performance
=> in the DB I indeed only have the last value for the feature where I disabled history and all the data for the others
Hello,
quick question about this release..
under utils/constants.js for Precipitation units would it be possible to add « millimeter per day »?
indeed when we retrieve precipitation from an external station via nodered/zigbee the station sends cumulative precipitation volumes over the hours during the day (with reset to zero at midnight)?
moreover I noticed that some Lidl/SilverCrest home automation devices under zigbee are compatible with Gladys (plug, presence sensor, …) but not the power strip spsz"a1 connected ((3 outlets + 4 USB, each identified independently by zb) this plug is identified by z2m (but mentioned as not supported), do you know if it’s planned by z2m?
for VOC I have the Xiaomi vockqjk11lm sensor for some time, I was getting temperature and humidity, but not VOC so I’m eagerly awaiting the arrival of the release
I gave feedback on it again yesterday. The OAuth 2.0 part of the code isn’t very robust.
Why not in a future release, yes! But if you want it to work with Zigbee you can’t just add the unit — there’s probably code to write in the Z2M part as well
Dramatic improvement in performance on dashboards with charts => it’s much faster
LQI Zigbee2Mqtt => Maybe we could add the LQI value on hover in a future version
Option to stop keeping the history of certain features to save DB storage and improve performance => My database went from 2.5GB to 400MB by removing 4 features (outlet current and voltage). I think this will be beneficial for large databases. Disabling can take a long time (if there is a lot of data to delete)
That’s probably not just what had an impact, basically when you delete feature histories, Gladys runs a « VACUUM » SQLite at the end of the deletion so the DB is actually purged.