OH2 or Homematic OPENS DOOR by itself when i wasn't at home!

Hello

Yesterday something strange and also dangerous happened.

I use a 2 channel homematic switch to lock und unlock my door (1 channel for opening “AUF”, the second for closing “ZU”).

The STATE datapoints of the 2 homematic-channels (hm-device-id: HM-LC-Sw2-FM:ccu:NEQ095xxxx) are linked with ITEMS which have “phy” in their names (as you can see it within the log entries i provide later on…).

So yesterday i was out of my house at work and suddenly i received a TELEGRAM message that OH opens my door.
I also would receive telegrams for closing…thats normal because a rule triggers, when the ZU or the AUF item changes to ON.

Here the log of the event.
The strange part was at 2017-04-08 15:02:15.102
No one triggered that item (i am sure)!

2017-04-08 15:01:13.783 [ItemStateChangedEvent     ] - homematic_HM_ES_PMSw1_Pl_ccu_NEQ040xxxx_2_VOLTAGE changed from 240.10 to 240.50
2017-04-08 15:01:13.853 [ThingUpdatedEvent         ] - Thing 'homematic:HM-ES-PMSw1-Pl:ccu:NEQ040xxxx' has been updated.
2017-04-08 15:01:14.085 [ThingUpdatedEvent         ] - Thing 'homematic:HM-Sec-WDS-2:ccu:MEQ059xxxx' has been updated.
2017-04-08 15:01:14.249 [ThingUpdatedEvent         ] - Thing 'homematic:HM-Sec-SD-2-Team:ccu:T-NEQ061xxxx' has been updated.
2017-04-08 15:01:14.444 [ThingUpdatedEvent         ] - Thing 'homematic:HM-Sen-MDIR-O-2:ccu:NEQ032xxxx' has been updated.
2017-04-08 15:02:14.605 [hingStatusInfoChangedEvent] - 'homematic:HM-LC-Sw2-FM:ccu:NEQ095xxxx' changed from OFFLINE (COMMUNICATION_ERROR) to ONLINE
2017-04-08 15:02:14.626 [ItemStateChangedEvent     ] - homematic_HM_LC_Sw2_FM_ccu_NEQ095xxxx_0_LOWBAT changed from NULL to OFF
2017-04-08 15:02:14.651 [ItemStateChangedEvent     ] - homematic_HM_LC_Sw2_FM_ccu_NEQ095xxxx_0_RSSI_DEVICE changed from NULL to -72
2017-04-08 15:02:15.102 [ItemStateChangedEvent     ] - xxxxAuf_phy_state changed from OFF to ON
2017-04-08 15:02:15.104 [ItemStateChangedEvent     ] - homematic_HM_LC_Sw2_FM_ccu_NEQ095xxxx_1_STATE changed from NULL to ON
2017-04-08 15:02:15.838 [ItemStateChangedEvent     ] - homematic_HM_LC_Sw2_FM_ccu_NEQ095xxxx_2_STATE changed from NULL to OFF
2017-04-08 15:02:15.890 [ThingUpdatedEvent         ] - Thing 'homematic:HM-LC-Sw2-FM:ccu:NEQ095xxxx' has been updated.
2017-04-08 15:02:16.105 [ThingUpdatedEvent         ] - Thing 'homematic:HM-LC-Sw2-FM:ccu:NEQ095xxxx' has been updated.
2017-04-08 15:02:17.598 [ItemCommandEvent          ] - Item 'xxxxAuf_phy_state' received command OFF

Could it be that the ccu2 itself changed the state of the hm-switch and oh2 only recognized it within the telegram-rule?
It seems that the hm-device was offline before…thats sometimes but it never switches when getting online again in the past.
Or is oh2 the active part of that problem?
Hard to say but maybe some had experiences with hm-devices which switch without a command?

thx for you help and have a nice sunday!

That might be more interesting to see in the log, rather than the time of recovery.

That looks like an update to OH from HM, in amongst several others

Was the door really open, is it just misreporting?

Where did that come from? Do you have a rule that turns the switch OFF after a couple of seconds?

Hello rossko57 and thx for your help.

I hope you mean that log:

017-04-08 14:58:52.256 [WARN ] [ommunicator.parser.GetParamsetParser] - Can't set value for datapoint 'NEQ032xxxx:1#NEXT_TRANSMISSION'
2017-04-08 14:59:52.394 [INFO ] [ternal.communicator.HomematicGateway] - No event since 37646 seconds from gateway 'ccu', restarting RPC server
2017-04-08 15:00:02.664 [WARN ] [ommunicator.parser.GetParamsetParser] - Can't set value for datapoint 'NEQ032xxxx:1#NEXT_TRANSMISSION'
2017-04-08 15:00:16.789 [WARN ] [eather.internal.bus.WeatherPublisher] - Weather forecast day 5 not available for locationId 'xxx_owm', only 4 available
2017-04-08 15:00:16.791 [WARN ] [eather.internal.bus.WeatherPublisher] - Weather forecast day 5 not available for locationId 'xxx_owm', only 4 available
2017-04-08 15:00:16.812 [WARN ] [eather.internal.bus.WeatherPublisher] - Weather forecast day 5 not available for locationId 'xxx_owm', only 4 available
2017-04-08 15:00:16.822 [WARN ] [eather.internal.bus.WeatherPublisher] - Weather forecast day 5 not available for locationId 'xxx_owm', only 4 available
2017-04-08 15:00:16.833 [WARN ] [eather.internal.bus.WeatherPublisher] - Weather forecast day 5 not available for locationId 'xxx_owm', only 4 available
2017-04-08 15:01:02.802 [INFO ] [ternal.communicator.HomematicGateway] - No event since 37717 seconds from gateway 'ccu', restarting RPC server
2017-04-08 15:01:14.305 [WARN ] [ommunicator.parser.GetParamsetParser] - Can't set value for datapoint 'NEQ032xxxx:1#NEXT_TRANSMISSION'
2017-04-08 15:02:14.443 [INFO ] [ternal.communicator.HomematicGateway] - No event since 37788 seconds from gateway 'ccu', restarting RPC server
2017-04-08 15:02:26.818 [WARN ] [ommunicator.parser.GetParamsetParser] - Can't set value for datapoint 'NEQ032xxxx:1#NEXT_TRANSMISSION'
2017-04-08 15:03:26.966 [INFO ] [ternal.communicator.HomematicGateway] - No event since 37861 seconds from gateway 'ccu', restarting RPC server

Unfortunately i sent a close-command when i read the “open”-telegram at 18:30. I came back home at 20:00 and then it was closed of course.

Thats right. When this item turns ON at first i get a telegram and 2s later it turns off again. thats so because my door-lock-drive just needs short impulses and not a stable signal for opening and closing.

I would try to fix the Homematic comms issue, but I cannot help with that.
Maybe relevant -