-
-
Notifications
You must be signed in to change notification settings - Fork 122
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] Don't send zero temperature/hum after reboot #354
Comments
It would be sufficient to send no value at after reboot until the values are stable.
|
The same is also true for the battery levels. Here is a chart from MQTT explorer you can see that after a reboot, first a value of zero and immediately afterwards a value of >2400 is reported, before awtrix settles on the correct value of about 600. Is this a reading error during the startup phase or an intialization error? |
Many things are possible. On the other hand i have no knowledge in filtering techniques. |
Looking at the code I think that one problem is that the sensor values may not have been read yet, when they are sent for the first time. Both reading and sending interval are set to 10 seconds by default. |
@Blueforcer In my setup the problem is that I am controlling thermostat with the temperature from awtrix. If the temperature drops to zero, my thermostat turns on. |
The first part is done (no PR yet). Zero values are not sent anymore. Here's the graph (from LTR: batt_raw batt_%, temp, hum, ldr_raw). The first two peaks in each graph are reboots with the 0.90 version. The third reboot with my reworked version shows only a peak in batt_raw (high) and ldr_raw (low). The zero values are already sorted out. I moved the Ulanzi on the second reboot, that's why the ldr_raw value changes (and probably also temp/hum start to creep, because the brightness went up). |
Feature Request
Describe the solution / feature you'd like
After every(?) reboot Awtrix sends zero temperature and humidity to MQTT. Is it possible to send any other value instead? Like Not available?
Describe alternatives you've considered
As a workaround, I can use fitler in Home Assistant to filter these values.
Additional context
The text was updated successfully, but these errors were encountered: