# Node-RED Docker Container BACnet Integration Issues: TypeError and Dashboard Glitches

**URL:** <https://discourse.nodered.org/t/node-red-docker-container-bacnet-integration-issues-typeerror-and-dashboard-glitches/89377>\
**Category:** Dashboard\
**Tags:** node-red-dashboard, docker\
**Created:** [9 July 2024 15:20 UTC](https://discourse.nodered.org/t/node-red-docker-container-bacnet-integration-issues-typeerror-and-dashboard-glitches/89377 "2024-07-09T15:20:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![evenrohancodes](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/evenrohancodes/32/92681_2.png) [@evenrohancodes](https://discourse.nodered.org/u/evenrohancodes)\
**Post date:** [9 July 2024 15:20 UTC](https://discourse.nodered.org/t/node-red-docker-container-bacnet-integration-issues-typeerror-and-dashboard-glitches/89377/1 "2024-07-09T15:20:56Z")

</div>

![noderederror1](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/b/0b5a6713a8478fb1236fea8c47ebf1d5554994ca.jpeg)  
I've been encountering persistent errors with my Node-RED Docker container, specifically when trying to use BACnet protocol communication. Here are the commands I used to create the Docker container:

> `docker run -d -p 1880:1880 -p 502:502 -v node_red_data:/data --name FORGE nodered/node-red`

Initially, the Node-RED dashboard functions correctly, but over time it starts glitching. The logs show repeated errors related to the `node-bacnet-contrib-extended` module, indicating a `TypeError: Cannot read properties of undefined (reading 'values')`. This occurs in the `read-single-point.js` file and seems to be tied to a timeout issue in the `node-bacnet` client library.

Below are the relevant log entries:

```auto
2024-07-08 21:20:23 exception -> TypeError: Cannot read properties of undefined (reading 'values')
2024-07-08 21:20:23 at /data/node_modules/node-bacnet-contrib-extended/read-single-point.js:203:52
2024-07-08 21:20:23 at /data/node_modules/node-bacnet/lib/client.js:778:21
2024-07-08 21:20:23 at Timeout._onTimeout (/data/node_modules/node-bacnet/lib/client.js:158:7)
2024-07-08 21:20:23 at listOnTimeout (node:internal/timers:573:17)
2024-07-08 21:20:23 at process.processTimers (node:internal/timers:514:7)
2024-07-08 21:20:23 value: undefined
2024-07-08 21:20:23 err: Error: ERR_TIMEOUT
2024-07-08 21:20:23 at Timeout._onTimeout (/data/node_modules/node-bacnet/lib/client.js:158:16)
2024-07-08 21:20:23 at listOnTimeout (node:internal/timers:573:17)
2024-07-08 21:20:23 at process.processTimers (node:internal/timers:514:7)

```

 ![noderederror](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/6/f6b991696d1f796000007a52a66399c736527aba.jpeg)

I'd appreciate any guidance on how to resolve this issue or improve the stability of the Node-RED dashboard for production in large volume purposes. Thanks in advance for your help!

---

<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 2024 08:15 UTC](https://discourse.nodered.org/t/node-red-docker-container-bacnet-integration-issues-typeerror-and-dashboard-glitches/89377/2 "2024-07-17T08:15:18Z")

</div>

@evenrohancodes I wouldn't advise using node-bacnet-contrib-extended in a production environment thought it's the best BACnet node for node-RED it's not in my view production grade.  
Nor is it BACnet approved against a Device Profile or have vendor ID so some customers may not allow the device onto their OT network

---

<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 August 2024 08:16 UTC](https://discourse.nodered.org/t/node-red-docker-container-bacnet-integration-issues-typeerror-and-dashboard-glitches/89377/3 "2024-08-16T08:16:13Z")

</div>

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