Non HA-Supervised Docker Container

[kneath]

I run Home Assistant with Docker, which means I can't install any add-ons since they require HAOS to run. Is there a chance we could get a regular docker container of BACnet/IP interface for those of us who have a non-managed install? Or maybe just some instructions for how to do that?

Thanks!

[GravySeal]

Hey kneath!

I do believe it's possible to run add-ons as separate containers right?
If you tried it, could you perhaps share some logs with me so I can see where it goes wrong?

If that doesn't work, it's possible to set up a container containing Python together with the required libraries.
Then it could run the main.py file to basically have the same functionality as the add-on.

[kneath]

Thanks! So far I've got it almost running. Bear with me because I'm hardly an expert at Docker and this is my first foray into bacnet, so I may be conflating some problems.

I'm using this docker-compose right now:

bacnetinterface:
    image: bacnetinterface:customv1
    build:
      context: ./bacnetinterface
      dockerfile: Dockerfile
      args:
        BUILD_FROM: ghcr.io/hassio-addons/base-python:13.1.2
    restart: unless-stopped
    logging:
      options:
        max-size: "50M"
        max-file: "2"
    volumes:
      - ./bacnetinterface-data:/data
    ports:
      - "80:81"
      - "8099:8099"

And I needed to create an options.json file in that data folder:

{
    "subscriptions": {
        "analogInput": true,
        "analogOutput": true,
        "analogValue": true,
        "binaryInput": true,
        "binaryOutput": true,
        "binaryValue": true,
        "multiStateInput": true,
        "multiStateOutput": true,
        "multiStateValue": true
    }
}

Where I'm stuck right now is it's having trouble getting the address (I think) from bacpypes:

bacnetinterface-1  | s6-rc: info: service init-nginx successfully started
bacnetinterface-1  | [BACpypes]
bacnetinterface-1  | objectName: null
bacnetinterface-1  | address: null/24
bacnetinterface-1  | objectIdentifier: null
bacnetinterface-1  | maxApduLengthAccepted: 1476
bacnetinterface-1  | segmentation: segmentedBoth
bacnetinterface-1  | vendorIdentifier: 15
bacnetinterface-1  | foreignBBMD: -
bacnetinterface-1  | foreignTTL: 255
bacnetinterface-1  | maxSegmentsAccepted: 64
bacnetinterface-1  | loglevel: null
bacnetinterface-1  | defaultPriority: null
bacnetinterface-1  | s6-rc: info: service init-interface successfully started
bacnetinterface-1  | s6-rc: info: service interface: starting
bacnetinterface-1  | s6-rc: info: service interface successfully started
bacnetinterface-1  | s6-rc: info: service nginx: starting
bacnetinterface-1  | s6-rc: info: service nginx successfully started
bacnetinterface-1  | s6-rc: info: service legacy-services: starting
bacnetinterface-1  | [21:07:47] INFO: Running interface
bacnetinterface-1  | s6-rc: info: service legacy-services successfully started
bacnetinterface-1  | Traceback (most recent call last):
bacnetinterface-1  |   File "/usr/bin/main.py", line 407, in <module>
bacnetinterface-1  |     asyncio.run(main())
bacnetinterface-1  |   File "/usr/local/lib/python3.12/asyncio/runners.py", line 194, in run
bacnetinterface-1  |     return runner.run(main)
bacnetinterface-1  |            ^^^^^^^^^^^^^^^^
bacnetinterface-1  |   File "/usr/local/lib/python3.12/asyncio/runners.py", line 118, in run
bacnetinterface-1  |     return self._loop.run_until_complete(task)
bacnetinterface-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
bacnetinterface-1  |   File "/usr/local/lib/python3.12/asyncio/base_events.py", line 685, in run_until_complete
bacnetinterface-1  |     return future.result()
bacnetinterface-1  |            ^^^^^^^^^^^^^^^
bacnetinterface-1  |   File "/usr/bin/main.py", line 285, in main
bacnetinterface-1  |     ) = get_configuration()
bacnetinterface-1  |         ^^^^^^^^^^^^^^^^^^^
bacnetinterface-1  |   File "/usr/bin/main.py", line 223, in get_configuration
bacnetinterface-1  |     ipv4_address = IPv4Address(ipv4_address)
bacnetinterface-1  |                    ^^^^^^^^^^^^^^^^^^^^^^^^^
bacnetinterface-1  |   File "/usr/local/lib/python3.12/site-packages/bacpypes3/pdu.py", line 136, in __call__
bacnetinterface-1  |     return cast(Address, type.__call__(cls, *args, **kwargs))
bacnetinterface-1  |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
bacnetinterface-1  |   File "/usr/local/lib/python3.12/site-packages/bacpypes3/pdu.py", line 1187, in __init__
bacnetinterface-1  |     raise ValueError("invalid address")
bacnetinterface-1  | ValueError: invalid address
bacnetinterface-1  | [21:07:48] INFO: Service BACnet Interface exited with code 1 (by signal 0)
bacnetinterface-1  | s6-rc: info: service legacy-services: stopping
bacnetinterface-1  | s6-rc: info: service legacy-services successfully stopped
bacnetinterface-1  | s6-rc: info: service nginx: stopping
bacnetinterface-1  | [21:07:48] INFO: Service NGINX exited with code 256 (by signal 15)

