|
From the wiki page here, the scan YAML includes a In my testing this always times out. Is this expected? - is this wait to catch some corner case? I must say I haven't quite understood its intent, but don't want to disturb it if it is necessary. My best guess is that in testing the value of the sensor isn't changing - hence timeout. But I'm concerned that the delay also introduces a race condition if more than one tag is scanned in succession. Anyone have any better knowledge? |
Replies: 1 comment
|
The nfc last scan by is the helper template setup to map the user unique id that comes in when the event is generated to a human readable name. The trigger timeout is in place to wait until that mapping occurs which should be milliseconds, but without it, you are likely to capture the name of the prior person that scanned. If you are seeing that timeout, it would suggest the template helper is not working correctly. Do you see the names getting updated in the sensor? |
The nfc last scan by is the helper template setup to map the user unique id that comes in when the event is generated to a human readable name.
The trigger timeout is in place to wait until that mapping occurs which should be milliseconds, but without it, you are likely to capture the name of the prior person that scanned. If you are seeing that timeout, it would suggest the template helper is not working correctly. Do you see the names getting updated in the sensor?