think its a bug, looks like its only creating the cluster status on boot, after a reboot the flag has changed. I'll log it on the github page and reference where I may have interpreted the issue from. thanks
Please don't post it there, that is the issue tracker for Cura, not for the printer API.
Oh, right. Damn. My fault. So @nallath where do we report firmware bugs?
I'm guessing you click on the 9 dots in the upper corner of this page, then click "support", then "submit a request" at the top of the screen.
Sounds like a bug.. but as he noted its gone in 8.0 firmware.. so that would mean said bug would not be fixed.
i've reported to Ultimaker Support, they said the API is not supported and to post here for help.
Perhaps i'll log it again with them as ive found its an issue with the firmware not the api as such, although that github page does contain the code for what seems like the UM S-Line firmware and api calls
No it's for Cura. The slicer.
So I'm being told that the feature is in 7.X but gone in 8.X and because UM is moving in that direction they won't be fixing bugs in 7.X for features that are going away.
However I believe there is also an API for digital factory (DF) and this is probably all supported there now. UM is moving towards DF (cloud based) versus local networking. It's free for users and easier for the programmers to deal with evidently.
Of course the other option is to stay with the firmware that works for you. Personally that would be my choice as it was a great printer years ago and was still a great printer with 7.X firmware.
Well we were on 7.x until students and teachers hit the popup on screen to update the firmware. Another QOL improvement I have asked for - to block the notification about firmware.
Downgrade seems like its too involved for what its worth so we have 8.x on 2 machines now which has given us nothing but grief so far
It sounds like you are pretty technical so I'd definitely do the downgrade. I think you need to do the "firmware recovery" method. But first you might want to put in some firewall rule to block those other machines from upgrading firmware.
Looks like a bug (and possibly a feature removal). Please post a much shorter description of the bugs on github and include a link to this thread.
Link to post
Share on other sites