The big day has finally arrived: Gladys Assistant v4.0.0 is available
I published an article on the blog that talks about all this:
This is just the beginning of the adventure, this launch is just the start! Developments will not slow down but rather intensify. I canât wait to see the Zibgee2mqtt, Tasmota HTTP, Bluetooth presence, Awox, and many more
A big thank you to everyone who contributed to this version
A big bravo to the whole team!!
I am one of those people who regularly watch the progress of Gladys without daring to take the plunge, but when I see the work and the motivation that have been provided for this V4, it really makes me want to try!!
Short post for users who had installed Gladys Assistant V4-Beta:
How to go from the beta to v4.0.0?
Case 1: If you had installed the beta « just to test » and you donât have much data on it, I advise you to just download the new Raspbian image from the website and reconfigure an instance, it takes 30 seconds and there is little interest in migrating your data from the old to the new.
Case 2: You have a lot of data on the v4-beta and you want to migrate to the new image.
Connect to your Pi via SSH (login: pi, password: raspberry)
You can stop Gladys by doing:
docker stop gladys
You can retrieve all the files in the folder /var/lib/gladysassistant on your Raspberry Pi, and copy them off your Pi.
Reinstall Gladys with the new Raspbian image, stop Gladys and restore the entire /var/lib/gladysassistant folder.
Then, restart Gladys with the command docker restart gladys
Oh @pierre-gilles the thing is that the Raspberry Pi running Gladys at my place hosts other services. It is not dedicated to Gladys. I may not be the only one in this situation. So is it possible to upgrade to version 4 (non-beta) without starting from a full Gladys image?
Extra thanks! Newbie question, but why doesnât Watchtower automatically update from beta to non-beta? So far, all updates have been completely transparent, and thatâs exactly the role of Watchtower, right?
And I jumped straight into my question, but all my congratulations on this launch, itâs a very beautiful work on your part with the help of the community.
Not yet, voice has not been ported to v4, for now itâs text-based via the interface or Telegram.
I would welcome any help on this part, by the way, if any developers read this message
Because we changed the Docker tag. The beta image was tagged « beta », and now that weâre in stable version, weâre on a stable tag that wonât change anymore
Also, I made significant changes to the Raspbian image (auto-expand of the partition, automatic system update) and I recommend everyone to switch to it so that it works well in the long term! The beta image was really intended for « beta » use