Skip to content

en.Installation

Jump to bottom Edit New page
Jens Maus edited this page Jul 9, 2021 · 9 revisions

After the necessary hardware and software requirements for the installation of RaspberryMatic have been checked and fulfilled accordingly, you can continue with the actual installation of RaspberryMatic using the following sections. The installation process differs from the hardware platform used, so that the installation for each hardware platform is explained separately using step-by-step instructions in the following sections.

Quick Start

For the impatient or for already advanced CCU / HomeMatic / Linux users, the following quick start guide should explain the basic steps that can be found in every hardware-based guide in a similar process to carry out the RaspberryMatic installation:

** When using a CCU3 hardware: **

  1. Under [Releases] (https://github.com/jens-maus/RaspberryMatic/releases/latest) download the latest version as RaspberryMatic-X.XX.XX.YYYYMMDD-ccu3.tgz archive.
  2. Log into the WebUI of the CCU3 that has already started.
  3. Under Settings -> Control Panel -> Central Maintenance, select the downloaded * .tgz file like a standard firmware update under Select file and then start the update via Upload.
  4. Then RaspberryMatic should be installed on the CCU3 hardware and can be used.

** When using your own RaspberryPi / ELV-Charly or Tinkerboard: **

  1. Under [Releases] (https://github.com/jens-maus/RaspberryMatic/releases/latest) download the latest version as RaspberryMatic-X.XX.XX.YYYYMMDD-ZZZ.zip archive (ZZZ corresponds to the hardware platform used - rpiX or tinkerboard, for ELV-Charly you use rpi3)
  2. Unpack the archive accordingly using suitable archiving tools.
  3. Flash the * .img file contained in the archive using imaging tools such as" [Etcher] (https://www.balena.io/etcher/) "onto a suitable SD card of at least 4 GB or, in the case of the If a "Tinkerboard S" is used, the image can also be transferred directly to the internal eMMC after connecting the Tinkerboard via USB.
  4. Insert the SD card into the RaspberryPi / ELV-Charly or Tinkerboard.
  5. Connect a suitable HomeMatic / homematicIP radio module via GPIO or USB.
  6. Then connect the RaspberryPi / ELV-Charly or Tinkerboard to the power and then RaspberryMatic should start up accordingly.

** When using a virtualization environment (vmWare ESXi, Proxmox, VirtualBox, etc.): **

  1. Under [Releases] (https://github.com/jens-maus/RaspberryMatic/releases/latest) download the latest version as RaspberryMatic-X.XX.XX.YYYYMMDD.ova file (not the *. zip file!)
  2. Import the downloaded * .ova file directly into the administration interface of the virtualization environment used and make the basic settings of the virtual RaspberryMatic VM in the subsequent dialogs.
  3. Connect a suitable HomeMatic / homematicIP radio module to the host machine via USB and have it passed to the RaspberryMatic VM.
  4. Then start the VM and then RaspberryMatic should start up normally and be accessible via the WebUI.

More detailed installation instructions for all supported platforms can be found in the following sections.

Basic installation (hardware)

The following sections describe how to install and operate RaspberryMatic using dedicated hardware or how to commission it in a virtualization environment.

  • [CCU3] (Installation-CCU3)
  • [ELV-Charly] (Installation-ELV-Charly)
  • [RaspberryPi] (Installation-RaspberryPi)
  • [ASUS Tinkerboard] (installation tinkerboard)
  • [Intel NUC] (Installation-IntelNUC)

Basic installation (virtual)

In addition to the installations on real hardware, there is also the possibility of installing RaspberryMatic in modern virtualization environments such as vmWare ESXi, Proxmox, VirtualBox, Synology VMM, etc. as a virtual x86 machine and together with a suitable [USB-based HomeMatic radio module] (Introduction # requirements) to be used. Here, RaspberryMatic is brought out as a so-called * .ova archive that can be imported directly into the common virtualization solution with just a few clicks. This is to be described separately for each supported virtualization platform below:

  • [vmWare ESXi] (installation-vmWare-ESXi)
  • [Proxmox Virtual Environment] (Installation-Proxmox-VE)
  • [Oracle VirtualBox] (Installation-VirtualBox)
  • [Synology Virtual Machine Manager] (Installation-Synology-VMM)
  • [QNAP VirtualizationStation] (Installation-QNAP-VirtualizationStation)
  • [vmWare Workstation Player] (Installation-vmWare-Workstation-Player)
  • [QEmu / KVM] (Installation-QEmu)
  • [HyperV] (Installation-HyperV)

Configuration transfer

If you have successfully completed the basic installation on your own hardware or in your virtualization environment and you already have a different or older CCU control center from the company eQ3 / ELV, you can find out in the following sections how to adopt your existing configuration.

Switch from CCU3

Due to the extensive compatibility between the operating system / firmware used on the CCU3 and RaspberryMatic, when switching from CCU3 firmware to RaspberryMatic, manual adjustments are generally only necessary if you switch directly from your CCU3 to a virtual RaspberryMatic system. More information about switching to a virtual RaspberryMatic can be found [here] (Installation # switch-to-virtual-raspberryMatic).

If you have installed RaspberryMatic directly on your existing CCU3 hardware using the [Installation Instructions] (Installation-CCU3), the configuration including the installed CCU add-ons should have been adopted automatically and no further steps are necessary. If, on the other hand, you change from the CCU3 hardware to another ARM-based hardware (RaspberryPi, Tinkerboard), after the fresh basic installation on this new hardware, the system backup (* .sbk) previously exported via CCU3 WebUI can be transferred to the new RaspberryMatic via WebUI import. Further steps are then no longer necessary.

Switch from CCU2

If you want to switch from an older CCU2 control unit with firmware version 2.x to RaspberryMatic, there are a few things to consider. If you have carried out the above basic installation steps on the new hardware or for the virtual RaspberryMatic and the new RaspberryMatic system works in principle and you can connect to the WebUI, you can access the data transfer from your old CCU2 (also LXCCU, YAHM, piVCCU2) as follows:

  1. If you want to take over the data from a CCU2 / LXCCU / YAHM / piVCCU2, you should make sure that you use the latest CCU2 firmware and a firmware version before you start taking over the configuration from your old CCU2 to RaspberryMatic. Otherwise, there could be certain problems with the switch if you also use the latest RaspberryMatic version.
  2. Log in to the old CCU2 using the WebUI and make a backup (* .sbk) of the current settings / configuration, etc. under Settings-> Control Panel-> Security-> Create backup and keep them safe if the following points apply lead to a mistake.
  3. Make a note of all the additional packages (CCU add-ons) listed under Settings-> Control Panel-> Additional Software, as these will have to be installed manually in a RaspberryMatic-compatible version later (after the configuration has been transferred to RaspberryMatic).
  4. Now go through the list of additional packages / CCU add-ons under Settings-> Control Panel-> Additional Software and basically uninstall ** ALL **, but exclude the following add-ons, otherwise their configuration will also be deleted (these can be deleted later under point 10 can then be installed "over it" again):
  5. Create a backup (* .sbk) again under Settings-> Control Panel-> Security-> Backup and keep it temporarily.
  6. Now shut down the old CCU2 and completely disconnect it from the power (_may not run parallel to RaspberryMatic! _).
  7. Completely delete the browser cache of the browser currently in use, then restart the web browser.
  8. Log in to the new RaspberryMatic using the WebUI and import the last backup (without additional software / add-ons) under Settings-> Control Panel-> Security-> Import backup.
  9. After the restart, which was carried out by the backup, you should reconnect to the RaspberryMatic WebUI and first enter the following NTP server string under Settings-> Control Panel-> Time / Position Settings-> NTP Server: 0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org This ensures that a valid NTP server is entered after the next reboot, from which the current time can be obtained when booting.
  10. Now you can go through the addon list noted in step 3 via the WebUI and install all addons in the respective [RaspberryMatic compatible version] (Administration # ccu-addons - additional software) in order to restore the previous functions.
  11. As a last step, RaspberryMatic should restart and then the WebUI with the old password / login data and all HomeMatic devices, programs, etc. should be available again. If, contrary to expectations, this does not work, you can now restore the first backup (before uninstalling add-ons) in your old installation and you should find the old version again. Please also note that, depending on the existing programming in your CCU, there may be an increased duty cycle (ie radio load) when booting up and you sometimes have to wait> 1h until communication disruptions to certain HomeMatic devices disappear.

Switch from CCU1

If you still have an old CCU1 hardware and would like to take the big leap from your CCU1 to RaspberryMatic, the same / similar procedure applies here as for [switching from a CCU2] (installation # switch-from-ccu2). In addition, it is important to have your CCU1 system backup (* .sbk) installed in the latest 2.xx RaspberryMatic version before switching to the latest 3.xx RaspberryMatic version. That means: you should first install the last RaspberryMatic version released as 2.xx version ([2.35.16.20180826] (https://github.com/jens-maus/RaspberryMatic/releases/tag/2.35.16.20180826)), then take over its CCU1 backup in it, and then update this 2.xx version of RaspberryMatic to the latest 3.xx version.

Switch to virtual RaspberryMatic

If you want to switch either from your older CCU2 / CCU3 control center or from a hardware-based RaspberryMatic system directly to a virtual RaspberryMatic system, you can proceed as follows:

  1. First you should use the [basic installation instructions] (installation # basic installation-virtual) in your respective virtualization environment to ensure that the new virtual RaspberryMatic boots up properly and that the WebUI can be accessed accordingly.
  2. Then you should create and download a corresponding system backup in your old installation / headquarters under Settings-> Control Panel-> Security-> Backup (* .sbk).
  3. Now go through the list of additional packages / CCU add-ons under Settings-> Control Panel-> Additional Software and basically uninstall ** ALL **, but exclude the following add-ons, otherwise their configuration will also be deleted (these can be deleted later under point 10 can then be installed "over it" again):
  4. Then create another / new system backup (* .sbk) and store it temporarily.
  5. Now you should deactivate the old CCU central unit or take it off the power, since you should not let two CCU central units with the same configuration run in parallel in your environment.
  6. If you have not already connected a USB-based radio module (HB-RF-USB, HmIP-RFUSB, HM-CFG-USB2) to your virtual RaspberryMatic system, you should now do this according to the installation instructions for your virtualization environment.
  7. Log into the WebUI of the virtual RaspberryMatic system and restore the system backup (without CCU add-ons) accordingly.
  8. As a last step, you should then manually reinstall all CCU add-ons that were previously manually uninstalled. Please note that you should check the compatibility of the CCU add-ons or x86 of a virtual RaspberryMatic beforehand.
  9. Finally, the new, virtual RaspberryMatic system, with all installed CCU add-ons, should be restarted once more. Please also note that, depending on the existing programming in your CCU, there may be an increased duty cycle (ie radio load) when booting up and you sometimes have to wait> 1h until communication disruptions to certain HomeMatic devices disappear.

Table of Contents                             RaspberryMatic Documentation © 2015-2024 Jens Maus and RaspberryMatic Contributors, licensed under CC BY-SA License 4.0

Dokumentation 🇩🇪 | Documentation 🇺🇸

  1. Einleitung | Introduction
  2. Installation | Installation
  3. Administration | Administration
  4. Nutzung | Usage
  5. Support | Support
  6. Sonstiges | Miscellaneous
Clone this wiki locally