Since I finally have HA running in Docker, I wanted to get started and gradually move the existing functionality from FHEM to HA.
But at the moment it’s still completely unclear to me how to do this. After all, FHEM should be completely gone (I’ve been bothered with that for long enough), but replacing all HM, MAX and IT systems with LAN/WLAN systems is not possible in terms of costs.
It would be great if someone could explain to me how to do this.
And if I’m on the wrong board here, it would be nice to point me to the right board or move this request there.
Don’t worry about being wrong here. It is only the feature request part of the forum that seems to be somewhat strictly about the post being correct and if your post is wrongly placed, then it will just get moved to the right spot.
Regarding your system, then Homematic hardware have a good integration in Homematic(IP)_Local, which connects to your CCU.
If you have no CCU at the moment, then the addon RaspberryMatic will set you up. You will need a RF device though, like this one. There are other options too, which the RaspberryMatic homepage should be able to help you with. Beware that some of the RF options might limit Homematic RF and/or Homematic Biscos functionality. Homematic IP seems to always supported with all RF options.
The Raspberrymatic homepage have instructions on how to set it up, but there is a ready-made addon with click-and-install functionality, if you are running HAOS.
MAX, I am a bit unsure of. MAX is discontinued by EQ-3 and Homematic IP is the successor.
And IT I have no clue what is. 
Many thanx for the quick answer…
And you suspect it right: I don’t have any CCU. All the different protocols are handled by a Pi3 as a plain RX/TX-Pi, running minimal headless Raspbian and work as bridge between FHEM - (W)LAN - SSC 1 to3 where the three SSC handle each an own proto (HM, MAX, IT). Also for HM there are two HM-LAN “UFO’s” they are grouped with the HM-SCC to a virtual CCU. That work’s like a MESH knowing from WLAN. So if I like to talk to a HM-device I just talk over the VCCU and they take one of the three transceiver who have the best RSSI for that device.
HM’s are all plain the old stuff. I haven’t any HM-IP due FHEM can’t handle it right and also the installation is quite old. MAX is just for the MAX switches. They are very cheap and do their job very well.
IT is simply Intertechno, a stupid one way proto. Many discounter main-plugs work with that and also many temp/hum sensors. Also, some tiny, cheap multichannel RC’s.
Ah, and before I forget: An Pi also control the whole heating: burner, pumps, valves a.s.o. This Pi also runs FHEM and need data from the outside like outdoor temp & hum, cumulated openings of all the radiator valves (HM), pesence of members of my family and things like that to drive the heating with the best efficiency. Most of it can be done by MQTT…
Presence by PING is a very (!) important thing here. Not only our phones are coupled this way, also the other PI’s and important (W)LAN devices…
That’s for now if my old grey mass between my ears haven’t forget some…
I will take a look at the side you offer. I’m sure that I need much more help before I can shut down fhem forever…
Ohhh wait…
I have take a look here: Installation HomeAssistant · jens-maus/RaspberryMatic Wiki · GitHub
There you can find a picture showing the HA GUI (https://github.com/jens-maus/RaspberryMatic/wiki/images/ha/ha-addon-step1.png).
When I look at the picture, I am afraid that my HA installation in Docker is not complete. Because I completely miss these options and the add-on store 
If you can reuse your CCU, then you just need the integration in HA and your entire Homematic network should be up and running.
If the CCU is not possible to reuse, then the Pi3 can run Debmatic and you have your CCU again, which the integration in HA can connect to.
HA have good support for MQTT, so the parts that use that should also be easy to move.
Addons can come in different variants.
If you are running HA Operating System or HA Supervised Installation, then you get the easy click-and-install of addons.
HA Operating System will lock the operating system completely down though, which is maybe a trade off by some.
HA Supervised Installation is installed on a Debian 12 operating system (Only the true Debian 12 will work here), so you get some more options, but there is a lot of requirements that needs to be fulfilled with this setup and it might not be so open in the end. I have earlier been running Debmatic on it with a HA Supervised Installation. You really need to understand Debian and how to setup, configure and maintain a server with all the different services needed. The help on such a setup can be quite hard to get for the Debian part.
You probably have a HA Core or HA Container installation.
In these two installations click-and-install addons are not available.
This does not mean addons is not available. You just have to find the docker files yourself, set them up and connect them to HA. There should be guides to this, but I have never looked into it, since I have only used HA Supervised Installation and then switched to HA Operating System.
Ahhh ohhh… bad… for me…
I’m happy that HA runs in a docker now, due the OMV-NAS works anyway 24/7. But to install a HASS (right syn for the supervised version?) parallel to OMV isn’t a good idea, I think. There are so many things that can going wrong and kill the NAS.
So… I’m a dumb in docker. My Linux/Debian skills are bad also, but much better than the docker stuff. So at this point I think it’s best, if I start over with a bare metal mini-PC I just buy at ePray.
Mini PC is a good choice.
It does not have to be a big one to run HA. Remember that many run it fine with a Raspberry Pi4 with 4Gb ram and a 32Gb SDcard, so whatever Mini PC you find should be better.
Just remember that UEFI is a requirement.
Jepp… It’s a HP Eliltedesk 800 G1 / i5 / Intel HD / 4GB RAM, 128GB SSD
Its maximum power consumption is 60W, so I assume that the average power requirement will be around 20W.
Maybe I’ll add another 4GB of RAM when I get the chance, if necessary, but otherwise it should be enough…
So I have to wait for it… Meanwhile, I can fix my burned 3D-printer mainboard… A little too
much power for the tiny crap connector ^^
One more bit regarding the Intertechno devices: Homegear is able to expose these in a way that’s compatible to HomeMatic. This does work with the old integration, which I wouldn’t recommend using though. I don’t know if this still works with the new integration. But I think there’s a good chance it can work.
And just for reference: Homegear is something like an emulated CCU, with support for other device types. It exposes the XML-RPC API also provided by a regular CCU. But I don’t think there’s much development going on with Homegear anymore. But if you primarily have old devices, you probably won’t have problems with device support.
So just for the sake of trying, I would suggest to give the Homegear Docker Container a shot. I think Homegear is also able to directly integrate with the HM-CFG-LAN devices to provide the communication.
Thank you very much for the tip; he is good! I’ll take a look at this as soon as possible.
But ultimately I could do without the IT protocol if absolutely necessary, or I could let a PI continue to run with a minimal FHEM installation and pass it on via MQTT. Or I can build an IT2MQTT gateway with an ESP…
IT can be replaced inexpensively with, for example, Shelly’s. Things are different with the HM devices. These are usually expensive devices, such as radiator thermostats, fire smoke detectors, 4-fold top-hat rail actuators and things like that
In that case try getting one of the other solutions to work. Debmatic probably is the next best option without breaking much.
Thanks for the tip. I just read up on the Git site. If I understand correctly, there is no support for e.g. HM-CFG-LAN (HM-CFG-LAN LAN Konfigurations-Adapter – FHEMWiki). I’ll read into it further, but that would almost be a knockout criterion; without them it doesn’t work. I can’t achieve everything with two HM transceivers, let alone one…
Well, at least Homegear does support the HM-CFG-LAN: 5. Configuration — Homegear HomeMatic BidCoS Manual 0.8 documentation
I used these together years ago when starting with HomeMatic.
And I believe it is possible to also use it with a CCU or RaspberryMatic to extend the range, as long as a real RF-Module is the primary one.
Ah ok… wasn’t so far with reading…
It’s not that easy to find a system into which the hardware environment that has grown over the years can be adopted.
If the HM-LAN goes in, that’s half the battle. If you can now somehow add the SCC’s into it, ideally so that you can form what FHEM calls a VCCU with the HM-SCC and the HM-LAN, then that would actually be the way…
(here you can see the old Pi3 where the three SCC’s are stacked)
I think in your case it would be best to ask at the HomeMatic forum. There you might find some experts that know their way around FHEM and how to migrate to something HA-compatible, without loosing the functionality you have right now.
… yea… I think so too … And I have to slow myself down a bit and take it slow; Little by little… I know myself… I always want to achieve too much too quickly at once…
So… me again…
In the meantime the small computer is there, an HP EliteDesk with an I5, 4GB RAM and a 128GB SSD.
My attempt to set up HASS according to “GitHub - home-assistant/supervised-installer: Installer for a generic Linux system” failed mercilessly. The problem is that everything works up to “Step 3: Install the OS Agent:”, but when you install “homeassistant-supervised.deb” the whole thing goes down the drain.
As far as I can understand so far, the installation destroys all network connections and then runs against the wall.
As far as I know, a newly installed Debian 12.2 uses the usual entries in /etc/network or /etc/wpa_supplicant, but the installation probably works with the network manager. But switching to the NM beforehand and transferring all power to it didn’t help either… The creator of this HowTo probably assumed things that are simply not present in a standard installation of Debian 12…
So after hours of pointless fiddling, I ended this attempt and flashed the “haos_generic-x86-64-11.1.img.xz” onto the SSD. This has worked so far, although it should perhaps be stated here that the thing only works via LAN and not via WLAN. This saves a beginner from spending hours searching for a non-existent option ^^
Anyway…
I’ve now tried to somehow bring in the HomeMatic stuff. The only option I could find related to the outdated CCU plugin, which runs after a test installation (or so it seems), but when I try to update it or try to change anything else, the GUI grays out and does nothing. So it’s also a waste of love…
As far as I’ve read, in the current HASS version access to install an external system is no longer possible, so Homegear or something similar cannot be installed on the system; At least I haven’t found a way…
So am I correct that nothing else can be installed on the system on which the above image was installed apart from the plugins offered?
Look into debmatic
It might solve your issues
And yes with HAOS you can only install add-ons that are in the addon store and controlled by HAOS.
You can install a hypervisor on the machine and gave one VM running HAOS with all the add-ons it provides and another VM that run all the ones the HAOS do not support.
Ok, thank you a lot… It seems that I have understood it right, so far…
Since debmatic is currently not available as a plugin (will it ever be?), the only way is via a VM or an external system (Pi or what ever) with debmatic, which can then be integrated into HA… Right?
Edit say: This way as an example? https://computingforgeeks.com/how-to-install-kvm-virtualization-on-debian/