-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
device number when using this library #31
Comments
Why you need a local device id? |
Hi. We also require the possibility to change our local device ID. Some devices we are communicating with refuse the connection unless we have a specific ID. |
Did you find a solution ? Or maybe there is another way ? |
We ended up using the YABE C library and skipping Node entirely. |
We also need the ability to specify a device id on read and write. Our bacnet server has three devices under one ip with certain AV and BV instance ids living under each, so AV1 lives under device 50203 while AV33 lives under the default 50200, which is what node-bacnet sees by default. So we can get AV33 using the IP, object id of 2 and instance of 33, but get object errors on instance of 1 because it does not live under device 50200. |
When running a program using this library (subscribing to COVs, reading and writing properties, etc), what is the local device ID? Is there a way to set it to something specific?
The text was updated successfully, but these errors were encountered: