ragingcomputer

#include "Keyboard.h"
#include <Keypad.h>

const int KEYDELAY = 100;
const int SEQDELAY = 500;

const byte ROWS = 2;
const byte COLS = 4;
// Define the Keymap
/* 

ragingcomputer

LibreNMS Custom Alert for Spanning Tree STP Blocking Ports

This can be configured as an Advanced Alerting Rule https://docs.librenms.org/Alerting/Rules/#advanced

Create a new rule and give it a name

ragingcomputer

Collect pfSense DHCP lease counts using telegraf and built-in tools

Existing Collector

pfSense has the ability to collect DHCP lease statistics in it's Status -> Monitoring menu. That means it has some way to collect them.

searching through the source on github reveals dhcpd_gather_stats.php referenced in rrd.inc

pfSense runs this command to collect dhcpd lease counts from the lan interface: /usr/local/bin/php-cgi -q /usr/local/bin/dhcpd_gather_stats.php lan and this for the opt1 interface: /usr/local/bin/php-cgi -q /usr/local/bin/dhcpd_gather_stats.php opt1

ragingcomputer

from pymssql import connect
import hashlib
import ipaddress
import subprocess

output_file = "/etc/icinga2/conf.d/ipcams/cameras.conf"

conn = connect(
    host="milestone_sql.fq.dn",
    user="read_user",

ragingcomputer

Use Python & requests to reboot Polycom Phones

Tested on Polycom VVX 310, VVX 410, and Trio 8800 phones Assumes all phones have the same admin password

Usage: Update phones.py with a list strings containing IP address of phones to reboot Assuming you aren't using default admin password on the phones, update "restart_phone(phone, "Polycom:456")"

ragingcomputer

#include <Keypad.h>
#include "Keyboard.h"

const byte ROWS = 2;
const byte COLS = 4;
// Define the Keymap
char keys[ROWS][COLS] = {
  {'1','2','3','4'},
  {'5','6','7','8'}
};

ragingcomputer

#include <Servo.h>
#include <LiquidCrystal.h>


#define PIN_SERVO_SHUTTER   6
#define PIN_SERVO_TILT  10
#define PIN_SERVO_PAN   9
#define PIN_BEEP   8

#define SHUTTER_START_POINT   35

ragingcomputer

SELECT mc.fullname AS CourseName, 
	ROUND((SUM(mf.filesize)/1024)/1024, 2) AS Storage_Used_MB
	
FROM mdl_files AS mf
LEFT JOIN mdl_context AS ctx ON mf.contextid = ctx.id
LEFT JOIN mdl_course AS mc ON ctx.instanceid = mc.id

WHERE mf.component = 'backup' 
AND mf.filearea = 'course'
AND NOT mf.filename = '.'

ragingcomputer

SELECT CONCAT(mu.firstname, ' ', mu.lastname, ' (', mu.email, ')' ) AS Teacher, 
	ROUND((SUM(mf.filesize)/1024)/1024, 2) AS Storage_Used_MB
	
FROM mdl_files AS mf
LEFT JOIN mdl_user AS mu ON mf.userid = mu.id

WHERE mf.component = 'user'
AND mf.filearea = 'backup'
AND NOT mf.filename = '.'

ragingcomputer

The video https://www.youtube.com/watch?v=z0Dmdwt8gNE Is just a repetition of the directions on this post https://community.openhab.org/t/aeon-minimote-configuration-oh-1-8-2/9585/9

Quoting TheKorn from Apr '16

I'm going to write this up in stupid levels of detail, not because I think you're an idiot but for people who search and run across this thread. (Plus when it inevitably comes up in the future, I can link back here and say "do that". 😉 )

There are at least four variants of this remote, possibly more. They all seem to have identical hardware and report identically via zwave as far as device IDs go, and react the same way when you push the buttons despite them being labeled very differently. Version one has the buttons labeled 1,2,3,4. Version two has each button labeled with a square. (Very helpful, Aeon. /s) White/black versions of both exist, etc.

We need a common nomenclature for the buttons. I'm going to go with the original white remote's button numbering, since writing "hit the lower le