Homematic device that becomes unavailable

Bonjour,

I have a problem with Homematic switches becoming unavailable in home assistant.

Home assistant is installed on an Intel NUC. It is completely up to date.

Home Assistant Core 2022.6.5
Home Assistant Supervisor 2022.05.3
Home Assistant OS 8.1

I use a CCU3 from homematic v3.63.9 (the latest version).

My problem: I have very regularly switches that become unavailable only when a service call is made on it. For example a switch.turn_on.

Calling the homematic reconnect service does not change anything. They are still unavailable.

If I go to the CCU3, and change the state of the switch directly from the CCU3 interface, then Home Assistant sees it again and it is no longer considered unavailable.

This is very strange.

Here are the logs when it crashes.

2022-06-15 07:57:14 DEBUG (SyncWorker_2) [pyhomematic.devicetypes.generic] HMGeneric.setValue: address = 'LEQ0181256:1', key = 'STATE' value = 'True'
2022-06-15 07:57:15 ERROR (SyncWorker_2) [pyhomematic.devicetypes.generic] HMGeneric.setValue: STATE on LEQ0181256:1 Exception: <Fault -1: 'Failure'>
2022-06-15 07:57:15 DEBUG (Thread-3) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-rf, address = LEQ0181256:0, value_key = UNREACH, value = True
2022-06-15 07:57:15 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: address=LEQ0181256:0, interface_id=homeassistant-rf, key=UNREACH, value=True
2022-06-15 07:57:15 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity LED comptoire fenetre: off>>
2022-06-15 07:57:15 DEBUG (Thread-3) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-rf, address = LEQ0181256:0, value_key = STICKY_UNREACH, value = True
2022-06-15 07:57:15 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: address=LEQ0181256:0, interface_id=homeassistant-rf, key=STICKY_UNREACH, value=True

Logs for homematic reconnect

2022-06-15 13:00:00 DEBUG (Thread-3) [pyhomematic._hm] RPCFunctions.listDevices...........
2022-06-15 13:00:00 DEBUG (Thread-3) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-rf, address = LEQ0181256:0, value_key = STICKY_UNREACH, value = True
2022-06-15 13:00:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: address=LEQ0181256:0, interface_id=homeassistant-rf, key=STICKY_UNREACH, value=True
2022-06-15 13:00:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity LED comptoire fenetre: off>>
2022-06-15 13:00:00 DEBUG (Thread-3) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-rf, address = LEQ0181256:0, value_key = UNREACH, value = True
2022-06-15 13:00:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: address=LEQ0181256:0, interface_id=homeassistant-rf, key=UNREACH, value=True

Does anyone have an idea of the problem? I have a possible solution with the CCU3, that is to say that every day, I change the status of each device, but it is not ideal at all.

Thanks you very much

That’s known problem. However, the integration is not being worked on anymore. You can check out the new integration, which currently is available as a custom integration. You can find more information here: https://github.com/danielperna84/custom_homematic

Thanks a lot Daniel for your answer.

So I changed and I use now the custom_homematic.

Note that I use mainly Node-Red.

I have now other problems. It is no longer possible to play a sound on “HM-OU-CFM-Pl”. Before, I was using the service “homematic.set_device_value” with the parameter :
{“address”:“JEQ0141048”,“param”:“SUBMIT”,“value”:“1,1,108000,9”,“channel”:2}

Now I use homematicip_local.set_device_value" with these parameters :
{“device_id”:“JEQ0141048”,“parameter”:“SUBMIT”,“value”:“1,1,108000,9”,“channel”:2}
or
{“device_id”:“JEQ0141048”,“parameter”:“SUBMIT”,“value”:“1,1,108000,9”,“value_type”:“string”,“channel”:2}
and it does not work. I have been testing different combinations for 1 hour without success.

Also, the remote control button events do not work. The name of the button is correctly set and I activate it in the entity. But I can’t really link these events.

If I use “homematic.keypress”, my event is called but I have to process by hand to know what has been entered, which is not very convenient.

Concerning the loss of connection, the problem does not seem to be solved but I will see in the long term.

Do you have any ideas for improvement?

Thanks you

Hello,

I confirm that the initial problem has not been solved. I still have devices that become unavailable in home assistant after an action (on or off for example) has been called.

And I just need to perform an action in the CCU3 for them to become active again in home assistant.

Except the basic configuration explained on github, there are other manipulations to do on homeassistant ?

Thanks you

Hello,

Concerning the problem on the device “HM-OU-CFM-Pl”, when analysing the python files and the logs, I find that the SUBMIT parameter is simply ignored.

_IGNORED_PARAMETERS_WILDCARDS_END: set[str] = {
    "OVERFLOW",
    "OVERHEAT",
    "OVERRUN",
    "REPORTING",
    "RESULT",
    "STATUS",
    "SUBMIT",
    "WORKING",
}

Is it really necessary not to process the SUBMIT as before?

Thanks you