alertR VS Tautulli

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

With Tautulli you have a better monitoring system than what Plex offers. Streaming history split by user, you can add notifications to a lot of services like Slack, email and so on. You can even create newsletters being sent out to users based on what was added to your server.

> How hard is this to configure?

Not at all. Just ensure that you have WoL enabled on the host machine and than proceed to send a magic packet. You could even do this with Home Assistant [1] if you are into that. I did this with a script that used tcpdump to monitor for incoming traffic [2] for Plex with an additional (dummy) Plex server on the Pi. I also remember faintly that I had to add 1 library and 1 video file to make this work though.

Powering down - or sleep - is a bit harder. I built a 'Sleep on LAN' app [3] for myself years ago that could power down (or sleep) a system on demand using a REST API. I used this and Tautulli [3] with Home Assistant that would check if there were any active streams and if there wasn't any activity for a specified amount of time I would send a SoL request to my service.

As you can see it isn't super hard or complicated, but a bit cumbersome to find all the moving bits and make it work. But when it does, it's IMHO fantastic.

1. https://www.home-assistant.io/integrations/wake_on_lan/

2. https://gist.github.com/alex3305/8cc73ddd2c8ca6328f20235480a...

2. https://github.com/alex3305/sleep-on-lan

3. https://tautulli.com/

In that case then I don't think there will be an easy way to transfer the metadata unfortunately (outside of some user-created script). One option that would at least help with the manual re-entry would be to use Tautulli's export feature or WebTools-NG's ExportTools to create a spreadsheet that has all the information in one place, and should be easier to copy/paste.

Also, take a look at Tautulli, tautulli.com. Its dashboard has more info than Plex. It shows transcode speed (1.0 = real time) and if subtitles are burning/transcoding/etc.

Tautulli for monitoring and notifications, plus some scripts for "maintenance," such as killing 4K transcodes and stopping remote streams after they've been paused for X minutes. These are from the JBOPS repository.

Tautulli. There's a feature where you can trigger notifications from events on your server, not just when it's down. I'm not sure there's a function to get your server to auto restart though.

Looks like Tautulli's mobile companion app.

The data Tautulli exports is great if you want to throw it in Excel to analyze your library, or as a backup of all the content you have on your server, but isn't really meant to be imported at a later date (the exporter guide. You should instead follow the Move an Install to Another System guide to move your server data to a new machine.

I enjoy https://tautulli.com/ for looking at my server's stats