[3.4.2 - 3.4.4] Persistent Event Notification after no Filament
-
Duet 6HC 3.4.2 - 3.4.4 running on an SBC. We are actually unsure which version this started happening with, but it's been recent. There appears to be an issue where the noFilament event gets stuck in queue when triggered. Acknowledging the notification clears the issue within that browser, but opening a browser on a different PC well after filament has been loaded and in the middle of the next job still results in the prompt.
Below are what is found in the Object Browser. @chrishamm - please let us know if you need any further info as this is pretty easy to recreate.
And the current state of the Filament Sensor:
-
@oozeBot it's been a persistent issue for quite a while https://forum.duet3d.com/topic/28788/event-notifications-not-dismissing-on-multiple-clients
It's getting fixed in 3.5 I believe -
@jay_s_uk yes it's already fixed in 3.5.
