Homey Community Forum

[APP] OctoPrint

Control and monitor your 3D printer
image

Together with a friend I helped develop an app for OctoPrint I thought you might like to know about :slight_smile:

Link to app store
Source code is available here

Supported Languages:

  • English
  • Norwegian

With this app you can:

  • Send notifications once a print has finished, with snapshot from webcam configured in OctoPrint.
  • Pause, resume and cancel a print.
  • See current state, tool temperature, bed temperature, time estimate, completion percentage, print time and time left.
  • All sensors and states are available as tags and can be used in flows.

Please report issues or ideas at the issues section on Github

10 Likes

That’s actually really nice!!

Hello and thank you for the work. I do not understand what to install and or. I have feedback on my application, but I cannot control my printer.

I love the app, now the printer is part of my home automation. But if i send a snapshot i just get the Homey logo shown. Is there something else which needs to be configured for that functionality. My webcam and snapshot settings in Octoprint works fine.

Thanks for this app, but i can’t seem to get my octoprint added.

I keep getting “could not find that pair session”

Any hints are welcome.

Thanks

Edit: problem found i switch to the browser during adding of the device after re adding without switching it worked.

Hello :slight_smile:

1.0.8 is now available in test.

  • Fixed flow_token_already_exists error
  • Minor translation fixes

1.0.7

Snapshot is now a global tag so it can be used everywhere, also you can customize the snapshot url under advanced settings if you prefer, otherwise it defaults to octoprints webcam snapshot url.

There was an issue with on/off being triggered untimely, this should now be fixed. Also better handling of device setup if something goes wrong. Buttons are also operational, pause/resume cancel.

!! After update (breaking changes) !!
This is a big update. Please remove device and re-add, then update your flows to make sure everything is functioning. Sorry for the inconvenience.

Changelog

  • Homey SDK v3
  • Improved translations
  • Easier/Quicker setup
  • Snapshot config moved to advanced settings
  • Snapshot is now a global token (tag)
  • Buttons are now functional
  • Adds trigger card for print paused
  • Fixed off trigger when it shouldn’t
  • Adds homey community topic id
  • Adds loading overlay in setup

Issues
Any issues, feel free to report here.

2 Likes

1.0.8 is now live!

!! After update (breaking changes) !!
I want to point out once again that this has some breaking changes, so before reporting bugs any bugs, please make sure you remove and re-add your device(s) and update your flows.

Sorry for the inconvenience.

1 Like

Maybe a stupid question:
I use one Raspi Octoprint setup to serve two printers…is it possible to add both of them?
When I try to add the second one, i get a message “duplicate device” using different applications keys.
Adding the printer i get a “flowtoken_already_exists” error.

1.0.9 is now out in test!

Changelog

  • Fixed run listener init
  • Adds camera in-app

@Tequila329 Not a stupid question at all.

The reason you get duplicate is that it is a duplicate, one device equals one octoprint server. This should work fine with one device, but there is nowhere for you to select between printers in the app so that part has to be done inside octoprint for now. If you want to see such a feature please create a new feature request here. I’m not sure if this is a common thing, being you can’t run both at the same time so I’ll have to think about it. Maybe it can be added in somehow.

For the last part “flowtoken_already_exists” it should now be fixed in 1.0.9.

OK, migrating vom Repetier Server (which can handle multiple servers on one Raspberry) Octoprint seems only one printer per server.

No problem, i can use the existing Pi to setup a second instance :+1:

i was really waiting for an app like this. So i tried but i can;t get the flows to work no matter what i try.
so far i tried the following: https://homey.app/f/JKItHw/
https://homey.app/f/wTXtHw/
https://homey.app/f/GY2uHw/
https://homey.app/f/Aa7uHw/
https://homey.app/f/xbeuHw/

so the question is what am i doing wrong

Sorry for the late reply. Did you figure it out?
I think your second flow should work as long as your pushover integration is.
If you haven’t already, could you also please try to re-install and re-add the device just to make sure.
Which version are you using? If you’re not yet using 1.0.9 from test maybe try that instead.

hello,
yes i did however it stopped working after some days so i am going to test the new test version.

gr. frans

@Jumpingmushroom Johny, would it be possible to implement checking for M112, M108, M410, M412 eventually status from Octoprint INT4 ? Eg.I have condition When not printing at 01AM / 5AM etc. in the morning…start countdown to turn off printer via IKEA Tradfri power socket. But…now during 20 hours print somehow it stopped reporting Octoprint connection error… naturally it reported Not printing so during night and after 10 hours the printer powered off…it was quite hard to find layer it failed later on :wink:

Yes, I have also countdown for “Print finished” - but scenario above is for situation "Yeah, I will start printing when I got time…and printer stays powered on for 3 days without activity :wink:

2nd time it happened I had serial.log enabled :

2021-05-12 04:01:00,900 - Recv: INT4
2021-05-12 04:01:01,420 - Recv: UVLO - end 494
2021-05-12 04:01:32,279 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2021-05-12 04:01:32,282 - Send: N952322 M105*26
2021-05-12 04:02:02,311 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2021-05-12 04:02:02,314 - Send: N952323 M105*27
2021-05-12 04:02:32,344 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2021-05-12 04:02:32,347 - Send: N952324 M105*28
2021-05-12 04:03:02,376 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2021-05-12 04:03:02,378 - Send: N952325 M105*29
2021-05-12 04:03:32,408 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2021-05-12 04:03:32,411 - Send: N952326 M105*30
2021-05-12 04:04:02,441 - No response from printer after 6 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.