SpaceLYnk - Issues on the BACnet connectivity

[Cristiano_Carli_Ballola]

I'm currently facing an issue while I'm trying to detect and connect to my BACnet network a SpaceLYnk controller.
Device discovery is able to detect the device, but the BACnet name doesn't match and the Model as well as vendor name and Description are not shown.

And this is the error message that pops-up when I'm trying to link the controller to my BACnet interface

Unknown object
BACnet
~/BACnet Interface/IP Network/Device_1100000/BACnetName
BACnet plugin
0
ReadProperty

Unknown object
BACnet
~/BACnet Interface/IP Network/Device_1100000/BACnetName
BACnet plugin
0
ReadProperty

The Controller is a SpaceLYnk V2.0, with FW v3.0.0
The issue is not related to the firmware version; it also popped up with fw version 2.8.3

As you can see, on the same structure, I have a 2nd controller (wiser for knx) which doesn't show any issue

Any idea on how to solve that issue?

[Erwin-vd-Zwart]

There is more wrong as it also does not show the vendor name..

Can you try to compare the BACnet settings of both devices? Try also a different Device ID like 112233 to test if there is a conflict with it.

Try also to give the controller another host name (when Device name (optional) is empty) because that is used in the BACnet name.

Try to disable the server and than enable it before doing a new discovery or reboot the controller first.

[Cristiano_Carli_Ballola]

Hello @Erwin-vd-Zwart 
These are the BACnet setting of the working controller (Wiser for KNX)

and these are the settings of the non working controller (SpaceLYnk)

Do you see anything what have to be changed/modified?
BTW
After a reboot, apparently, the device is correctly listed

but, unfortunately, the same error pops up when I try to add it to the BACnet Interface

And if I perform a new "discover All" within the Device Discovery, the controller is listed again with the previous configuration

[Cristiano_Carli_Ballola · Accepted solution]

UPDATE

I have deleted the BACnet Client App from the controller and, apparently, is now working correctly.

[Erwin-vd-Zwart · Accepted solution]

Ah, that is normal behavior, you cannot use the client and server at the same time as they both use port 47808 and that results in a port conflict.

When having the BACnet client installed the server must be disabled.

When you want to use the server again you must delete the client app like you did now.