2024-06-27, 05:08 AM
Well, this works kinda as designed: you engine is sending frequent 127489 pgn messages with status fields in normal state. These get translated to notifications, in normal state. The number of messages is not a problem in itself, even if this is a bit verbose.
What is a bit off is that the notification in normal state has method as visual, when notifications in normal state should have method as empty. This is easy to fix.
The real problem seems to be that openplotter-notifications shows each notification separately. In this kind of situation where a device sends frequent notifications the system gets bogged down trying to display them individually. If there is a real error state in 127489 it will result in repeated notifications, but for the same path, so a new update should be treated as the same notification, not a separate one.
So even if we drop the method is visual a real problem with the engine would cause the same runaway openplotter-notifications overloading your system.
What is a bit off is that the notification in normal state has method as visual, when notifications in normal state should have method as empty. This is easy to fix.
The real problem seems to be that openplotter-notifications shows each notification separately. In this kind of situation where a device sends frequent notifications the system gets bogged down trying to display them individually. If there is a real error state in 127489 it will result in repeated notifications, but for the same path, so a new update should be treated as the same notification, not a separate one.
So even if we drop the method is visual a real problem with the engine would cause the same runaway openplotter-notifications overloading your system.