You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
No audio cues on PAUSE or filament runout
Describe the solution you'd like
An in browser audio cue when the printer is paused or has run out of filament
Describe alternatives you've considered
I realise there are other options such as Moonraker Push Notifications, Beeper in Klipper and Telegram, however I don't always have my phone near me or it is on silent/DND and my printers don't have a beeper.
I do however, always have a fluidd instance open on at least 2 computers (desktop in office, laptop in printer room), so it would be nice to have a natively supported and user friendly check box in options to notify of printer status changes.
Additional information
I realise that this has been discussed previously in both #129 & #520 however, we have moved on since 2022 and fluidd has matured since then, so I thought I'd open this back up for discussion.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
No audio cues on
PAUSE
or filament runoutDescribe the solution you'd like
An in browser audio cue when the printer is paused or has run out of filament
Describe alternatives you've considered
I realise there are other options such as Moonraker Push Notifications, Beeper in Klipper and Telegram, however I don't always have my phone near me or it is on silent/DND and my printers don't have a beeper.
I do however, always have a fluidd instance open on at least 2 computers (desktop in office, laptop in printer room), so it would be nice to have a natively supported and user friendly check box in options to notify of printer status changes.
Additional information
I realise that this has been discussed previously in both #129 & #520 however, we have moved on since 2022 and fluidd has matured since then, so I thought I'd open this back up for discussion.
The text was updated successfully, but these errors were encountered: