Homematic Entities keep getting disabled

[Schleek]

I agree to the following

• I have read the documentation right now
• I have read the FAQs right now
• I am aware of the latest release notes
• I am aware that an integration that was installed via HACS also needs to be updated via HACS
• The Backend (CCU/Homegear/...) is working as expected, devices are taught in and are controllable by its own UI.
• I am running the latest version of the custom_component (and Home Assistant)

The problem

I have several programs on my CCU3, such as switching off all the lights or opening all the shutters (stores).

On my Home Assistant dashboard, I have configured a section for quick settings with entries like:

• entity: button.ccu3_webui_p_all_stores_up
  name: All storen up
• entity: button.ccu3_webui_p_all_stores_down
  name: All stores down
  Since the last two versions of the Homematic(IP) Local integration, these entities are repeatedly getting disabled. I have to manually re-enable them each time, which disrupts the functionality of my setup.

Could you please investigate why this is happening and provide guidance on how to resolve the issue? Thank you.

What version of HomematicIP (local) has the issue?

1.77

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

No response

What type of installation are you running?

Home Assistant Container

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

CCU3

Which version of your homematic backend are you running?

3.79.6

What hardware are you running for your system?

Synology DS920+

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)

config_entry-homematicip_local-7dec6ba51c96b466c442cc2017fa9b46(1).json

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

[SDvanDeElk]

Same for me. It looks like that for me it happens only to system variables which are deactivated by default. If I activate them, they deactivate automatically after a certain period of time. However, not clear to me when. The timespan seems to vary. Sometimes it works for 1-2 days. sometimes the activation only lasts for a couple of hours.

Setup: HA 2024.12.3, Homematic (IP) local 1.76.1 CCU 3.79.6

[SukramJ]

@SDvanDeElk Please update to the latest version.
@Schleek please add screenshots of your programs overview in CCU WebUI

[SDvanDeElk]

Never update on the .0 version. I wait with updating until the .1 version is available. Will check afterwards.

[SukramJ]

Never update on the .0 version. I wait with updating until the .1 version is available. Will check afterwards.

@SDvanDeElk If you are no willing to update to 1.77.0 then please stop posting to this thread!

[SDvanDeElk]

Why should I stop giving hints. OP had an issue with the current version and he mentioned he had the issue since the last 2 versions. I was giving a hint that within the previous version the problem with disabling entities persisted and it seems not to be related to just his installation. Such information might be useful for various reasons and various people during trouble shooting. And as already mentioned, I will update with the next update of HA core to 2025.1.1.

[SukramJ]

I simply don't care about older versions.
That's why i request people to update to the latest version before creating an issue.

[Schleek]

Thank you @SukramJ for your answer and your hard work in this integration. Here are the screenshots (Mix of english, german and luxembourgish)

When activating the entities again last time, I associated a label with every entity. That label is gone as well, when the entity is getting disabled.

Here a look at the entities with the "button" label:

[Schleek]

I enabled them again this morning, now they are disabled again.

[SukramJ]

The program on the CCU is still enabled?

1.77.0 introduced switches to enable/disable programs on the CCU. Are these switches still available?

[SukramJ]

Unfortunately I can't reproduce this myself, so only debugging helps.

• Activate all entities as expected.
• Enable debug logging for the integration, and wait until the problem occurs again.
• Stop debug logging.
• Upload the log file as zip here

[Schleek]

Good evening,
I enabled the switches as well. 2 Minutes later, everything was again unavailable.
I cropped the two minutes 21:28 and 21:29 in the debug log.
HA_debug_Schleek.txt.zip

[eikowagenknecht]

Happens to me as well. One thing to add: When they are automatically disabled, they also reset their name to the original value if the entity had been renamed in home assistant before. (eg a system variable I use as eg_bad_luefter reset itself to kg_flur_homematic_ccu3_sv_lueftung_bad. And they use the custom name in Home Assistant that was set.

If the type was changed (e.g. from switch to fan), the new type is completely gone and the old is available with the autogenerated name in disabled state.

Seems like they are somehow thoroughly deleted and then recreated from scratch.

For me the last trigger of this behavior was a reboot of the Homematic Addon.

[SukramJ]

@Schleek Thanks, but we have to repeat this. Unfortunately not all packages were covered.

Please add this to your configuration.yaml, or extend the existing logging configuration, and restart HA afterwards.

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

[SukramJ]

@eikowagenknecht Feel free tu upload debug logs too.

[Schleek]

@SukramJ
Thanks, I extended the logging. Here we go again, 3 minutes of logs where it happened.
home-assistant.Schleek.log.zip

[SukramJ]

Thanks @eikowagenknecht for the hint with the CCU restart as trigger. So I could recreate and fix this.

@Schleek What is the trigger in your case? Looks like you reloaded the integration.

[SukramJ]

Please test version 1.78.0b3 and give feedback

[Schleek]

Thanks. Until now, it seems to be ok. Give me a day or two to confirm ;)