Where is the Show HTML5 desktop notifications menu describe here :
https://duet3d.dozuki.com/Wiki/Duet_Web_Control_Manual#Section_Notifications
??

Sorry I cannot tell what version of web interface, it's a new fresh install and i'm new to duet, but I've updated everything to the latest versions available (RFF3, last firmware, last web version)

Thanks

@the_dragonlord I don't remember if I did the file or get on the web but you have to make duetbot as a service with a file "duetbot.service" or whatever into /etc/systemd/system as root

File content (edited):

[Unit]
Description=node js duetbot for telegram
#after network is up
After=network.target 

[Service]
WorkingDirectory=/usr/bin
ExecStart=duetbot
Restart=on-failure
RestartSec=1500ms
Type=forking
#user pi or root, will determine where the script will search the configuration file **.duetbot.json** 
User=pi
# Note Debian/Ubuntu uses 'nogroup', RHEL/Fedora uses 'nobody'
Group=nogroup
Environment=PATH=/usr/bin:/usr/local/bin
Environment=NODE_ENV=production
# log send to syslog
StandardOutput=syslog
StandardError=syslog

# syslog name id
SyslogIdentifier=duetbot

[Install]
WantedBy=multi-user.target

And don't forget to execute after that :

#to load the file for the systemctl manager
systemctl daemon-reload

# to start and test
service duetbot start 

# to check if loaded an active
service duetbot status 

# if all is good you can tell the system to execute it as a service on boot :
systemctl enable duetbot

#if it's ok the system will respond :
Created symlink /etc/systemd/system/multi-user.target.wants/duetbot.service → /etc/systemd/system/duetbot.service.

Excellent job ! Thanks

OK guys, maybe you will tell me I'm not doing the right way but it took me some time to find the information...
Because I was searching here :
https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md

But at least I've found the correct changes notes here :
https://github.com/Duet3D/DuetWebControl/releases

Question: what are you doing such confusing things ? Every time I'm searching the documentation it's a pain ! too much documents with too much versions !!

I think I understood, I've upgraded the firmware (combined) and I checked the releases notes with it ... but at least the bin file upgraded the Web interface...and not the firmware by the way, when I checked I see "RepRapFirmware for Duet 2 WiFi/Ethernet 3.1.1 (2020-05-19b2)" instead of the 3.2.0-b2

Thanks guys for the support

Thanks guys

that's ok now thank you , I just have Z stall height errors, I need to tune that.

I just want to know how can it be done, make an emergency stop in case of heater failure (or at least a pause during the print).
Is it possible ?

Very weird but errors disappears as they came...

My errors are disappears now (at least those, I have others..)

But what about the warning and not a critical default and automatic print stop in case of heater fault ???

@zerspaner_gerd It was that, thanks !!

but now I have a new error, I don't think it's relative but appeared right after the change :
Error: M106: Fan number 2 not found

It appear twice, the only call to M106 en config is this :

; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

No call to a fan number 2...

Thanks

@zerspaner_gerd you are certainly right, I will modify this (this is my gcodes than I uses on Marlin, I just went to Duet a few days ago...)

And btw T0 is not the solution, tested without luck.

Thanks guys, I'll post results when I could try

here the begining of one gcode file:

; generated by PrusaSlicer 2.2.0+win64 on 2020-05-24 at 17:05:55 UTC

M107

M582 T1 ; check if filament is present

M220 S100 ;Reset Feedrate
M221 S100 ;Reset Flowrate

M140 S55 R40 ; set bed temp
M190 S55-10 ; wait for bed temp
M104 S210 ; set extruder temp

M300 S40 P10 ; chirp

M118 P3 S"HOMING" ; message HTTP
M118 P4 S"HOMING" ; message TELNET

G28 ; Home all axes
;M420 S1; restore manual mesh

M300; beep
G92 E0 ;Reset Extruder
G1 Z2.0 F3000 ;Move Z Axis up
G1 X5 Y20 Z2.0 F3000.0 ; Move to start position
M109 S210 ; wait for extruder temp
G1 X5 Z0.3
G1 X5 Y200.0 Z0.3 F1500.0 E15 ; Draw the first line
G1 X5 Y200.0 Z0.3 F5000.0 ; Move to side a little
G1 X5.4 Y20 Z0.3 F1500.0 E30 ; Draw the second line
G92 E0 ; Reset Extruder
G10 S1; retract
G1 Z10 F3000 ; Move Z Axis up
G1 X30
G11; recover after retraction G10

M118 P4 S"PRINT_START" ; message TELNET
G21 ; set units to millimeters
G90 ; use absolute coordinates
M82 ; use absolute distances for extrusion
G92 E0
; Filament gcode
G1 Z0.260 F30000.000
G1 E-3.00000 F2700.00000
G92 E0
G1 X64.064 Y47.624 F30000.000
G1 E3.00000 F2700.00000
G1 F1200.000
G1 X65.084 Y46.449 E3.07805
G1 X66.328 Y45.514 E3.15611
G1 X67.739 Y44.860 E3.23416
G1 X100.092 Y36.264 E4.91391
G1 X101.141 Y36.067 E4.96746

It happen on all my prusaslicer generated gcodes, just after the start gcode, I didn't found any M104 S1 in the code.
I'll send the code tomorrow now, going to sleep right now.

But yes the gcode seems to send a heater temp to 1 just before print and the warning came later when it detect that the temp is to low to extrude, but it does not stop the print !