After updating to version 4.3.3, a problem reappeared, which constantly reappears and is as annoying as can be.
It is about the fact that after a scene is triggered in which an alarm sound was set on NSPanel Pro, the message “Triggered by NSPanel - Devices locates: home name” appears on the display.
Normally, that message should disappear depending on the display setting, in 15, 30 … seconds. Unfortunately, after the message appears on the display, it remains permanently active, until the “Back” button is pressed.
Is there a possibility that this problem can be fixed forever?
I know that there is a version in the works in which there is a fix for this problem, but that version when I tested it presented a lot of problems, which is why I gave up.
It would be useful if the problem were fixed.
I understand what you mean. The issue is that the pop-up still doesn’t disappear after 15 or 30 seconds as set, right?
This is because this type of notification is considered important—we’re concerned that if it disappears automatically, users might miss it. So it stays on-screen to ensure the user sees it and closes it manually.
In version 4.4.x, we’ve optimized the notification settings. Users can now choose between alarm only or pop-up + alarm . If the alarm option is selected, similar pages will no longer appear.
Thank you for your answer.
I understand your logic related to the alert message displayed on NSPanel.
Unfortunately, this logic, in everyday life, is a wrong logic.
The displayed message is a general message.
Based on the displayed message, neither the device nor the scene that triggered that message can be identified.
From my point of view, it is illogical to display a message that does not contain any useful information and even less do I see the logic related to displaying the message permanently, until the user’s manual intervention.
As a result, for me, a user of NSPanel for years, that message is completely useless, pointless.
Here is an example:
I have a scene that triggers a sound on NSPanel when the apartment entrance door is opened. Based on the displayed message, I have no way of knowing what triggered it. Only based on the set sound can the source of the displayed message be identified. For example, if I leave home, when I leave, the scene that starts the alarm sound on the NSPanel is triggered. That message triggered by my leaving home remains permanently displayed and the display heats up and becomes a heat source. Another example is related to the moment when a scene is triggered or the status of a device changes, at night. If the NSPanel is installed in a bedroom or even a living room, it is extremely annoying to wake up from sleep because a message appears on the display, a message that disappears only if you move to the device and make a tap!
At the moment, the only solution is to turn off the power to the NSPanel both when leaving home and every evening.
Please make an effort and if possible, hurry up with the implementation of the user’s right to choose whether or not they need a message that does not provide any indication of the event that triggered it.
Thank you.
Thank you for your detailed explanation. In version 4.4.0, we allow users to customize notification content, so you can set text that reminds you more effectively.
Regarding whether the pop-up can disappear along with the set alert sound, we can discuss this further. Currently, if there’s a specific time period during which you don’t want to receive notifications, you can set a scene to define the effective time range.
If your NSPanelPro is upgraded to version 4.3.x or above, and the app is updated to the latest version, you will see a separate option when setting up scenes:
“Alarm Beeps” (without displaying a pop-up on the device screen).
I’ve recorded a video—please take a look.
Thanks for the reply.
I tried to look at your recording but it’s just a photo.
In the meantime I discovered the new scene format for NSPanel, where there is a solution for the problems I reported.
In the description of the new update I didn’t notice any reference to the changes in the scenes, or maybe I overlooked them, which is why I didn’t look for the solutions there.
The extended scene format for NSPanel allows you to choose the type of notification and allows you to add a message to identify the source of the notification.
For those who have encountered similar problems, I recommend deleting the scenes related to nSPane and adding them again because I noticed that in certain situations the changes made were not saved.
