Home Assistant

2026-03-22T21:09:40Z

Apn :

= Disclaimer =
I use this page as a very drafty "personal" notepad / memo. It's a bit messy but straight to the point and I don't intend to structure it better ;-)

= Raspberry PI & Home Assistant OS =
== Custom routes issue ==
When installing HA natively on a RPI if static routing is needed, then the best solution is this one: 
https://www.reddit.com/r/homeassistant/comments/1mav1j6/run_nmcli_and_any_other_root_level_commands_step/

Step-by-Step: Access Full Root Shell on HAOS via Port 22222
# Install the Add-on Add HassOS SSH port 22222 Configurator via the Home Assistant Add-on Store (manual repository add required).
# Generate SSH Keys On your hassOS terminal :ssh-keygen cat ~/.ssh/id_rsa.pub
# Paste Public Key into Configurator Add-on Open the add-on config panel and paste your public key (id_rsa.pub) into the configuration.
# Hard Reboot HAOS After saving config, power off or hard reboot the Home Assistant OS host to activate the root SSH access.
# SSH into HAOS Root (Port 22222) On your terminal:ssh -p 22222 root@127.0.0.1
# Use nmcli and Other Commands Now you can run:This is the only method to modify connections that don’t appear in the GUI.nmcli connection show nmcli connection delete <name>
# (Optional) Delete or Reset Network Configurations You can also:cd /etc/NetworkManager/system-connections/ rm <stale-profile>.nmconnection reboot
# Cleanup Once fixed: Uninstall the 22222 Configurator & Remove your public key if desired

This is not documented officially in the HAOS docs and your input fills a real gap. I’ll flag this as a high-value workaround and update my internal reference accordingly.

Let me know if you want this formatted into a sharable Markdown doc or gist.
Sources:
* https://community.home-assistant.io/t/add-on-hassos-ssh-port-22222-configurator/264109
* https://community.home-assistant.io/t/command-not-found-nmcli/902180
* https://github.com/home-assistant/operating-system/blob/0724608f/Documentation/network.md#L151-L189 </pre>

=== Adding the route ===
Then specifically for my case:
<pre>apn@macbook-pro-apn ~ % ssh -p 22222 root@192.168.1.111
Enter passphrase for key '/Users/apn/.ssh/id_ed25519':
Welcome to Home Assistant OS.

Use `ha` to access the Home Assistant CLI.
# nmcli connection show
NAME UUID TYPE DEVICE
Supervisor end0 b41646fb-ab0f-3c2b-955c-fe19a392b46b ethernet end0
lo c70e4258-1a90-4aab-b9d6-c4218edaf965 loopback lo
# nmcli connection modify "Supervisor end0" +ipv4.routes "192.168.2.0/24 192.168.1.101"
# nmcli connection up "Supervisor end0"
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/4)
# </pre>

= Garage Remote control =

Sometimes a remote control can send multiple button/click triggers even when a button is pushed once.

That's the case with the [https://fr.aliexpress.com/item/4001062612446.html ''Tuya Zigbee3.0 Remote Control With 4 Key'']] that I just bought to trigger a Zigbee dry relay MHCOZY TYZG-001-RF (only used in Zigbee mode & cabled in NO - Normally opened). This dry relay simulates a push button to open a Garage door.

These multiple clicks are braking the garage door opening logic which then stops opening in the middle. In order to solve this, I used what we call in IT a '''mutex'''.

Here are the scripts to make this work properly:

== MHCOZY ZG-001 ==

[[Fichier:MHCOZY TYZG-001-RF.png]]

Go to '''Settings > Automations & scenes > Scripts''' and create the following script:
<pre>alias: Pulse TUZG Relay (0.5s)
mode: single
sequence:
- target:
entity_id: light.mhcozy_tyzg_001_rf
action: light.turn_on
- delay:
milliseconds: 500
- target:
entity_id: light.mhcozy_tyzg_001_rf
action: light.turn_off
</pre>

== Tuya Zigbee3.0 Remote Control ==

[[Fichier:Tuya Remote Control.png]]

Go to '''Settings > Devices & services > Helpers''' and create the following Boolean '''Toggle''':
<pre>Name: garage_remote_control_lock
Entity ID: input_boolean.garage_remote_control_lock</pre>
Make sure it's set to Off (click on it when created to set its state).

Then go to '''Settings > Automations & scenes > Automations''' and create the following script:
<pre>alias: Garage remote control
description: Trigger the garage door opening/closing via the remote control with lock to prevent duplicates
triggers:
- event_type: zha_event
event_data:
device_ieee: $your_device_ieee_identifier
command: arm
trigger: event
conditions:
- condition: state
entity_id: input_boolean.garage_remote_control_lock
state: "off"
actions:
- action: input_boolean.turn_on
data: {}
target:
entity_id: input_boolean.garage_remote_control_lock
- action: script.pulse_relay_0_5s
data: {}
- delay:
seconds: 10
- action: input_boolean.turn_off
data: {}
target:
entity_id: input_boolean.garage_remote_control_lock
mode: single</pre>

To make sure the value is at OFF at HA startup (i.e. to avoid specific bad situations when the HA crashes in the middle of the door opening automation and the toggle does not get reset), then create another automation:
<pre>alias: Garage remote control lock reset on startup
triggers:
- event: start
trigger: homeassistant
actions:
- target:
entity_id: input_boolean.garage_remote_control_lock
action: input_boolean.turn_off
data: {}
mode: single</pre>

== ZHAQuirks for TS0601 ==

The TS0601 by _TZE204_nklqjk62 is not recognized by HomeAssistant ZHA.

=== Signature of the device ===
<pre>{
"node_descriptor": {
"logical_type": 1,
"complex_descriptor_available": 0,
"user_descriptor_available": 0,
"reserved": 0,
"aps_flags": 0,
"frequency_band": 8,
"mac_capability_flags": 142,
"manufacturer_code": 4417,
"maximum_buffer_size": 66,
"maximum_incoming_transfer_size": 66,
"server_mask": 10752,
"maximum_outgoing_transfer_size": 66,
"descriptor_capability_field": 0
},
"endpoints": {
"1": {
"profile_id": "0x0104",
"device_type": "0x0100",
"input_clusters": [
"0x0000",
"0x0004",
"0x0005",
"0x0006",
"0xef00"
],
"output_clusters": [
"0x000a",
"0x0019"
]
},
"2": {
"profile_id": "0x0104",
"device_type": "0x0402",
"input_clusters": [
"0x0500"
],
"output_clusters": []
},
"242": {
"profile_id": "0xa1e0",
"device_type": "0x0061",
"input_clusters": [],
"output_clusters": [
"0x0021"
]
}
},
"manufacturer": "_TZE204_nklqjk62",
"model": "TS0601",
"class": "ts0601_garage.TuyaGarageSwitchTO"
}</pre>

=== How-to make it work ===
<pre>
[core-ssh zhaquirks]$ pwd
/config/zhaquirks
[core-ssh zhaquirks]$ cat ts0601_garage.py
"""Tuya based cover and blinds."""
from typing import Dict

from zigpy.profiles import zgp, zha
from zigpy.quirks import CustomDevice
import zigpy.types as t
from zigpy.zcl.clusters.general import Basic, GreenPowerProxy, Groups, Ota, Scenes, Time
from zigpy.zcl.clusters.security import IasZone

from zhaquirks.const import (
DEVICE_TYPE,
ENDPOINTS,
INPUT_CLUSTERS,
MODELS_INFO,
OUTPUT_CLUSTERS,
PROFILE_ID,
)

from zhaquirks.tuya import NoManufacturerCluster, TuyaLocalCluster
from zhaquirks.tuya.mcu import (
DPToAttributeMapping,
TuyaMCUCluster,
TuyaOnOff,
)
from zhaquirks.tuya.ts0601_dimmer import TuyaOnOffNM

ZONE_TYPE = 0x0001

class ContactSwitchCluster(TuyaLocalCluster, IasZone):
"""Tuya ContactSwitch Sensor."""

