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 
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
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.Just writing to give a heads up. This app will no longer be maintained, if you’d like to adopt the app, please let me know.
That’s a pity ;-(
Yeah thats a pitty, hope it will continue to work in the future
I cant even add it. Put in the ip and API key but it cant pair
In the past several months I’ve been working on the code off and on (when I had some time, but couldn’t do anything while away from home anyway) for the Octoprint app, to add some additional functionality I missed in the app (mainly missing trigger cards).
In this time I also looked at some possible improvements and fixes that were requested here and the (original) github page as jon (sadly) abandoned the app.
There are some small breaking changes (see at the bottom for more information) making it harder (without re-pairing) to revert back to the stable/test version (the one in the app-store).
Update: v1.1.1 doesn’t have this breaking change anymore!
By just hiding the capabilities, instead of deleting them, this will keep the tags alive in old (already paired) devices (with still updating values), so no breaking changes anymore!
I have tested it very thoroughly.
If you however still find any issue(s) feel free to contact me in PM or on my github page (the issue page is open), and I’ll try to fix it in time.
If you have any requests, you can also send them in PM or on my github page, and I’ll see if I can add them.
In the end I might have gone a bit overboard, more then I expected at the start (LOL), adding lots(!) of additional features.
I wanted to share my fork of the app as more people are probably interested in at least some of the features.
You can find my fork on my github page. (click)
(How to install apps via CLI)
For now I probably won’t be taking over the app, as I just lack the (free) time for it, maybe in the future when life and work offers me more free time.
And the changes (most likely) won’t make it into the official app (app store), for now.
The changelog has become a bit long that it is kinda hard to post it here, so I’ll just summarize it here with most of the added features, you can still find the full changelog and all available flow cards (and their tags) etc. on my github page (in the readme).
Summarized changelog:
- Added: Target temperature for bed (0°C - 130°C) and tool (0°C - 300°C);
- Added: Target and measured Temperatures for a chamber (0°C - 75°C) (enable in the device’s advanced settings);
- Added lots and lots of Trigger (14 (total 18), Action (8), and Condition (3) flow cards;
- Added: Current (selected) file name;
- Added: Estimated end time (date and time);
- Added: Emergency stop (double click mandatory, to stop accidental clicks);
- Added: Send (any) G-Code (flow card);
- Added: An error has occurred (trigger card);
- Added: Bed or Tool cooled down (trigger card, threshold editable in the device’s advanced settings);
- Added: Home printer/axis (flow card);
- Added: Move axis to (flow card);
- Added: Dutch translation;
- Added: 3 Maintenance actions (restart Octoprint, reboot Raspberry Pi, shutdown Raspberry Pi);
- Changed: Cancel button now also needs to be double clicked, to stop accidental clicks;
- Changed: Heated bed can now be disabled (in the device’s settings), this will hide any heated bed capabilities and flow cards;
- Changed: Settings page was removed, and all settings moved to the device’s (advanced) settings;
- Changed: Many minor changes internally to make the code a bit more robust;
And might have forgotten a few.
## Note: breaking changes
There are some small (for the better) breaking changes, also making it harder (without re-pairing) to revert back to the stable/test version (the one in the app-store).
2 Likes
Thank you Caseda, it’s a pity you are giving up just after reaching final line ! 
Yet very very much appreciated.
So far so good - installation, adding printer, measuring values, but more testing is required.
If the finish line wasn’t a massive wall called “available time”, I could have “finished” 
.
1 Like
OK, so I actually thought of a (very/too) easy way to fully “fix” the breaking changes in my fork. 
Almost embarrassing that I didn’t thought of it before/immediatly.
So instead of just deleting the old capabilities, i’ll just hide them from your current device (tokens will remain active!, and still update their values), and new included devices just won’t have these (old) capabilities anymore (kinda a custom interpretation of deprecating a capability).
The update is now live on my github now (v1.1.1), and I’ll update my original post above.
Breaking free updating!
1 Like
Strange thing, i installed the plugin ans got it working. But when the IP changed on the PI i got dissconnected. So i changed the PI to always have the same IP, but now im unable to install the plugin. Get the flowtoken_already_exists after added the OctoPrint to the Homey. Could someone help me please?
Try rebooting Homey, that should fix the stuck flowtoken id’s of the old device.
hah, it was that simple 
I tried to add my octopi but always get and timeout, i tried with local ip and with local domain 
any advice?
Instal eg. NetScan to see if Homey really can access your OctoPi
1 Like
thank you for the advice, netscan works liek a charm with the octopi
#edit
now it works, dont know why because i justed tested with netscan and after that adding was not a problem…
Hi all
I seem to get stuck in the basics here. I am trying to add OctoPrint as a device over my browser, but I keep on getting the message: “Could not connect to OctoPrint. Make sure your address and API key is correct.”
I do enter the IP address and the API key but it won’t work. I tried including the ports to the IP, but did not work either. I’m certain that Homey and OctoPrint are in the same network and both are online since I can see them in the list of the devices connected via Wifi to my router.
I can connect through the OctoRemote app, so it’s likely something wrong on how I provide the address and API key?!
Any idea what I’m doing wrong?
Thanks
Just to be sure, you are using the version from Caseda, right ?
