2 Reboots required to get Flexy in active connection

[ChrScha]

For installation of the Agent there is a reboot required. After this the device does not send data, but requires another reboot.

One restart should be sufficient.

[alexjhawk]

Hi @ChrScha,

Thank you for reporting this.

To clarify, are you referring to the data about the Ewon device itself (such as the firmware information displayed on the device's Cumulocity page) or the historical data for tags?

Thank you,

@alexjhawk

[ChrScha]

Hi @alexjhawk,

After an initial install + reboot, data flows in; Then it stops and also my operations are not picked up by the Flexy.

Something is wrong with sending the data to the MQTT broker it seems.

Obviously a restart helped to reestablish the MQTT connection.

I use Firmware 14.6s0 (English) Connector v1.4.0.

[alexjhawk]

Hi @ChrScha,

Thank you for the additional details and the included firmware + connector version information. I will work to replicate the issue on my end and implement a fix in an upcoming version. I will let you know if I need any additional information and keep you up to date on progress.

• @alexjhawk

[SeanThomas11]

I too have seen this issue in registering new Flexys with our dedicated tenants across multiple firmware and connector versions. After installing the connector and initial bootstrapping configuration file and the first reboot, the JVM process begins and the Flexy downloads the CA Cert, but it hangs at the mqtt connect step requiring a reboot before registration. After reboot the JVM continues through mqtt connect and allows for bootstrapping registration. However it requires another reboot before accepting the device credentials, logging in and ultimately transmitting measurements.

[ChrScha]

Measurements flow in directly after the installation an registration now.

[alexjhawk]

This is great to hear. Thank you for the update, @ChrScha.