inba

Thank you! This is what I was looking for ?

I want to "abort" (pause & restart) a print. So I tried to set a state (PUT /print_job/state) on the WebGUI. But it doesn't stop (Yes, I'm successfully authenticated since I started the job) If I put "abort" (with quotation) in the box and click "Try out" the response is: { "message": "'str' object has no attribute 'get'" } If I send abort, the response is: { "message": "400: Bad Request" } Which command do I have to "send" to the printer, to abort/pause/print and how is the formatting? Thank you! ?

I solved the problems. As @starbuck said, for renaming I had to quote the name.

Another interesting thing: GET /printer/status => "maintenance". In the "Inside the Ultimaker 3 - Day 2 - Remote access (part 1)" it says "maintenance: Someone is actively doing things with the printer, for example changing materials or PrintCores." I'm only accessing the printer through the WebGUI, why is the status "maintenance"? Could this be the problem?

@pbackx: The screens from my inital post are directly taken from the online documentation, which is located on the printer. On each command there is a "Try out" button, where you can test the command. Both commands are not working, although I got authenticated. I'm pretty sure the LED & name should be easily set, since it's well documented (post) and it worked once (green LEDs) There is an old version of the api documentation online, just to see how it looks like => Swagger UI @starbuck: Thanks for the help. Anyway SSH is no option for me at this time ?. Yes I did authenticate (first post, first bluish image). But why are the LED's not working? Is it a bug or a wrong api call? I'll try to change the name with quotation marks the next time. Some background info: I'm working on a project to control the printer. After some time I finally got the digest authentication working, which I successfully tested with /auth/verify. But I wanted to do a "real" simple test like setting a value. So I tried these two PUT-Commands (LED+Name), described in the "Inside the Ultimaker 3".

Hey, thanks for your answers, but I don't agree, but I like you to elaborate ? But please have a look at "Inside the Ultimaker 3 - Day 3 - Remote access (part 2)". There are two "PUT" examples: LED & Systemname. I have seen the case glowing red and green, so it is possible. I can't reproduce it, but it tried some weird combinations of /printer/led and /printer/led/blink with postman. Regarding the name: How do I know the right JSON String (I doubt there is). In the API Documentation on the printer there are some other examples with JSON and PUT (e.g. /system/display_message). There it is clearly stated, that the input hast to be JSON and how it looks like (Example Value on the left). Even in the /system/name/ example from the forum post, there is no JSON only the new name (MyUltimaker3) Thank you anyway ?

Hi, I got a problem with the API. I registered my application, got my id+key and verified it with the the proper API commands (Timestamps differ!). After that I wanted to change the LED Color like in the "Inside the Ultimaker 3 - Day 3 - Remote access (part 2)". So I tried {"brightness": 120.0, "saturation": 100.0, "hue": 100.0} even if the "Example Value" said "value" instead of brightness. (Postman API call returned (/printer/led) returned "brightness") The problem was that the color didn't change. Reboot. Again nothing. I logged up the log after the reboot and found this in the log: Jun 08 06:51:30 ultimakersystem-ccbdd3004c87 systemd[1]: Time has been changed Jan 01 00:00:59 ultimakersystem-ccbdd3004c87 connmand[254]: ntp: time slew +1528440630.651671 s Jan 01 00:00:53 ultimakersystem-ccbdd3004c87 flipflop_wsgi.py[413]: 00:00:53 - WAR - app.libs.printer_api:189 - Failed to set the LED color for printer at http://192.168.0.14/api/v1 ... Jan 01 00:00:43 ultimakersystem-ccbdd3004c87 flipflop_wsgi.py[413]: 00:00:43 - WAR - app.libs.printer_api:189 - Failed to set the LED color for printer at http://192.168.0.14/api/v1 Why is the IP different? Or is this just coincidence? The IP changed indeed from 14 to 31, mhhhh Anyway I tried another command, which was also mentioned in the forum post => Changing the name. The example name was "MyUltimaker3", I tried "Ultimaker3" instead. Does anyone got an idea why this is a bad request? Another thing is the old firmware. The log says: Jan 01 00:00:29 ultimakersystem-ccbdd3004c87 python3[226]: 1970-01-01 00:00:29,605 INFO systemUpdate Comparing firmware 'stable' old version '4.2.5.20180102' with new version '4.3.2.20180308' with result: False Are these just bugs? (Updating is not that easy.I have to ask for permission, since I'm not alone exploring the device ) P.S: I'm using Firefox 60.0.2 & Postman 6.1.3