@nxt-1 Interesting, can you provide me full curl of:
curl -v 'http://localhost:8080/rr_status?type=3'
curl -v http://localhost:8080/rr_fileinfo
(those two below probably will not work)
curl -v 'http://localhost:8080/rr_model?key=job'
curl -v 'http://localhost:8080/rr_model?key=state'
@chrishamm Awesome, thanks for the great spot, not sure how I missed it.
@Nxt-1 would you mind giving it another go please? also api_version not needed anymore, software will try to detect it automatically.
@nxt-1 That's bit odd according to the previous post it should be either one of those two URLs.
@stuartofmt / @chrishamm any idea why either doesn't work?
@nxt-1 Right, so the second paste is wrong and missing URI 
and I had a thought as well, since there's '?' in URI bash might be screwing around with it try again with:
curl -v http://localhost:8080/machine/system
curl -v "http://localhost:8080/rr_model?key=boards"
@nxt-1 hiya, would you be able to provide me output from these two commands(run from the nano itself):
curl -v http://localhost:8080/machine/system
curl -v http://localhost:8080/rr_model?key=boards
?
@stuartofmt Ah that's quite cool. I've already put that in, however I stripped in my case and just checked for the appropriate content-type header on each URL, in both cases it should be app/json, otherwise it's just wrong.
I'm doing it all in golang, since it's quite nice for such nice things and portability and lack of dependencies.
I have notifications for any email service assuming it can do smtp so should in theory work everywhere. Can you point me to this duetmonitor? First time I'm hearing about this and haven't seen it.
If you want to poke around code and see what's there, that's the current that will go to master soon.
https://gitlab.com/Toriniasty/reprap_notify/-/tree/feature/apiV3/
@stuartofmt Cool. I'll have a look tomorrow (that is if I will survive tomorrow heatwave...). Cheers buddy.
Hey folks,
I want to share a download link with the version that should now work with v2 and v3 API.
If you could test it and let me know if it's all good that we'd be great and I will release it officially.
Only change you need to make is additional entry in your configuration file adding api_version in the connection section(v2 or v3) e.g.:
connection:
host: 192.168.0.11
polling_time: 30
error_count: 5
api_version: v3
Without further ado:
https://1drv.ms/u/s!Aq3gq6mIQqpsisE-e3Adz3wsP6dAJw
Link is going to expire in 2 weeks, after that I will just merge it
@chrishamm Many thanks for that, it definitely extends what I've seen.
However I am missing a 'final status' if that makes sense e.g. there's the status for cancelling yet there's no cancelled status or processing and no processed which makes it hard to understand and put the proper function in place to determine final status without hammering the API and making a request every let say 100ms which could still lead to some false positives.
So I finally found some time and resurfaced my duet enabled printer so I have started updating the app.... So hopefully soon there will be something to show 
@chrishamm How do I currently identify finished print? Previously it was in rr_status marked as 'I'(capital I), now I can see see only in rr_model?key=state status: idle, pause, printing.
@madeinta1wan This is due to API changes introduces in RRv3. There's a chance but it requires few hours of work which I currently do not have, however I will try to squeeze that in somehow. The code is opensource so if someone would make an PR I will happily merge it.
@festivejelly You can run it both ways, either from command line or double click. If it doesn't quit and windows stay open it should just work.
@thebaseddoge Simply start two programs with from two different directories with two different config files
@festivejelly There's no feedback unless there's a problem If you want to run on rpi you need an arm build.
@mct82 Hey, so I got a bit of spare time today and I've looked into it. Renotifications didn't work because I forgot to add two more if's.
I've created new release here: https://gitlab.com/Toriniasty/reprap_notify/-/releases/v7
@mct82 Basically yeah, you would also need to update struct for json payload.
In regards to windows, time.Now().Unix() should without any problem on windows. That's something I would need to check later during the week. but feel free to look around, add some timers maybe and logging
Actually just tested it quickly. It works literally as you did. Just copy paste slack webhook url, put it in config and it should just appear.
text is not needed, as it is send via attachments in slack:
https://api.slack.com/reference/messaging/attachments
@mct82 Hey, that's a good spot with if condition. I found the same problem in email and telegram too 
... So if you will head down to releases page there should be a new one with the fix.
In regards to Slack. I can't remember, but it should just work ootb when you change enable do true and put webhook url in. If you will still struggle let me know, I will try to see and check it during week.
@LB said in notifications upon start/pause/finish of print:
Do I have to download something and import it or how would it work?
Ah. Okey. To be fair, I haven't seen plugins functionality and I'm not sure how it is supposed to work. Maybe one day I will have a look and see if there's any possibility.... Anyhow, to make the notifier work just download one file from release page matching your system that's running, configure it via example yaml file and start it.
@LB If you're talking about renotification then it is already there
@scumdead Can you give it a go with new release?
https://gitlab.com/Toriniasty/reprap_notify/-/releases/v5
Also could you please write in english, I only understood what you've said because of the error in the post. Hope it will be all good now.
Also added re-notify feature.