Collective often break on Upload Changes

[Raiden]

Since latest update there seem to be an issue with uploading any changes to my collective.

Everything seem to go fine, all devices get green check marks, but upon returning to main screen one of the devices is showing red icon and is unresponsive breaking the collective. It is often the same one (XS), although today another one did this upon some changes to the feeders schedule (X2). Full collective is made up of X4, X2, XS, XP8, and WaveEngine. If I do not change anything it seems mostly stable, issue I had with XP8 disconnecting and breaking collective at least daily seem to be gone since new update, but I guess something else broke now

I have at this point given up on trusting collective to stay stable for any period of time, but do have a decent enough solution of rebooting it all. I have all power to the collective plugged into smart outlets that I can control remotely, funny enough those never seem to have any issues

Still I would like to report this in hopes it will gets fixed, for now it is a very high chance that if I change anything and upload those changes, collective will break and I will have to reboot everything.

 

[thom_smith]

Understand waning trust based on repeated collective borken events. However a collective broken is an unusual event, source should be able to be identified and resolved then regaining your trust.

I know CoralVue has been working on configuration upload fixes for an upcoming firmware release but unsure the issue causes collective broken errors.

How frequently does the collective broken occur? Is it only during configuration uploads? What is the duration of the collective broken status? Does it recover on its own if you wait?
By reboot, do you mean Reboot Device (actually entire collective) or power reset? Can you share screenshots of your Device Properties output below the three dots in upper right to see if it yields any information as you why? We can try checking this out here but your best bet may be opening a ticket with support@coralvue.com for fastest resolution. With your permission, they can remotely login to your collective and troubleshoot.

 

[Raiden]

Video shows what happens. The message aboout out of sync device I have not seen before, but suppose explains the issue.

From my experience this will not recover on its own and I have to cut power to wave engine and xp8 to shut it all off and restart. This is why I have those plugged into Kasa power strip, so I can do so remotely.

 

[Danny]

Is it always the same X2 controller that does that? If so it might be a wifi issue or the X2 itself. Even in a collective the wifi has to be good at all the controllers when you do an update or it will get an error. Also try rebooting your router and see if that will fix it. I have seen some strange things cause by the router.

 

[thom_smith]

The configuration sync message may be a normal occurrence. I have a large collective and frequently see it for a few seconds after uploading configuration. It may occur if there is any sort of network latency causing a delay in one of the controls downloading the new configuration from the cloud. The configuration sync message alone isn't an issue as long as it doesn't persist for more than a few moments. If it lasts longer, that would be an indication the upload failed for a device and would normally be depicted by a red X on the upload status screen.

I know of two configuration upload issues they have been actively working on. One is believed to be resolved in the current firmware under test. And another which only I have reported that has been difficult to duplicate but also hasn't occurred for me in the current firmware under test. To my knowledge neither causes a collective broken though. Definitely suggest a ticket to support@coralvue.com where Carlos or Connor will take a look and likely engage others.