Hi Community,
https://catalog.dataminer.services/details/736b747d-fde5-4914-a040-13785670938e
Version 1.0.1.6
We are currently using the Lawo Power Core connector to monitor multiple PowerCore devices, including a unit in our lab environment. This connector uses the Ember+ protocol to communicate with the PowerCore units and is configured to use port 9000. All units are able to connect initially. However, we are experiencing intermittent connection issues where the status transitions from “Disconnected” to “Connecting”, then “Connected”, followed by “Walking over Ember Tree.”
For our production PowerCore units, these connection drops occur every 5 to 20 minutes and in some cases, the connection fails to recover and remains stuck in the “Connecting” state. Restarting the element is currently the only way to restore connectivity.
Reviewing the connector logs, we see the following message each time the connection is lost: "Ember S101 Consumer Connection lost due to: The given key was not present in the dictionary, retry will occur within 1 min".
Based on some initial research, it appears the connector may not tolerate dynamically changing Ember trees from the PowerCore devices. This kind of makes sense when you look at our LAB powercore. The LAB powercore barley has anything running on it and we don't get as many drops in connections on our dataminer lab system. We sometimes get a couple a day and some days none.
Other things to note, we use Cerebrum to talk to these powercore without any issues using ember+. They just use a different port.
I'm hoping someone else might have run into the same issue or can recommend something? Otherwise I will pass this onto the skyline support team.
Here is small snippet of the drops and logs below.


Hi David,
Based on the provided element log, the connector is currently failing to process a specific Ember+ parameter. This leads to the reconnect mechanism being triggered.
It appears that a particular Ember+ leaf is incorrectly mapped internally, which is causing this behavior. To resolve this, could you please contact the support team and request the creation of a connector ticket to ensure full support for your devices?
Once the connector mapping is updated to properly support your Ember tree, the reconnect issues should no longer occur.
Thanks in advance for your assistance.
Hi Robin
Thanks for your response. I've sent a support request through to skyline to take a look at this for me. Its with support level 2 now. Thanks heaps for your input.
Thanks,
Dave