I created a python script that runs as a service to read out the Fluvius energy meter via the P1 port to USB on a Raspberry Pi. See installation notes here: https://github.com/smartathome/fluvius2mqtt/tree/main
The output into Home Assistant looks like this:
I want to read out a SMA Sunny Boy data and make it available via MQTT to Home Assistant. Installation of SBFSpot on a Rasberry Pi is really easy. The tool to be used for this is SBFSpot. The SMA procotol used is proprietary and happens over 502/tcp.
curl -s https://raw.githubusercontent.com/sbfspot/sbfspot-config/master/sbfspot-config | sudo bash
sudo vi cd /usr/local/bin/sbfspot.3/SBFspot.cfgto change the MQTT configuration and set the following MQTT_Data:
MQTT_Data=Timestamp,SunRise,SunSet,InvSerial,InvName,InvSwVer,InvTime,InvStatus,InvTemperature,InvGridRelay,EToday,ETotal,PACTot,UDC1,UDC2,IDC1,IDC2,PDC1,PDC2,GridFreq
/usr/local/bin/sbfspot.3/SBFspot -v -finq -nocsv -mqtt
sudo raspi-config
ssh-keygen -o -a 100 -t ed25519
sudo passwd root
sudo vi /etc/network/interfacesAdd at the end of the file the following:
# Added by user on 2023-XX-XX
auto eth0
iface eth0 inet static
address 192.168.0.240/24
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1
dns-nameservers 192.168.0.1 8.8.8.8
# End of Additionsudo systemctl restart networking.serviceAnd test with
ip add showReboot your RPi again (or do it later if you plan to reboot anyway)
sudo -i apt-get update -y && apt-get upgrade -y
sudo sed -i '/# The named pipe \/dev\/xconsole/,$d' /etc/rsyslog.conf sudo service rsyslog restart
sudo apt-get install -y syslog-ng
sudo apt-get install -y git dirmngr
cd /home/pi git clone https://github.com/azlux/log2ram.git cd log2ram chmod +x install.sh sudo ./install.sh Change the log size value to 128M sudo vi /etc/log2ram.confReboot
sudo apt-get install -y sendmail mailutils sendmail-bin sudo mkdir -m 700 /etc/mail/authinfo/ sudo cd /etc/mail/authinfo/Create a Sendmail authentication file:
sudo vi sendmail-authAnd paste the following info:
AuthInfo: "U:root" "I:YOUR LOGIN" "P:YOUR PASSWORD"Save and exit vi. Next do the makemap:
sudo makemap hash sendmail-auth < sendmail-auth sudo chmod 400 sendmail-authChange the Sendmail configuration now
sudo vi /etc/mail/sendmail.mc Add the following below right above first "MAILER_DEFINITIONS" line: # Added by yourname on 2018-XX-XX define(`SMART_HOST',`[192.168.Y.XX]')dnl define(`RELAY_MAILER_ARGS', `TCP $h 587')dnl define(`ESMTP_MAILER_ARGS', `TCP $h 587')dnl define(`confAUTH_OPTIONS', `A p')dnl TRUST_AUTH_MECH(`EXTERNAL DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl FEATURE(`authinfo',`hash -o /etc/mail/authinfo/sendmail-auth.db')dnl # End of AdditionApply the changes to the configuration and restart Sendmail:
sudo make -C /etc/mail sudo /etc/init.d/sendmail reloadTest if you can send an email to yourself:
echo "Just testing my Sendmail email relay" | mail -s "Sendmail email relay" you@here.com
sudo apt-get install -y ntp ntpdate sudo vi /etc/ntp.confAnd replace the XX with your country code
0.XX.pool.ntp.org sudo /etc/init.d/ntp stopAnd query to see NTP being in sync
sudo ntpd -gq sudo /etc/init.d/ntp start sudo ntpd -pn
sudo apt-get install snmp snmpd sudo vi /etc/snmp/snmpd.confAnd put the following configuration lines
agentAddress udp:161 rocommunity public 192.168.X.0/24Restart your SNMP daemon
sudo /etc/init.d/snmpd restartAnd test on your local machine
snmpwalk -Os -c public -v 1 localhost
su - cat >/etc/systemd/system/nfs-common.service <<\EOF [Unit] Description=NFS Common daemons Wants=remote-fs-pre.target DefaultDependencies=no [Service] Type=oneshot RemainAfterExit=yes ExecStart=/etc/init.d/nfs-common start ExecStop=/etc/init.d/nfs-common stop [Install] WantedBy=sysinit.target EOF
cat >/etc/systemd/system/rpcbind.service <<\EOF [Unit] Description=RPC bind portmap service After=systemd-tmpfiles-setup.service Wants=remote-fs-pre.target Before=remote-fs-pre.target DefaultDependencies=no [Service] ExecStart=/sbin/rpcbind -f -w KillMode=process Restart=on-failure [Install] WantedBy=sysinit.target Alias=portmap EOF
cat >/etc/tmpfiles.d/rpcbind.conf <<\EOF #Type Path Mode UID GID Age Argument d /run/rpcbind 0755 root root - - f /run/rpcbind/rpcbind.xdr 0600 root root - - f /run/rpcbind/portmap.xdr 0600 root root - - EOF systemctl enable rpcbind.service systemctl enable nfs-commonInstall raspiBackup (from this website)
sudo mkdir -p /backupAvoid accidental file storage, when folder is not mounted
sudo chattr +i /backup sudo vi /etc/fstabAnd add
server.yourdomain.com:/volume1/backups/host.yourdomain.com/backup nfs rsize=8912,wsize=8912,timeo=14 0 0 sudo mount /backupNow install the raspiBackup tool
curl -s https://raw.githubusercontent.com/framps/raspiBackup/master/installation/install.sh | sudo bash
Go through the configuration tool, later on you can go back to it via: raspiBackupInstallUI.sh-Backup versions: smart strategy-Backup to tar-No compression-Backup mode standard-Email notification set
Uncomment the crontab (backup will run every Sunday at 5am):sudo vi /etc/cron.d/raspiBackupAnd finally testsudo raspiBackup
Generate an SSH keypair for easy loginssh-keygen ssh-copy-id -p 22 admin@server.yourdomain.comLog into your server, make yourself root and copy the public key into the raspberry
cat /root/.ssh/id_rsa.pub | ssh user@hhost.yourdomain.com "mkdir -p ~/.ssh && cat >> ~/.ssh/authorized_keys"Test if it's working by using:
ssh user@host.yourdomain.com
Setup unattended upgrade based on this tutorialsudo apt update sudo apt install unattended-upgradesConfigure unattended upgrades and uncomment:
sudo vi /etc/apt/apt.conf.d/50unattended-upgrades
"origin=Debian,codename=${distro_codename}-updates";
"origin=Debian,codename=${distro_codename}-proposed-updates";
"origin=Debian,codename=${distro_codename},label=Debian";
"origin=Debian,codename=${distro_codename},label=Debian-Security";
"origin=Debian,codename=${distro_codename}-security,label=Debian-Security"; And uncomment:Unattended-Upgrade::Remove-Unused-Dependencies "false";Now enable Automatic Updates (and press Yes)
sudo dpkg-reconfigure --priority=low unattended-upgrades
To view the unattended upgrades:sudo systemctl status unattended-upgrades.service-
When installing the standard Watchtower container onto DSM 6.0 with Docker, I ran into 2 issues which caused the container not to run and constantly restart itself (see container logs for the error messages):
Both issues have a solution. First being that an older docker image has to be used, second being that DSM UI somewhere filters out a file mapping when creating the container.
sudo ln -s /var/run/docker.sock /volume1/docker/docker.sock
sudo docker run -d --name watchtower-new -v /volume1/docker/docker.sock:/var/run/docker.sock centurylink/watchtower --interval 82800 --cleanup
I have a server with a Supermicro X7SBI motherboard. It has a dedicated IPMI port but I could no do anything with it, as this was a second hand server and the IPMI had a fixed IP address in the 83... range and the admin password was unknown to me. I thought that resetting it was straightforward, but ran into a few issues:
First issue: Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
So at first, I thought that the device itself was broken. I unplugged it, checked it, but I could see the IP address and the webserver was accessible, so that seems ok. So I tried to factory reset the BIOS, still no help. Then, after some Googling, I found out that 2 fixes were needed.
//add logs
These articles explain what needs to be done: different ipmi_si port address and add kernel boot parameter
Run everything as root:
vi /etc/default/grub and change GRUB_CMDLINE_LINUX_DEFAULT="quiet" to
GRUB_CMDLINE_LINUX_DEFAULT="quiet ipmi_si.type=kcs ipmi_si.ports=0xca2"
Save and exit, then update your GRUB
update-grub
Second issue: Still, there is a second problem with this version of ipmitool for Debian 12
root@debian:~# ipmitool raw 0x6 0x46 0x02
IANA PEN registry open failed: No such file or directory
61 64 6d 69 6e 00 00 00 00 00 00 00 00 00 00 00
root@debian:~# lsmod | grep ipmi
ipmi_si 73728 0
ipmi_devintf 20480 0
ipmi_msghandler 77824 2 ipmi_devintf,ipmi_si
root@debian:~# ipmitool lan set 1 ipsrc static
IANA PEN registry open failed: No such file or directoryAfter some Googling, I found out there is some config missing for ipmitool. This command will solve that:
2. Copy missing enterprise numberswget -O /usr/share/misc/enterprise-numbers.txt https://jff.email/cgit/ipmitool.git/plain/debian/enterprise-numbers.txt?h=debian/1.8.19-5
After which I could reset the ipmi ADMIN password and set the static IP address. Yeehaa!root@debian:~# ipmitool user set name 2 ADMIN
root@debian:~# ipmitool user set password 2
Password for user 2:
Password for user 2:
Set User Password command successful (user 2)
root@debian:~# ipmitool lan set 1 ipsrc static
root@debian:~# ipmitool lan set 1 ipaddr 192.168.0.199
Setting LAN IP Address to 192.168.0.199
root@debian:~# ipmitool lan set 1 defgw ipaddr 192.168.0.1
Setting LAN Default Gateway IP to 192.168.0.1
root@debian:~# ipmitool lan print
Set in Progress : Set Complete
Auth Type Support : NONE MD2 MD5 PASSWORD
Auth Type Enable : Callback :
: User : MD5
: Operator : MD5
: Admin : MD5
: OEM : MD5
IP Address Source : Static Address
IP Address : 192.168.0.199
Subnet Mask : 255.255.255.0
MAC Address : 00:30:48:95:76:55
SNMP Community String : public
IP Header : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10
BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Enabled
Gratituous ARP Intrvl : 2.0 seconds
Default Gateway IP : 192.168.0.1
Default Gateway MAC : 00:00:00:00:00:00
Backup Gateway IP : 0.0.0.0
Backup Gateway MAC : 00:00:00:00:00:00
RMCP+ Cipher Suites : 0,1,2,3,6,7,8,11,12
Cipher Suite Priv Max : uuuOXXuuOXXuOXX
: X=Cipher Suite Unused
: c=CALLBACK
: u=USER
: o=OPERATOR
: a=ADMIN
: O=OEM
docker psOutput:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 78bd86bc763a 7cdd2aec3527 "/usr/local/bin/docke" 12 months ago Up 23 minutes 0.0.0.0:6789->6789/tcp, 0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcp, 0.0.0.0:8843->8843/tcp, 0.0.0.0:3478->3478/udp, 0.0.0.0:10001->10001/udp, 6789/udp, 0.0.0.0:8880->8880/tcp unifi
cd /volume1/docker/unifi/cert && mv *.pem _backups/
chmod 400 *.pem*
docker logs -f 78bd86bc763aLogging:
[2019-02-09 08:08:13,866]Starting unifi controller service. [2019-02-09 08:08:13,868] WARNING: Running UniFi in insecure (root) mode [2019-02-09 08:12:27,477] Exit signal received, shutting down [2019-02-09 08:12:33,211] Cert directory found. Checking Certs [2019-02-09 08:12:33,440] Cert has changed, updating controller... [2019-02-09 08:12:33,443] Using openssl to prepare certificate... [2019-02-09 08:12:33,488] Removing existing certificate from Unifi protected keystore... [2019-02-09 08:12:33,903] Inserting certificate into Unifi keystore... Importing keystore /tmp/tmp.cuWCGLJI1p to /unifi/data/keystore... Warning: The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /unifi/data/keystore -destkeystore /unifi/data/keystore -deststoretype pkcs12". [2019-02-09 08:12:34,684] Cleaning up temp files [2019-02-09 08:12:34,688] Done! [2019-02-09 08:12:34,692] Starting unifi controller service. [2019-02-09 08:12:34,693] WARNING: Running UniFi in insecure (root) mode
I am reinstalling my Unifi Controller on Docker and need to re-adopt my Unifi AP devices. There are several ways to do this:
With option 1, I ran into the issue that my network is different from the default one that a Unifi AP resets to (default IP = 192.168.1.20) and I wanted a way to change that back to the fixed IP address it had before. Thanks to this article for some help. Later on, it turned out there was even a more convenient way for me to do this, see below.
vi /etc/udhcpc/udhcpcFrom:
UDHCPC_FALLBACK_IP="192.168.1.20"UDHCPC_FALLBACK_NETMASK="255.255.255.0"
UDHCPC_FALLBACK_IP="NEW_IP"UDHCPC_FALLBACK_NETMASK="255.255.255.0"
set-default
ping -c 4 unifi.yourdomain.com
mca-cli
set-inform http://unifi.yourdomain.com:8080/inform