cannot execute actions from HASS to HM after upgrading to 1.65 #1712

hmax-72 · 2024-09-06T05:54:05Z

hmax-72
Sep 6, 2024

The problem

After upgrading HASS to the latest Version (2024.9) and upgrading Homematic-Integration to 1.65 I'm experiencing the issue that after some time (1-2 days) it is not possible to change states of HM-Devices. I already turned on debug logging (in the HA-Dialog), but was not able to find any related error in the logs.
As a first try to fix it, I also updated Raspberrymatic to the lateast version.

Just to mention: I'm mainly using HomematicIP-wired devices (99%).

A Restart of HASS fixes the problem (I did not find any other possibility).

What version of HomematicIP (local) has the issue?

1.65

What was the last working version of HomematicIP (local)?

No response

What type of installation are you running?

Home Assistant OS

What type of installation are you running for your homematic backend?

RaspberryMatic Standalone

Which version of your homematic backend are you running?

3.77.7.20240826

What hardware are you running for your system?

IBM Thinstation

Which config details do you use

TLS
callback data (see)

Which interfaces do you use?

Homematic IP
Homematic (Bidcos-RF)
Groups (Heating-Group)
BidCos-Wired (HM-Wired)

Diagnostics information (no logs here)

No response

Log file extract. Anything in the logs that might be useful for us? The log (Setting/System/Logs -> load full log) is the best source to support trouble shooting!

No response

Additional information

No response

SukramJ · 2024-09-06T06:07:30Z

SukramJ
Sep 6, 2024
Maintainer

As you can probably imagine, your error message is useless as long as there is no log data attached.

I already turned on debug logging (in the HA-Dialog), but was not able to find any related error in the logs.

The debug log is not about errors, because they are also displayed in the normal log.

Add this to your configuration.yaml an restart HA. The period of missing updates must be included in the log.

logger:
  default: warn
  logs:
    hahomematic: debug
    custom_components.homematicip_local: debug

Afterwards attach the full log as file here.

Please attach the integration diagnosis as well.
Check your CCU logs to see if there are any problems, and if necessary, a restart will help.

There are hundreds of users who have your setup and no problems.

0 replies

kramer74 · 2024-09-09T21:16:19Z

kramer74
Sep 9, 2024

Hallo zusammen,

ich habe derzeit das gleiche Problem, das nach einer gewissen Zeit keine Kommandos mehr aus geführt werden:

2024-09-09 23:05:41.313 DEBUG (MainThread) [hahomematic.client] SET_VALUE: 00021D89A1AEE9:3, STATE, True
2024-09-09 23:05:41.313 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('setValue', ('00021D89A1AEE9:3', 'STATE', True))

Auf dem RaspberryMatic ist im "lighttpd-access.log" keine Nachricht der Art:
192.168.77.141 192.168.77.155 - [09/Sep/2024:23:03:43 +0200] "POST /api/homematic.cgi HTTP/1.1" 200 978 "-" "HomeAssistant/2024.9.1 aiohttp/3.10.5 Python/3.12"
mehr zu sehen...

Sowohl HA als auch RaspberryMatic sind im gleichen LAN. Und die Firewall von RM steht auf Vollzugriff...

Nur ein Neustart von HA behebt das Problem...

0 replies

SukramJ · 2024-09-10T03:23:41Z

SukramJ
Sep 10, 2024
Maintainer

Das Kommando wird ohne Fehler übertragen.
Mach bitte dein eigenes Issue auf und liefere die angeforderten Daten.
Bitte bleib bei der Sprache des TE.

0 replies

SukramJ · 2024-09-11T10:19:49Z

SukramJ
Sep 11, 2024
Maintainer

@hmax-72 Any news here?

0 replies

hmax-72 · 2024-09-12T19:14:15Z

hmax-72
Sep 12, 2024
Author

Sadly not. I was on a Business trip, so I was not able to do more troubleshooting. But the problem still exists.
To gain some more information, I created an automation which constantly turns a (HM wired-)switch on, checks if it's reported as on in HASS and truns it of again.
Hopefully this will provide some more information about the exact time to find more information in the logs.

0 replies

hmax-72 · 2024-09-13T12:59:06Z

hmax-72
Sep 13, 2024
Author

Today it happened again.

Following you'll find the Log-Section of the last working test-cycle. The log starts slightly before and slightly after the on and off triggers. In Raspberrymatic the switch is off with the timestamp fitting to the HASS-Trigger.

