-
Notifications
You must be signed in to change notification settings - Fork 29
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
Spikey/erroneous values #77
Comments
Hi,
I am currently working on filtering error values and submitting nan instead.
If you don't like the nan you can add `filter_out: nan` to remove them. See esphome manual <https://esphome.io/components/sensor/index.html#filter-out>.
Cheers Fabian
…On 16 December 2024 5:48:44 pm GMT+00:00, geftactics ***@***.***> wrote:
Been running for a while and seeing a few odd spikes:
BATTERY_VOLTAGE (Smart Shunt) - Usually ~12.6v, but I saw one reading today of -114.45v
PV_POWER (Smart Solar) - Usually 4w, but saw 18435w
I saw similar in another issue there were NAN issues, but not sure if this is the same? Maybe we could add some logic to try and detect and filter erroneous values (It could be the victron kit sending these, I've not yet managed to find out of this is the case)
--
Reply to this email directly or view it on GitHub:
#77
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
|
Hi @geftactics I just released an update to fix the spikey values issues. Can you please test and report back if the issue is fixed for you? |
Just rebuilt today, will report back soon! |
EPSHome caches the git repo for 24h. So unlikely that this an issue. Have you also added a Do you have the exact value received? I am assuming this is the BATTERY_VOLTAGE of a Smart Shunt? |
Been running for a couple of days and seeing a few odd spikes:
BATTERY_VOLTAGE (Smart Shunt) - Usually ~12.6v, but I saw one reading today of -114.45v
PV_POWER (Smart Solar) - Usually 4w, but saw 18435w
I saw similar in another issue there were NAN issues, but not sure if this is the same? Maybe we could add some logic to try and detect and filter erroneous values (It could be the victron kit sending these, I've not yet managed to find out of this is the case)
The text was updated successfully, but these errors were encountered: