Incorrect values in some sensors
dmsims opened this issue · 12 comments
Car is unlugged (my wife has taken it to work at 7.40am - time now 12.02pm) some sensors show incorrect values e.g.
Power Draw 2,000W
Current Draw 8.1A
Car connected Plugged in
Expected behavior
Sensors should be zero or correct value
Screenshots
Home Assistant Version
Core
2024.1.0
Supervisor
2023.12.0
Operating System
11.2
Frontend
20240103.3
Integration Version
v0.3.1
Additional context
Using Chrome on Windows 11 - Refresh, shift Refresh or closing HA tab and reopening a new HA tab does not change the values
Does the Ohme app think the car is still plugged in? What does the sensor for Charger online show?
Can you double check the version please (and that if you've updated, you restarted home assistant after)? I'd expect to see the 'Charger Online' sensor if on 0.3.1 (unless you've disabled/hidden it of course).
Could you also check that the Ohme app is reporting values correctly and if you have any errors in the home assistant log.
Yep v0.3.1 just had not updated the Dashboard
Ohme app
Cannot see anything relevant in logs:
Error while dispatching event for sensor.victron_battery_timetogo_239 to <Job track state_changed event {'sensor.victron_battery_timetogo_239'} HassJobType.Callback <bound method TrackTemplateResultInfo._refresh of <TrackTemplateResultInfo {Template<template=({% set s = states('sensor.victron_battery_timetogo_239')|int %} {{ '%02d:%02d' % ((s/3600)|int, (s%3600)/60) }}) renders=1268>: <RenderInfo Template<template=({% set s = states('sensor.victron_battery_timetogo_239')|int %} {{ '%02d:%02d' % ((s/3600)|int, (s%3600)/60) }}) renders=1268> all_states=False all_states_lifecycle=False domains=frozenset() domains_lifecycle=frozenset() entities=frozenset({'sensor.victron_battery_timetogo_239'}) rate_limit=None has_time=False exception=None is_static=False>}>>>
12:31:14 – (ERROR) helpers/event.py - message first occurred at 3 January 2024 at 22:15:43 and shows up 636 times
Error doing job: Task exception was never retrieved
12:31:03 – (ERROR) Volkswagen We Connect ID (custom integration) - message first occurred at 3 January 2024 at 23:09:36 and shows up 1002 times
/vehicles/WVWZZZE1ZMP059574/domains/automation/chargingProfiles: Unknown attribute nextChargingTimer with value {'id': 0, 'targetSOCreachable': 'invalid'}
12:31:03 – (WARNING) Volkswagen We Connect ID (custom integration) - message first occurred at 3 January 2024 at 23:08:42 and shows up 11086 times
Failed to retrieve new electricity rates for 2200019751366/19L3494714 - using cached rates. Next attempt at 2024-01-04 01:38:53.890141+00:00
10:31:03 – (WARNING) Octopus Energy (custom integration) - message first occurred at 01:37:09 and shows up 6 times
Failed to connect. Timeout of ClientTimeout(total=15, connect=None, sock_read=None, sock_connect=None, ceil_threshold=5) exceeded.
10:31:03 – (WARNING) Octopus Energy (custom integration) - message first occurred at 01:37:09 and shows up 6 times
Failed to retrieve smart meter consumption data - using cached version. Next attempt at 2024-01-04 02:55:25.099889+00:00
10:30:48 – (WARNING) Octopus Energy (custom integration) - message first occurred at 01:38:30 and shows up 25 times
Failed to connect. Timeout of ClientTimeout(total=15, connect=None, sock_read=None, sock_connect=None, ceil_threshold=5) exceeded.
10:30:48 – (WARNING) Octopus Energy (custom integration) - message first occurred at 01:37:29 and shows up 24 times
Error handling request
10:22:55 – (ERROR) /usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py - message first occurred at 08:03:34 and shows up 3 times
Error fetching switch_leds data: The device is currently not available. Maybe on standby?
08:52:46 – (ERROR) devolo Home Network - message first occurred at 3 January 2024 at 23:24:44 and shows up 5 times
Looks like a lot of network errors from other integrations - are you getting updates on anything? (VW and Octopus, for example).
The Ohme app screenshot you have posted suggests that Ohme thinks the car is still plugged in. Worth trying to reboot the Ohme charger? Not sure if that will fix it, but you shouldn't see the complete screen if the car is unplugged.
Ohme App should look like this if it thinks car is unplugged.
The Ohme app screenshot you have posted suggests that Ohme thinks the car is still plugged in.
It does indeed. It should show 'Not Plugged In' at the top of the screen. I would power the Ohme off for 10 minutes at the fusebox, looks like it is offline.
Cycled the charger for 10 mins
The Charger online sensor in the integration updated correctly:
The Ohme app still shows exactly the same screen (even killed it and restarted)
Charger shows as online in app
You may have to plug in and unplug for it to reset the status
I went and looked at the actual charger (but the app still showed it as being plugged in)
As soon as I plugged the car in the Ohme screen changed to "Smart charging" and all the values in the integration returned to those expected
If its all working for now I'll close this down and put it down to an API issue.
Dan