Author: Stefan

Proxmox Host backup

Backup the following folders/files:

/var/lib/pve-cluster/config.db
/etc/corosync/*
/etc/network/interfaces
/etc/hostname
/etc/hosts

March 10, 2024

Create sensor for remaining battery time

In this example the home battery system has a capacity of 300Ah (15kWh / 48V).
As a safe minimal value is 15% capacity left is chosen. When grid is failing, there is still 2.5kWh left. When charging occurs, this will be shown instead of the remaining time.

You can use the created sensor ‘sensor.template_time_left_on_battery_min_soc’ to display on your dashboard.

  - sensor:
      - unique_id: time_left_on_battery_min_soc
    #   unit_of_measurement: "Hours"
        icon: mdi:sort-clock-ascending
        state: >
          {% set battery_current = states('sensor.battery_current')|float %}
          {% set battery_soc = states('sensor.battery_percent')|float %}
          {% set loads_current = states('sensor.ac_loads')|float/states('sensor.battery_voltage')|float %}
          {% set battery_min_soc = 15 %}
          {% set battery_max_capacity = 300 %}
          {% if (battery_soc-battery_min_soc) < 0 %}
            {{ 0 }}
          {% elif (loads_current) < 0 %}
            {{ 'Charging' }}
          {% else %}
            {{ ((((battery_soc-battery_min_soc)*battery_max_capacity)/100)/loads_current | float ) | round(2) }}
          {% endif %}

February 15, 2024

Convert value ‘unavailable’ to 0

template:
  # Solar production - Prevent showing unavailable instead of 0
  - sensor:
      - name: "Solar Current Power"
        unit_of_measurement: "W"
        state: "{{ 0 if states('sensor.on_grid_l1_power') == 'unavailable' else states('sensor.on_grid_l1_power' ) }}"

February 15, 2024

SSL in Home Assistant
Place your fullchain.pem and privkey.pem in folder /ssl

Apply SSL to your HA Instance by adding the following code to your configuration.yaml
```
# SSL Certificate
http:
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
```
February 15, 2024
KPN / XS4ALL / pfSense IPTV
(This article is in dutch language because it is only applicable on dutch TV providers)

Hierbij mijn werkende configuratie voor IPTV met pfSense als router.
Hierbij is op glasvezelaansluiting een NTU gemonteerd die het optische signaal omzet naar koper/UTP.

Ik maak gebruik van een Qotom computer die voorzien is van 6 netwerk interfaces (Intell chipset). Daardoor heb ik interfaces Igb0 t/m Igb5 tot mijn beschikking. Daarbij heb ik gekozen om mijn interne IPTV via een apart VLAN te laten lopen. Dit is NIET noodzakelijk. Dit kan namelijk ook gewoon via LAN.
Als je dat wil doen, zorg dan dat je de firewall rules uit IPTV_LAN overneemt (incl. ip options!) naar je LAN firewall rules.

Hieronder een reeks screenshots zoals ik het geconfigureerd heb.
Voor vragen kun je me altijd benaderen via comments onder aan deze pagina. (registreren noodzakelijk i.v.m. spam)

Interface Assignments

In mijn configuratie zijn onderstaande aansluitingen van belang:
Igb0 = WAN (verbonden via UTP-kabel aan de NTU)
Igb1 = LAN
Igb3 = IPTV_LAN

wan Interface details

lan Interface details

iptv_wan Interface details

iptv_lan Interface details

FiREWALL RULES LAN

FIRewall rules iptv_Wan

Let op! Bij de bovenste regel is via Advanced options ‘Allow IP options’ aangevinkt’

FIRewall rules iptv_LAn

Let op! Bij de bovenste 2 regels is via Advanced options ‘Allow IP options’ aangevinkt’

IGMP PROXY

NAT OUTBOUND

Set Outbound Nat mode op ‘Hybrid mode’.
Zorg dat je onderstaande mapping toevoegd. Er zullen ook automatische rules aangemaakt worden.

EXTRA AANDACHT VOOR:
- Als je de Settopbox rechtstreeks aansluit op een netwerkaansluiting van pfsense, raakt de pfsense interface disconnected tijdens her-/opstart van de settopbox. De IGMP-Proxy crasht daardoor. Het via een switch aansluiten van van de settop box loste dit probleem op.
December 16, 2022
Proxmox backup already exists
When you run into this error:

“TASK ERROR: zfs error: cannot create ‘rpool/vm-302-state-update’: dataset already exists”

Try this solution:
```
zfs destroy rpool/vm-302-state-update
```
May 14, 2021

Proxmox ZFS replace drive

1: have a look what is there:

ls -alh /dev/disk/by-id/
zpool status
zpool list -v

2: set the hard drive you want to change offline:

zpool offline "POOLNAME"  "HARD-DRIVE-ID or the whole path"
## example:
zpool offline rpool wwn-0x50014ee25ba1a5e4

3: change the hard drives physically
shutdown and replace the disk (no hot-swap)

4: create an empty GPT Partition Table on the new hdd with parted:

parted /dev/new-disk
(parted)# print
(parted)# mklabel GPT
(parted)# Yes
(parted)# q

5: replace them in the ZFS Pool:

zpool replace "POOLNAME" "HARD-DRIVE-ID or the whole path old hard drive"  "HARD-DRIVE-ID or the whole path NEW hard drive"
## example:
zpool replace rpool wwn-0x50014ee25ba1a5e4 wwn-0x5000cca27edf438f

6: have a look what’s going on:

zpool status
....
resilver in progress since Sat Feb 29 11:43:52 2020
328G scanned at 3,77G/s, 75,5G issued at 888M/s, 328G total
  8,83G resilvered, 23,01% done, 0 days 00:04:51 to go
....

February 6, 2021

Remove Proxmox 6.x/5.1+ Subscription Notice
(source: https://johnscs.com/remove-proxmox51-subscription-notice/)

With the release of Proxmox 5.1 and newer (including 6.2) you’ll find the code related to the no subscription message that pops up on login has changed and prior instructions for removing it wont work.

To remove “You do not have a valid subscription for this server” run the command bellow. You will need to SSH to your Proxmox machine or use the node console through the PVE web interface.

If you update your Proxmox server and the update includes a new version of the file we are about to edit then you’ll need to run the command again.

Run the following one line command and then clear your browser cache (depending on the browser you may need to open a new tab or restart the browser):
```
sed -i.bak "s/data.status !== 'Active'/false/g" /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js &amp;&amp; systemctl restart pveproxy.service
```
Here are alternative step by step instructions so you can understand what the above command is doing:
1. Change to working directory
  cd /usr/share/javascript/proxmox-widget-toolkit
2. Make backup of file
  cp proxmoxlib.js proxmoxlib.js.bak
3. Edit the file
  nano proxmoxlib.js
4. Locate this line of code inside the file (use ctrl+w in nano)
  if (data.status !== 'Active') {
5. Replace it with this
  if (false) {
6. Restart the Proxmox service (also be sure to clear your browser cache, depending on the browser you may need to open a new tab or restart the browser)
  systemctl restart pveproxy.service
August 29, 2020

Author: Stefan

Proxmox Host backup

Victron MQTT configurations

Ping network devices

Create sensor for remaining battery time

Convert value ‘unavailable’ to 0

SSL in Home Assistant

KPN / XS4ALL / pfSense IPTV

Interface Assignments

wan Interface details

lan Interface details

iptv_wan Interface details

iptv_lan Interface details

FiREWALL RULES LAN

FIRewall rules iptv_Wan

FIRewall rules iptv_LAn

IGMP PROXY

NAT OUTBOUND

Proxmox backup already exists

Proxmox ZFS replace drive

Remove Proxmox 6.x/5.1+ Subscription Notice