Skip to content
Discussion options

You must be logged in to vote

Dealing with Proprietary objects in BAC0 (in fact, with BACpypes3) requires some work. The library needs to know in advance, what kind of "type" the property is.

Some guess work can be done when reading... but to write to those properties, you got to be certain.

For now, the way I understood BACpypes3, I haven't looked too deep in the "guess the type path" and I adopted the explicit way of defining proprietary objects and properties. This way, we can safely read and write those.

For your convenience, I added one attempt to define the proprietary objects for priva blue contollers here :
https://github.com/ChristianTremblay/BAC0/blob/develop/BAC0/core/proprietary_objects/privablue_105.py

He…

Replies: 3 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Answer selected by hvdort
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@ChristianTremblay
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants