EEBus / HomeMaticIP HmIP-HCU1

[thecem]

Describe the bug

EEBus connection failed

Steps to reproduce

configure EVCC and accept EEBus in HmIP-HCU1.

Configuration details

hems:
  type: eebus
  ski: 905nice #<SKI der HmIP-HCU1>

###############################################################
eebus:
  #shipid: EVCC-65dnice
  certificate:
    public: |
      -----BEGIN CERTIFICATE-----
public
      -----END CERTIFICATE-----

    private: |
      -----BEGIN EC PRIVATE KEY-----
private
      -----END EC PRIVATE KEY-----

Log details

[eebus ] INFO 2024/09/17 15:35:32 Local SKI: 65dnice
[eebus ] DEBUG 2024/09/17 15:35:32 starting websocket server on :4712
[eebus ] DEBUG 2024/09/17 15:35:32 mdns: announce
[eebus ] DEBUG 2024/09/17 15:35:32 mdns: using zeroconf
[eebus ] DEBUG 2024/09/17 15:35:32 mdns: new - ski: 905nice name: HCU1-1234 brand: Homematic-IP model: HmIP-HCU1 typ: EMS identifier: HmIP-HCU1-1234 register: false host: HCU1-1234.local. port: 60398 addresses: [192.168.1.30 fd98:69bc:5044:e246:21a:22ff:fe23:9945]
[eebus ] DEBUG 2024/09/17 15:35:43 trying to connect to 905nice at HCU1-1234.local.
[eebus ] DEBUG 2024/09/17 15:35:43 initiating connection to 905nice at HCU1-1234.local.:60398/ship/
[eebus ] DEBUG 2024/09/17 15:35:43 ski 905nice connected
[eebus ] DEBUG 2024/09/17 15:35:43 Send: read 1 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/09/17 15:35:43 Recv: d:_i:HCU1-1234:NodeManagement to NodeManagement read 30 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/09/17 15:35:43 Send: d:_i:HCU1-1234 reply 2 30 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/09/17 15:35:43 Recv: d:_i:HCU1-1234:NodeManagement to NodeManagement reply 32 1 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/09/17 15:35:43 Send: d:_i:HCU1-1234 call 3 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/09/17 15:35:43 Send: d:_i:HCU1-1234 read 4 NodeManagementUseCaseData
[eebus ] DEBUG 2024/09/17 15:35:43 cs-lpp: 5 DeviceDiagnosis Server found
[eebus ] DEBUG 2024/09/17 15:35:43 cs-lpc: 5 DeviceDiagnosis Server found
[eebus ] DEBUG 2024/09/17 15:35:43 Send: d:_i:HCU1-1234 call 5 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/09/17 15:35:43 Send: d:_i:HCU1-1234 read 6 DeviceConfigurationKeyValueDescriptionListData
[eebus ] DEBUG 2024/09/17 15:35:43 Send: d:_i:HCU1-1234 call 7 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/09/17 15:35:43 Send: d:_i:HCU1-1234 read 8 ElectricalConnectionDescriptionListData
[eebus ] ERROR 2024/09/17 15:35:43 operation is not supported on function electricalConnectionParameterDescriptionListData
[eebus ] DEBUG 2024/09/17 15:35:43 Recv: d:_i:HCU1-1234:NodeManagement to NodeManagement call 34 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/09/17 15:35:43 Send: d:_i:HCU1-1234 result 9 34 ResultData 0
[eebus ] DEBUG 2024/09/17 15:35:43 Recv: d:_i:HCU1-1234:NodeManagement to NodeManagement result 37 3 ResultData 0
[eebus ] DEBUG 2024/09/17 15:35:43 Recv: d:_i:HCU1-1234:NodeManagement to NodeManagement reply 41 4 NodeManagementUseCaseData
[eebus ] DEBUG 2024/09/17 15:35:43 ski 905nice event cs-lpc-UseCaseSupportUpdate
[eebus ] DEBUG 2024/09/17 15:35:43 ski 905nice event cs-lpc-UseCaseSupportUpdate
[eebus ] DEBUG 2024/09/17 15:35:43 ski 905nice event cs-lpc-UseCaseSupportUpdate
[eebus ] DEBUG 2024/09/17 15:35:43 ski 905nice event cs-lpc-UseCaseSupportUpdate
[eebus ] DEBUG 2024/09/17 15:35:43 Recv: d:_i:HCU1-1234:NodeManagement to NodeManagement read 44 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/09/17 15:35:43 Send: d:_i:HCU1-1234 reply 10 44 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/09/17 15:35:43 Recv: d:_i:HCU1-1234:NodeManagement to NodeManagement read 46 NodeManagementDestinationListData
[eebus ] DEBUG 2024/09/17 15:35:43 Send: d:_i:HCU1-1234 reply 11 46 NodeManagementDestinationListData
[eebus ] DEBUG 2024/09/17 15:35:43 Recv: d:_i:HCU1-1234:NodeManagement to NodeManagement read 48 NodeManagementUseCaseData
[eebus ] DEBUG 2024/09/17 15:35:43 Send: d:_i:HCU1-1234 reply 12 48 NodeManagementUseCaseData
[eebus ] DEBUG 2024/09/17 15:35:43 Recv: d:_i:HCU1-1234:NodeManagement to NodeManagement result 50 5 ResultData 0
[eebus ] DEBUG 2024/09/17 15:35:43 Recv: d:_i:HCU1-1234:DeviceConfiguration to DeviceConfiguration reply 51 6 DeviceConfigurationKeyValueDescriptionListData
[eebus ] DEBUG 2024/09/17 15:35:43 Recv: d:_i:HCU1-1234:NodeManagement to NodeManagement result 53 7 ResultData 0
[eebus ] DEBUG 2024/09/17 15:35:43 Send: d:_i:HCU1-1234 read 13 DeviceConfigurationKeyValueListData
[eebus ] DEBUG 2024/09/17 15:35:43 Recv: d:_i:HCU1-1234:ElectricalConnection to ElectricalConnection reply 54 8 ElectricalConnectionDescriptionListData
[eebus ] DEBUG 2024/09/17 15:35:43 Recv: d:_i:HCU1-1234:DeviceConfiguration to DeviceConfiguration reply 57 13 DeviceConfigurationKeyValueListData
[eebus ] WARN 2024/09/17 15:35:53 missing heartbeat- entering failsafe mode

What type of operating system are you running?

HomeAssistant Add-on

Nightly build

• I have verified that the issue is reproducible with the latest nightly build

Version

v0.130.11

[andig]

Missing heartbeat. /cc @DerAndereAndi

[DerAndereAndi]

Without a trace log there is nothing that can be analyzed.

but also: why would you want to connect a hems with another hems? That is intended to work.