2024-09-13 07:02:53.706 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-BidCos-RF, channel_address = CENTRAL, parameter = PONG, value = RaspberryMatic2-BidCos-RF#13.09.2024 07:02:53.696667'
2024-09-13 07:02:53.707 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Reduce pending PING count: RaspberryMatic2-BidCos-RF - 0 for ts: 2024-09-13 07:02:53.696667
2024-09-13 07:02:53.713 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = CENTRAL:0, parameter = PONG, value = RaspberryMatic2-HmIP-RF#13.09.2024 07:02:53.702098'
2024-09-13 07:02:53.713 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Reduce pending PING count: RaspberryMatic2-HmIP-RF - 0 for ts: 2024-09-13 07:02:53.702098
2024-09-13 07:02:56.418 DEBUG (MainThread) [custom_components.homematicip_local.control_unit] Scheduled fetching of programs and sysvars for RaspberryMatic2
2024-09-13 07:02:56.514 DEBUG (MainThread) [hahomematic.client.json_rpc] POST method: SysVar.getAll
2024-09-13 07:02:56.515 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_ALL_SYSTEM_VARIABLES: Getting all system variables
2024-09-13 07:02:56.600 DEBUG (MainThread) [hahomematic.client.json_rpc] POST_SCRIPT: method: ReGa.runScript [get_system_variables_ext_marker.fn]
2024-09-13 07:02:56.601 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_SYSTEM_VARIABLES_EXT_MARKERS: Getting system variables ext markers
2024-09-13 07:02:56.601 DEBUG (MainThread) [hahomematic.platforms.hub] UPDATE_SYSVAR_ENTITIES: 27 sysvars received for RaspberryMatic2
2024-09-13 07:02:56.679 DEBUG (MainThread) [hahomematic.client.json_rpc] POST method: Program.getAll
2024-09-13 07:02:56.679 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_ALL_PROGRAMS: Getting all programs
2024-09-13 07:02:56.679 DEBUG (MainThread) [hahomematic.platforms.hub] UPDATE_PROGRAM_ENTITIES: 12 programs received for RaspberryMatic2
**2024-09-13 07:03:00.070 DEBUG (MainThread) [hahomematic.client] SET_VALUE: 00161A499D4B0E:30, STATE, True
2024-09-13 07:03:00.070 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('setValue', ('00161A499D4B0E:30', 'STATE', True))**
2024-09-13 07:03:00.224 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = CONFIG_PENDING, value = False
2024-09-13 07:03:00.225 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = UNREACH, value = False
2024-09-13 07:03:00.225 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = IP_ADDRESS, value = 10.0.0.50
2024-09-13 07:03:00.225 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIPW-DRAP 00179A4989A966 Ip Address
2024-09-13 07:03:00.229 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00161A499D4B0E:0, parameter = CONFIG_PENDING, value = False
2024-09-13 07:03:00.230 INFO (MainThread) [hahomematic.performance] Execution of _set_value took 0.15978s (interface_id: RaspberryMatic2-HmIP-RF)
2024-09-13 07:03:00.232 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00161A499D4B0E:0, parameter = UNREACH, value = False
2024-09-13 07:03:00.236 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00161A499D4B0E:30, parameter = SECTION_STATUS, value = 0
2024-09-13 07:03:00.237 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00161A499D4B0E:30, parameter = STATE, value = True
2024-09-13 07:03:00.237 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for 1/5_DRS8 ch30
2024-09-13 07:03:00.238 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00161A499D4B0E:30, parameter = SECTION, value = 2
2024-09-13 07:03:00.238 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00161A499D4B0E:30, parameter = PROCESS, value = 0
**2024-09-13 07:03:03.234 DEBUG (MainThread) [hahomematic.client] SET_VALUE: 00161A499D4B0E:30, STATE, False
2024-09-13 07:03:03.234 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('setValue', ('00161A499D4B0E:30', 'STATE', False))**
2024-09-13 07:03:03.377 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = CONFIG_PENDING, value = False
2024-09-13 07:03:03.377 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = UNREACH, value = False
2024-09-13 07:03:03.378 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = IP_ADDRESS, value = 10.0.0.50
2024-09-13 07:03:03.378 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIPW-DRAP 00179A4989A966 Ip Address
2024-09-13 07:03:03.383 INFO (MainThread) [hahomematic.performance] Execution of _set_value took 0.149221s (interface_id: RaspberryMatic2-HmIP-RF)
2024-09-13 07:03:03.384 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00161A499D4B0E:0, parameter = CONFIG_PENDING, value = False
2024-09-13 07:03:03.384 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00161A499D4B0E:0, parameter = UNREACH, value = False
2024-09-13 07:03:03.392 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00161A499D4B0E:30, parameter = SECTION_STATUS, value = 0
2024-09-13 07:03:03.393 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00161A499D4B0E:30, parameter = STATE, value = False
2024-09-13 07:03:03.393 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for 1/5_DRS8 ch30
2024-09-13 07:03:03.394 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00161A499D4B0E:30, parameter = SECTION, value = 0
2024-09-13 07:03:03.394 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00161A499D4B0E:30, parameter = PROCESS, value = 0
2024-09-13 07:03:07.256 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = CONFIG_PENDING, value = False
2024-09-13 07:03:07.256 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = UNREACH, value = False
2024-09-13 07:03:07.257 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = IP_ADDRESS, value = 10.0.0.50
2024-09-13 07:03:07.257 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIPW-DRAP 00179A4989A966 Ip Address

