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
influxdb-related issue (I presume) - EDIT: also possibly the BOM Australia sensor component.
After upgrade, logs show the traceback below, but there aren't any obvious consequences of this - data is still being saved to the database as far as I can tell. There were no similar errors prior to the upgrade.
EDIT - on closer inspection, weather data from the BOM component is not being saved since the upgrade, though appears correctly in the history component.
2017-06-21 20:06:09 ERROR (Thread-7) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/influxdb.py", line 164, in influx_event_listener
json_body[0]['fields'][key] = float(value)
TypeError: float() argument must be a string or a number, not 'datetime.datetime'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
result = self.fn(*self.args, **self.kwargs)
File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/influxdb.py", line 170, in influx_event_listener
non_decimal.sub('', value))
TypeError: expected string or buffer
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
HASS 0.47.0
Python 3.4.2
influxdb-related issue (I presume) - EDIT: also possibly the BOM Australia sensor component.
After upgrade, logs show the traceback below, but there aren't any obvious consequences of this - data is still being saved to the database as far as I can tell. There were no similar errors prior to the upgrade.
EDIT - on closer inspection, weather data from the BOM component is not being saved since the upgrade, though appears correctly in the history component.
The text was updated successfully, but these errors were encountered: