I've posted about weird goings on several times where devices have triggered apparently without command - no rule, no physical event, no reason. I've been putting the culprit down to the Homekit (eternal) Beta as the 'produced by' column is empty in the device events (and maker api always shows if that's the source whereas as Homekit does not populate the column EVER)
I just noticed the Garage Door was open and we did not command it to open. I only noticed as I have a notification rule that triggers a message on a dashboard tile if it's open for 10 minutes.
So this time (for the first time) when I check the events, 'Produced By' shows 'maker api - node red' as the source of the open command as well as the close:
1 - 'maker api - node red' should not be able to open the garage door as I've explicitly not allowed it - the device is and always has been unchecked for that instance:
2 - I closed the door myself using a dashboard, which uses a completely separate instance of maker api named - 'maker api - HD+'
We didn't accidentally open the door on the dashboard as I was half asleep after a few pints of particularly strong Sam Smith's lager, my wife was nowhere near and it needs a PIN number after clicking the tile.
Apologies for the delayed response - I'm in the UK
Aww bollocks....Garage Roller Door is a different device (a virtual contact connected to my alarm system using mqtt). I've grabbed the events from the wrong device - the contact that is on the door that opened. I'm feeling a little stupid now
As above - my bad for grabbing the events from the wrong device. Apologies
It's still unknown however what caused the door to open on its own. There are no rules that can open the door and I've gone as far as adding a relay to my alarm system that breaks the power to the line open connection when the system is set. I'm back to blaming the Homekit Beta. It's feasible that a HomePod heard something from the TV that sounded like 'Hey Siri, open the Garage Door' The correct events are shown below:
The 'produced by' is empty so I don't whether it was Homekit or not. I'm sure that 'produced by' never identifies the Homekit Beta when it is the trigger. That stops me identifying the cause.
The only other thing I've not checked, is what is logged when I open the door using the switch which is connected to the 'Garage Door' module (Fibaro Roller Shutter 3). If operating that switch populates the events table with an identical entry to above, it's possible that the switch itself could be at fault.
I'll do an open and close from Homekit, followed by an open and close from the switch to see how they're logged and report back.
That proves it wasn't the switch and with no rules set up that can open the door (Maker API - HD+ can open it but 'produced by' always identifies that when used):
It can only be Homekit that opened the door even if there's nothing indicated. Hubitat doesn't show it in 'produced by' and unlike Amazons Alexa, Apple don't provide a means to check history. Diagnosis by crystal ball perhaps...
I have had a similar issue recently with 2 z-wave Kwikset locks. The first time it happened, I thought it must be a fluke but it happened again (2 days ago) to a different lock. There are 3 family members who have access via Apple Home and none of them triggered the open command (I checked as soon as I heard the door unlock). No one has access to Hubitat UI and I don't use the HE dashboard. The description in the logs is "Front Lock was unlocked via command [digital][6:4]".
I have a similar configuration but I use Homebridge and not the built in Homekit app. All my "rules" are in Node-RED too. I write all events and logs to a database via Node-RED so I was able to check when it happened. I have now set up an alert when any of the doors are unlocked and the "type" is "digital" as that command could only have come via Homekit or Hubitat UI (I do not have any flows in Node-RED that will unlock any doors). Unfortunately, I don't think this will work for a Garage Door device but like you, I have an alert if the door is open for a certain duration.
I tried to use the HomeLog for HomeKit app to see if it would be useful in figuring out if the "unlock" originated in Homekit but that information was not available.
Could be something other than the hub. Your logs are confusing, and I don't know where the command is shown that corresponds to it being opened. Is there one? At what time?
At one point in time I had my garage door controlled by a Z-Wave relay. It opened uncommanded more than once. There was nothing to account for it in the hub. After the second time, I stopped using that device and went in a different direction. I'm not a big fan of automating garage doors. For one thing, closing them remotely is hazardous, and if not remote, then it doesn't really need to be automated at all.
I have used it on multiple occasions to let people into the house when I am not at home. The front door (automated lock) has a manual deadbolt that we use at night. If I forget to unlock that, there is no way into the house for others who have access only to that lock. With the remote garage door, I can open that and unlock the backdoor.
I appreciate that. Here I'm using the Fibaro Roller Shutter 3 z wave module, connected to the tubular motor of the roller type door, so to Homekit it's seen as a shade rather than a 'garage door'. Things are not so heavy duty in the UK - I'd happily stand beneath it as it would fall to bits before doing any harm lol.
Having the garage door connected to HE is a convenience. We don't use radio fobs with it and the only switch is in the garage. The connection to HE enables us to use a dashboard tile (which is PIN protected to prevent accidental use). I have it on the Homekit app so that when I arrive home on my motorbike, I can open the door using 'Hey Siri' from my helmet headset (connection to the alarm ensures I cannot open it until disarmed)
As stated although it's a garage door, it's connected to a shade controller as are all of the curtains in the house. Never have they opened/closed unexpectedly with no apparent command....
With no "Produced By" entry, and the source being DEVICE, I'd take that at face value. If it were an app, it would show the app in Produced By. This is exactly how my Z-Wave relay looked when my garage door opened -- a command with no obvious cause. Disconcerting.
Only one of my Z-Wave relays, of which I had four in service, ever did this. I don't use those anymore. I have seen Z-Wave dimmers come on un-commanded as well from time to time, certainly rarely. I have no idea what could cause this. Evidently, the device was commanded, but not by the hub.
Thanks for this pointer. I went back and looked at my mysterious "unlock" from a few days ago and indeed it was unlocked by MakerAPI (Homebridge instance). So either someone in my family inadvertently hit unlock on the Apple Home app or they don't want to fess up to it
@Bravenel That's one point that I'm making. See below that I posted earlier today. This is the result of opening the door with Homekit. Homekit does not populate the 'produced by' column. It should but it doesn't...
That's the case for all devices - Homekit is not identified when used. I just turned on the Dining Room light with Homekit - here is the event - no reference to the Homekit app:
Do any of the actions taken in Apple Home (other than by the Garage Door) have the app in the "Produced by"? I use MakerAPI/Homebridge and it always shows the name of the MakerAPI instance that is connected to Homebridge.
No. As mentioned I've commented on this a few times and tagged Victor but didn't get a response. Anything using maker API (inc Homebridge when I was using it) populates the "produced by" column. Any device, when turned on/off by Homekit beta leaves it empty.
In this scenario it would only prove that Homekit opened the door but not why. Only Apple have access to the Homekit history. "Produced by" should list Homekit beta though when it's the source, but it doesn't
HomeKit integration does not currently populate the Produced By field. We will address that... So it is one possibility that someone used HomeKit to open the door.
