You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In case of a scraping error the 'last' value is retained, but only until a reboot.
At that point the sensor value becomes "unavailable" and any attributes are not available as well.
This situation persists until the scraping is successful.
Describe the solution you'd like
On error, it would be nice to make 'last' value persistent to prevent to lose it in case of a system reboot.
Attributes as well if possible.
Describe alternatives you've considered
A workaround is to manually create a template sensor that receives the value from the scarping sensor and updates it only if the state is not "unavailable".
The text was updated successfully, but these errors were encountered:
g1za
changed the title
Make the on-error value persistent
Feature request: Make the on-error value persistent
Oct 3, 2023
Is your feature request related to a problem? Please describe.
In case of a scraping error the 'last' value is retained, but only until a reboot.
At that point the sensor value becomes "unavailable" and any attributes are not available as well.
This situation persists until the scraping is successful.
Describe the solution you'd like
On error, it would be nice to make 'last' value persistent to prevent to lose it in case of a system reboot.
Attributes as well if possible.
Describe alternatives you've considered
A workaround is to manually create a template sensor that receives the value from the scarping sensor and updates it only if the state is not "unavailable".
The text was updated successfully, but these errors were encountered: