-
Notifications
You must be signed in to change notification settings - Fork 92
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
MQTT Device list topic #373
Comments
maybe im missing something...but isnt this what probe is for? |
This is what the probe is for. The MQTT implementation breaks the document into separate devices. We could have a single probe payload, that would be an option. Or we can provide a separate device list. If you subscribe to |
i think im following you now. the agent could be configured with user-customized topic prefixes. So youre suggesting a topic with payload like the following to inform client apps of where to look for their device of interest; is that right? {
"myDeviceA_UUID":{
"id": "deviceA_ID",
"name": "deviceA_NAME",
"topics":{
"probe": "MTConnect/Probe/myDeviceA_UUID",
"current": "MTConnect/Current/myDeviceA_UUID",
"sample": "MTConnect/Sample/myDeviceA_UUID"
}
},
"myDeviceB_UUID":{
"id": "deviceB_ID",
"name": "deviceB_NAME",
"topics":{
"probe": "MTConnect/Probe/myDeviceB_UUID",
"current": "MTConnect/Current/myDeviceB_UUID",
"sample": "MTConnect/Sample/myDeviceB_UUID"
}
}
# ... rest of devices
} |
Hi @wsobel. We usually subscribe to Thank you. |
Create a topic that lists all the devices as a JSON array of name, uuid, and relates topic.
What should the topic be?
Does the payload make sense?
The text was updated successfully, but these errors were encountered: