alertR VS flower

I see that the alertr.de website is down, and it appears that the server responds with error 10 when I try to test send a message. Is it a problem on the server side or do I have to do some more debugging on my side?

Set up a the ManagerClientDatabase (an tutorial exists here: https://github.com/sqall01/alertR/wiki/Tutorial-ManagerClientDatabase)

Around Christmas I published a handful of scripts I use internally to monitor my Linux hosts for security breaches (https://github.com/sqall01/LSMS). Somehow, it got a lot of attention which I did not expected. Since these scripts can be used with AlertR, I decided to additionally write a tutorial how you can set up both projects to work with each other. Here is the link: https://github.com/sqall01/alertR/wiki/Tutorial-SensorClientFIFO-LinuxSecurityMonitoring

The awesome news: AlertR now supports the new data type: GPS. With GPS a position and the time it was recorded is stored. But this alone is not awesome but just lame. The awesome thing is that a new sensor client was added: Sensor Client GPS. This sensor fetches periodically GPS data from a provider and allows you to use geofencing to monitor if the monitored GPS device is outside or inside a specific area. Naturally, this new client comes with its own Tutorial. Personally, I use it to monitor if my car is parked at home and as car alarm system with the help of an old Android mobile phone.

For a long time, there were templates for Alert and Manager clients. Meaning, a developer has an easy way to start writing native Alert and Manager clients for AlertR. However, a template for Sensor clients was missing. With the restructuring of how the sensor processing works internally in the clients earlier this year, I have now completed a template for Sensor clients (https://github.com/sqall01/alertR/tree/master/sensorClientTemplate). This template gives every developer an easy start in implementing a native sensor client for AlertR without having to start from an already finished Sensor client and starting to rewrite it for fitting the needs.

Link to tutorial

One or two weeks ago I had the idea to use a calendar to schedule actions that are then executed by AlertR. More specifically, in my case, I wanted the schedule to change the temperature of my thermostats as well as switching some appliances on and off depending on the time and day. Fortunately, AlertR already had everything it needed to do this. So, here is now a tutorial on how you can do this.

No it does not use MQTT. It uses a custom json based protocol. The exact layout is documented here: https://github.com/sqall01/alertR/wiki/Protocol

Use flower to monitor workers and tasks.

Not sure what your criteria for good observability ist, but flower served me well enough for this in the last couple of years.

From experience i would not use threads for this or any background jobs. I would use Celery or Flask-RQ2 to be your workers, you will also probably end up using them to run other tasks as you encounter the need for other jobs. They both use Redis as a broker and job store and you can use Redis for other things like caching and so many other useful features. I kind of like RQ2 more then Celery because its a little simpler but Celery has a lot more to offer, more features. RQ2 has rq-dashboard for monitoring jobs and Celery has Flower.