Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!
SmartConnector Forum
Schneider Electric support forum about SmartConnector applications for integration of other building management systems (BMS) into EcoStruxure Building Operation.
Link copied. Please paste this link to share this article on your social media post.
Dear Schneider Support,
I am working on an integration between EcoStruxure Building Operation (EBO) and an MQTT broker. I followed the recommendations provided by Schneider and successfully established the MQTT client connection, but I am still unable to correctly retrieve the luminosity (lux) value inside EBO.
The topic in question is:
slegdomo/sensor/0004742C016E/metrics/luminosity
The broker publishes numeric values correctly (e.g., 32
or 39
), confirmed with MQTT Explorer, but in EBO the corresponding point does not update and does not show anything.
I have already configured:
The MQTT Client in EBO (connection is established and online).
A Data Group and subscription topic pointing to the path above.
Value format set to numeric (lux).
Binding of the luminosity
point to the Data Group.
Please find attached screenshots to get a better idea .
I kindly request your technical support with a more detailed tutorial or specific guidance on:
The correct payload format supported by EBO (when the value is just an integer without JSON).
The recommended Value format and Data point configuration so that EBO interprets the value as numeric (lux).
Whether the direct topic .../metrics/luminosity
should be used, or if it must be mapped through ../luminosity/Value
.
Thank you in advance for your assistance in helping me finalize this integration.
Best regards,
Jorge Guedes
Link copied. Please paste this link to share this article on your social media post.
There is no value for pair in this payload and no static point ID..
Also the mapping of the PointID and Value are empty but with this payload you can’t map it..
Do you have access to modify the payload?
Payload pairs should look like this:
{“mypointID”:”luminosity”,"myvalue":"23"}
The values in the mapping of the PointID should be "/mypointID" and Value should be "/myvalue” so the same as in your payload.
Link copied. Please paste this link to share this article on your social media post.
Unfortunately I cannot change the device payload. It publishes a non-JSON on this topic.
Another thing, when I do a test with JSON pairs, the EBO still doesn’t populate the variable unless a new message is published.
Example (with JSON test):
Topic: slegdomo/sensor/0004742C016E/metrics/luminosity
Payload (retained): {"mypointID":"luminosity","myvalue":"23"}
This message is retained on the broker (visible in MQTT Explorer). If the payload never changes, EBO does not show/update the value after restart/rebind—it only updates when a fresh publish arrives.
Could you please advise how to force EBO to read the retained message on subscribe (i.e., populate the point even when the broker already holds the retained value and no new publish occurs)?
If there are specific EBO settings for retained handling / clean session / re-subscription behavior to achieve this, I’d appreciate the exact steps.
Link copied. Please paste this link to share this article on your social media post.
What version do you have? I just tested on EBO 7.2.348 and when i disable my client, send a new retained value to the topic, enable my client in EBO and the retained value is immediately taken over..
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.
Welcome to your new personalized space.
of