en.Installation
Installation
Jens Maus edited this page2 weeks ago · 52 revisions After the necessary hardware and software requirements for the installation of RaspberryMatic have been checked and met, you can proceed with the actual installation of RaspberryMatic using the following sections. The installation process differs depending on the hardware platform used, so in the following sections the installation is explained separately for each hardware platform using step-by-step instructions.
Quick Start For the impatient or for already advanced CCU/HomeMatic/Linux users, the following quick start guide is intended to explain the basic steps that can be found in a similar process in every hardware-based guide to carry out the RaspberryMatic installation:
When using CCU3 hardware:
Download the latest version as an archive under ReleasesRaspberryMatic-X.XX.XX.YYYYMMDD-ccu3.tgz . Log in to the WebUI of the already started CCU3. Under select Einstellungen -> Systemsteuerung -> Zentralen-Wartungthe downloaded *.tgzfile like a standard firmware update under Datei auswählenand then start the update via Hochladen. RaspberryMatic should then be installed on the CCU3 hardware and can be used. When using your own RaspberryPi/ELV-Charly or Tinkerboard:
Download the latest version as an archive under ReleasesRaspberryMatic-X.XX.XX.YYYYMMDD-ZZZ.zip (ZZZ corresponds to the hardware platform used - rpiXor tinkerboard, for ELV-Charly you use rpi3) Unpack the archive accordingly using suitable archiving tools. *.imgFlash the file contained in the archive onto a suitable SD card with at least 4 GB in size using imaging tools such as " Etcher " or, if you are using a "Tinkerboard S", the image can be transferred directly to the internal eMMC after connecting the Tinkerboard via USB . Insert the SD card into the RaspberryPi/ELV-Charly or Tinkerboard. Connect a suitable HomeMatic/homematicIP radio module via GPIO or USB. Then connect the RaspberryPi/ELV-Charly or Tinkerboard to the power and then RaspberryMatic should boot up accordingly. When using a virtualization environment (vmWare ESXi, Proxmox, VirtualBox, etc.):
Download the latest version as a file under Releases (do not use the file!)RaspberryMatic-X.XX.XX.YYYYMMDD.ova*.zip Import the downloaded *.ovafile directly into the administration interface of the virtualization environment used and make the basic settings of the virtual RaspberryMatic VM in the subsequent dialogs. Connect a suitable HomeMatic/homematicIP radio module to the host machine via USB and have it passed through to the RaspberryMatic VM. Then start the VM and then RaspberryMatic should boot up normally and be accessible via WebUI. More detailed installation instructions for all supported platforms can be found in the following sections.
Basic installation (Hardware) The following sections describe how you can install and operate RaspberryMatic using dedicated hardware or how you can put it into operation in a virtualization environment.
CCU3 ELV-Charly RaspberryPi ASUS Tinkerboard Intel NUC Basic installation (virtual) In addition to installations on real hardware, there is also the option of installing RaspberryMatic in modern virtualization environments such as vmWare ESXi, Proxmox, VirtualBox, Synology VMM, etc. as a virtual x86 machine and using it together with a suitable USB-based HomeMatic radio module . RaspberryMatic is *.ovareleased as a so-called archive that can be imported directly into common virtualization solutions with just a few clicks. This will be described separately for each supported virtualization platform below:
Proxmox Virtual Environment Home Assistant Add-on Docker Container (OCI) Linux Container (LXC) QEmu/KVM Kubernetes/K8s Synology Virtual Machine Manager QNAP VirtualizationStation UNRAID XCP-ng/XenServer Oracle VirtualBox vmWare ESXi vmWare Workstation Player HyperV Configuration takeover 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 center from eQ3/ELV, you can find out in the following sections how you can adopt your existing configuration.
Switching from CCU3 Due to the extensive compatibility between the operating system/firmware used on the CCU3 and RaspberryMatic, when switching from a 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 .
If you have installed RaspberryMatic directly on your existing CCU3 hardware using the installation instructions , the configuration including the installed CCU add-ons should have been automatically adopted and no further steps are necessary. However, if you switch from the CCU3 hardware to another ARM-based hardware (RaspberryPi, Tinkerboard), after the fresh basic installation on this new hardware you can *.sbkimport the system backup ( ) previously exported via CCU3 WebUI into the new RaspberryMatic via WebUI. Further steps are then no longer necessary.
Switching from CCU2 If you want to switch from an older CCU2 central unit with firmware version 2.x to RaspberryMatic, there are a few things to consider. Once you have completed the 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 start transferring data from your old CCU2 (also LXCCU, YAHM, piVCCU2) do as follows:
If you want to switch to RaspberryMatic, you should first make sure that you are using the latest CCU2 firmware version before you start transferring the configuration ( *.sbkbackup) from your old CCU2 to RaspberryMatic. Otherwise there could be problems with the switch if, for example, you switch from a very old CCU2 version directly to the currently most current RaspberryMatic. A good approach here is to use a version of RaspberryMatic that comes closest to the currently most current CCU2 firmware. For example, when using the CCU2 2.59.7 firmware, you should first update the 3.59.6.20211009 version for the switch and then (if there were no problems) to the currently most current RaspberryMatic version. Log in to the old CCU2 using WebUI and make Einstellungen->Systemsteuerung->Sicherheit->Backup erstellena backup ( *.sbk) of the current settings/configuration, etc. and keep it safe in case the following points lead to an error. Make a note of all Einstellungen->Systemsteuerung->Zusatzsoftwarethe additional packages (CCU addons) listed below as these will have to be manually installed later (after the configuration has been transferred to RaspberryMatic) in a RaspberryMatic-compatible version. Now Einstellungen->Systemsteuerung->Zusatzsoftwarego through the list of additional packages/CCU addons and basically uninstall ALL of them, but exclude the following addons from this, otherwise their configuration will be deleted (these can be reinstalled "over" later under point 10): CUxD JP-HB-Devices-addon HB-TM-Devices-AddOn Einstellungen->Systemsteuerung->Sicherheit->BackupCreate a backup ( ) again under create *.sbkand store it temporarily. Now shut down the old CCU2 and completely disconnect it from the power ( it must not run in parallel with RaspberryMatic! ). Completely delete the browser cache of the browser you are currently using, then restart the web browser. Log in to the new RaspberryMatic using WebUI and Einstellungen->Systemsteuerung->Sicherheit->Backup einspielenimport the most recently saved backup (without additional software/addons). After rebooting through the backup, you should reconnect to the RaspberryMatic WebUI and first enter Einstellungen->Systemsteuerung->Zeit-/Positionseinstellungen->NTP-Serverthe following NTP server string: 0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org This ensures that after the next reboot a valid NTP server is entered from which the current time can be obtained when booting up. 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 to restore the previous functions. The last step should be to restart RaspberryMatic and then the WebUI with the old password/login data as well as all HomeMatic devices, programs, etc. will be available again. If, contrary to expectations, this does not work, you can now restore the first backup in your old installation (before uninstalling add-ons) and you should find the old status again. Please also note that, depending on the existing programming in your CCU, there may be an increased duty cycle (ie radio utilization) when starting up and you sometimes have to wait >1 hour until communication problems with certain HomeMatic devices disappear. Switching from CCU1 If you still have old CCU1 hardware and would now like to make the big leap from your CCU1 to RaspberryMatic, the same/similar process applies as when switching from a CCU2 . Furthermore, it is important that you first *.sbkhave your CCU1 system backup ( ) installed in the latest 2.xx RaspberryMatic version before switching to the latest 3.xx RaspberryMatic version. So: you should first install the last RaspberryMatic version released as 2.xx version ( 2.35.16.20180826 ), then transfer your CCU1 backup to it, and then update this 2.xx version of RaspberryMatic to the latest 3.xx version .
However, since it cannot be completely ruled out that certain problems may arise due to the very large version jump (CCU1 -> CCU3), we recommend a complete new setup (deregister all HomeMatic devices, factory reset, re-train CCU3/RaspberryMatic, freshly configured, etc.) and then it is best to avoid such large version jumps completely in the future and keep your CCU/RaspberryMatic system regularly updated.
Upgrade to virtual RaspberryMatic If you want to switch directly from your older CCU2/CCU3 central station or from a hardware-based RaspberryMatic system to a virtual RaspberryMatic system, you can proceed as follows:
First, you should use the basic installation instructions in your respective virtualization environment to ensure that the new virtual RaspberryMatic boots up properly and that the WebUI is accessible accordingly. You should then Einstellungen->Systemsteuerung->Sicherheit->Backupcreate and download a corresponding system backup in your old installation/center (*.sbk). Now Einstellungen->Systemsteuerung->Zusatzsoftwarego through the list of additional packages/CCU addons and basically uninstall ALL of them, but exclude the following addons from this, otherwise their configuration will be deleted (these can be reinstalled "over there" later under point 8): CUxD JP-HB-Devices-addon HB-TM-Devices-AddOn Then create another/new system backup ( *.sbk) and keep it temporarily. Now you should deactivate the old CCU central unit or take it off the power supply, as you should not have two CCU central units with the same configuration running in parallel in your environment. 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 do this now according to the installation instructions for your virtualization environment. Log in to the WebUI of the virtual RaspberryMatic system and have the system backup (without CCU add-ons) restored accordingly. As a final step, you should then manually reinstall all CCU add-ons that were previously uninstalled manually. It should be noted that you should check the compatibility of the CCU addons or x86 of a virtual RaspberryMatic beforehand. Finally, the new, virtual RaspberryMatic system, with all the CCU add-ons installed, should be finally restarted. Please also note that, depending on the existing programming in your CCU, there may be an increased duty cycle (ie radio utilization) when starting up and you sometimes have to wait >1 hour until communication problems with certain HomeMatic devices disappear.
