Getting values from Schneider EBO?

utterfredrik

Hi,
We have alot of data in our building automation system and would like to export some of it to IoT-open.
The system we use is EcoStruxure Building Operation from Schneider, and I have noticed that there is a MQTT interface in their menues.
How do I set this up? Do I use the MQTT-interface or do you have some other way of integrating?

Thank you!
//Fredrik

Jesper

Hello,

I know of an edge-app that has been used previously. But it looks like it is only one-way and from IoT Open to EcoStruxure. Either an addition to the app or a separate app needs to be created to handle EcoStruxure formatting to IoT Open values.

To run the apps the installation would need a connected edge-client as well.

It does not show on your configuration but to connect to the broker you would need to set both username and password for the MQTT connection. The username can be any text, and the password needs to be an API-key from the plattform. It is also mandatory to use secure connection with SSL.

rejas

Hmm, what more MQTT-parameters do you have after Hash sign replacement? Do you se any where you can alter the mqtt-topic?

utterfredrik

Managed to set up everything and now I'm exporting values from EBO to IoT-open.
Posting pictures of what I had to change in case someone else is doing this after me, It was not that hard, I think something got messed up with my API-key, after generating a new one it worked.

utterfredrik

My follow up on this is if there is any way of posting to multiple functions in one topic by putting the identifyer in the payload?

Jesper

Unfortunately the system is design so that one topic equals one measurement value. It is after all the "topic" of the value...

I looked at the MQTT traffic and it works for now but the MQTT payload should always be formatted as a JSON object according to the specification here.

This increases the compatibility with other softwares interacting with the platform. I would suggest changing the "Value format" field to something like {"value": @(VALUE)} and if possible also include the current unix-timestamp from EBO if possible. The time now will be when the message is saved in our database. With time it would be something like {"value": @(VALUE), "timestamp": @(TIMESTAMP)}, but with the correct variable name if such exists.

Another tip is to att a format meta-key to the functions to display the values more human friendly in the function editor. A good start is something like %.2f kWh.

utterfredrik

Jesper I have changed the payload according to the documentation. Thank you for your tips and input!
Will read the documentation in more detail 🙂

rejas

Snyggt jobbat @utterfredrik 😃