Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[homeatic] HM-PBI-4-FM not working #6027

sascha777 opened this issue Aug 10, 2018 · 4 comments


None yet
3 participants
Copy link

commented Aug 10, 2018


I am new to openhab 2.3.0-1 running on a pi 3 with an HM-MOD-RPI-PCB module and yahm 2.8.6.
I have some things and items from binding homeatic already up and running but struggle to get my new homeatic HM-PBI-4-FM (firmware 1.5) adressed.

The HM-PBI-4-FM is properly configured in yahm and successfully tested as well. The paperUi automatically detects the new thing without any error. In VS Code I also added a new item for channel 1 pressShort (tried in paperUi as well).

Switch HM_EG_WZ_Schliesskontakt_1_State {channel="homematic:HM-PBI-4-FM:PEQ01xxxxx:OEQ11xxxxx:1#PRESS_SHORT"}

Normally I see all my items state changes in the log and expected the HM-PBI-4-FM to do so too.
But when triggering the HM-PBI-4-FM I don't see any logs written nor does my rule fire.

I assume this is a bug in the binding. Could someone please check on that?



This comment has been minimized.

Copy link

commented Aug 20, 2018

Going to try a new hardware...


This comment has been minimized.

Copy link

commented Dec 20, 2018

I have the same problem


This comment has been minimized.

Copy link

commented Dec 20, 2018

I didn't get it working. Sent it back and replaced it with another solution.


This comment has been minimized.

Copy link

commented May 14, 2019

I had the same problem and just wasted 3 hours of my life with it.
On the upside, I figured out the problem.

It's actually documented in the Troubleshooting section of the OpenHab Homematic binding.

It seems buttons like the HM-PB-2-WM55 do just send these kind of events to the CCU if they are mentioned in a CCU program. A simple workaround to make them send these events is, to create a program (rule inside the CCU) that does just have a "When" part and no "Then" part, in this "When" part each channel needs to be mentioned at least once.

So adding a dummy program in the CCU for these channels fixes the issue. Worked like a charm for me.

@sascha777 sascha777 closed this May 15, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.