I have an “Advanced Flow” that more or less just logs to Simple SysLog when the door event is triggering. And also a simple flow that just sends notification to my phone when the door is Unlocked.
The HomeyScript in this image is just to manipulate the result out so I can map source + id to write a cleaner notification result to send out.
The issue I have is that this rarely triggers, it does happen but it is like 20-25% of the time. Not even the syslog has anything about an event ever occurred.
I also for now have a regular and simpler flow to test it all out. And this has about a 90-95% success rate.
My Lock is a Nimly Touch Pro and I have a Zigbee router ~1 to 1,5meter away from the lock. The Zigbee router is a Sonoff S60ZB Smartplug so it is on the floor but clear from any obstacle. And on the second floor, straight above the door, I have a Sonoff Zigbee 3.0 USB Dongle Plus (Flashed to be a router). So the coverage should be good.
How come that the Advanced flow is failing so much compared to the simpler flow?
Anyone have any hints on what might be wrong or how to fix?
What happens if you replace the ‘doorlock event’-trigger by two triggers: ‘door lockeg’/‘door unlocked”?
The difference between simple and advanced flow is extremely unlikely to have anything to do with it. I’d recommend some more thorough testing, comparing the performance of the different trigger cards available for your lock. The two flows you show use two different trigger cards which almost certainly is the cause of the difference.
That is what my simple flow does. The Lock and Unlock trigger cards do not send out the id and the source of the event. That is something I need to be able to se that the door was opened using Tag and the Tag id was 2. I can then use HomeyScript to write a result “Mom opened door with tag” etc.
Yeah you are probably right about that. When zoneing out and thinking about it, it must be the Trigger card that is the cause.
I’d recommend some more thorough testing, comparing the performance of the different trigger cards available for your lock.
I have been looking for some way to debug this much deeper. But I fail to figure out how. You have any idea on how to do this?
What would be awesome was if I somehow can see what Homey is doing in the background and see if they get this trigger card information. Maybe this is something that has to be done in the Nimly App?
The syslog app and/or mobile alerts is the way to do it. I’d just set up an advanced flow with each of the different available trigger cards for your lock sending you a notification (different one for each trigger card) when it triggers. No other cards or logic in between, just for testing. Then try the different actions on your lock a bunch of times each and see which triggers fire and how reliably. That will help narrow down whether there’s an issue with the triggers and if so, which ones.
Ah ok. Thank you. That is exactly what I have today. Will have to let it run for a few days to test! Thanks
Maybe the three parameters (Reason, Source and ID) are not available in all cases, causing an error in the subsequent flowcards that use them, which stops the flow from executing.
Yeah I have added this now for extensive logging;
Will have to let it run for a day and two to collect some data.
Just got an notification that my alarm was turned off, but there is no notification about the door being unlocked.. But I got the lock event.
And checking the timeline also tells me that there is no unlock OR a lock even, but the flow logged that there was a lock event..
While typing this I got the unlock events from my Son and it was put in the locks timeline, as notification on my phone and in the log.
This is getting frustrating now since I do not think I am able to debug this anymore. And I am not sure where the issue is. Is it on Homeys end? Is it at Nimlys end?
edit:
I am sure I am on the latest version of the Connector Module; “zb_sw_build_id”: “4.8.02” and the version in nimlys guid on how to update the FW on the module is 4.8.01.
