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

Custom app not removed after time set through "lifetime" value #335

Closed
Kefut opened this issue Sep 25, 2023 · 9 comments
Closed

Custom app not removed after time set through "lifetime" value #335

Kefut opened this issue Sep 25, 2023 · 9 comments
Labels
bug Something isn't working

Comments

@Kefut
Copy link

Kefut commented Sep 25, 2023

Hi,

I'm using a Ulanzi TC001 with AWTRIX-LIGHT v0.48 and publish custom apps through MQTT from Homeassistant.
As you can see from the snippet below I try to delete the custom app after 24h (86400 seconds) in case there has not been an update. Unfortunately the "lifetime" value doesn't seem to work as the app just doesn't disappear.

service: mqtt.publish data: qos: 0 retain: false topic: awtrix_1/custom/batwarn payload: >- { "text": "{{sensors}}", "icon": 12123, "textCase": 2, "save": true, "lifetime": 86400, "scrollSpeed": 75, "repeat": 1}

Is this a bug or am I doing something wrong here?

Thanks for your help

@Kefut Kefut added the bug Something isn't working label Sep 25, 2023
@Blueforcer
Copy link
Owner

Blueforcer commented Sep 25, 2023

Of course you're doing something wrong:
Don't open a issue with such an old firmware version. We're at 0.88...
Feel free to reopen, if you have the same issue with the latest firmware

@Kefut
Copy link
Author

Kefut commented Sep 25, 2023

My mistake - I am actually on 0.88! 0.48 was a typo. Sorry for the confusion.

@Blueforcer Blueforcer reopened this Sep 25, 2023
@Blueforcer
Copy link
Owner

Blueforcer commented Sep 25, 2023

You need to set the lifetime in seconds.
Not milliseconds. In your case it would take a very long time to disappear 😄

@Kefut
Copy link
Author

Kefut commented Sep 25, 2023

I want 24h, so it's 24 x 60 x 60 --> 86400sec

@Blueforcer
Copy link
Owner

I'm not sure it's made for such a long period ..
Need to check it this afternoon.

@Kefut
Copy link
Author

Kefut commented Sep 25, 2023

Thanks for checking - didn't see any limitations in the docu besides that the number needs to be an integer and didn't expect 1day to be too long.

Blueforcer added a commit that referenced this issue Oct 15, 2023
### New Features ( for my Copycats ;-) )
- Adds API to put AWTRIX into deepsleep.  #326
- Adds dev setting to enable/disable dfplayer for old Awtrix2_Convertion (its disabled by default)

### Fixes
Minor bugfixes #345 #338 #335
@Blueforcer
Copy link
Owner

Should be fine now by change the datatype to long.
I didnt test it with 24h, please feel free to reopen the issue if the problem still persist

@Kefut
Copy link
Author

Kefut commented Oct 24, 2023

Just checked and unfortunately it's still not working.

@heimchemiker
Copy link

I also have this problem. I'm using OpenHAB to publish this data to my MQTT Server, but this should not make a difference. I want it to not show the solar production one hour (=3600s) after it turned to "producing" 0 W. Here my last MQTT publish is from 21:47 (it's now 2:13, so this last change was ~4.5h ago), the MPTT Message was:
{ "icon": "sol-stop", "text": "0 W", "duration": 5, "color": "#FFFFFF", "progress": 0, "progressC": "#FFFFFF", "progressBC": "#222222", "lifetime": 3600 }
And it was still displaying the message.
I'm on version 0.96

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants