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

petro · March 4, 2020, 1:48pm

I don’t know why you are complaining here about this card… it’s a custom card and with that comes the risk of it being deserted.

gkron · March 4, 2020, 1:50pm

Well I was letting people know if they use it and haven’t upgraded yet. Thought that was the right thing to do. Sorry for offending you.

petro · March 4, 2020, 1:52pm

You didn’t offend me. I just don’t see the point in complaining while informing

checkleylane · March 4, 2020, 6:11pm

calendar card seems to be broken in the latest update ~?

SkynetNexus · March 4, 2020, 8:47pm

Thankyou, not sure what the problem was then, I rebooted several times and tried accessing the shared folders from 2 computers with no luck.

I saw there was another upgrade 106.5, so I upgraded and Samba started working again.

Anwen · March 4, 2020, 10:59pm

I just updated from 0.105.5 to 0.105.6 (HA Supervised on Ubuntu 18.04 host on a NUC). I checked all the breaking changes, I updated everything in HACS, I checked my config with the Config checker add-on. All good. So I hit the update button. I now have no front end - no safe mode, no nothing, just a screen that says This site can't be reached, 192.168.0.151 refused to connect. I can SSH in and I have access to my files through WinSCP, but I have no idea what to fix. I did a config check and it completed successfully. My logs are empty. I tried downgrading to 0.105.5, and that completed successfully, but didn’t get me a front end. I tried upgrading back. No change. Here’s what I have:

➜  ~ ha core info
arch: amd64
audio_input: null
audio_output: null
boot: true
custom: false
image: homeassistant/intel-nuc-homeassistant
ip_address: 172.30.32.1
last_version: 0.106.5
machine: intel-nuc
port: 8123
ssl: false
version: 0.106.5
wait_boot: 600
watchdog: true

I tried to see if I could restore a snapshot somehow, but I can’t use hass-cli, I get the following error:

➜  ~ hass-cli info
error: HTTPError: 502 Server Error: Bad Gateway for url: http://hassio/homeassistant/api/discovery_info
Run with -x to see full exception information

I even tried rebuilding the core, but it just gives an error:

Processing... Done.

Error: Unknown Error, see logs

ha core logs shows me a blank file.

I’ve never had an issue upgrading in the two years I’ve been using HA. I would really appreciate some ideas for how to get myself back to normal!

DavidFW1960 · March 4, 2020, 11:06pm

Did you try rebooting the machine?

Anwen · March 4, 2020, 11:10pm

I haven’t, I thought about it but was afraid I might lose my ability to get back in. I’ll try it…

Anwen · March 4, 2020, 11:26pm

No dice. Tried rebooting, and then completely shutting down and restarting. I still don’t have a front end, or any errors in the log to figure out where to go next.

DavidFW1960 · March 4, 2020, 11:57pm

can you see if the homeassistant container is running?

Anwen · March 5, 2020, 12:10am

When I SSH into the host, docker ps shows me all the add-on containers, hassio_dns, hassio_audio, and hassio_supervisor running, but not home assistant. I tried to look at the supervisor log and its just a mass of errors of VSCode trying to connect to the API continuously scrolling:

20-03-04 22:32:38 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-03-04 22:32:38 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-03-04 22:32:38 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode

How can I get the home assistant container up and running?

DavidFW1960 · March 5, 2020, 12:19am

check you don’t have ip_bans.yaml blocking your ip address

Anwen · March 5, 2020, 12:27am

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.

nickrout · March 5, 2020, 5:36am

So how do you think upgrading HA core is going to make samba work?

dgaust · March 5, 2020, 7:05am

I don’t have a solution, but I have the exact same problem.

Martso · March 5, 2020, 11:35am

Yes, it looks like the Logbook spam was fixed in 0.106.5 by this pull:

github.com/home-assistant/core

Filter out duplicate logbook states

home-assistant:dev ← home-assistant:filter-duplicate-logbook-states

opened 04:31AM - 03 Mar 20 UTC

balloob

+43 -1

## Breaking change  ## Proposed change  Filter out duplicate states based on the state (not attributes). So if a light changes from brightness 50 to 100, don't make a new logbook event. This should make the logbook more readable. ## Type of change  - [ ] Dependency upgrade - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New integration (thank you!) - [x] New feature (which adds functionality to an existing integration) - [ ] Breaking change (fix/feature causing existing functionality to break) - [ ] Code quality improvements to existing code or addition of tests ## Example entry for `configuration.yaml`:  ```yaml # Example configuration.yaml ``` ## Additional information  - This PR fixes or closes issue: fixes #32434 and fixes #32257 - This PR is related to issue: - Link to documentation pull request: ## Checklist  - [ ] The code change is tested and works locally. - [ ] Local tests pass. **Your PR cannot be merged unless tests pass** - [ ] There is no commented out code in this PR. - [ ] I have followed the [development checklist][dev-checklist] - [ ] The code has been formatted using Black (`black --fast homeassistant tests`) - [ ] Tests have been added to verify that the new code works. If user exposed functionality or configuration variables are added/changed: - [ ] Documentation added/updated for [www.home-assistant.io][docs-repository] If the code communicates with devices, web services, or third-party tools: - [ ] The [manifest file][manifest-docs] has all fields filled out correctly. Updated and included derived files by running: `python3 -m script.hassfest`. - [ ] New or updated dependencies have been added to `requirements_all.txt`. Updated by running `python3 -m script.gen_requirements_all`. - [ ] Untested files have been added to `.coveragerc`. The integration reached or maintains the following [Integration Quality Scale][quality-scale]:  - [ ] No score or internal - [ ] 🥈 Silver - [ ] 🥇 Gold - [ ] 🏆 Platinum  [dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html [manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html [quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html [docs-repository]: https://github.com/home-assistant/home-assistant.io

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?

Anwen · March 5, 2020, 1:40pm

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

Mariusthvdb · March 5, 2020, 3:36pm

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?

Mariusthvdb · March 5, 2020, 3:55pm

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…

dap35 · March 5, 2020, 4:03pm

Try stopping HA and deleting the database. It will recreate on startup.