_CONSTANT_ATTRIBUTES = {ZONE_TYPE: IasZone.ZoneType.Contact_Switch}

def _update_attribute(self, attrid, value):
self.debug("_update_attribute '%s': %s", attrid, value)
super()._update_attribute(attrid, value)

class TuyaGarageManufCluster(NoManufacturerCluster, TuyaMCUCluster):
"""Tuya garage door opener."""

attributes = TuyaMCUCluster.attributes.copy()
attributes.update(
{
# ramdom attribute IDs
0xEF02: ("dp_2", t.uint32_t, True),
0xEF04: ("dp_4", t.uint32_t, True),
0xEF05: ("dp_5", t.uint32_t, True),
0xEF0B: ("dp_11", t.Bool, True),
0xEF0C: ("dp_12", t.enum8, True),
}
)

dp_to_attribute: Dict[int, DPToAttributeMapping] = {
# garage door trigger ¿on movement, on open, on closed?
1: DPToAttributeMapping(
TuyaOnOffNM.ep_attribute,
"on_off",
),
2: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"dp_2",
),
3: DPToAttributeMapping(
ContactSwitchCluster.ep_attribute,
"zone_status",
lambda x: IasZone.ZoneStatus.Alarm_1 if x else 0,
endpoint_id=2,
),
4: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"dp_4",
),
5: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"dp_5",
),
11: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"dp_11",
),
# garage door status (open, closed, ...)
12: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"dp_12",
),
}

data_point_handlers = {
1: "_dp_2_attr_update",
2: "_dp_2_attr_update",
3: "_dp_2_attr_update",
4: "_dp_2_attr_update",
5: "_dp_2_attr_update",
11: "_dp_2_attr_update",
12: "_dp_2_attr_update",
}

class TuyaGarageSwitchTO(CustomDevice):
"""Tuya Garage switch."""

signature = {
MODELS_INFO: [
("_TZE200_nklqjk62", "TS0601"),
("_TZE200_wfxuhoea", "TS0601"),
("_TZE204_nklqjk62", "TS0601"),
],
ENDPOINTS: {
# <SimpleDescriptor endpoint=1 profile=260 device_type=0x0051
# input_clusters=[0, 4, 5, 61184]
# output_clusters=[10, 25]>
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaGarageManufCluster.cluster_id,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
},
# <SimpleDescriptor endpoint=242 profile=41440 device_type=97
# input_clusters=[]
# output_clusters=[33]
242: {
PROFILE_ID: zgp.PROFILE_ID,
DEVICE_TYPE: zgp.DeviceType.PROXY_BASIC,
INPUT_CLUSTERS: [],
OUTPUT_CLUSTERS: [GreenPowerProxy.cluster_id],
},
},
}

replacement = {
ENDPOINTS: {
1: {
DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaGarageManufCluster,
TuyaOnOffNM,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
},
2: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.IAS_ZONE,
INPUT_CLUSTERS: [
ContactSwitchCluster
],
OUTPUT_CLUSTERS: [],
},
242: {
PROFILE_ID: zgp.PROFILE_ID,
DEVICE_TYPE: zgp.DeviceType.PROXY_BASIC,
INPUT_CLUSTERS: [],
OUTPUT_CLUSTERS: [GreenPowerProxy.cluster_id],
},
},
}
[core-ssh zhaquirks]$ cd ..
[core-ssh config]$ tail -n 2 configuration.yaml
zha:
custom_quirks_path: /config/zhaquirks
</pre>

Then restart Home Assistant and discover the device. If the device was previously wrongly discovered, just delete it and discover it again.

=== Result ===
[[Fichier:TS0601.png]]

=== Credits ===
* https://github.com/zigpy/zha-device-handlers/issues/2533
* https://community.home-assistant.io/t/tuya-ts0601-zigbee-garage-door-opener/466400/5

== Garage door control ==
I finally replaced my ZigBee relay & sensor used to control the Garage door by a full wired logic connected to the GPIO and using the Raspberry Pi GPIO (rp_gpio) HACS add-on.
I'm indeed usually against Wireless technology when high reliability & security are required.

