[Resolved] COULD NOT CONNECT to collector.currently.cloud

Support Status
#1

Starting September 20th 3:40PM CEST, we are observing Currently One devices not being able to connect to our Cloud Service. We are investigating.
[Resolved] Re-provisioning the service/certificate for collector.currently.cloud resolved the issue.

#2
#3

Is it possible to keep other services alive if one fails?
In this case, it does not read out any values from HAN-port until it can connect to collector.currently.cloud.
The same problem is that the app doesn’t show any values if it fails to connect to the mqtt broker.

Otherwise, it works like a charm!

/ Erik

#4

Great suggestion, it will be implemented really soon. :+1:

1 Like
#5

Issue verfying the root SSL certificate. The collector.currently.cloud service is running in Google Cloud, so this certificate business is beyond our control.

#6

We noticed a different Root Certificate being provisioned by Google Cloud for collector.currently.cloud. We are in the process of re-provisioning the service, and are hoping that this will restore the correct Root Certificate. :crossed_fingers:

#7
#8

Re-provisioning the service/certificate for collector.currently.cloud resolved the issue.

#9

It might be another issue, but since yesterday, my device has some severe problem. This is whats printed in the log:

  lineBuf OVERFLOW 255(255)
_onReceiveError 2
  lineBuf OVERFLOW 255(255)
  lineBuf OVERFLOW 255(255)
  lineBuf OVERFLOW 255(255)
  lineBuf OVERFLOW 255(255)
  lineBuf OVERFLOW 255(255)
  lineBuf OVERFLOW 255(255)
  lineBuf OVERFLOW 255(255)
config /events 2023-09-21T08:22:08+0200
==== connected to /events ====

It communicated on mqtt yesterday between kl 18-19, but has been dead afterwards. Also, the app is frozen…