That's the Log where my test is not working any more (3 mins later - see my last post). Between the two log section is not a single error or warning logged.

**2024-09-13 07:06:00.070 DEBUG (MainThread) [hahomematic.client] SET_VALUE: 00161A499D4B0E:30, STATE, True
2024-09-13 07:06:00.070 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('setValue', ('00161A499D4B0E:30', 'STATE', True))**
2024-09-13 07:06:05.029 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = CONFIG_PENDING, value = False
2024-09-13 07:06:05.029 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = UNREACH, value = False
2024-09-13 07:06:05.029 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = IP_ADDRESS, value = 10.0.0.50
2024-09-13 07:06:05.030 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIPW-DRAP 00179A4989A966 Ip Address
2024-09-13 07:06:26.425 DEBUG (MainThread) [custom_components.homematicip_local.control_unit] Scheduled fetching of programs and sysvars for RaspberryMatic2
2024-09-13 07:06:26.519 DEBUG (MainThread) [hahomematic.client.json_rpc] POST method: SysVar.getAll
2024-09-13 07:06:26.519 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_ALL_SYSTEM_VARIABLES: Getting all system variables
2024-09-13 07:06:26.606 DEBUG (MainThread) [hahomematic.client.json_rpc] POST_SCRIPT: method: ReGa.runScript [get_system_variables_ext_marker.fn]
2024-09-13 07:06:26.606 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_SYSTEM_VARIABLES_EXT_MARKERS: Getting system variables ext markers
2024-09-13 07:06:26.607 DEBUG (MainThread) [hahomematic.platforms.hub] UPDATE_SYSVAR_ENTITIES: 27 sysvars received for RaspberryMatic2
2024-09-13 07:06:26.687 DEBUG (MainThread) [hahomematic.client.json_rpc] POST method: Program.getAll
2024-09-13 07:06:26.687 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_ALL_PROGRAMS: Getting all programs
2024-09-13 07:06:26.687 DEBUG (MainThread) [hahomematic.platforms.hub] UPDATE_PROGRAM_ENTITIES: 12 programs received for RaspberryMatic2
2024-09-13 07:06:29.270 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001F58A9A71ED6:0, parameter = DUTY_CYCLE_LEVEL, value = 4.5
2024-09-13 07:06:29.271 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for RPI-RF-MOD 001F58A9A71ED6 Duty Cycle Level
2024-09-13 07:06:29.380 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001F58A9A71ED6:0, parameter = CARRIER_SENSE_LEVEL, value = 0.0
2024-09-13 07:06:29.380 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for RPI-RF-MOD 001F58A9A71ED6 Carrier Sense Level
2024-09-13 07:06:35.423 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = CONFIG_PENDING, value = False
2024-09-13 07:06:35.424 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = UNREACH, value = False
2024-09-13 07:06:35.424 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = IP_ADDRESS, value = 10.0.0.50
2024-09-13 07:06:35.424 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIPW-DRAP 00179A4989A966 Ip Address
2024-09-13 07:06:56.426 DEBUG (MainThread) [custom_components.homematicip_local.control_unit] Scheduled fetching of programs and sysvars for RaspberryMatic2
2024-09-13 07:06:56.517 DEBUG (MainThread) [hahomematic.client.json_rpc] POST method: SysVar.getAll
2024-09-13 07:06:56.517 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_ALL_SYSTEM_VARIABLES: Getting all system variables
2024-09-13 07:06:56.605 DEBUG (MainThread) [hahomematic.client.json_rpc] POST_SCRIPT: method: ReGa.runScript [get_system_variables_ext_marker.fn]
2024-09-13 07:06:56.605 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_SYSTEM_VARIABLES_EXT_MARKERS: Getting system variables ext markers
2024-09-13 07:06:56.606 DEBUG (MainThread) [hahomematic.platforms.hub] UPDATE_SYSVAR_ENTITIES: 27 sysvars received for RaspberryMatic2
2024-09-13 07:06:56.706 DEBUG (MainThread) [hahomematic.client.json_rpc] DO_RENEW_LOGIN: method: Session.renew [VikmnJhafO]
2024-09-13 07:06:56.782 DEBUG (MainThread) [hahomematic.client.json_rpc] POST method: Program.getAll
2024-09-13 07:06:56.782 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_ALL_PROGRAMS: Getting all programs
2024-09-13 07:06:56.782 DEBUG (MainThread) [hahomematic.platforms.hub] UPDATE_PROGRAM_ENTITIES: 12 programs received for RaspberryMatic2
2024-09-13 07:07:01.059 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = CONFIG_PENDING, value = False
2024-09-13 07:07:01.060 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = UNREACH, value = False
2024-09-13 07:07:01.060 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = IP_ADDRESS, value = 10.0.0.50
2024-09-13 07:07:01.060 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIPW-DRAP 00179A4989A966 Ip Address
2024-09-13 07:07:01.068 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:0, parameter = CONFIG_PENDING, value = False
2024-09-13 07:07:01.069 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:0, parameter = ERROR_UNDERVOLTAGE, value = False
2024-09-13 07:07:01.069 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:0, parameter = UNREACH, value = False
2024-09-13 07:07:01.069 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:0, parameter = ERROR_OVERHEAT, value = False
2024-09-13 07:07:01.069 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:0, parameter = ACTUAL_TEMPERATURE, value = 27.0
2024-09-13 07:07:01.069 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for 1/3_DRD3 Actual Temperature
2024-09-13 07:07:01.070 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:0, parameter = OPERATING_VOLTAGE_STATUS, value = 0
2024-09-13 07:07:01.070 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:0, parameter = OPERATING_VOLTAGE, value = 24.2
2024-09-13 07:07:01.070 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:0, parameter = ERROR_CODE, value = 0
2024-09-13 07:07:01.076 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:1, parameter = ERROR_RESTART_NEEDED, value = False
2024-09-13 07:07:01.077 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:1, parameter = ERROR_COPROCESSOR, value = True
2024-09-13 07:07:01.077 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:1, parameter = ERROR_OVERHEAT, value = False
2024-09-13 07:07:01.077 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:1, parameter = ERROR_OVERLOAD, value = False
2024-09-13 07:07:01.077 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:1, parameter = ERROR_CODE, value = 4
2024-09-13 07:07:01.083 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:5, parameter = ERROR_RESTART_NEEDED, value = False
2024-09-13 07:07:01.083 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:5, parameter = ERROR_COPROCESSOR, value = True
2024-09-13 07:07:01.083 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:5, parameter = ERROR_OVERHEAT, value = False
2024-09-13 07:07:01.084 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:5, parameter = ERROR_OVERLOAD, value = False
2024-09-13 07:07:01.084 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 001698A9A9705E:5, parameter = ERROR_CODE, value = 4
2024-09-13 07:07:01.203 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = CONFIG_PENDING, value = False
2024-09-13 07:07:01.204 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = UNREACH, value = False
2024-09-13 07:07:01.206 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = RaspberryMatic2-HmIP-RF, channel_address = 00179A4989A966:0, parameter = IP_ADDRESS, value = 10.0.0.50
2024-09-13 07:07:01.206 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIPW-DRAP 00179A4989A966 Ip Address