=== Hardware ===
* Dry contact relay: [https://www.amazon.com.be/dp/B0F59PPVZB 5 Pack 5V Channel Relay Module, 1 Channel Relay Module with Optocoupler High or Low Level Trigger Expansion Board for Raspberry Pi Arduino Board]
* Breakout board: [https://www.amazon.com.be/dp/B0DM4YKVCX Geekworm G469 GPIO Terminal Block Breakout Board for Raspberry Pi 4B/3B+/3B/ Zero 2W]
* Jumper wire cables: [https://www.amazon.com.be/dp/B074P726ZR AZDelivery Jumper Wire Cable 3 x 40 pcs. each 20 cm M2M/ F2M/F2F, 40 Pin Male to Male, 40 Pin Female to Female, Compatible with Arduino and Raspberry Pi Breadboard including an E-Book]

=== Cabling ===
[[Fichier:Gpio.jpg|300px|]]
* Garage door magnetic sensor: GPIO_17 (pin #11) + GND (pin #9)
* Relay:
** DCC+ => 5V (pin #4)
** DCC- => GND (pin #6)
** Signal (relay trigger) => GPIO_4 (pin #7)

=== Configuration ===
<pre>[core-ssh config]$ tail -n 12 configuration.yaml
switch:
- platform: rpi_gpio
switches:
- port: 4
name: "Garage door button - GPIO_4"
unique_id: "garage_door_switch_port_4"
binary_sensor:
- platform: rpi_gpio
sensors:
- port: 17
name: "Garage door sensor - GPIO_17"
unique_id: "garage_door_sensor_port_17"</pre>

=== Credits ===
* https://github.com/andrewshilliday/garage-door-controller#hardware-setup
* https://pinout.xyz/pinout/ground
* https://forum.hacf.fr/t/gpio-sur-rpi-4/73908
* https://newbiely.com/tutorials/raspberry-pi/raspberry-pi-door-sensor-relay

= Heating system control =
== eBUS Adapter Stick C6 ==
How is it recognized by HAOS:
<pre>[402858.821291] usb 1-1.3: new full-speed USB device number 3 using xhci_hcd
[402858.916632] usb 1-1.3: New USB device found, idVendor=303a, idProduct=1001, bcdDevice= 1.02
[402858.916664] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[402858.916676] usb 1-1.3: Product: USB JTAG/serial debug unit
[402858.916687] usb 1-1.3: Manufacturer: Espressif
[402858.916695] usb 1-1.3: SerialNumber: 58:E6:C5:F6:A1:8C
[402858.964414] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
[402858.964666] usbcore: registered new interface driver cdc_acm
[402858.964679] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters</pre>

The stick is configured by default on WiFi.
We need to connect to the WiFi, via the Opened SSID EBUS, then IP 192.168.4.1 and then change its connection type from TCP to USB Serial:
[[Fichier:EBUS C6.png]]

== eBUSd app ==
=== Configuration ===
USB eBUS adapter (--device): enh:/dev/ttyACM0

=== First and second start-up of the app ===
<pre>[11:12:55] INFO: eBUSd addon version 26.1.6
[11:12:56] INFO: Seeding default mqtt-hassio.cfg into addon config folder.
[11:12:56] INFO: ebusd --foreground --updatecheck=off --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=<redacted> --mqttpass=<redacted> --mqttjson --mqttint=/config/mqtt-hassio.cfg --device=enh:/dev/ttyACM0 --mqttjson
2026-03-18 11:12:57.257 [device notice] transport opened
2026-03-18 11:12:57.263 [main notice] ebusd 26.1.26.1 started with broadcast scan on device: /dev/ttyACM0, serial speed, enhanced
2026-03-18 11:12:57.505 [bus notice] bus started with own address 31/36
2026-03-18 11:12:57.505 [bus notice] signal acquired
2026-03-18 11:12:57.505 [device notice] reset, supports info
2026-03-18 11:12:58.135 [mqtt notice] connection established
2026-03-18 11:12:59.045 [bus error] signal lost
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: warning: service s6rc-oneshot-runner is marked as essential, not stopping it
2026-03-18 11:14:01.404 [main notice] SIGTERM received
2026-03-18 11:14:01.531 [device error] transport closed
2026-03-18 11:14:01.531 [main notice] ebusd stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[11:14:06] INFO: eBUSd addon version 26.1.6
[11:14:07] INFO: ebusd --foreground --updatecheck=off --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=<redacted> --mqttpass=<redacted> --mqttjson --mqttint=/config/mqtt-hassio.cfg --device=enh:/dev/ttyACM0 --mqttjson
2026-03-18 11:14:07.723 [device notice] transport opened
2026-03-18 11:14:07.727 [main notice] ebusd 26.1.26.1 started with broadcast scan on device: /dev/ttyACM0, serial speed, enhanced
2026-03-18 11:14:07.944 [bus notice] bus started with own address 31/36
2026-03-18 11:14:07.944 [device notice] reset, supports info
2026-03-18 11:14:07.948 [mqtt notice] connection established</pre>

=== MQTT ===
Two topics are created automatically under core-mosquitto\ebusd\global :
- running
- uptime

=== WebUI ===
<pre>
root@b4d7ad18-ebusd:/# ebusctl info
version: ebusd 26.1.26.1
device: /dev/ttyACM0, serial high speed, enhanced, firmware 1.1[6112].1[6112]
signal: acquired
symbol rate: 23
max symbol rate: 118
min arbitration micros: 2
max arbitration micros: 4326
min symbol latency: 3
max symbol latency: 10
scan: finished
reconnects: 0
masters: 3
messages: 717
conditional: 0
poll: 253
update: 16
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0703;HW=7401", loaded "vaillant/bai.0010006101.inc" ([Scan_id_product='']), "vaillant/08.bai.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=70000;SW=0510;HW=6403", loaded "vaillant/15.700.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd
</pre>

== Climate card ==
In configuration.yaml, add this configuration (specific to the Vaillant VRC700):
<pre>
mqtt:
climate:
- name: VRC700
unique_id: vaillant_vrc700_zone1_gv34

max_temp: 23
min_temp: 15
precision: 0.1
temp_step: 0.5

modes:
- 'auto'
- 'heat'
- 'cool'
- 'off'

mode_state_template: >-
{% set values = { 'auto':'auto', 'day':'heat', 'night':'cool', 'off':'off'} %}
{% set state = value_json.value.value %}
{{ values[state] if state in values.keys() else 'off' }}
mode_state_topic: "ebusd/700/Z1OpMode"

mode_command_template: >-
{% set values = { 'auto':'auto', 'heat':'day', 'cool':'night', 'off':'off'} %}
{{ values[value] if value in values.keys() else 'auto' }}
mode_command_topic: "ebusd/700/Z1OpMode/set"

temperature_state_topic: "ebusd/700/Z1ActualRoomTempDesired"
temperature_state_template: "{{ value_json.value.value }}"
temperature_command_topic: "ebusd/700/Z1ActualRoomTempDesired/set"

current_temperature_topic: "ebusd/700/Z1RoomTemp"
current_temperature_template: "{{ value_json.value.value }}"
</pre>

Result:

[[Fichier:VRC700 HA.png]]

In order to see the Mode current status & buttons (auto, day, night, off), then edit the yaml code of the card added on the dashboard and add the features section :
<pre>
type: thermostat
entity: climate.vrc700
features:
- type: climate-hvac-modes
hvac_modes:
- auto
- heat
- cool
- "off"
</pre>

== Credits & sources ==
* eBUSd HA integation: https://www.home-assistant.io/integrations/ebusd
* eBUSd USB stick: https://adapter.ebusd.eu/v5-c6/stick.en.html
* Global how-to (HA, Vaillant, eBUS, thermostat & climate): https://fromeijn.nl/connected-vaillant-to-home-assistant/
* Thermostat & climate integration: https://github.com/john30/ebusd/discussions/764
* Vaillant heat curves explained : https://protonsforbreakfast.wordpress.com/2024/10/16/vaillant-heat-pump-controls-part-1-the-heat-curves/

Home Assistant

2026-03-22T21:06:10Z

Apn : /* Climate card */

= Raspberry PI & Home Assistant OS =
== Custom routes issue ==
When installing HA natively on a RPI if static routing is needed, then the best solution is this one: 
https://www.reddit.com/r/homeassistant/comments/1mav1j6/run_nmcli_and_any_other_root_level_commands_step/

Step-by-Step: Access Full Root Shell on HAOS via Port 22222
# Install the Add-on Add HassOS SSH port 22222 Configurator via the Home Assistant Add-on Store (manual repository add required).
# Generate SSH Keys On your hassOS terminal :ssh-keygen cat ~/.ssh/id_rsa.pub
# Paste Public Key into Configurator Add-on Open the add-on config panel and paste your public key (id_rsa.pub) into the configuration.
# Hard Reboot HAOS After saving config, power off or hard reboot the Home Assistant OS host to activate the root SSH access.
# SSH into HAOS Root (Port 22222) On your terminal:ssh -p 22222 root@127.0.0.1
# Use nmcli and Other Commands Now you can run:This is the only method to modify connections that don’t appear in the GUI.nmcli connection show nmcli connection delete <name>
# (Optional) Delete or Reset Network Configurations You can also:cd /etc/NetworkManager/system-connections/ rm <stale-profile>.nmconnection reboot
# Cleanup Once fixed: Uninstall the 22222 Configurator & Remove your public key if desired

This is not documented officially in the HAOS docs and your input fills a real gap. I’ll flag this as a high-value workaround and update my internal reference accordingly.

Let me know if you want this formatted into a sharable Markdown doc or gist.
Sources:
* https://community.home-assistant.io/t/add-on-hassos-ssh-port-22222-configurator/264109
* https://community.home-assistant.io/t/command-not-found-nmcli/902180
* https://github.com/home-assistant/operating-system/blob/0724608f/Documentation/network.md#L151-L189 </pre>

=== Adding the route ===
Then specifically for my case:
<pre>apn@macbook-pro-apn ~ % ssh -p 22222 root@192.168.1.111
Enter passphrase for key '/Users/apn/.ssh/id_ed25519':
Welcome to Home Assistant OS.

Use `ha` to access the Home Assistant CLI.
# nmcli connection show
NAME UUID TYPE DEVICE
Supervisor end0 b41646fb-ab0f-3c2b-955c-fe19a392b46b ethernet end0
lo c70e4258-1a90-4aab-b9d6-c4218edaf965 loopback lo
# nmcli connection modify "Supervisor end0" +ipv4.routes "192.168.2.0/24 192.168.1.101"
# nmcli connection up "Supervisor end0"
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/4)
# </pre>

= Garage Remote control =

Sometimes a remote control can send multiple button/click triggers even when a button is pushed once.

That's the case with the [https://fr.aliexpress.com/item/4001062612446.html ''Tuya Zigbee3.0 Remote Control With 4 Key'']] that I just bought to trigger a Zigbee dry relay MHCOZY TYZG-001-RF (only used in Zigbee mode & cabled in NO - Normally opened). This dry relay simulates a push button to open a Garage door.

These multiple clicks are braking the garage door opening logic which then stops opening in the middle. In order to solve this, I used what we call in IT a '''mutex'''.

Here are the scripts to make this work properly:

== MHCOZY ZG-001 ==

[[Fichier:MHCOZY TYZG-001-RF.png]]

Go to '''Settings > Automations & scenes > Scripts''' and create the following script:
<pre>alias: Pulse TUZG Relay (0.5s)
mode: single
sequence:
- target:
entity_id: light.mhcozy_tyzg_001_rf
action: light.turn_on
- delay:
milliseconds: 500
- target:
entity_id: light.mhcozy_tyzg_001_rf
action: light.turn_off
</pre>

== Tuya Zigbee3.0 Remote Control ==

[[Fichier:Tuya Remote Control.png]]

Go to '''Settings > Devices & services > Helpers''' and create the following Boolean '''Toggle''':
<pre>Name: garage_remote_control_lock
Entity ID: input_boolean.garage_remote_control_lock</pre>
Make sure it's set to Off (click on it when created to set its state).

Then go to '''Settings > Automations & scenes > Automations''' and create the following script:
<pre>alias: Garage remote control
description: Trigger the garage door opening/closing via the remote control with lock to prevent duplicates
triggers:
- event_type: zha_event
event_data:
device_ieee: $your_device_ieee_identifier
command: arm
trigger: event
conditions:
- condition: state
entity_id: input_boolean.garage_remote_control_lock
state: "off"
actions:
- action: input_boolean.turn_on
data: {}
target:
entity_id: input_boolean.garage_remote_control_lock
- action: script.pulse_relay_0_5s
data: {}
- delay:
seconds: 10
- action: input_boolean.turn_off
data: {}
target:
entity_id: input_boolean.garage_remote_control_lock
mode: single</pre>

To make sure the value is at OFF at HA startup (i.e. to avoid specific bad situations when the HA crashes in the middle of the door opening automation and the toggle does not get reset), then create another automation:
<pre>alias: Garage remote control lock reset on startup
triggers:
- event: start
trigger: homeassistant
actions:
- target:
entity_id: input_boolean.garage_remote_control_lock
action: input_boolean.turn_off
data: {}
mode: single</pre>

== ZHAQuirks for TS0601 ==

The TS0601 by _TZE204_nklqjk62 is not recognized by HomeAssistant ZHA.

=== Signature of the device ===
<pre>{
"node_descriptor": {
"logical_type": 1,
"complex_descriptor_available": 0,
"user_descriptor_available": 0,
"reserved": 0,
"aps_flags": 0,
"frequency_band": 8,
"mac_capability_flags": 142,
"manufacturer_code": 4417,
"maximum_buffer_size": 66,
"maximum_incoming_transfer_size": 66,
"server_mask": 10752,
"maximum_outgoing_transfer_size": 66,
"descriptor_capability_field": 0
},
"endpoints": {
"1": {
"profile_id": "0x0104",
"device_type": "0x0100",
"input_clusters": [
"0x0000",
"0x0004",
"0x0005",
"0x0006",
"0xef00"
],
"output_clusters": [
"0x000a",
"0x0019"
]
},
"2": {
"profile_id": "0x0104",
"device_type": "0x0402",
"input_clusters": [
"0x0500"
],
"output_clusters": []
},
"242": {
"profile_id": "0xa1e0",
"device_type": "0x0061",
"input_clusters": [],
"output_clusters": [
"0x0021"
]
}
},
"manufacturer": "_TZE204_nklqjk62",
"model": "TS0601",
"class": "ts0601_garage.TuyaGarageSwitchTO"
}</pre>

=== How-to make it work ===
<pre>
[core-ssh zhaquirks]$ pwd
/config/zhaquirks
[core-ssh zhaquirks]$ cat ts0601_garage.py
"""Tuya based cover and blinds."""
from typing import Dict

from zigpy.profiles import zgp, zha
from zigpy.quirks import CustomDevice
import zigpy.types as t
from zigpy.zcl.clusters.general import Basic, GreenPowerProxy, Groups, Ota, Scenes, Time
from zigpy.zcl.clusters.security import IasZone

from zhaquirks.const import (
DEVICE_TYPE,
ENDPOINTS,
INPUT_CLUSTERS,
MODELS_INFO,
OUTPUT_CLUSTERS,
PROFILE_ID,
)

from zhaquirks.tuya import NoManufacturerCluster, TuyaLocalCluster
from zhaquirks.tuya.mcu import (
DPToAttributeMapping,
TuyaMCUCluster,
TuyaOnOff,
)
from zhaquirks.tuya.ts0601_dimmer import TuyaOnOffNM

ZONE_TYPE = 0x0001

class ContactSwitchCluster(TuyaLocalCluster, IasZone):
"""Tuya ContactSwitch Sensor."""

_CONSTANT_ATTRIBUTES = {ZONE_TYPE: IasZone.ZoneType.Contact_Switch}

def _update_attribute(self, attrid, value):
self.debug("_update_attribute '%s': %s", attrid, value)
super()._update_attribute(attrid, value)

class TuyaGarageManufCluster(NoManufacturerCluster, TuyaMCUCluster):
"""Tuya garage door opener."""

attributes = TuyaMCUCluster.attributes.copy()
attributes.update(
{
# ramdom attribute IDs
0xEF02: ("dp_2", t.uint32_t, True),
0xEF04: ("dp_4", t.uint32_t, True),
0xEF05: ("dp_5", t.uint32_t, True),
0xEF0B: ("dp_11", t.Bool, True),
0xEF0C: ("dp_12", t.enum8, True),
}
)

dp_to_attribute: Dict[int, DPToAttributeMapping] = {
# garage door trigger ¿on movement, on open, on closed?
1: DPToAttributeMapping(
TuyaOnOffNM.ep_attribute,
"on_off",
),
2: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"dp_2",
),
3: DPToAttributeMapping(
ContactSwitchCluster.ep_attribute,
"zone_status",
lambda x: IasZone.ZoneStatus.Alarm_1 if x else 0,
endpoint_id=2,
),
4: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"dp_4",
),
5: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"dp_5",
),
11: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"dp_11",
),
# garage door status (open, closed, ...)
12: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"dp_12",
),
}

data_point_handlers = {
1: "_dp_2_attr_update",
2: "_dp_2_attr_update",
3: "_dp_2_attr_update",
4: "_dp_2_attr_update",
5: "_dp_2_attr_update",
11: "_dp_2_attr_update",
12: "_dp_2_attr_update",
}

class TuyaGarageSwitchTO(CustomDevice):
"""Tuya Garage switch."""

signature = {
MODELS_INFO: [
("_TZE200_nklqjk62", "TS0601"),
("_TZE200_wfxuhoea", "TS0601"),
("_TZE204_nklqjk62", "TS0601"),
],
ENDPOINTS: {
# <SimpleDescriptor endpoint=1 profile=260 device_type=0x0051
# input_clusters=[0, 4, 5, 61184]
# output_clusters=[10, 25]>
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaGarageManufCluster.cluster_id,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
},
# <SimpleDescriptor endpoint=242 profile=41440 device_type=97
# input_clusters=[]
# output_clusters=[33]
242: {
PROFILE_ID: zgp.PROFILE_ID,
DEVICE_TYPE: zgp.DeviceType.PROXY_BASIC,
INPUT_CLUSTERS: [],
OUTPUT_CLUSTERS: [GreenPowerProxy.cluster_id],
},
},
}

