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

COV stop after a while #536

Open
kazemiprince opened this issue Oct 23, 2024 · 4 comments
Open

COV stop after a while #536

kazemiprince opened this issue Oct 23, 2024 · 4 comments

Comments

@kazemiprince
Copy link

I am testing COV(for analog input object) with Yabe and I see COV stop sending new values to Yabe and have to subscribe again to see new values.
sometimes it stop after 1-2 minutes and sometimes it stop sooner.

@JoelBender
Copy link
Owner

Subscriptions have a "lifetime" parameter, Clause 13.14.1.1.4, what is the value from Yabe? Do the notifications stop for different versions of the parameter?

@kazemiprince
Copy link
Author

its lifetime is 120 seconds.
notification stop randomly. I though it's because I run bacnet on another thread, but even if I run it on main , it stop again.
what I see is if I decrees the lifetime to 30 seconds, it will be much much better.

@skehd13
Copy link

skehd13 commented Nov 11, 2024

Checking the logs, it appears that self.algorithm.triggered = True is running late on line 55 of the service.Detect.py file. If we move that line to line 52, COV still appears to work.

Is this method correct?

@JoelBender
Copy link
Owner

Perhaps, that's not in the BACpypes code.

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