0 replies

SukramJ · 2024-09-13T13:05:07Z

SukramJ
Sep 13, 2024
Maintainer

Deine CCU sendet keine Events mehr, da kann ich also nichts machen.
Mehr kann ich aus deinem selektiven Log nicht entnehmen.

0 replies

SukramJ · 2024-09-13T14:20:57Z

SukramJ
Sep 13, 2024
Maintainer

In den Logs von RM/CCU könnten entsprechende Fehler sein.
Ich würde dir empfehlen, das DU dich direkt an RM oder das Homematic Forum für die Ursachenforschung wendest.

0 replies

hmax-72 · 2024-09-14T12:55:31Z

hmax-72
Sep 14, 2024
Author

sorry, das macht so keinen Sinn.

VOR dem Update auf die aktuelle Version (1.65) war die Integration super stabil. VIEL und stabiler und besser wie die originale von HASS!
Bei HM habe ich nichts geändert (also kein Update, zumindest nicht als das Problem aufgetreten ist).
ein Restart von HASS löst das Problem. HM läuft durch.

Müssen die Events irgendwie abonniert werden? Lässt sich das Abo irgendwie prüfen oder regelmäßig erneuern?
Das HM-Log zeigt keine Auffälligkeiten. Es werde es aber zeitnah nach einem Fehler nochmal prüfen.

