Anyone using Barix Barionet as Modbus?

I have a Barionet 100, running a custom bcl I use for Milestone XProtect, that are connected to exterior PIR motions sensors to trigger alerts and recordings.

I’d like to use those same PIRs for turning on lights, so I setup the Modbus options in my config, but I get these errors.

Connection to (192.168.20.5, 12302) failed: [Errno 111] Connection refused
10:12:01 AM – /usr/local/lib/python3.8/site-packages/pymodbus/client/sync.py (ERROR) - message first occurred at September 19, 2020, 11:01:22 PM and shows up 572 times
Modbus Error: [Input/Output] Unable to decode request
10:11:40 AM – /usr/local/lib/python3.8/site-packages/pymodbus/transaction.py (ERROR) - message first occurred at September 19, 2020, 11:03:01 PM and shows up 270 times
Unable to decode response Modbus Error: Unknown response 99
10:11:40 AM – /usr/local/lib/python3.8/site-packages/pymodbus/factory.py (ERROR) - message first occurred at September 19, 2020, 11:03:01 PM and shows up 270 times

Home Assistant server is showing up as an active TCP connection, but drops out every once in a while.

Yes I have maybe 15 or more Barionets. Several connected to Hassio.

I have written MQTT auto discovery code for barionet in BCL.

Also Modbus TCP/IP work perfectly from Hassio - just add in configure.yaml. Important to use Mosbus port 502 on barionet

let me know ?

Yes, please share any information or code you can. I’d really appreciate it.

Please share your BCL code here so I can assist ?

Also share your configure.yaml part where you set up the mobs communication

# Barix Barionet Configurationn
modbus:
  name: Barix
  type: tcp
  host: 192.168.20.5
  port: 12302

Resurrecting a neglected Barix Barionet today — it’s alive! Stumbled on this post but the content on github is gone.

do you still have this running around somewhere? I’d be interested in working with it. Thanks!

The code above never changed, but the repo was made private.