Created with Sketch.

This is release of RaspberryMatic which is a maintenance release with the following bugfixes and feature changes:

Downloads License Donate GitHub sponsors

Hier klicken fΓΌr deutschsprachige πŸ‡©πŸ‡ͺπŸ‡¦πŸ‡ΉπŸ‡¨πŸ‡­ Version des ChangeLogs/Diskussionsbeitrag

🚧 Changes:

For all changes, see the full commit log.

CCU/HomeMatic service changes:

  • updated OCCU version to 3.65.8-2 integrating full compatibility to the CCU3 3.65.8 firmware which comes with the following changes:
    • Correct display and use of the HmIP-HAP-B1 (Silvercrest).
    • Update of ReGaHss to R1.00.0388.0232. Fixes among other things an error in the objectID assignment.
    • Wrong display of the parameter “Type of two-point control” at HmIP-WTH-2 corrected.
    • Check and, if necessary, correct the factory SSH configuration.
    • Display of default profile after teaching roller blind and shutter actuators corrected.
  • modified startup to manually load the rpi_rf_mod_led kernel module in case a rx8130 RTC is identified (RPI-RF-MOD on GPIO) and the docker/OCI platform is used. This should make the LED of a RPI-RF-MOD work in case a manual docker/OCI environment is used, e.g. under RaspberryPiOS (#1893).
  • updated /bin/createBackup.sh to perform some additional safety measures to ensure a proper/valid backup archive is created which seem to not have been the case under all circumstances (cf. https://homematic-forum.de/forum/viewtopic.php?f=65&t=75205).
  • added /usr/local/eQ-3-Backup to excluded backup path in createBackup.sh.
  • updated generic_raw_uart to latest version.

WebUI changes:

  • modified 0007-WebUI-Enhanced-FirmwareUpdate WebUI patch to use createBackup.sh also for the WebUI based backup and to use a somewhat improved error reporting in case createBackup.sh returns an error. In addition the create_backup tcl routine is now correctly executed without brackets (cf. https://homematic-forum.de/forum/viewtopic.php?f=65&t=75205).
  • reworked 0007-WebUI-Enhanced-FirmwareUpdate WebUI patch to display a plain http url in the popup requester for notifying users how they can follow the firmware update process (#1891).
  • added fix in 0135-WebUI-Add-ControlPanel-AdvancedSettings WebUI patch where using encodeURIComponent() and escape() fixes certain character encoding issues caused by omitting URL encoding altogether (#1897).

Operating system changes:

  • to make sure that dangling third-party monit configuration symlinks will not produce monit errors a cleanup action has been added to the S96StartAddons init script removing such dangling symlinks know to cause certain issues.
  • added a new 0014-ca-certificates-local buildroot upstream patch which introduces the possibility to put own certificate authority (CA) files in/usr/local/share/ca-certificates and use the update-ca-certificatescomannd-line script commonly known from debian-like systems to update the cert files in /etc/ssl/certs so that commands like curl, wget and also lighttpd can use own CA files from there. Thus, upon startup RaspberryMatic will now update ca certificates and allow users to put own CA certificates into /usr/local/share/ca-certificates (#1910).
  • added arm_boost=1 for compatible RaspberryPi4 models to bump frequency from 1.5GHz to 1.8GHz for potentially increased performance (#1913).
  • removed duplicate ASMedia quirk (174c:55aa:u) in the used kernel cmdline.
  • updated rpi-eeprom to latest pieeprom-2022-08-02 version and added missing rpi-userland patch to fix build with newer buildroot versions.
  • updated java-azul 1.8 LTS to latest versions available.
  • updated raspberrypi kernel+firmware to latest 1.20220811.
  • updated upstream kernel to 5.15.63 LTS.
  • updated buildroot to latest 2022.05.1.

πŸ‘ͺ Contributors (alphabetically):

πŸ“ Support:

For support on installation and help please visit the following web pages:

RaspberryMatic – Documentation πŸ‡ΊπŸ‡Έ
RaspberryMatic – Discussions πŸ‡ΊπŸ‡Έ
RaspberryMatic – Dokumentation πŸ‡©πŸ‡ͺ
RaspberryMatic – Forum πŸ‡©πŸ‡ͺ

πŸ“¦ Download:

The following installation archives can be downloaded for different hardware platforms. To verify their integrity a sha256 checksum is provided as well. You can either upload these files using the WebUI-based update mechanism or unarchive them to e.g. flash the included *.img files on a fresh installation media (e.g. microSD card):