HA Homematic Plugin vs config.yaml

Configuration
1

Hello i have an stupid question about the Homematic integration:
Right now i have my Homematic integration done in the config.yaml with :

#----------------------------- Homematic / Raspberrymartic -----------------------------
homematic:
  interfaces:
    Funk:
      host: !secret raspberrymatic_host
      port: 2001
      resolvenames: json
      username: !secret raspberrymatic_username
      password: !secret raspberrymatic_pw
    Wired:
      host: !secret raspberrymatic_host
      port: 2000
      resolvenames: json
      username: !secret raspberrymatic_username
      password: !secret raspberrymatic_pw
    HMIP:
      host: !secret raspberrymatic_host
      port: 2010
      resolvenames: json
      username: !secret raspberrymatic_username
      password: !secret raspberrymatic_pw
    #CuxD:
      #host: !secret raspberrymatic_host
      #port: 8701
      #resolvenames: json
      #username: !secret raspberrymatic_username
      #password: !secret raspberrymatic_pw
    #Tcl:
      #host: !secret raspberrymatic_host
      #port: 8181
      #resolvenames: json
      #username: !secret raspberrymatic_username
      #password: !secret raspberrymatic_pw
    groups:
      host: !secret raspberrymatic_host
      port: 9292
      resolvenames: json
      username: !secret raspberrymatic_username
      password: !secret raspberrymatic_pw
      path: /groups
  hosts:
    ccu3:
      host: !secret raspberrymatic_host
      username: !secret raspberrymatic_username
      password: !secret raspberrymatic_pw

which works very fine.

Today i have seen that via supervisor(hass.io) is also an HomeMatic CCU ad-on provided.

What is the difference between these integrations?

2

The add-on emulates the CCU so you can have it running on the same machine. But you still have to integrate it with the yaml. It would just point to a different IP address.