RHuijgen

Hi Primeiro, If I understand the symptoms correctly what you have run into to be expected, the printer opens up the connection but is not associated to an account until the pin-flow is finished. There is no risk at this point of your files ending up where they shouldn't. However you issues continues to raise eyebrows within our team, so we would like to take this into the official support channels to make sure we can help you better (and log it for future issues). Would you mind opening up a support ticket at https://support.ultimaker.com/hc/en-us/requests/new?ticket_form_id=360000516440 so we can give it the attention it deserves? It would also help us a lot of you add the log files to this ticket, you can find how to do that here: https://support.ultimaker.com/hc/en-us/articles/360015583819-Save-log-files-to-USB Hi gdog, considering the importance of our Cloud ecosystem to the Ultimaker products and customers, we have a extensive support article about security of our system that we usually share with IT departments at our business customers: https://support.ultimaker.com/hc/en-us/articles/360018732359 I hope this information can shed some light on our confidence in our cloud security

Hi Primeiro (and others following this thread) Your problem is odd one; -If there is a print-job in the digital factory queue, that means someone had access to the printer through a cloud or local connection. Their (account) name would show up as owner of the printjob if this was the case. -If there is a print-job in the digital factory History then it's likely a remnant of the previous owner. printjobs were saved on the printer in the past and without a factory reset, these were migrated to the Cloud account of the current owner of the machines. It might be that one of these remnants was accidentally reprinted by the current owner of the printer. Accidental connection: A accidental account connection through a typo seems unlikely though. Our connection flow only allows for the right pincode to be entered for 10 minutes and the pincodes are completely random. We don't see enough connections realised at the same moment for this to be a risk. Also it would mean Primeiro would loose connection to the printer, since the printer is only ever connected to a single Ultimaker account. Since you disconnected your machine (understandable with strange printjobs appearing on your buildplate) it will be hard for us to find out what happened exactly. However if you end up connecting again and the problems is still there here's what you could do to get to the bottom of it: -download the printer report and look for the owner of the unfamiliar printjob -download the logs and send them to us -provide us with the printer ID so we can have a look at who is sending you these printjobs I'm sorry we can not give you a more definitive answer at this moment. Kind regards Roderick

Hi Primeiro, I'm sorry to hear that the connection is not working as expected. To help us understand what's going on, would you mind telling us; -Was the printer internet connected before this Saturday? -Does your queue in digital factory show the unfamiliar printjobs? (https://digitalfactory.ultimaker.com/app/print-jobs/in_progress) -Did the "connect reset"option fix the problem? ---If not, does the local connect interface show the unfamiliar printjobs? (type the print IP adress in your browser when you are on the same network) We don't suspect unauthorised access to your machine, but since it's pre-owned it could indeed be a ghost of the past trying to print already queued printjobs Kind regards, Roderick

Hi there, Although I'm happy that your issues are resolved, it's possible that your problem was caused by our scheduled maintenance this morning. If you experience something similar in the future, you can open up https://status.ultimaker.com/ to see if the application should be running as expected. Kind regards, Roderick

Hi Jeremy, It's unfortunate that you ran into this issue. Without any logs it's hard to know exactly what is going on, but there is at least one actions that might solve your problem; Resetting Digital Factory on your S5 will be a surefire way to ensure the grouping feature is turned off. However this will mean that you will have to reconnect your S5 to the network, and you will loose all data on the machine (Print history, print data on the dashboard, etc) If the problem persists after this, or resetting is not an option for you, we kindly ask you to add the logs to this thread so we can have a look at the Cura connection with the teams and see what might be going on. https://support.ultimaker.com/hc/en-us/articles/360016538000-Saving-Ultimaker-Cura-logs https://support.ultimaker.com/hc/en-us/articles/360015583819-Save-log-files-to-USB

Hi David, I am glad to hear that you enjoy our Cura Connect application. Unfortunately we try to avoid tweaking of the firmware in order to be able to service your machine when you run into problems. Your feedback does makes sense thought, but I would like to know a bit more about your situation if I may (get into the context and whatnot) Could you tell me how an image of the end results (Completed or not) impacts your actions when you are not in the office? Does an incomplete print job makes you rush to the office earlier in order to restart it? Do you have a colleague fix it for you? or do you just like to know what to expect when you finally get there? We have been playing around with the idea of a snapshot of the finished product or even a Timelapse of the proces, but have not worked on creating these features yet. I would be happy to hear your thoughts about what information you would need to improve your workflow. Kind regards Roderick