search

danielperna84 / hahomematic

Python 3 Interface for Home Assistant to interact with HomeMatic devices
MIT License
130 stars 22 forks source link

HMIP-FSM16/HMIP-FSI16/HMIP-BSM/HMIP-FDT won't detected as light until init click #1601

Closed morpheus12 closed 2 months ago

morpheus12 commented 2 months ago

I agree to the following

The problem

Hi Team, first great Plugin! I'm using it in 3 instances but here first time with higher than 1.61.XX Its about a holiday home of my aunt. Here i have a ccu3 which is handling about 50 HMIP components and 3 HM-RF (the old RGBW Controller). Today she told me the home assistant app is not working. After login i saw all HM-Components are not reacting. In the logs of ha i saw an entry about HM-IP-RF ist not reacting pong is not answering as expected. After a few minutes in the CCU3 webui i got the same error message that some components are not reacting. So i rebooted the CCU3. Afterwords all is looking good. But in HA my dashboards with mushroom cards are not working.

mhh...strange

Therefore i have taken a look into the overview dashboard of HA and figured out some components are syncing data like hmip-wth, the old HM RGBW Controller, but hmip-fsm16/fsi16 and hmip-bsm/hmip-fdt are looking weird image

They looks like a power-plug/switch initally with the flash-symbol. For instance "Deckenlicht_Kueche" (FSM16) After switching them in the overview dashboard to on the appearence change to a light switch like "Licht_Kueche_Arbeitsflaeche" (FSM16).

image Here i've done this with "Deckenlicht_Kueche". As you can see now the symbol switched to a "switch". This update take effekt within 3-4sec.

After they switched here in the overview-dashboard to a "light-switch" they're working in my own created mushroom dashboards (mushroom light card is used for it) as expected. image

I assume the mushroom cards are not working because the entity is not "flagged correctly" as light until i click them initially in the overview dashboard to on.

I've restarted Home assistant to see the behavior (currently HA Core 2024.6.4, HA-OS 12.3). image So the "already clicked" FSM/FSI actors are marked correctly. So i guess the problem is related to the ccu3 restart before.

Performing a manual relod/init of the plugin to update the ccu-data doesn't change anything.

Interesting topic: some of the actors are "enhanced" by an switch-adoption helper (to combine them as group with dimmers or the old hm rgbw controller). This once are working fine from the beginning.

But i saw one hmip-fdt which is working fine from the beginning but others not.

Perhaps there is a kind of self-healing or correct initiation. I will keep the last "incorrect" actors in this state and will have a look tomorrow on it. I will keep you up-to-date

thanks for reading until here.

What version of HomematicIP (local) has the issue?

1.63.1

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

assumption: 1.60

What type of installation are you running?

Home Assistant OS

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

CCU3

Which version of your homematic backend are you running?

3.61.7

What hardware are you running for your system?

Intel Nuc

Which config details do you use

Which interfaces do you use?

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

morpheus12 commented 2 months ago

Short Update: after about 1h all actors which wheren't clicked manually are now self-healed

SukramJ commented 2 months ago

TL;DR

In the logs of ha i saw an entry about HM-IP-RF ist not reacting pong is not answering as expected.

Please add logs (Full logs) and Integration diagnostics.

morpheus12 commented 2 months ago

config_entry-homematicip_local-73cfb8cf40e7284e9fd8825ef3780362.json

Here i got the Integration Diagnostics.

The HA Log (i'm a idiot) is deleted. Since 2 days no real entries in the log file of HA. 2024-06-22 22:41:14.154 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-06-22 22:41:14.160 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration homematicip_local which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-06-22 22:41:18.694 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues 2024-06-22 22:41:18.843 WARNING (MainThread) [hass_nabucasa.cloud_api] Fetched https://alexa-api.nabucasa.com/access_token (400) 2024-06-22 22:41:27.492 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 642: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues

Homematic is working fine since the last reboot.

SukramJ commented 2 months ago

Homematic is working fine since the last reboot.

Sounds like a local communication problem and not like an issue with this integration. So i'll close this, because only the log contains the relevant information.