-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Gateway address parsing #312
Comments
Hi 👋! |
Here is an example of an xml part from knxproj
<IPConfig Assign="Fixed" IPAddress="10.2.155.72" – it would be great to get information about this and other IP addresses in the json upload For example, as a suggestion, somewhere an additional field in this structure:
|
🤔 I guess many interfaces will not have a fixed IP address, but use DHCP. But parsing the security infos along with the IP infos may come handy. You can always use Knx IP discovery to find current interface information in a live installation. The second part I don't understand. What would group addresses have to do with interfaces in that context? |
In the second part, I mean that through the interfaces we get access to certain group addresses. And each interface corresponds to n number of such addresses. For example , we have several interfaces with IP addresses in our project (more than one): 10.0.5.65, 10.0.5.68, 10.1.5.70, 10.1.5.71. And let's assume 1000 group addresses in total. |
Ah I see. So you can always look up the devices in the same line as the interface in the topology tree. Then look up their used communication objects and linked GAs. That will yield GAs that the interface can see for sure. But it wouldn't take couplers / routers into account. |
Hi,
thanks for the functionality of the library, but is it possible to add information about gateway addresses applicable to each tag in the resulting json file?
The text was updated successfully, but these errors were encountered: