Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Permanent notification #933

Closed
marek-vrana opened this issue Jul 15, 2023 · 17 comments
Closed

[Feature Request] Permanent notification #933

marek-vrana opened this issue Jul 15, 2023 · 17 comments
Milestone

Comments

@marek-vrana
Copy link
Contributor

FEATURE DESCRIPTION

I'd like to display a permanent notification with popupNotify (until closed). Currently when I declare sleepTimeout in config it always fires with higher prio than the time sent with entityUpdateDetail command. Sending 0 with entityUpdateDetail also had the same effect, so it possibly may be a bug.

ADDITIONAL CONTEXT

N/A

PANEL / FIRMWARE VERION

EU

@joBr99
Copy link
Owner

joBr99 commented Jul 15, 2023

What's the timeout you are sending with popupnotify? 0 should work.

@marek-vrana
Copy link
Contributor Author

I'm sending it like this:

pageType~popupNotify
entityUpdateDetail~id~Title~65535~btn1~3840~btn2~61440~desc~65535~0

So by entityUpdateDetail I meant popup notify.

@joBr99
Copy link
Owner

joBr99 commented Jul 16, 2023

Just tested on my panel and it works fine.

Can you run weblog 3 in your tasmota console and post the log from tasmota from sending the notification until it's disappearing?

@marek-vrana
Copy link
Contributor Author

Well, setting sleepTimeout to 0 and adjusting anything in app.yaml afterwards will show the screensaver on my nspanel with missing icons. I'm using latest tft 4.1.1 and actually I'm using esphome - do you think it's more related to it?

@marek-vrana
Copy link
Contributor Author

okay, I did a bit more testing. The culprit here is the screensaver. Originally I thought it's because custom sensors, but I think it behaves the same with weather entities, it's just not that visible because of 1hr update interval.
So if you use a sensor with frequent refresh interval (e.g. local temperature sensor) in your screensaver, fullscreen notification get's overwritten.
Is there anything that can be fixed so that when notification fires, screensaver will not take precedence?

@joBr99
Copy link
Owner

joBr99 commented Jul 26, 2023

need to check in earlier versions the notification blocked weather/screensaver updates in the HMI Project

@antibill51
Copy link

I encounter the same problem.
The notification disappears after 15/20 seconds.

@joBr99
Copy link
Owner

joBr99 commented Aug 8, 2023

can you please send an exmaple of your popupNotify command's that have this issue?

@joBr99 joBr99 added this to the 4.2.X milestone Aug 8, 2023
@joBr99
Copy link
Owner

joBr99 commented Aug 8, 2023

So I've seen this on my panel a few times now, however I wasn't able to spot why the panel is switching to the screensaver and it's also not consistent for me. For the most time the notification stays there a really long time.

Can you enable run weblog 3 on the tasmota console and post the log during the moment the notification is going away?

@joBr99
Copy link
Owner

joBr99 commented Aug 8, 2023

okay nevermind, just had this again and the panel is requesting to exit the popup

21:03:03.203 MQT: tele/tasmota_nspwohn/RESULT = {"CustomRecv":"event,buttonPress2,popupNotify,bExit"}

@joBr99
Copy link
Owner

joBr99 commented Aug 8, 2023

I've uploaded an version that is showing the sleepValue and the sleepTimeout on the popup Page, maybe that helps to diagnose the Problem. In my tests both values stay zero so far :/

An workaround for a permanent notification in the meantime might be using an high value as timeout. Maximum should be 2147483647 seconds.
Would be interesting if the issue is also happening with this value too.

FlashNextion http://nspanel.pky.eu/nspanel-sleeptimer.tft

@joBr99
Copy link
Owner

joBr99 commented Aug 8, 2023

Using a high value and counting seconds seems to be way more stable than doing nothing.

Try latest development version; in case the sleepTimeout in the popupNotify is 0 it is now replacing zero with the number of seconds of a year.

FlashNextion http://nspanel.pky.eu/nspanel.tft

FlashNextion http://nspanel.pky.eu/lui.tft

@marek-vrana
Copy link
Contributor Author

Hi, I uploaded sleeptimer.tft to my panel and with both 4.1.4 and latest dev version can only confirm what I stated before:

  • When I omit custom sensors from screensaver and leave only Met.no entities, sleepTimeout and sleepValue stay at 0. When set to 2147483647 it's 2147483647 and timeout counting. Screensaver is not shown.

  • With custom sensors enabled, no matter if I use 0 or 2147483647, after couple of seconds sleepTimeout is overwritten with value from nspanel config's sleepTimeout (currently 5). In case I use 2147483647 sleep value sometimes reaches 28sec, sometimes 9, sometimes 2, 7.. it feels random. Hard to tell exactly when I use 0 as the count starts only once the value is overwritten.

screensaver:
  entities:
    - entity: sensor.gw2000a_v2_2_3_outdoor_temperature
    - entity: weather.home
      type: 0
    - entity: weather.home
      type: 1
    - entity: weather.home
      type: 2
    - entity: delete
    - entity: sensor.nspanel_temperature
      icon: mdi:home-thermometer-outline

I wasn't able to download tft from your latest post (404).

@joBr99
Copy link
Owner

joBr99 commented Aug 15, 2023

This would have been the correct URL:

FlashNextion http://nspanel.pky.eu/lui.tft

@marek-vrana
Copy link
Contributor Author

still behaves the same. Need to comment out custom sensors, otherwise screensaver is shown.

@joBr99
Copy link
Owner

joBr99 commented Aug 20, 2023

I've found the issue please reflash development version.

FlashNextion http://nspanel.pky.eu/lui.tft

@joBr99 joBr99 closed this as completed in e580333 Aug 20, 2023
github-actions bot pushed a commit that referenced this issue Aug 20, 2023
@marek-vrana
Copy link
Contributor Author

it works! thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants