[SOLVED] [Homematic] HM-PB-2-WM55 PRESS_LONG event not fired until button release

lopez1de · February 1, 2018, 11:10am

I’m on openhab 2.2.0-1 release and have the problem, the the event PRESS_LONG of the HM-PB-2-WM55 is triggered when I release the button. But it should trigger after 0.4 seconds. What I get instead is the behavior of PRESS_LONG_RELEASE. On my old installation with openhab 2.0 everything went as it should. The only problem there was the problem that PRESS_LONG was triggered about four times per seconds. But this is another story.

Does anyone have an idea that was going wrong?

job · February 1, 2018, 11:20am

I guess, this is related.

lopez1de · February 1, 2018, 11:25am

Hm, I don’t think so. I have no errors in the logs. The event is comming correctly:

homematic:HM-PB-2-WM55:ccu:NAA0000000:1#PRESS triggered SHORT

But the event is trigger only if I release the button.

job · February 1, 2018, 11:35am

Ok, strange. I am also on 2.2 and i see these warnings. What bridge are you using? I’m using the of the latest nightly Homegear.

I don’t think the event timing is done by the binding, but by the bridge.

lopez1de · February 1, 2018, 11:43am

I’m using piVCCU.

lopez1de · February 1, 2018, 11:50am

Created an issue

job · February 1, 2018, 12:06pm

This is my log running Homegear 0.8.0-something vs openHAB 2.2.0-1. Looks good to me. I just pressed once, but kept pressing until the release.

2018-02-01 13:01:13.304 [WARN ] [virtual.PressVirtualDatapointHandler] - Unknown value 'CONT' for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed

==> /var/log/openhab2/events.log <==

2018-02-01 13:01:13.311 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered 
2018-02-01 13:01:13.318 [vent.ItemStateChangedEvent] - AZKEY_CONT1 changed from NULL to ON
2018-02-01 13:01:13.329 [vent.ItemStateChangedEvent] - AZKEY_LONG1 changed from NULL to ON
2018-02-01 13:01:13.333 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG

==> /var/log/openhab2/openhab.log <==

2018-02-01 13:01:13.527 [WARN ] [virtual.PressVirtualDatapointHandler] - Unknown value 'CONT' for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed

==> /var/log/openhab2/events.log <==

2018-02-01 13:01:13.531 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG

==> /var/log/openhab2/openhab.log <==

2018-02-01 13:01:13.784 [WARN ] [virtual.PressVirtualDatapointHandler] - Unknown value 'CONT' for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed

==> /var/log/openhab2/events.log <==

2018-02-01 13:01:13.791 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG

==> /var/log/openhab2/openhab.log <==

2018-02-01 13:01:14.134 [WARN ] [virtual.PressVirtualDatapointHandler] - Unknown value 'CONT' for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed

==> /var/log/openhab2/events.log <==

2018-02-01 13:01:14.140 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG

==> /var/log/openhab2/openhab.log <==

2018-02-01 13:01:14.311 [WARN ] [virtual.PressVirtualDatapointHandler] - Unknown value 'CONT' for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed

==> /var/log/openhab2/events.log <==

2018-02-01 13:01:14.318 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG

==> /var/log/openhab2/openhab.log <==

2018-02-01 13:01:14.583 [WARN ] [virtual.PressVirtualDatapointHandler] - Unknown value 'CONT' for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed

==> /var/log/openhab2/events.log <==

2018-02-01 13:01:14.603 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG

==> /var/log/openhab2/openhab.log <==

2018-02-01 13:01:14.800 [WARN ] [virtual.PressVirtualDatapointHandler] - Unknown value 'CONT' for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed

==> /var/log/openhab2/events.log <==

2018-02-01 13:01:14.808 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG

==> /var/log/openhab2/openhab.log <==

2018-02-01 13:01:15.068 [WARN ] [virtual.PressVirtualDatapointHandler] - Unknown value 'CONT' for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed

==> /var/log/openhab2/events.log <==

2018-02-01 13:01:15.072 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG

==> /var/log/openhab2/openhab.log <==

2018-02-01 13:01:15.320 [WARN ] [virtual.PressVirtualDatapointHandler] - Unknown value 'CONT' for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed

==> /var/log/openhab2/events.log <==

2018-02-01 13:01:15.328 [vent.ItemStateChangedEvent] - AZKEY_LONG1 changed from ON to OFF

2018-02-01 13:01:15.331 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG

==> /var/log/openhab2/openhab.log <==

2018-02-01 13:01:15.587 [WARN ] [virtual.PressVirtualDatapointHandler] - Unknown value 'CONT' for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed

==> /var/log/openhab2/events.log <==

2018-02-01 13:01:15.594 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG

==> /var/log/openhab2/openhab.log <==

2018-02-01 13:01:15.846 [WARN ] [virtual.PressVirtualDatapointHandler] - Unknown value 'CONT' for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed

==> /var/log/openhab2/events.log <==

2018-02-01 13:01:15.859 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG

==> /var/log/openhab2/openhab.log <==

2018-02-01 13:01:16.093 [WARN ] [virtual.PressVirtualDatapointHandler] - Unknown value 'CONT' for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed

==> /var/log/openhab2/events.log <==

2018-02-01 13:01:16.102 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG

==> /var/log/openhab2/openhab.log <==

2018-02-01 13:01:16.366 [WARN ] [virtual.PressVirtualDatapointHandler] - Unknown value 'CONT' for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed

==> /var/log/openhab2/events.log <==

2018-02-01 13:01:16.372 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG

==> /var/log/openhab2/openhab.log <==

2018-02-01 13:01:16.689 [WARN ] [virtual.PressVirtualDatapointHandler] - Unknown value 'CONT' for PRESS virtual datapoint, only SHORT,LONG,LONG_RELEASE allowed

==> /var/log/openhab2/events.log <==

2018-02-01 13:01:16.693 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG

2018-02-01 13:01:16.703 [vent.ItemStateChangedEvent] - AZKEY_LONG_RELEASE1 changed from NULL to ON

2018-02-01 13:01:16.707 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG_RELEASE

Maybe this is a different bridge behaviour? Do you run the latest CCU2-Firmware with your piVCCU?

The behaviour of the multiple PRESS_LONG events is fine, you can increase/decrease brightness/volume with that.

ei_Gelb_Geek · February 1, 2018, 12:11pm

This is not a mistake! That’s how Homematic works. After the set time (on the device), a long keystroke is detected. As soon as you release the button, the event will be executed!
You can even create a program directly on the CCU, long key press -> turn on the light … you’ll see, the light turns on as soon as you let go of the key.

Schreibtischtaster = HM-PBI-4-FM Firmware. 1.5

EDIT:
HM-PB-2-FM -> Fires as you discribe …

lopez1de · February 1, 2018, 12:23pm

Thanks for all the replies. But this makes no sense to me. For what reason there is a PRESS_LONG and a PRESS_LONG_RELEASE event if both do the same?

But it really looks like it specific to the piVCCU. I’m on the current firmware 2.31.25 on the piVCCU.

Was using homegear before and never had this problem.

job · February 1, 2018, 12:45pm

If you look at my log, they don’t do the same. (I removed all these warnings from the CONT-stuff.)

LONG is triggered several times within the pressing, LONG_RELEASE just at the end.

2018-02-01 13:01:13.311 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered 
2018-02-01 13:01:13.318 [vent.ItemStateChangedEvent] - AZKEY_CONT1 changed from NULL to ON
2018-02-01 13:01:13.329 [vent.ItemStateChangedEvent] - AZKEY_LONG1 changed from NULL to ON
2018-02-01 13:01:13.333 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG
2018-02-01 13:01:13.531 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG
2018-02-01 13:01:13.791 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG
2018-02-01 13:01:14.140 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG
2018-02-01 13:01:14.318 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG
2018-02-01 13:01:14.603 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG
2018-02-01 13:01:14.808 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG
2018-02-01 13:01:15.072 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG
2018-02-01 13:01:15.328 [vent.ItemStateChangedEvent] - AZKEY_LONG1 changed from ON to OFF
2018-02-01 13:01:15.331 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG
2018-02-01 13:01:15.594 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG
2018-02-01 13:01:15.859 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG
2018-02-01 13:01:16.102 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG
2018-02-01 13:01:16.372 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG
2018-02-01 13:01:16.693 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG
2018-02-01 13:01:16.703 [vent.ItemStateChangedEvent] - AZKEY_LONG_RELEASE1 changed from NULL to ON
2018-02-01 13:01:16.707 [vent.ChannelTriggeredEvent] - homematic:HG-HM-PB-2-WM55:homegear:OEQ0486825:1#PRESS triggered LONG_RELEASE

ei_Gelb_Geek · February 1, 2018, 1:03pm

Yes that is a CCU or Device Firmware Bug …

HM-PBI-4-FM -> Fires @ release
HM-PB-2-FM -> Fires immediately after indicate Long Press

The Binding Developer can’t do anything … if there is no Event … then no Action from Binding

Pull this Issue to Eq3 Devs

I have no HM-PB-2-WM55… @job and @lopez1de are the Firmware of your HM-PB-2-WM55 the same ?

https://www.homematic-inside.de/hardware/firmware-versions

job · February 1, 2018, 1:49pm

I’m using 1.4.

lopez1de · February 1, 2018, 9:22pm

I have found the solution. I changed the connection from “gesichert” (secure) to “standard” which changes the behaviour to the desired one.

lopez1de · February 2, 2018, 5:19am

Now I get the same error messages as @job with my HM-PB-2-WM55 set to “no secure connection”.

ei_Gelb_Geek · February 2, 2018, 11:32am

This is very interesting…

The Cont Error must be fixed by the Homematic Binding Developer. Report on Github is available.