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

Commandable Objects #56

Open
kheldaroz402 opened this issue Aug 30, 2024 · 2 comments
Open

Commandable Objects #56

kheldaroz402 opened this issue Aug 30, 2024 · 2 comments

Comments

@kheldaroz402
Copy link

Hi Joel,

I've started converting my code to bacpypes3.

In bacpypes we had commandable objects - do they exist in bacpypes3 or is it done differently?

eg

from bacpypes.local.object import (
    AnalogValueCmdObject,
    AnalogOutputCmdObject,
    BinaryOutputCmdObject,
    BinaryValueCmdObject,
    DateValueCmdObject,
    MultiStateValueCmdObject,
    MultiStateOutputCmdObject

)
@bbartling
Copy link

bbartling commented Aug 30, 2024 via email

@JoelBender
Copy link
Owner

Look in the bacpypes3.local... modules which are intended for servers/gateways:

from bacpypes3.local.binary import BinaryValueObjectCmd
from bacpypes3.local.analog import AnalogValueObjectCmd

Note that BinaryOutputObject and AnalogOutputObject are always Commandable and there are other variants as well, like intrinsic reporting and fault detection. There are lots of places for improvements, especially considering the overlap of different kinds of functionality and side effects (by which I mean changes in one property imply changes to other properties).

All of these things are going to need tests as outlined by ASHRAE 135.1.

p.s.- I didn't realize I swapped the Object and Cmd part. Humph.

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