lethuer

I have the exact same problem with telegram notifications !

> I have the exact same problem with telegram notifications ! Again I enabled Octolapse plugin and remembered this bug with many telegram notifications. Is there any progress in solving...

> This is also a problem when using Octolapse - [this line](https://github.com/fabianonline/OctoPrint-Telegram/blob/b1f90950293575005d3be4d791602a662222a366/octoprint_telegram/telegramNotifications.py#L241) causes notifications every time octolapse performs a z-hop after a snapshot. > > Octolapse is using relative positioning,...

Sometimes I also observe that described behaviour, but isn't needed to print something. Just turn on the plug, connect and wait should turn off the printer. My idle time is...

Here are my settings.   For M81 I included the ip address... But the plug didn't switched off. In terminal: `Send: M81 192.168.178.46 Recv: M106 P0 S0 Recv: //action:notification...

Awesome ! That works immediately if I send this manually in terminal :) Now let me ask: After Idle time I can't observe M81 command in the terminal. If gcode...

Okay I will try if it is waited until reaching desired nozzle temperature... Is here the correct location ? 

I also configured @TPLINKOFF code in section of cancelling a print. Unfortunately I can't observe in terminal that this is sent. Not directly after aborting the print and also not...

I tried again and now received this: `Changing monitoring state from "Printing" to "Cancelling" Send: N15 M108*30 Recv: ok N14 P15 B3 Recv: ok N15 P15 B3 Send: N16 M117...

> Based on your printer response to m81 I suspect the other option of using @TPLINKOFF command would be better But I didn't observe any command is sent if @TPLINKOFF...