Node Version: 12.4.0
Node BACstack Version: 0.2.4
Feature Request / Question
- It is not uncommon to have more than one bacnet devices sitting on the same ip address because the target address could be like a subnet which can house many other devices.
In order to reach out to a specific device, commands like the read property will have to be explicit. Unicasting to an address is not sufficient as there can be more than 1 devices responding to the call. Hence to narrow down to a specific target device the parametersnet and adr must be set. At the moment whoIs does not disclose this.
We will need to decode these information and make it available.
Current Behaviour (Bug Report)
N/A
Expected Behaviour (Bug Report)
- I would like the WhoIs response to include the following data.
"header": {
"func": 10,
"sender": {
"address": "10.1.201.53",
"forwardedFrom": null,
"type": 0,
"net": 7778,
"adr": [
127,
0,
0,
1,
180,
196
]
},
The structure is recommended as this will make things easier for the lib user. All they need to do here would be to pass on the 'sender' object into the api like readProp and not care about the details.
Steps to reproduce Issue (Bug Report)
Node Version:
12.4.0Node BACstack Version:
0.2.4Feature Request / Question
In order to reach out to a specific device, commands like the read property will have to be explicit.
Unicastingto an address is not sufficient as there can be more than 1 devices responding to the call. Hence to narrow down to a specific target device the parametersnetandadrmust be set. At the momentwhoIsdoes not disclose this.We will need to decode these information and make it available.
Current Behaviour (Bug Report)
N/A
Expected Behaviour (Bug Report)
The structure is recommended as this will make things easier for the lib user. All they need to do here would be to pass on the 'sender' object into the api like
readPropand not care about the details.Steps to reproduce Issue (Bug Report)