Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reader tamper state #105

Closed
s3r4fin opened this issue Mar 1, 2023 · 5 comments
Closed

reader tamper state #105

s3r4fin opened this issue Mar 1, 2023 · 5 comments

Comments

@s3r4fin
Copy link

s3r4fin commented Mar 1, 2023

The requirement is get current state of tamper and receive event when tamper state changes.

Related LSTAT command & LSTAT response seems dropped on libosdp library.

@sidcha sidcha closed this as completed in 426525f Mar 4, 2023
@sidcha
Copy link
Member

sidcha commented Mar 4, 2023

@s3r4fin local status reports (CMD_LSTAT, REPLY_LSTATR) are now supported using the PD events API. Look for OSDP_EVENT_STATUS.

@s3r4fin
Copy link
Author

s3r4fin commented Mar 6, 2023

Thank you so much! Event works fine!
Can CP ask for tamper status on start?

sidcha added a commit that referenced this issue Mar 6, 2023
CP may want to ask for local status explicitly in addition to the
async reports from the PD. Add OSDP_CMD_STATUS command to just that.

Related-to: #105
Signed-off-by: Siddharth Chandrasekaran <[email protected]>
@sidcha
Copy link
Member

sidcha commented Mar 6, 2023

Can CP ask for tamper status on start?

Didn't think of that use case. Now it can with OSDP_CMD_STATUS :).

@s3r4fin
Copy link
Author

s3r4fin commented Mar 15, 2023

Thank you! It works

@Stuckya
Copy link
Contributor

Stuckya commented May 19, 2023

Popping this back onto the radar. This doesn't appear to be working with the Python bindings.

I've opened a PR to address the issue here: #116

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants