# BACnet Status Not Initializing: Reject-Message-To-Network **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [July 25, 2022, 6:47pm UTC](https://forum.inductiveautomation.com/t/bacnet-status-not-initializing-reject-message-to-network/62283 "2022-07-25T18:47:23Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![aidansks](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@aidansks](https://forum.inductiveautomation.com/u/aidansks)\ **Post date:** [July 25, 2022, 6:47pm UTC](https://forum.inductiveautomation.com/t/bacnet-status-not-initializing-reject-message-to-network/62283/1 "2022-07-25T18:47:23Z")
Hello, I have been having trouble adding my BACnet devices into Ignition using the module, following some posts here I’ve worked through different errors to get the correct IP’s setup and was then getting an IAmRequest warning. After restarting my gateway this warning went away and now I have a DefaultTransport error: “Received Reject-Message-To-Network with reason ‘4’: The message is too long to be routed to this DNET.” I assumed that the IAmRequest warning meant I had some connection to the BACnet gateway & that the WhoIs was received, but I am not certain. I am also not sure if this DefaultTransport error is coming from BACnet or just the network I’m on with Ignition. I haven’t been able to find much documentation for this error message so I would appreciate any input! ---
**Author:** ![aidansks](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@aidansks](https://forum.inductiveautomation.com/u/aidansks)\ **Post date:** [July 26, 2022, 1:14pm UTC](https://forum.inductiveautomation.com/t/bacnet-status-not-initializing-reject-message-to-network/62283/2 "2022-07-26T13:14:22Z")
Solved my issue - Had the wrong device ID for BACnet. Not sure why I was getting two different error messages before and after restarting though…