0.106: Light brightness stepping, better Safe Mode and person dialog

There’s more people with the same problem here. I’m glad to know it’s not just me.

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 :frowning:

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.

Capture

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

Looks like hourly. source

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?

https://github.com/home-assistant/core/issues/32584

Wohooooo brightness_step_pct is definitly a big deal ! :slight_smile:

But wouldn’t it be absolute consistent and super cool if you do the same on all the other direct related guys?
I mean:
color_temp_step_pct
white_value_step_pct

:heart_eyes:
#justaIdea

Did you figure this out? I upgraded last night and my floorplan no longer works giving the same error.

There is an issue open with the card developer for this:

Thanks @tom_l , this fixed for me:

1. floorplan.js
Line 61 of floorplan.js
this.config = Object.assign({},config);

2. floorplan-card.js
Can you change line 16 or 17 to
this.config = JSON.parse(JSON.stringify(config));

3. clear app & browser cach

Yes CMC is totally broken. But BitFetch just released a custom component that is almost a drop in replacement for CMC and has numerous other benefits as well (more generous API limits, faster response time, live instead of delayed data, etc).