The GetIPAddressRequest message request works only for cameras.
You’ll probably need to use the Configuration API to get the hardware address for metadata. So do new Metadata(item.FQID) and then get the parent hardware path from the Metadata.ParentItemPath property. From there you can get the Hardware object and retrieve the Address property value.
You’re probably right that the GetIPAddressRequest is reserved for camera devices only.
I’m not sure the reason for it applying only to camera devices. With the exception of the configuration api, we don’t usually want/need hardware IP information in the client applications since the recording server is the only one to communicate with cameras.
It might be that the GetIPAddressRequest/Response messageids predate the configuration api, and were added to support the original Matrix Monitor software which needed to connect directly to cameras for video instead of pulling it from the image server.
Thanks Josh.
That works great.
Just for the sake of knowing. My reasoning for wanting to know the IP:port of the metadata device is to make sure it aligns with the Metadata Provider application. The server will continue to reach out to the provider, but if the provider isn’t on the right IP:port, they’ll never connect. I wanted to give the user a heads up about the problem.
Thanks again.
Ty