Gladys Assistant v4.7.3 is available!

News
1

Hello everyone!

Since this morning, Gladys Assistant v4.7.3 is available and brings 2 changes that may seem minor but are quite important :slight_smile:

The changes

The complete changelog is available here.

How to update?

If you installed Gladys with the official Raspberry Pi OS image, your instances will update automatically in the coming hours. This may take up to 24 hours, no need to worry.

If you installed Gladys with Docker, make sure you are using Watchtower (See the documentation)

Congratulations to everyone who participated in this release!

2

Missing more than the « at the same time Â» condition is in the air of the times !!! :scream: :innocent: :rofl:

3

Is that « at the same time Â»?

4

the « at the same time Â» of our dear President!!! :innocent: I’m being told in my earpiece that we’ve lost @pierre-gilles there!!! :crazy_face:

5

Hello Pierre-Gilles
test performed, it works.
I have a scene that uses the time condition Ap18h30 and Av 8h30 to turn on an outdoor lamp that works correctly and more simply now, thanks to you :grinning:. I just need to delete my old scene that used Node Red.
Have a good day

6

Thanks for your feedback @Psoy! :slight_smile:

7

It’s day and night in terms of response time at my place :hushed_face:
Gladys has found all her youth again :sweat_smile:

Thanks!!

8

After my Gladys instance crashed (no crash, actually a child unplugged my RPi’s power supply haha), I’m restarting it tonight. I’m still on 4.7.2, is there a way to force watchtower to update?

EDIT: I didn’t find a way to force watchtower… Especially since by restarting it, I extended the duration before the update check…
So I restarted watchtower with a very short interval (every hour) to be less frustrated :grin::grin::grin:

9

And yet, it’s possible with the run-once command :slight_smile:

See doc:

Example:

docker run \
  --rm \
  -v /var/run/docker.sock:/var/run/docker.sock \
  containrrr/watchtower \
  --cleanup --include-restarting --run-once

This command can be run alongside the existing watchtower, it will force an update, and then this container will be automatically deleted thanks to the « â€“rm Â» option

10

You will be timeouted by DockerHub and will probably miss the next update (you will get it later)

From what I remember, it’s a 6-hour softban.

11

Oh ok, I had seen this command but I was afraid it might not be compatible with the container already running! :+1:

Do you know what the minimum interval I can use is?
I already had this issue on my NAS, but it was because the updates concerned 20 apps.
I’m not sure if this will lead to a soft ban.
Has this ever happened to you?

EDIT: I just read this:

Anonymous and Free Docker Hub users are limited to 100 and 200 container image pull requests per six hours.

I should be fine!

12

Yeah that’s right I knew there were 6 hours in history :sweat_smile: