check you donāt have ip_bans.yaml blocking your ip address
I donāt have an ip_bans.yaml. I really truly appreciate your help but we probably shouldnāt be doing all this in this thread. If you have any other ideas, feel free to PM me.
So how do you think upgrading HA core is going to make samba work?
1 Like
I donāt have a solution, but I have the exact same problem.
1 Like
Yes, it looks like the Logbook spam was fixed in 0.106.5 by this pull:
It seems like every update previously had a state record, just without updating last_changed. So hopefully no increase in db bloat? When Iām driving a lot OwnTracks can send a couple thousand updates in a day.
Wonder if this makes the Map location more accurate, or would trigger automations in more situations?
without changing anything in the recorder or plugwise settings (climate.kantoor), after updating to 106.5, my log is spammed with:
2020-03-05 16:27:18 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (MySQLdb._exceptions.OperationalError) (1205, 'Lock wait timeout exceeded; try restarting transaction')
[SQL: INSERT INTO states (domain, entity_id, state, attributes, event_id, last_changed, last_updated, created, context_id, context_user_id) VALUES (%s, %s, %s, %s, %s, %s, %s, %s, %s, %s)]
[parameters: ('climate', 'climate.kantoor', 'auto', '{"hvac_modes": ["heat", "auto"], "min_temp": 4, "max_temp": 30, "preset_modes": ["away", "vacation", "no_frost", "asleep", "home"], "current_temperat ... (916 characters truncated) ... \',\\n cooling:\'mdi:snowflake\',\\n auto:\'mdi:autorenew\'}\\nreturn icon[action] ? icon[action] : \'mdi:pause-circle\';\\n"}}', 49994523, datetime.datetime(2020, 3, 5, 15, 19, 52, 318206, tzinfo=<UTC>), datetime.datetime(2020, 3, 5, 15, 19, 52, 318206, tzinfo=<UTC>), datetime.datetime(2020, 3, 5, 15, 26, 27, 871974), 'e7f0b3bd7redacted74', None)]
(Background on this error at: http://sqlalche.me/e/e3q8)
and it is the only recorder issue mentioned.
not its not, few other entities are mentioned alsoā¦
2020-03-05 16:42:21 ERROR (Recorder) [homeassistant.components.recorder] Error in database connectivity: (MySQLdb._exceptions.OperationalError) (1205, 'Lock wait timeout exceeded; try restarting transaction')
[SQL: INSERT INTO events (event_type, event_data, origin, time_fired, created, context_id, context_user_id) VALUES (%s, %s, %s, %s, %s, %s, %s)]
[parameters: ('state_changed', '{"entity_id": "input_number.alarmclock_wd_hour", "old_state": null, "new_state": {"entity_id": "input_number.alarmclock_wd_hour", "state": "7.0", "at ... (245 characters truncated) ... :00", "last_updated": "2020-03-05T15:19:53.217977+00:00", "context": {"id": "5b3a29e9a1834a4cbb7814d26c881807", "parent_id": null, "user_id": null}}}', 'LOCAL', datetime.datetime(2020, 3, 5, 15, 19, 53, 218038, tzinfo=<UTC>), datetime.datetime(2020, 3, 5, 15, 41, 28, 8334), '5b3aredactedd26c881807', None)]
(Background on this error at: http://sqlalche.me/e/e3q8). (retrying in 3 seconds)
2020-03-05 16:42:21 ERROR (Recorder) [homeassistant.components.recorder] Error in database update. Could not save after 11 tries. Giving up
2020-03-05 16:43:12 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (MySQLdb._exceptions.OperationalError) (1205, 'Lock wait timeout exceeded; try restarting transaction')
[SQL: INSERT INTO events (event_type, event_data, origin, time_fired, created, context_id, context_user_id) VALUES (%s, %s, %s, %s, %s, %s, %s)]
[parameters: ('state_changed', '{"entity_id": "variable.virtual_light_daylight", "old_state": null, "new_state": {"entity_id": "variable.virtual_light_daylight", "state": "off : 1 : ... (141 characters truncated) ... :00", "last_updated": "2020-03-05T15:19:53.224020+00:00", "context": {"id": "e00e923122b34aa88c5224bbd75a50d8", "parent_id": null, "user_id": null}}}', 'LOCAL', datetime.datetime(2020, 3, 5, 15, 19, 53, 224085, tzinfo=<UTC>), datetime.datetime(2020, 3, 5, 15, 42, 21, 907690), 'e00e92redacted4bbd75a50d8', None)]
(Background on this error at: http://sqlalche.me/e/e3q8)
anyone else seeing this?
@bouwew would you know what causes this?
also, in a separate post for visibility:
still seeing:
2020-03-05 16:47:58 ERROR (MainThread) [homeassistant.components.hue.light] Error fetching group data:
2020-03-05 16:48:18 ERROR (MainThread) [homeassistant.components.hue.light] Error fetching group data:
2020-03-05 16:48:23 ERROR (MainThread) [homeassistant.components.hue.sensor_base] Error fetching sensor data:
2020-03-05 16:48:27 ERROR (MainThread) [homeassistant.components.hue.light] Error fetching light data:
2020-03-05 16:48:42 ERROR (MainThread) [homeassistant.components.hue.light] Error fetching group data:
in an undesirable quantity.
not fixed at all I am afraid, now how to ping Balloob without tagging himā¦
1 Like
Try stopping HA and deleting the database. It will recreate on startup.
k, thanks, using mariadb though so no database in the /config to delete I am afraid.
Have you restarted the mariadb?
just did, restarting, letās see what happens. thanks. I could witness a successful MariaDB restart fortunately.
If it comes down to it you could drop the HA tables 
Anyone know how frequently the coronavirus integration updates? Been 40 minutes for me now - not that itās vital - just was comparing the numbers in the integration versus the actual site, and they are different.
Just want to follow up that a solution has been found to the issue I posted yesterday about HA not startingā¦see https://github.com/home-assistant/core/issues/32514. It gets us back up and running, but something still needs to be fixed so it doesnāt happen to begin withā¦
1 Like
I suspect the coinmarketcap integration is broken as the underlying coinmarketcap public api has now been decommissioned.
Has anyone else experienced issues?
Scrolling bug still present on 106.5 and iPhone.
Still there on 106.5
Iāve opened the issue. Unfortunately I canāt seem to tag it, as I donāt have write access?