TerrariumPI

Release 4.11.1 - Maintenance update

With this update we fix some small issues and updated all external libraries.

Updated the Docker builds to make them a bit faster and smaller in size.

Added some extra warnings at the documentation pages for the DHTXX sensors.

A new Portuguese translation is added by MakoShark2 and other languages are updated.

It has been 10 years now when this project started. It started all to learn a new programming language Python, and as a lazy programmer does, to automate stuff.

Release 4.11.0 - Brighten up the displays

In this update, the big changes are in the notification system. The biggest change is the Display code and logic. The code has been completely rewritten, and works much better now.

Release 4.10.2 - Live Raspberry PI webcam fix

Due to Bookworm adoption the Raspberry PI live webcam was broken. In this release this has been fixed. That is all.

Release 4.10.1 - Another Docker fix release

This release is again for Docker users only. Somehow the Docker health check is working differently, and that was killing the container before the software could start. So the health check is changed, and should wait for a maximum of three minutes to startup before restarting the container when unhealthy.

And for the Bullseye Docker image, there was an OS package missing which made not to start up. This has also been fixed.

Release 4.10.0 - Make GPIO relays work like they should

GPIO relay changes

In this release we have changed the GPIO relay code. So if you use those relays, pay attention to the following.

Release 4.9.2 + 4.9.3 - Docker fixes

The Docker builds where broken and should now be fixed again. That is all.

Release 4.9.1 - Fine tuning

Fine tuning total power and water usage

The previous release did improve the speed a lot with caching the total power and water usage. This saves a lot of CPU time with a big database.

Release 4.9.0 - More speed or less waiting

Speed up by adding more caching and threading

When TerrariumPI is running for a couple or years, you will get a lot of relay data which it used for the total power and water usage. After 7 years, it took about 15 seconds each time it was calculated. Which is half the time of the engine run time.

Release 4.8.4 - Ancient bug fix

Settle time bug

Apparently there was a bug in the code for many, many years :disappointed:. The settle time value was calculated from the time the relay was toggled on. But when the relay on duration is higher than the settle time value, the settle time was useless.