Troubleshooting EnOcean

Troubleshooting an O3 Edge

The O3 Edge is not communicating

• Check that the O3 Edge (the model name must end in "E8" or "E9") is communicating over the correct frequency (868 MHz for O3-EDGE-02-E8 models, 902 MHz for O3-EDGE-02-E9 models).

Communications are unreliable

• Check the overall send and receive packet counts. If necessary, create the Total Receive, Total Receive Error, Total Send, and Total Send Error objects.
• Use a packet sniffer such as DolphinView to detect devices broadcasting excess packets.
• Check for changes in the physical environment. For example, a new concrete or metal wall can affect communications adversely. Be aware of potential noise sources such as lighting ballasts or electrical equipment that can interfere with EnOcean signal strength.
• Modify the environment to improve communications. If this is not possible, consider moving the O3 Edge or installing a repeater.

Troubleshooting EnOcean Objects

EnOcean object values are not updating

• Check that the network SV and device SV objects have been created with the correct instance numbers.
• Check that the device SV object is using the correct XML mapping file.
• Check that the EnOcean objects (AVs, BVs, CSVs) have been created with the correct instances. An active hyperlink appears in the device SV Subordinates column when the object is created correctly.

The Device Address CSV object is not learning a new address

• Manually set the Device Address CSV object value to 0 to clear any previous addresses.

EnOcean object values are lost when a controller is shut down

• When an O3 Edge is shut down for a short time, events from COV-only input sensors (like window or door contacts) that were triggered during the shutdown period may be lost. These device types are unable to resynchronize after power up. The only way to resynchronize is to trigger a packet from the input sensor.