This article aims to explain how EnOcean telegrams can be sent and received within MobiusFlow. The article briefly covers the supported telegram types and illustrates how these types affect the setup of a given flow.

Receiving

Overview

EnOcean telegrams can be received and injected into a given flow using the Subscribe to Broadcast Command node, labeled 'sub bcmd'. This node is shown below.

Upon opening the node configuration, the Command ID config parameter is presented. The EnOcean telegram type to be injected into the flow is specified here. This is shown in the screenshot below.

Once an incoming telegram of the specified type is detected by the sub bcmd node, the node will forward this telegram out of its output.

Command Types

The table below shows which Command ID entries relate to which telegram types. The table also shows screenshots of each Command ID being used within the sub bcmd node configuration.

Type	Command ID	Example Screenshot
ERP1 (EnOcean Radio Protocol 1- Fixed Length)	ENOCEAN_RADIO_ERP1
ERP1 VLD (EnOcean Radio Protocol 1 - Variable Length	ENOCEAN_RADIO_ERP1_VLD
MSC (Manufactuere Specific Commands)	ENOCEAN_RADIO_MSC
RMC (Remote Management Command)	ENOCEAN_RADIO_RMC

Example

In this example, a sub bcmd node is used to subscribe to incoming EnOcean RMC telegrams. The sub bcmd node is linked to a debug node to allow the telegram to be displayed. This setup is shown in the flow below.

The configuration of the sub bcmd node is shown below.

Following the deployment, an incoming RMC telegram was received. This was displayed in the debug panel using the debug node. This result is shown in the screenshot below.

Notable parts of this response include the message topic (shown in the red box below) stating the telegram type as well as which EnOcean connector received the telegram and on which Mobius hub the telegram was received (HubID/ServiceID/TelegramType). Furthermore, the actual data contained with the telegram is shown in the green box in the screenshot below.

Telegram Response Profiles

It's worth noting that other telegram types (e.g. ERP1 or MSC) have different response profiles to the RMC profile exemplified in the previous section. All profiles are documented in the table below.

Telegram Type	Example Response Profile
ERP1
ERP1 VLD
MSC
RMC

Sending

Overview

EnOcean telegrams can be sent from the flows using the Send Broadcast Command node, labeled 'send bcmd'. This node is shown below.  

On opening the node's configuration, a Command ID is required to specify the function of the node. To allow the node to send EnOcean telegrams, the Command ID should read 'ENOCEAN_RADIO_TX'. This is shown in the configuration window below.

The node accepts and forwards data contained within the payloads of incoming messages. The appropriate incoming message structure is shown below.

msg.payload = {
 sid: (EnOcean Connector Service ID),
 rawData: (Command Data)
}

sid: The Service ID of the EnOcean connector that will be used to transmit the EnOcean telegram. This takes the form of a 3 digit hex string.

rawData: An array of single-byte numbers containing the transmission data. The length of this array will depend on the telegram type.

Checksums and Sync Byte

All EnOcean telegram types feature a sync byte and some checksum bytes to ensure message integrity. These features, outlined in red, are shown within an RMC telegram profile below.

When forming a telegram, the user does not need to include the sync byte or checksum bytes, as these are automatically added by MobiusFlow. In the example above, the RMC (Remote Management Command) type is described. This telegram type will be further used in the later example in this article.

Telegram Types

The type of telegram being sent is specified within the 'Packet Type' field in the rawData of the outgoing telegram. This is shown in the context of an RMC telegram (Packet Type 7) in the red box below.

Note, the type of telegram specified vastly affects the remaining profile of the telegram so the correct telegram profile must be used with the specified type. The following table shows which packet type values correspond to which telegram types.

Example

In this example, the send bcmd node is used to send an RMC EnOcean telegram. An inject node, labeled Trigger, is used to initially trigger the flow. This is wired to a function node, labeled Form Telegram, which is used to transmute the incoming trigger message into the outgoing EnOcean telegram. Finally, the function node is wired to the send bcmd node which is used to send the newly formed EnOcean telegram. This entire flow is shown below.

The function node has been configured to contain the following setup. This sets the Service ID (sid) and rawData properties of the message payload.

In the above screenshot, the rawData has been divided to illustrate the distinct header, data, and optional data segments. The colours used to show these segments match the colours used to describe the RMC telegram structure in the following table.

Also note, within the function node, the sid property has been set to the hex string 'F01', to match the service ID of the connector that will be used to send the message. In this case, the connector being used has sid F01 and this is shown in red in the diagnostics window below.

The code contained within the function node is shown in code form below.

msg.payload = {
sid: 'F01', // Connector Service ID
rawData: [
 0x00,
 0x04 + 2, // Data Length
 0x0A,     // Optional Data Length
 0x07,     // Remote Man Type
 0x04,     // Function Number
 0x51,     // Function Number
 0x00,     // Manufacturer ID
 0x47,     // Manufacturer ID
 100,      // data byte 0
 200,      // data byte 1
 0x00,     // Destination ID
 0x00,     // Destination ID
 0x00,     // Destination ID
 0x00,     // Destination ID
 0x00,     // Source ID
 0x00,     // Source ID
 0x00,     // Source ID
 0x00,     // Source ID
 0xFF,     // dBm
 0x00      // Send With Delay
]};
return msg;

When the flow is triggered, the function node generates the EnOcean telegram and this is sent using the send bcmd node.