[GravySeal]

Great!
Seems like you got pretty far already.
What's still missing is /usr/bin/BACpypes.ini.
This gets generated in the add-on through supervisor API calls.
To get most things working as a standalone program, it'd be better if I made everything relying on just /data/options.json.
I'll make an attempt at this sometime this weekend.

[GravySeal]

Did you attempt making an options.json file with all configuration keys you need yet? It should be possible in v1.5.0

[kneath]

Thank you, and yes (ish)! Adding address to options.json got everything running. BACpypes logging still says it's looking for address: null/24 — is that correct? I still need to hook this into my bacnet network, which is a whole other can of worms of my own making.

bacnetinterface-1  | s6-rc: info: service s6rc-oneshot-runner: starting
bacnetinterface-1  | s6-rc: info: service s6rc-oneshot-runner successfully started
bacnetinterface-1  | s6-rc: info: service base-addon-banner: starting
bacnetinterface-1  | curl: (6) Could not resolve host: supervisor
bacnetinterface-1  | [17:47:08] ERROR: Something went wrong contacting the API
bacnetinterface-1  | s6-rc: info: service base-addon-banner successfully started
bacnetinterface-1  | s6-rc: info: service fix-attrs: starting
bacnetinterface-1  | s6-rc: info: service base-addon-log-level: starting
bacnetinterface-1  | s6-rc: info: service fix-attrs successfully started
bacnetinterface-1  | curl: (6) Could not resolve host: supervisor
bacnetinterface-1  | [17:47:08] ERROR: Something went wrong contacting the API
bacnetinterface-1  | s6-rc: info: service base-addon-log-level successfully started
bacnetinterface-1  | s6-rc: info: service legacy-cont-init: starting
bacnetinterface-1  | s6-rc: info: service legacy-cont-init successfully started
bacnetinterface-1  | s6-rc: info: service init-nginx: starting
bacnetinterface-1  | s6-rc: info: service init-interface: starting
bacnetinterface-1  | [17:47:08] INFO: Running init-interface.
bacnetinterface-1  | [17:47:08] INFO: Running init-nginx.
bacnetinterface-1  | [17:47:08] INFO: Allowed addresses for NGINX: 127.0.0.1 172.20.0.3 192.168.0.89
bacnetinterface-1  | curl: (6) Could not resolve host: supervisor
bacnetinterface-1  | [17:47:08] ERROR: Something went wrong contacting the API
bacnetinterface-1  | [17:47:08] INFO: Generated ingress configuration successfully!
bacnetinterface-1  | s6-rc: info: service init-nginx successfully started
bacnetinterface-1  | [BACpypes]
bacnetinterface-1  | objectName: null
bacnetinterface-1  | address: null/24
bacnetinterface-1  | objectIdentifier: null
bacnetinterface-1  | maxApduLengthAccepted: 1476
bacnetinterface-1  | segmentation: segmentedBoth
bacnetinterface-1  | vendorIdentifier: 15
bacnetinterface-1  | foreignBBMD: -
bacnetinterface-1  | foreignTTL: 255
bacnetinterface-1  | maxSegmentsAccepted: 64
bacnetinterface-1  | loglevel: null
bacnetinterface-1  | defaultPriority: null
bacnetinterface-1  | s6-rc: info: service init-interface successfully started
bacnetinterface-1  | s6-rc: info: service interface: starting
bacnetinterface-1  | s6-rc: info: service interface successfully started
bacnetinterface-1  | s6-rc: info: service nginx: starting
bacnetinterface-1  | s6-rc: info: service nginx successfully started
bacnetinterface-1  | s6-rc: info: service legacy-services: starting
bacnetinterface-1  | [17:47:08] INFO: Running interface
bacnetinterface-1  | s6-rc: info: service legacy-services successfully started
bacnetinterface-1  | [17:47:09]|INFO     |server.py         ->_serve                              : Started server process [254]
bacnetinterface-1  | [17:47:09]|INFO     |on.py             ->startup                             : Waiting for application startup.
bacnetinterface-1  | [17:47:14]|INFO     |on.py             ->startup                             : Application startup complete.
bacnetinterface-1  | [17:47:14]|INFO     |server.py         ->_log_started_message                : Uvicorn running on http://127.0.0.1:7813 (Press CTRL+C to quit)
bacnetinterface-1  | [17:47:14]|WARNING  |h11_impl.py       ->handle_events                       : Invalid HTTP request received.
bacnetinterface-1  | [17:47:14] INFO: Running NGINX
bacnetinterface-1  | 2024/08/18 17:47:14 [notice] 262#262: using the "epoll" event method
bacnetinterface-1  | 2024/08/18 17:47:14 [notice] 262#262: nginx/1.24.0
bacnetinterface-1  | 2024/08/18 17:47:14 [notice] 262#262: OS: Linux 5.15.0-107-generic
bacnetinterface-1  | 2024/08/18 17:47:14 [notice] 262#262: getrlimit(RLIMIT_NOFILE): 1048576:1048576
bacnetinterface-1  | 2024/08/18 17:47:14 [notice] 262#262: start worker processes
bacnetinterface-1  | 2024/08/18 17:47:14 [notice] 262#262: start worker process 308
bacnetinterface-1  | [17:47:40]|INFO     |h11_impl.py       ->send                                : 192.168.0.89:0 - "GET / HTTP/1.0" 404

[GravySeal]

The [BACpypes] section looks at the .ini that's generated through Supervisor API calls, but since that's been replaced with options.json it should be fine. If it failed to get an address, the application would quit immediately.
I think it's time to see what happens when you connect your BACnet network.

[kneath]

Okay, apologies for the long delay… I've had a fun journey with my HVAC installer and finally have the networking in a good place.

Here's where I'm at: I think I have all the config right, but I can't see any devices.

This is after clicking read all devices. This is my config.json:

{
    "subscriptions": {
        "analogInput": true,
        "analogOutput": true,
        "analogValue": true,
        "binaryInput": true,
        "binaryOutput": true,
        "binaryValue": true,
        "multiStateInput": true,
        "multiStateOutput": true,
        "multiStateValue": true
    },
    "address": "192.168.0.42/24"
}

I have tried many variations of address with/without subnet identifier, including 192.168.0.42 (the bacnet device) and 192.168.0.227 (the server) to no avail.

I am now at least certain the devices are available on the network. I can see them from BDT from another computer:

The server output is the same as above. Any idea how to further debug?

[Bepacom-Raalte]

In Home Assistant, the add-on runs on the host network. You could try the physical IP address of the port that's connected to the BACnet/IP network. Perhaps you have to open port 47808 UDP as well, as this is the port BACnet/IP uses.
If you're using the most recent version of the add-on, the entire config could be as follows:

{
  "objectName": "EcoPanel",
  "address": "192.168.0.227/24",
  "objectIdentifier": 420,
  "defaultPriority": 15,
  "devices_setup": [
    {
      "deviceID": "all",
      "CoV_lifetime": 60,
      "CoV_list": [
        "all"
      ],
      "quick_poll_rate": 5,
      "quick_poll_list": [],
      "slow_poll_rate": 600,
      "slow_poll_list": [
        "all"
      ],
      "resub_on_iam": true,
      "reread_on_iam": false
    }
  ],
  "entity_list": [
    "sensor.incomfort_cv_pressure",
    "input_boolean.cooltoggle",
    "input_number.coolnumber"
  ],
  "api_accessible": true,
  "loglevel": "DEBUG",
  "segmentation": "segmentedBoth",
  "vendorID": 15,
  "maxApduLenghtAccepted": 480,
  "maxSegmentsAccepted": 64
}

Please share the logs of the add-on, maybe we could find some useful information there.

[kneath]

Ah of course — I didn't even think about opening up the bacnet port. Putting it on host networking got things working!

[Bepacom-Raalte]

Great, glad to hear! Just let me know if there are any more issues.

[kneath]

All working good! The HA integration worked no problem.

I ended up removing the docker container from the host network, and it seems happy just exposing the tcp & udp ports:

    image: bacnetinterface:customv1.21
    build:
      context: ./bacnetinterface
      dockerfile: Dockerfile
      args:
        BUILD_FROM: ghcr.io/hassio-addons/base-python:13.1.2
    restart: unless-stopped
    logging:
      options:
        max-size: "50M"
        max-file: "2"
    volumes:
      - /home/kneath/pinesbot/bacnetinterface-data:/data
    ports:
      - "8099"
      - "47808/udp"

The only other quirk is I also modified init-nginx/run to include my laptop's IP so I could access the web ui. That was helpful for me in debugging this, and by default it's only accessible on localhost. I don't know if there's a way around that for others or not.

for address in $ip_addresses
do
    ip_address="${address%/*}"
    subnet_mask="${address#*/}"
    ip_array+=("$ip_address")
done
+ip_array+=("192.168.0.89")

[GravySeal]

In the options, there's a boolean key api_accessible that opens up the web ui to the world. In Home Assistant, it's not necessary as it's done through ingress. In this setup, it's a little more difficult.