Pre-release test v4.10.0: Broadlink, Roller shutters, Performance 🚀, LQI Z2M, VOC Z2M, Keep history, Webcals

Hi everyone!

We’re back from summer, and I’ve merged quite a few PRs that progressed over the summer, notably:

  • Synchronization of Webcals calendars

And many other changes, full list here: Comparing v4.9.2...master · GladysAssistant/Gladys · GitHub

I’m looking for testers before hitting the « release Â» button :slight_smile:

To test, I built an image on the dev tag:

gladysassistant/gladys:dev

If you test, please say what you tested, and what worked / or didn’t!

Thanks to those who will test :folded_hands:

5 Likes

Hello,

j’ai fait un test sur :

  • LQI Zigbee2MQTT

  • VOC Zigbee2MQTT


    => it works well

  • 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

2 Likes

Big release :eyes:

2 Likes

What about the Withings service?

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 :slight_smile:

Okay, thanks for the feedback :slight_smile:

I looked into it; to me there is no Zigbee device that reports this kind of feature. It must be MQTT.

Here is my test feedback :

  • Dramatic improvement in performance on dashboards with charts :white_check_mark: => it’s much faster
  • LQI Zigbee2Mqtt :white_check_mark: => 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 :white_check_mark: => 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. :warning: Disabling can take a long time (if there is a lot of data to delete)
2 Likes

Could someone tell me how I can find out the size of my database (DB) ?
How can I see the change after deleting unnecessary data !

On your Pi over SSH

ls -l --block-size=M /var/lib/gladysassistant/*.db

1 Like

Great, thanks for your reply @cicoub13 !

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.

It must have cleaned up

:eyes:

1 Like

Wouldn’t it be interesting to trigger this VACUUM as a task once a week/month during the night?

:shushing_face:

Yes, good idea, I think it would be nice to integrate it into the routine that cleans up the states :slight_smile:

It’s released!

If you have any other feedback, don’t hesitate and we’ll include it in a future release!

1 Like