0 replies

SukramJ · 2024-09-14T14:01:06Z

SukramJ
Sep 14, 2024
Maintainer

sorry, das macht so keinen Sinn.

Danke, ich mach das hier den ersten Tag in Vertretung, und sowas hab ich noch nie gesehen.

VOR dem Update auf die aktuelle Version (1.65) war die Integration super stabil. VIEL und stabiler und besser wie die originale von HASS!

Dann mach doch mal ein Rollback.

Müssen die Events irgendwie abonniert werden?

Klar das passiert ein mal beim Start.

Lässt sich das Abo irgendwie prüfen oder regelmäßig erneuern?

Warum? Der Mechanismus funktioniert so seit Jahren, und ist von HM auch nicht so vorgesehen.

Um noch mal eins klar zu Stellen: Wenn deine CCU nach einiger Zeit nichts sendet kann ich nichts machen.
Bei mir läuft ein System, das hat auch nach drei Monaten noch keine Probleme mit HM Komponenten.
Aus den Logauszügen, die Du zur Verfügung gestellt hast, lässt sich auch nichts anders herauslesen.

Afterwards attach the full log as file here.
Please attach the integration diagnosis as well.

Bitte beim nächsten mal beachten. Ansonsten ist eine weitere Analyse Zeitverschwendung, und das Tickert kann geschlossen werden.

0 replies

hmax-72 · 2024-09-21T14:15:46Z

hmax-72
Sep 21, 2024
Author

Kleines Update zwischendurch: Bisher ist das Problem nicht nochmal aufgetreten. Daher habe ich keine neuen Infos.

Um das Thema abzufedern habe ich eine Automation gebaut, die die Rückmeldungen von HM überwacht und ggf. HASS automatisch neu startet. Das ist zwar keine Lösung, aber immerhin ein workaround.
Dass der Auslöser u.U. in HM liegt, kann gut sein. Nachdem die Integration bisher so super funktioniert hat, habe ich vermutet, dass evt. beim Update was passiert ist. Ist scheinbar nicht so.
Vielleicht kommt ja mal so eine Art interner Monitor in der Integration, der die Events ggf. automatisch neu abonniert.

Sorry, dass ich dich genervt habe.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

cannot execute actions from HASS to HM after upgrading to 1.65 #1712

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 11 comments

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

cannot execute actions from HASS to HM after upgrading to 1.65 #1712

hmax-72 Sep 6, 2024

The problem

What version of HomematicIP (local) has the issue?

What was the last working version of HomematicIP (local)?

What type of installation are you running?

What type of installation are you running for your homematic backend?

Which version of your homematic backend are you running?

What hardware are you running for your system?

Which config details do you use

Which interfaces do you use?

Diagnostics information (no logs here)

Log file extract. Anything in the logs that might be useful for us? The log (Setting/System/Logs -> load full log) is the best source to support trouble shooting!

Additional information

Replies: 11 comments

SukramJ Sep 6, 2024 Maintainer

kramer74 Sep 9, 2024

SukramJ Sep 10, 2024 Maintainer

SukramJ Sep 11, 2024 Maintainer

hmax-72 Sep 12, 2024 Author

hmax-72 Sep 13, 2024 Author

SukramJ Sep 13, 2024 Maintainer

SukramJ Sep 13, 2024 Maintainer

hmax-72 Sep 14, 2024 Author

SukramJ Sep 14, 2024 Maintainer

hmax-72 Sep 21, 2024 Author

hmax-72
Sep 6, 2024

SukramJ
Sep 6, 2024
Maintainer

kramer74
Sep 9, 2024

SukramJ
Sep 10, 2024
Maintainer

SukramJ
Sep 11, 2024
Maintainer

hmax-72
Sep 12, 2024
Author

hmax-72
Sep 13, 2024
Author

SukramJ
Sep 13, 2024
Maintainer

SukramJ
Sep 13, 2024
Maintainer

hmax-72
Sep 14, 2024
Author

SukramJ
Sep 14, 2024
Maintainer

hmax-72
Sep 21, 2024
Author