Homematic - HmIPW-FIO6 no keypress event

barnie1 · October 30, 2021, 10:38pm

Hi,

I have connected pushbuttons to my HmIPW-FIO6 modules and unfortunately I do not get homematic.keypress events. The only thing I see in the log are HMGeneric Events

2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-HMIP, address = 00175A498C4ACB:0, value_key = CONFIG_PENDING, value = False
2021-10-31 00:13:00 INFO (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: address=00175A498C4ACB:0, interface_id=homeassistant-HMIP, key=CONFIG_PENDING, value=False
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 8: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 12: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 16: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 20: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 24: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 28: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-HMIP, address = 00175A498C4ACB:0, value_key = UNREACH, value = False
2021-10-31 00:13:00 INFO (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: address=00175A498C4ACB:0, interface_id=homeassistant-HMIP, key=UNREACH, value=False
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 8: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 12: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 16: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 20: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 24: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 28: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-HMIP, address = 00175A498C4ACB:5, value_key = PRESS_SHORT, value = True
2021-10-31 00:13:00 INFO (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: address=00175A498C4ACB:5, interface_id=homeassistant-HMIP, key=PRESS_SHORT, value=True
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 8: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 12: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 16: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 20: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 24: off>>
2021-10-31 00:13:00 DEBUG (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.event: Using callback <bound method HMDevice._hm_event_callback of <Entity Taster HWR:4ACB 28: off>>

Does anyone have any ideas what I can do? All other devices like thermostats, window sensors and blinds work fine.

mdo · November 12, 2024, 1:15pm

Hi, same for me - currently no idea how to include those FIO6 modules into home assistant.
They don’t even show anything in device manager

@barnie1 did you find a solution?
Somehow your post is the only one on “home assistant and FIO6 modules” on the whole Internet😅

danielperna84 · November 12, 2024, 5:30pm

You should consider switching to GitHub - danielperna84/custom_homematic: Custom Home Assistant Component for HomeMatic

The old (core) integration is not being maintained anymore, and therefore does not receive support for „new“ devices.

mdo · November 12, 2024, 8:20pm

Hi @danielperna84 I am using your integration (and I am very happy with it!! Thank you!)

I found the “solution”.
In RaspberryMatic there is the feature to “forward events” - this must be activated per channel and then the events are registered in HA.
Those events then can be processed accordingly.

mdo · November 12, 2024, 8:31pm

But @danielperna84 perhaps you have an answer on that.

I now am able to register the events on the activated (RM) channels of FIO6 modules.

But there is NO direct relation between the event and the channel in HA. I need to create a separate automation for that, correct? (For light automatization i need an ON/OFF toggle and not just “event”)

danielperna84 · November 12, 2024, 8:36pm

The event you receive will be something like PRESS_SHORT or similar. When using Device Automations I believe (I’m actually not using HomeMatic anymore) it is prefilled with Events like “xyz wurde kurz gedrückt”. Buttons have not state like on or off.

The way automations usually are done in this case is to the switch.toggle or light.toggle service, which flips the state of the actor on every press of the button.

mdo · November 12, 2024, 9:00pm

All correct what you are saying.

But still: there is no direct relation/connection between event on CH1 and the corresponding control CH8.
so, in terms of “knowing, whether the switch is currently on or off” after several tappings, i would need to count the events or have a separate automation, that is toggling CH8 with each CH1 tap.
And that’s a bit strange imo - because why should the toggle not react in parallel to the tapping events.

danielperna84 · November 13, 2024, 9:34pm

I think my problem is, that I don’t know what the device is doing, or what you’re expecting to happen.

If CH1 is a “button” channel that controls another switch-actor with a load (like a lamp), and CH8 is a “output” that turns a status LED on or off, then yes, in this case you need an automation that makes CH8 “follow” the state of the actor. Imagine you turn on the lamp-actor via an automation, or manually from the HA interface. In this case, at least in my opinion, CH8 should still turn on or off, according to the state of the lamp, NOT in relation to CH1, as that wouldn’t reflect the actual state of the light anymore.