# Node-red bacnet

**URL:** <https://discourse.nodered.org/t/node-red-bacnet/30155>\
**Category:** Industrial\
**Created:** [15 July 2020 23:08 UTC](https://discourse.nodered.org/t/node-red-bacnet/30155 "2020-07-15T23:08:04Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![mellis](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mellis/32/27014_2.png) [@mellis](https://discourse.nodered.org/u/mellis)\
**Post date:** [15 July 2020 23:08 UTC](https://discourse.nodered.org/t/node-red-bacnet/30155/1 "2020-07-15T23:08:04Z")

</div>

I just found the node-red-contrib-bacnet and am testing it with a BACnet IP device. It works extremely well! 0.2.4.  
just a few questions:

- Is there any way to make the BACnet-read-node payload output on a BACnet COV instead of poll on an inject? I'd like the flow to react as soon as the value changes. BACnet provides for a COV subscription. What I don't know is if a BACnet read node can be subscribed to that way and if it can if it's payload can be triggered on a COV update.
- I'm not sure if I understand the use of the "client" address under "device and Interface" or just "Device" on the command node. I can put anything in there and it doesn't seem to make a difference.

Again We are exceeding impressed with node red and coming from the building automation world (professionally) can see a lot of potential use cases. BACnet is a common protocol in commercial building automation systems.

Thank you in advance.

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [16 July 2020 03:29 UTC](https://discourse.nodered.org/t/node-red-bacnet/30155/2 "2020-07-16T03:29:07Z")

</div>

Maybe these type of Q's would be best to address at the origin with the author, it seems also a node for monitoring the value using COV is on the issue list

> <https://github.com/BiancoRoyal/node-red-contrib-bacnet/issues/19>
>
> Feature
> (X) feature request
> What is the motivation / use case for changing the behavior?
>  
> COV is supported by the node-bacnet library and...

---

<div class="post-metadata">

**Author:** ![mtoko](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mtoko/32/138_2.png) [@mtoko](https://discourse.nodered.org/u/mtoko)\
**Post date:** [16 July 2020 08:50 UTC](https://discourse.nodered.org/t/node-red-bacnet/30155/3 "2020-07-16T08:50:08Z")

</div>

If you search the forum about bacnet there is a few interesting posts. I have sent a private message with some details

---

<div class="post-metadata">

**Author:** ![iiLaw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/iilaw/32/14782_2.png) [@iiLaw](https://discourse.nodered.org/u/iiLaw)\
**Post date:** [16 July 2020 15:14 UTC](https://discourse.nodered.org/t/node-red-bacnet/30155/4 "2020-07-16T15:14:17Z")

</div>

COV not supported in Node-RED but is in underlying BACnet library. Also it isn't an Ashrae approved so fine for your own use but you might have issues trying to deploy in a commercial BMS/Automation network.

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [16 July 2020 18:24 UTC](https://discourse.nodered.org/t/node-red-bacnet/30155/5 "2020-07-16T18:24:17Z")

</div>

> [@iiLaw](#):
>
> Also it isn't an Ashrae approved

That would be a strong decision point to consider - not doing it - wait until it gets accepted and standardized. Otherwise I guess you could get into trouble in respect to interoperability

---

<div class="post-metadata">

**Author:** ![iiLaw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/iilaw/32/14782_2.png) [@iiLaw](https://discourse.nodered.org/u/iiLaw)\
**Post date:** [17 July 2020 14:30 UTC](https://discourse.nodered.org/t/node-red-bacnet/30155/6 "2020-07-17T14:30:00Z")

</div>

Don't think it's Klaus intent to get it certified

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [17 July 2020 14:40 UTC](https://discourse.nodered.org/t/node-red-bacnet/30155/7 "2020-07-17T14:40:01Z")

</div>

OK, I just thought, if it is a good idea, he could propose it to someone who is member in the BACnet steering committé or so or to someone in one of the work groups working with standardization. (I worked with Siemens before and I know one person in Building Automation that does these things)

But can you high lite what is so good with COV that is not provided by the current BACnet stack itself?

---

<div class="post-metadata">

**Author:** ![iiLaw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/iilaw/32/14782_2.png) [@iiLaw](https://discourse.nodered.org/u/iiLaw)\
**Post date:** [18 July 2020 17:31 UTC](https://discourse.nodered.org/t/node-red-bacnet/30155/8 "2020-07-18T17:31:14Z")

</div>

COV is in the underlying library node-bacnet just not surfaced in node-red Node

I believe the correct way is for the node-bacnet to be approved to a given PIC for example: BACnet Application Specific Controller (B-ASC)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [16 September 2020 17:31 UTC](https://discourse.nodered.org/t/node-red-bacnet/30155/9 "2020-09-16T17:31:30Z")

</div>

Closed on 16 September 2020 17:31 UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.