I can’t say for certain if it’ll work immediately, but if it doesn’t we can always make it work together.
If the Daikin unit transforms each AC into a separate BACnet device, I don’t see much of an issue. The add-on should work with multiple devices in the network.
Hi Bagunda !
What version of HA have you used ? I can’t start the addon…
Do you know what can be the issue ?
Thanks!
I ended up buying the unit and have got it connected.
It seems that everything is shown up mixed into the one BACNET device, then I need to decifer which entities go to which AC.
At the add-on level the data is reading ok, but so far not through the integration so need to figure that out
Has anyone else had their Bacnet devices stop responding after the recent updates?
I just deleted, wiped and started again with the latest files fresh after I found it had stopped communicating… Still values not being parsed in bacnet.
I am only a new user so just trying to get it all working.
But also facing this, their if an issue raised with lots of communication. The developer is actively investing
@GravySeal, I appreciate your generous support on creating Bepacom add-on for us. i have been using and it’s working for me in the latest update.
Only concern I am having is that, when a BACnet device goes offline, it doesn’t reflect on HA entity value as unavailable or offline or etc. HA entities keep reading last value.
Is there a fix to make this more accurate ?
I do plan to add this somewhere in the future, but for now it’s not possible yet.
So much to do… yet so little time! Wish I had more free time to work on it.
hello,
i have installed the add on but can’t connect do our bacnet devices. The home assistant is in another vlan, 10.1.3.x and the bacnet devices on 192.168.0.x. Firewall is open and i have changed the IP of the add-on to the 192.x range.
I have a demo ha on the 192.168.0.xxx and the devices are reachable but not on the main ha installation, is there an way to connect to another vlan?
6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-interface: starting
[09:09:59] INFO: Running init-nginx.
[09:09:59] INFO: Allowed addresses for NGINX: 127.0.0.1 10.1.3.xxx 172.30.xxx.1 172.30.xxx.1 172.28.xxx.172
[09:09:59] INFO: Running init-interface.
[09:09:59] INFO: Generated ingress configuration successfully!
s6-rc: info: service init-nginx successfully started
[BACpypes]
objectName: EcoPanel
address: 192.168.0.xxx/24
objectIdentifier: 421
maxApduLengthAccepted: 1476
segmentation: segmentedBoth
vendorIdentifier: 15
foreignBBMD: -
foreignTTL: 255
maxSegmentsAccepted: 64
loglevel: WARNING
defaultPriority: 15
s6-rc: info: service init-interface successfully started
s6-rc: info: service interface: starting
s6-rc: info: service interface successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
[09:10:00] INFO: Running interface
s6-rc: info: service legacy-services successfully started
[09:10:07]|WARNING |h11_impl.py ->handle_events : Invalid HTTP request received.
[09:10:07] INFO: Running NGINX
2025/02/05 09:10:07 [notice] 311#311: using the “epoll” event method
2025/02/05 09:10:07 [notice] 311#311: nginx/1.26.2
2025/02/05 09:10:07 [notice] 311#311: OS: Linux 6.6.73-haos
2025/02/05 09:10:07 [notice] 311#311: getrlimit(RLIMIT_NOFILE): 1073741816:1073741816
2025/02/05 09:10:07 [notice] 311#311: start worker processes
2025/02/05 09:10:07 [notice] 311#311: start worker process 363