I'm connecting to data using the SkySpark BACnet connector. I need to use a few AV/BV objects as sensors or commands within fault rules, although they are not actually BACnet inputs or outputs.
What is the recommended way to tag these points? Does it make most sense to tag them with "sensor"/"cmd" even though they are not inputs/outputs or is it better to use some other naming category?
For example, I've created "pseudoSensor" and "pseudoCmd" tags for these AV/BV points that I need for rules, to distinguish them from proper inputs/outputs, but wondered if it makes more sense to just call them sensor/cmd, or if there's another solution I'm not seeing.
for reference on this same topic: https://www.project-haystack.org/forum/topic/131
Holly Amerson Tue 12 Aug
I'm connecting to data using the SkySpark BACnet connector. I need to use a few AV/BV objects as sensors or commands within fault rules, although they are not actually BACnet inputs or outputs.
What is the recommended way to tag these points? Does it make most sense to tag them with "sensor"/"cmd" even though they are not inputs/outputs or is it better to use some other naming category?
For example, I've created "pseudoSensor" and "pseudoCmd" tags for these AV/BV points that I need for rules, to distinguish them from proper inputs/outputs, but wondered if it makes more sense to just call them sensor/cmd, or if there's another solution I'm not seeing.
for reference on this same topic: https://www.project-haystack.org/forum/topic/131