replacement = {
ENDPOINTS: {
1: {
DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaGarageManufCluster,
TuyaOnOffNM,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
},
2: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.IAS_ZONE,
INPUT_CLUSTERS: [
ContactSwitchCluster
],
OUTPUT_CLUSTERS: [],
},
242: {
PROFILE_ID: zgp.PROFILE_ID,
DEVICE_TYPE: zgp.DeviceType.PROXY_BASIC,
INPUT_CLUSTERS: [],
OUTPUT_CLUSTERS: [GreenPowerProxy.cluster_id],
},
},
}
[core-ssh zhaquirks]$ cd ..
[core-ssh config]$ tail -n 2 configuration.yaml
zha:
custom_quirks_path: /config/zhaquirks
</pre>

Then restart Home Assistant and discover the device. If the device was previously wrongly discovered, just delete it and discover it again.

=== Result ===
[[Fichier:TS0601.png]]

=== Credits ===
* https://github.com/zigpy/zha-device-handlers/issues/2533
* https://community.home-assistant.io/t/tuya-ts0601-zigbee-garage-door-opener/466400/5

== Garage door control ==
I finally replaced my ZigBee relay & sensor used to control the Garage door by a full wired logic connected to the GPIO and using the Raspberry Pi GPIO (rp_gpio) HACS add-on.
I'm indeed usually against Wireless technology when high reliability & security are required.

=== Hardware ===
* Dry contact relay: [https://www.amazon.com.be/dp/B0F59PPVZB 5 Pack 5V Channel Relay Module, 1 Channel Relay Module with Optocoupler High or Low Level Trigger Expansion Board for Raspberry Pi Arduino Board]
* Breakout board: [https://www.amazon.com.be/dp/B0DM4YKVCX Geekworm G469 GPIO Terminal Block Breakout Board for Raspberry Pi 4B/3B+/3B/ Zero 2W]
* Jumper wire cables: [https://www.amazon.com.be/dp/B074P726ZR AZDelivery Jumper Wire Cable 3 x 40 pcs. each 20 cm M2M/ F2M/F2F, 40 Pin Male to Male, 40 Pin Female to Female, Compatible with Arduino and Raspberry Pi Breadboard including an E-Book]

=== Cabling ===
[[Fichier:Gpio.jpg|300px|]]
* Garage door magnetic sensor: GPIO_17 (pin #11) + GND (pin #9)
* Relay:
** DCC+ => 5V (pin #4)
** DCC- => GND (pin #6)
** Signal (relay trigger) => GPIO_4 (pin #7)

=== Configuration ===
<pre>[core-ssh config]$ tail -n 12 configuration.yaml
switch:
- platform: rpi_gpio
switches:
- port: 4
name: "Garage door button - GPIO_4"
unique_id: "garage_door_switch_port_4"
binary_sensor:
- platform: rpi_gpio
sensors:
- port: 17
name: "Garage door sensor - GPIO_17"
unique_id: "garage_door_sensor_port_17"</pre>

=== Credits ===
* https://github.com/andrewshilliday/garage-door-controller#hardware-setup
* https://pinout.xyz/pinout/ground
* https://forum.hacf.fr/t/gpio-sur-rpi-4/73908
* https://newbiely.com/tutorials/raspberry-pi/raspberry-pi-door-sensor-relay

= Heating system control =
== eBUS Adapter Stick C6 ==
How is it recognized by HAOS:
<pre>[402858.821291] usb 1-1.3: new full-speed USB device number 3 using xhci_hcd
[402858.916632] usb 1-1.3: New USB device found, idVendor=303a, idProduct=1001, bcdDevice= 1.02
[402858.916664] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[402858.916676] usb 1-1.3: Product: USB JTAG/serial debug unit
[402858.916687] usb 1-1.3: Manufacturer: Espressif
[402858.916695] usb 1-1.3: SerialNumber: 58:E6:C5:F6:A1:8C
[402858.964414] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
[402858.964666] usbcore: registered new interface driver cdc_acm
[402858.964679] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters</pre>

The stick is configured by default on WiFi.
We need to connect to the WiFi, via the Opened SSID EBUS, then IP 192.168.4.1 and then change its connection type from TCP to USB Serial:
[[Fichier:EBUS C6.png]]

== eBUSd app ==
=== Configuration ===
USB eBUS adapter (--device): enh:/dev/ttyACM0

=== First and second start-up of the app ===
<pre>[11:12:55] INFO: eBUSd addon version 26.1.6
[11:12:56] INFO: Seeding default mqtt-hassio.cfg into addon config folder.
[11:12:56] INFO: ebusd --foreground --updatecheck=off --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=<redacted> --mqttpass=<redacted> --mqttjson --mqttint=/config/mqtt-hassio.cfg --device=enh:/dev/ttyACM0 --mqttjson
2026-03-18 11:12:57.257 [device notice] transport opened
2026-03-18 11:12:57.263 [main notice] ebusd 26.1.26.1 started with broadcast scan on device: /dev/ttyACM0, serial speed, enhanced
2026-03-18 11:12:57.505 [bus notice] bus started with own address 31/36
2026-03-18 11:12:57.505 [bus notice] signal acquired
2026-03-18 11:12:57.505 [device notice] reset, supports info
2026-03-18 11:12:58.135 [mqtt notice] connection established
2026-03-18 11:12:59.045 [bus error] signal lost
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: warning: service s6rc-oneshot-runner is marked as essential, not stopping it
2026-03-18 11:14:01.404 [main notice] SIGTERM received
2026-03-18 11:14:01.531 [device error] transport closed
2026-03-18 11:14:01.531 [main notice] ebusd stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[11:14:06] INFO: eBUSd addon version 26.1.6
[11:14:07] INFO: ebusd --foreground --updatecheck=off --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=<redacted> --mqttpass=<redacted> --mqttjson --mqttint=/config/mqtt-hassio.cfg --device=enh:/dev/ttyACM0 --mqttjson
2026-03-18 11:14:07.723 [device notice] transport opened
2026-03-18 11:14:07.727 [main notice] ebusd 26.1.26.1 started with broadcast scan on device: /dev/ttyACM0, serial speed, enhanced
2026-03-18 11:14:07.944 [bus notice] bus started with own address 31/36
2026-03-18 11:14:07.944 [device notice] reset, supports info
2026-03-18 11:14:07.948 [mqtt notice] connection established</pre>

=== MQTT ===
Two topics are created automatically under core-mosquitto\ebusd\global :
- running
- uptime

=== WebUI ===
<pre>
root@b4d7ad18-ebusd:/# ebusctl info
version: ebusd 26.1.26.1
device: /dev/ttyACM0, serial high speed, enhanced, firmware 1.1[6112].1[6112]
signal: acquired
symbol rate: 23
max symbol rate: 118
min arbitration micros: 2
max arbitration micros: 4326
min symbol latency: 3
max symbol latency: 10
scan: finished
reconnects: 0
masters: 3
messages: 717
conditional: 0
poll: 253
update: 16
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0703;HW=7401", loaded "vaillant/bai.0010006101.inc" ([Scan_id_product='']), "vaillant/08.bai.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=70000;SW=0510;HW=6403", loaded "vaillant/15.700.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd
</pre>

== Climate card ==
In configuration.yaml, add this configuration (specific to the Vaillant VRC700):
<pre>
mqtt:
climate:
- name: VRC700
unique_id: vaillant_vrc700_zone1_gv34

max_temp: 23
min_temp: 15
precision: 0.1
temp_step: 0.5

modes:
- 'auto'
- 'heat'
- 'cool'
- 'off'

mode_state_template: >-
{% set values = { 'auto':'auto', 'day':'heat', 'night':'cool', 'off':'off'} %}
{% set state = value_json.value.value %}
{{ values[state] if state in values.keys() else 'off' }}
mode_state_topic: "ebusd/700/Z1OpMode"

mode_command_template: >-
{% set values = { 'auto':'auto', 'heat':'day', 'cool':'night', 'off':'off'} %}
{{ values[value] if value in values.keys() else 'auto' }}
mode_command_topic: "ebusd/700/Z1OpMode/set"

temperature_state_topic: "ebusd/700/Z1ActualRoomTempDesired"
temperature_state_template: "{{ value_json.value.value }}"
temperature_command_topic: "ebusd/700/Z1ActualRoomTempDesired/set"

current_temperature_topic: "ebusd/700/Z1RoomTemp"
current_temperature_template: "{{ value_json.value.value }}"
</pre>

Result:

[[Fichier:VRC700 HA.png]]

In order to see the Mode current status & buttons (auto, day, night, off), then edit the yaml code of the card added on the dashboard and add the features section :
<pre>
type: thermostat
entity: climate.vrc700
features:
- type: climate-hvac-modes
hvac_modes:
- auto
- heat
- cool
- "off"
</pre>

== Credits & sources ==
* eBUSd HA integation: https://www.home-assistant.io/integrations/ebusd
* eBUSd USB stick: https://adapter.ebusd.eu/v5-c6/stick.en.html
* Global how-to (HA, Vaillant, eBUS, thermostat & climate): https://fromeijn.nl/connected-vaillant-to-home-assistant/
* Thermostat & climate integration: https://github.com/john30/ebusd/discussions/764
* Vaillant heat curves explained : https://protonsforbreakfast.wordpress.com/2024/10/16/vaillant-heat-pump-controls-part-1-the-heat-curves/

Home Assistant

2026-03-22T20:57:43Z

Apn : /* Climate card */

2026-03-22T10:32:32Z

Apn :

Apn : +eBUS

FreeBSD

2026-02-09T10:33:01Z

Apn : /* ZFS snapshots */

= Named =
== Manually updating a Dynamic controlled zone ==
''"If you have to edit the zone files of dynamic zones manually while the DNS server is running, you'll have to freeze the zones with '''# rndc freeze <myzone>''' before editing and unfreeze them with '''# rndc thaw <myzone>''' after editing. This is because named(8) has internal state information and external journal files attached to dynamic zones that have to be kept in sync with the zone files<ref>https://forums.freebsd.org/threads/dynamic-dns-with-bind-and-isc-dhcp-server.33849/</ref>"''.

= Rsync =

To delete files in the target if they disappeared from the source, then add the --delete option to your command. For example:

rsync -avh source/ dest/ --delete 
NB: -avh is for --archive --verbose --human-readable<ref>https://askubuntu.com/a/665918</ref>.

== Migration of folders to a new server ==

=== One shot ===

<pre>
rsync -av /var/db/ports/ root@newice3:/var/db/ports/
rsync -av /etc/ root@newice3:/etc/oldice3/
rsync -av /usr/local/etc/ root@newice3:/usr/local/etc/oldice3/
rsync -av /etc/ssh/ssh_config /etc/ssh/sshd_config newice3:/etc/ssh/
rsync -av /etc/banner /etc/motd.template /etc/pki/ newice3:/etc/
rsync -av /etc/pki/ newice3:/etc/pki/
rsync -av /usr/local/lib/sasl2/smtpd.conf root@newice3:/usr/local/lib/sasl2/
rsync -av /var/ftp/ newice3:/var/ftp/
</pre>

=== 1 full + diff at the migration time ===

<pre>
rsync -av --exclude={'rc.d','oldice3','newice3','namedb','openvpn','pkg.conf','portsnap.conf'} /usr/local/etc/ root@newice3:/usr/local/etc/ --delete --dry-run
rsync -av /etc/pf.blocked.ip.conf root@newice3:/etc/ --dry-run
rsync -av /etc/pf.blocked.webspam.conf root@newice3:/etc/ --dry-run
rsync -av /etc/pf.blocked.webspam_awstats.conf root@newice3:/etc/ --dry-run
rsync -av /root/ root@newice3:/root/ --delete --dry-run
rsync -av /home/ root@newice3:/home/ --delete --dry-run
rsync -av /var/www/ root@newice3:/var/www/ --delete --dry-run
rsync -av /usr/local/www/ root@newice3:/usr/local/www/ --delete --dry-run
rsync -av /var/log/ root@newice3:/var/log/oldice3/ --delete --dry-run
rsync -av /var/awstats/ root@newice3:/var/awstats/ --delete --dry-run
rsync -av /var/log/www/ root@newice3:/var/log/www/ --delete --dry-run
rsync -av /var/db/fail2ban/ root@newice3:/var/db/fail2ban/ --delete --dry-run
rsync -av /var/db/mysql/ root@newice3:/var/db/mysql/ --delete --dry-run (to do when mysql server is off)
</pre>

= Nginx =
== Maxmind ==
Country based filtering can be performed in nginx thanks to the free Maxmind databases.

A cron job shall be used to update these databases on a daily basis<ref>https://herrbischoff.com/2021/05/nginx-how-to-restrict-access-by-geographical-location-on-freebsd/</ref>

= ZFS snapshots =
FreeBSD creates a snapshot at each update (freebsd-update fetch && freebsd-update install). These snapshots are not needed anymore should your system restarts & runs correctly. Moreover they take loads of space on your hardrive.

== Procedure to delete ==

=== List & check ===
<pre>root@icecube BSD:~ # bectl list
BE Active Mountpoint Space Created
14.3-RELEASE-p6_2025-12-19_121434 - - 927M 2025-12-19 12:14
default NR / 814G 2023-12-01 23:34
</pre>
Check that the active Boot Envionment is the default (NR set on default).

<pre>root@icecube BSD:~ # zfs list -t snapshot
NAME USED AVAIL REFER MOUNTPOINT
zroot/ROOT/default@2025-12-19-12:14:34-0 927M - 812G -
</pre>

=== Delete ===

<pre>root@icecube BSD:~ # bectl destroy 14.3-RELEASE-p6_2025-12-19_121434
</pre>

=== Results ===
<pre>root@icecube BSD:~ # bectl list
BE Active Mountpoint Space Created
default NR / 813G 2023-12-01 23:34
root@icecube BSD:~ # zfs list -t snapshot
no datasets available
</pre>

= Reboot or no reboot after a minor system upgrade ? =

After a system upgrade performed thanks to :
<pre>root@icecube BSD:~ # freebsd-update fetch
root@icecube BSD:~ # freebsd-update install
</pre>

If the output of these two commands differs, then reboot your system:
<pre>root@icecube BSD:~ # freebsd-version -k
14.3-RELEASE-p7
root@icecube BSD:~ # uname -r
14.3-RELEASE-p7
</pre>

= PF =
After a reboot of FreeBSD, PF may fail to start due to tables being too big (i.e. > 100k entries). 
This is explained here with a quick & dirty non-permanent fix : 
https://forums.freebsd.org/threads/table-loading-in-pf-issues.86101/#post-577832
# First load the PF Options only (specific to big tables handling): pfctl -Of /etc/pf.conf
# Then restart PF the usual way

<pre>root@icecube BSD:~ # service pf restart
Disabling pf.
Enabling pf/etc/pf.conf:98: cannot define table firehol4: Cannot allocate memory
pfctl: Syntax error in config file: pf rules not loaded
/etc/rc.d/pf: WARNING: Unable to load /etc/pf.conf.
.
root@icecube BSD:~ # sed -n '98p' /etc/pf.conf
table <firehol4> persist file "/etc/pf_table_firehol4"
root@icecube BSD:~ # wc -l /etc/pf_table_firehol4
99856 /etc/pf_table_firehol4
root@icecube BSD:~ # pfctl -Of /etc/pf.conf
root@icecube BSD:~ # service pf restart
Disabling pf.
Enabling pf.
root@icecube BSD:~ # </pre>

= References =
{{references}}

FreeBSD

2026-02-06T09:27:32Z

Apn : /* PF */

= Named =
== Manually updating a Dynamic controlled zone ==
''"If you have to edit the zone files of dynamic zones manually while the DNS server is running, you'll have to freeze the zones with '''# rndc freeze <myzone>''' before editing and unfreeze them with '''# rndc thaw <myzone>''' after editing. This is because named(8) has internal state information and external journal files attached to dynamic zones that have to be kept in sync with the zone files<ref>https://forums.freebsd.org/threads/dynamic-dns-with-bind-and-isc-dhcp-server.33849/</ref>"''.

= Rsync =

To delete files in the target if they disappeared from the source, then add the --delete option to your command. For example:

rsync -avh source/ dest/ --delete 
NB: -avh is for --archive --verbose --human-readable<ref>https://askubuntu.com/a/665918</ref>.

== Migration of folders to a new server ==

=== One shot ===

<pre>
rsync -av /var/db/ports/ root@newice3:/var/db/ports/
rsync -av /etc/ root@newice3:/etc/oldice3/
rsync -av /usr/local/etc/ root@newice3:/usr/local/etc/oldice3/
rsync -av /etc/ssh/ssh_config /etc/ssh/sshd_config newice3:/etc/ssh/
rsync -av /etc/banner /etc/motd.template /etc/pki/ newice3:/etc/
rsync -av /etc/pki/ newice3:/etc/pki/
rsync -av /usr/local/lib/sasl2/smtpd.conf root@newice3:/usr/local/lib/sasl2/
rsync -av /var/ftp/ newice3:/var/ftp/
</pre>

=== 1 full + diff at the migration time ===

<pre>
rsync -av --exclude={'rc.d','oldice3','newice3','namedb','openvpn','pkg.conf','portsnap.conf'} /usr/local/etc/ root@newice3:/usr/local/etc/ --delete --dry-run
rsync -av /etc/pf.blocked.ip.conf root@newice3:/etc/ --dry-run
rsync -av /etc/pf.blocked.webspam.conf root@newice3:/etc/ --dry-run
rsync -av /etc/pf.blocked.webspam_awstats.conf root@newice3:/etc/ --dry-run
rsync -av /root/ root@newice3:/root/ --delete --dry-run
rsync -av /home/ root@newice3:/home/ --delete --dry-run
rsync -av /var/www/ root@newice3:/var/www/ --delete --dry-run
rsync -av /usr/local/www/ root@newice3:/usr/local/www/ --delete --dry-run
rsync -av /var/log/ root@newice3:/var/log/oldice3/ --delete --dry-run
rsync -av /var/awstats/ root@newice3:/var/awstats/ --delete --dry-run
rsync -av /var/log/www/ root@newice3:/var/log/www/ --delete --dry-run
rsync -av /var/db/fail2ban/ root@newice3:/var/db/fail2ban/ --delete --dry-run
rsync -av /var/db/mysql/ root@newice3:/var/db/mysql/ --delete --dry-run (to do when mysql server is off)
</pre>

= Nginx =
== Maxmind ==
Country based filtering can be performed in nginx thanks to the free Maxmind databases.

A cron job shall be used to update these databases on a daily basis<ref>https://herrbischoff.com/2021/05/nginx-how-to-restrict-access-by-geographical-location-on-freebsd/</ref>

= ZFS snapshots =
FreeBSD creates a snapshot at each FreeBSD update (freebsd-update fetch && freebsd-update install). These snapshots are not needed anymore should your system restarts & runs correctly. Moreover they take loads of space on your hardrive.

== Procedure to delete ==

=== List & check ===
<pre>root@icecube BSD:~ # bectl list
BE Active Mountpoint Space Created
14.3-RELEASE-p6_2025-12-19_121434 - - 927M 2025-12-19 12:14
default NR / 814G 2023-12-01 23:34
</pre>
Check that the active Boot Envionment is the default (NR set on default).

<pre>root@icecube BSD:~ # zfs list -t snapshot
NAME USED AVAIL REFER MOUNTPOINT
zroot/ROOT/default@2025-12-19-12:14:34-0 927M - 812G -
</pre>

=== Delete ===

<pre>root@icecube BSD:~ # bectl destroy 14.3-RELEASE-p6_2025-12-19_121434
</pre>

=== Results ===
<pre>root@icecube BSD:~ # bectl list
BE Active Mountpoint Space Created
default NR / 813G 2023-12-01 23:34
root@icecube BSD:~ # zfs list -t snapshot
no datasets available
</pre>

= Reboot or no reboot after a minor system upgrade ? =

After a system upgrade performed thanks to :
<pre>root@icecube BSD:~ # freebsd-update fetch
root@icecube BSD:~ # freebsd-update install
</pre>

If the output of these two commands differs, then reboot your system:
<pre>root@icecube BSD:~ # freebsd-version -k
14.3-RELEASE-p7
root@icecube BSD:~ # uname -r
14.3-RELEASE-p7
</pre>

= PF =
After a reboot of FreeBSD, PF may fail to start due to tables being too big (i.e. > 100k entries). 
This is explained here with a quick & dirty non-permanent fix : 
https://forums.freebsd.org/threads/table-loading-in-pf-issues.86101/#post-577832
# First load the PF Options only (specific to big tables handling): pfctl -Of /etc/pf.conf
# Then restart PF the usual way

<pre>root@icecube BSD:~ # service pf restart
Disabling pf.
Enabling pf/etc/pf.conf:98: cannot define table firehol4: Cannot allocate memory
pfctl: Syntax error in config file: pf rules not loaded
/etc/rc.d/pf: WARNING: Unable to load /etc/pf.conf.
.
root@icecube BSD:~ # sed -n '98p' /etc/pf.conf
table <firehol4> persist file "/etc/pf_table_firehol4"
root@icecube BSD:~ # wc -l /etc/pf_table_firehol4
99856 /etc/pf_table_firehol4
root@icecube BSD:~ # pfctl -Of /etc/pf.conf
root@icecube BSD:~ # service pf restart
Disabling pf.
Enabling pf.
root@icecube BSD:~ # </pre>

= References =
{{references}}

FreeBSD

2026-02-06T09:26:12Z

Apn : /* PF */

= Named =
== Manually updating a Dynamic controlled zone ==
''"If you have to edit the zone files of dynamic zones manually while the DNS server is running, you'll have to freeze the zones with '''# rndc freeze <myzone>''' before editing and unfreeze them with '''# rndc thaw <myzone>''' after editing. This is because named(8) has internal state information and external journal files attached to dynamic zones that have to be kept in sync with the zone files<ref>https://forums.freebsd.org/threads/dynamic-dns-with-bind-and-isc-dhcp-server.33849/</ref>"''.

= Rsync =

To delete files in the target if they disappeared from the source, then add the --delete option to your command. For example:

rsync -avh source/ dest/ --delete 
NB: -avh is for --archive --verbose --human-readable<ref>https://askubuntu.com/a/665918</ref>.

== Migration of folders to a new server ==

=== One shot ===

<pre>
rsync -av /var/db/ports/ root@newice3:/var/db/ports/
rsync -av /etc/ root@newice3:/etc/oldice3/
rsync -av /usr/local/etc/ root@newice3:/usr/local/etc/oldice3/
rsync -av /etc/ssh/ssh_config /etc/ssh/sshd_config newice3:/etc/ssh/
rsync -av /etc/banner /etc/motd.template /etc/pki/ newice3:/etc/
rsync -av /etc/pki/ newice3:/etc/pki/
rsync -av /usr/local/lib/sasl2/smtpd.conf root@newice3:/usr/local/lib/sasl2/
rsync -av /var/ftp/ newice3:/var/ftp/
</pre>

=== 1 full + diff at the migration time ===

<pre>
rsync -av --exclude={'rc.d','oldice3','newice3','namedb','openvpn','pkg.conf','portsnap.conf'} /usr/local/etc/ root@newice3:/usr/local/etc/ --delete --dry-run
rsync -av /etc/pf.blocked.ip.conf root@newice3:/etc/ --dry-run
rsync -av /etc/pf.blocked.webspam.conf root@newice3:/etc/ --dry-run
rsync -av /etc/pf.blocked.webspam_awstats.conf root@newice3:/etc/ --dry-run
rsync -av /root/ root@newice3:/root/ --delete --dry-run
rsync -av /home/ root@newice3:/home/ --delete --dry-run
rsync -av /var/www/ root@newice3:/var/www/ --delete --dry-run
rsync -av /usr/local/www/ root@newice3:/usr/local/www/ --delete --dry-run
rsync -av /var/log/ root@newice3:/var/log/oldice3/ --delete --dry-run
rsync -av /var/awstats/ root@newice3:/var/awstats/ --delete --dry-run
rsync -av /var/log/www/ root@newice3:/var/log/www/ --delete --dry-run
rsync -av /var/db/fail2ban/ root@newice3:/var/db/fail2ban/ --delete --dry-run
rsync -av /var/db/mysql/ root@newice3:/var/db/mysql/ --delete --dry-run (to do when mysql server is off)
</pre>

= Nginx =
== Maxmind ==
Country based filtering can be performed in nginx thanks to the free Maxmind databases.

A cron job shall be used to update these databases on a daily basis<ref>https://herrbischoff.com/2021/05/nginx-how-to-restrict-access-by-geographical-location-on-freebsd/</ref>

= ZFS snapshots =
FreeBSD creates a snapshot at each FreeBSD update (freebsd-update fetch && freebsd-update install). These snapshots are not needed anymore should your system restarts & runs correctly. Moreover they take loads of space on your hardrive.

== Procedure to delete ==

=== List & check ===
<pre>root@icecube BSD:~ # bectl list
BE Active Mountpoint Space Created
14.3-RELEASE-p6_2025-12-19_121434 - - 927M 2025-12-19 12:14
default NR / 814G 2023-12-01 23:34
</pre>
Check that the active Boot Envionment is the default (NR set on default).

<pre>root@icecube BSD:~ # zfs list -t snapshot
NAME USED AVAIL REFER MOUNTPOINT
zroot/ROOT/default@2025-12-19-12:14:34-0 927M - 812G -
</pre>

=== Delete ===

<pre>root@icecube BSD:~ # bectl destroy 14.3-RELEASE-p6_2025-12-19_121434
</pre>

=== Results ===
<pre>root@icecube BSD:~ # bectl list
BE Active Mountpoint Space Created
default NR / 813G 2023-12-01 23:34
root@icecube BSD:~ # zfs list -t snapshot
no datasets available
</pre>

= Reboot or no reboot after a minor system upgrade ? =

After a system upgrade performed thanks to :
<pre>root@icecube BSD:~ # freebsd-update fetch
root@icecube BSD:~ # freebsd-update install
</pre>

If the output of these two commands differs, then reboot your system:
<pre>root@icecube BSD:~ # freebsd-version -k
14.3-RELEASE-p7
root@icecube BSD:~ # uname -r
14.3-RELEASE-p7
</pre>

= PF =
After a reboot of FreeBSD, PF may fail to start due to tables being too big (i.e. > 100k entries). 
This is explained here with a quick & dirty non-permanent fix : 
https://forums.freebsd.org/threads/table-loading-in-pf-issues.86101/#post-577832
# First load the PF Options only (specific to big tables handling): pfctl -Of /etc/pf.conf
# Then restart PF the usual way

<pre>root@icecube BSD:~ # service pf restart
Disabling pf.
Enabling pf/etc/pf.conf:98: cannot define table firehol4: Cannot allocate memory
pfctl: Syntax error in config file: pf rules not loaded
/etc/rc.d/pf: WARNING: Unable to load /etc/pf.conf.
.
root@icecube BSD:~ # sed -n '98p' /etc/pf.conf
table <firehol4> persist file "/etc/pf_table_firehol4"
root@icecube BSD:~ # wc -l /etc/pf_table_firehol4
99856 /etc/pf_table_firehol4
root@icecube BSD:~ # pfctl -Of /etc/pf.conf
root@icecube BSD:~ # service pf restart
Disabling pf.
Enabling pf.</pre>

= References =
{{references}}

FreeBSD

2026-02-06T09:23:52Z

Apn : /* PF */

= Named =
== Manually updating a Dynamic controlled zone ==
''"If you have to edit the zone files of dynamic zones manually while the DNS server is running, you'll have to freeze the zones with '''# rndc freeze <myzone>''' before editing and unfreeze them with '''# rndc thaw <myzone>''' after editing. This is because named(8) has internal state information and external journal files attached to dynamic zones that have to be kept in sync with the zone files<ref>https://forums.freebsd.org/threads/dynamic-dns-with-bind-and-isc-dhcp-server.33849/</ref>"''.

= Rsync =

To delete files in the target if they disappeared from the source, then add the --delete option to your command. For example:

rsync -avh source/ dest/ --delete 
NB: -avh is for --archive --verbose --human-readable<ref>https://askubuntu.com/a/665918</ref>.

== Migration of folders to a new server ==

=== One shot ===

<pre>
rsync -av /var/db/ports/ root@newice3:/var/db/ports/
rsync -av /etc/ root@newice3:/etc/oldice3/
rsync -av /usr/local/etc/ root@newice3:/usr/local/etc/oldice3/
rsync -av /etc/ssh/ssh_config /etc/ssh/sshd_config newice3:/etc/ssh/
rsync -av /etc/banner /etc/motd.template /etc/pki/ newice3:/etc/
rsync -av /etc/pki/ newice3:/etc/pki/
rsync -av /usr/local/lib/sasl2/smtpd.conf root@newice3:/usr/local/lib/sasl2/
rsync -av /var/ftp/ newice3:/var/ftp/
</pre>

=== 1 full + diff at the migration time ===

<pre>
rsync -av --exclude={'rc.d','oldice3','newice3','namedb','openvpn','pkg.conf','portsnap.conf'} /usr/local/etc/ root@newice3:/usr/local/etc/ --delete --dry-run
rsync -av /etc/pf.blocked.ip.conf root@newice3:/etc/ --dry-run
rsync -av /etc/pf.blocked.webspam.conf root@newice3:/etc/ --dry-run
rsync -av /etc/pf.blocked.webspam_awstats.conf root@newice3:/etc/ --dry-run
rsync -av /root/ root@newice3:/root/ --delete --dry-run
rsync -av /home/ root@newice3:/home/ --delete --dry-run
rsync -av /var/www/ root@newice3:/var/www/ --delete --dry-run
rsync -av /usr/local/www/ root@newice3:/usr/local/www/ --delete --dry-run
rsync -av /var/log/ root@newice3:/var/log/oldice3/ --delete --dry-run
rsync -av /var/awstats/ root@newice3:/var/awstats/ --delete --dry-run
rsync -av /var/log/www/ root@newice3:/var/log/www/ --delete --dry-run
rsync -av /var/db/fail2ban/ root@newice3:/var/db/fail2ban/ --delete --dry-run
rsync -av /var/db/mysql/ root@newice3:/var/db/mysql/ --delete --dry-run (to do when mysql server is off)
</pre>

= Nginx =
== Maxmind ==
Country based filtering can be performed in nginx thanks to the free Maxmind databases.

A cron job shall be used to update these databases on a daily basis<ref>https://herrbischoff.com/2021/05/nginx-how-to-restrict-access-by-geographical-location-on-freebsd/</ref>

= ZFS snapshots =
FreeBSD creates a snapshot at each FreeBSD update (freebsd-update fetch && freebsd-update install). These snapshots are not needed anymore should your system restarts & runs correctly. Moreover they take loads of space on your hardrive.

== Procedure to delete ==

=== List & check ===
<pre>root@icecube BSD:~ # bectl list
BE Active Mountpoint Space Created
14.3-RELEASE-p6_2025-12-19_121434 - - 927M 2025-12-19 12:14
default NR / 814G 2023-12-01 23:34
</pre>
Check that the active Boot Envionment is the default (NR set on default).

<pre>root@icecube BSD:~ # zfs list -t snapshot
NAME USED AVAIL REFER MOUNTPOINT
zroot/ROOT/default@2025-12-19-12:14:34-0 927M - 812G -
</pre>

=== Delete ===

<pre>root@icecube BSD:~ # bectl destroy 14.3-RELEASE-p6_2025-12-19_121434
</pre>

=== Results ===
<pre>root@icecube BSD:~ # bectl list
BE Active Mountpoint Space Created
default NR / 813G 2023-12-01 23:34
root@icecube BSD:~ # zfs list -t snapshot
no datasets available
</pre>

= Reboot or no reboot after a minor system upgrade ? =

After a system upgrade performed thanks to :
<pre>root@icecube BSD:~ # freebsd-update fetch
root@icecube BSD:~ # freebsd-update install
</pre>

If the output of these two commands differs, then reboot your system:
<pre>root@icecube BSD:~ # freebsd-version -k
14.3-RELEASE-p7
root@icecube BSD:~ # uname -r
14.3-RELEASE-p7
</pre>

= PF =
After a reboot of FreeBSD, PF may fail to start due to tables being too big (i.e. > 100k entries). 
This is explained here with a quick & dirty non-permanent fix : 
https://forums.freebsd.org/threads/table-loading-in-pf-issues.86101/#post-577832
# First load the PF Options only (specific to big tables handling): pfctl -Of /etc/pf.conf
# Then restart PF the usual way

<pre>root@icecube BSD:~ # service pf restart
Disabling pf.
Enabling pf/etc/pf.conf:98: cannot define table firehol4: Cannot allocate memory
pfctl: Syntax error in config file: pf rules not loaded
/etc/rc.d/pf: WARNING: Unable to load /etc/pf.conf.
.
root@icecube BSD:~ # pfctl -Of /etc/pf.conf
root@icecube BSD:~ # service pf restart
Disabling pf.
Enabling pf.</pre>

= References =
{{references}}

Home Assistant

2026-01-30T22:48:54Z

Apn : /* Cabling */