I updated to 0.76 and now my configuration says invalid for all the entities, help please !!
I added the authorization in my config file and now i’m getting the below message every time I refesh the website and the ios app. Is this normal?
config:
# add this part for authorization
auth_providers:
- type: homeassistant
# uncomment this to enable backwards compatible API password support
# - type: legacy_api_passwordAs instructed in the error log maintaining the following in config fixed my problem.
mqtt:
username: USER
password: PASSWORD
Only password need, username is not.
to keep everything in backward compatibility, you can use http.api_password as mqtt.password, e.g.
http:
api_password: !secret http_password
mqtt:
password: !secret http_password
could #15929 be a wrong link?
think you had a paste-error.
this would be the correct one https://github.com/home-assistant/home-assistant/pull/15929
thx!
1 reply
60 <-> 59, shift one column on keyboard 
You need to enable legaci_api_password auth_provider for now. We are working on decouple REST API with HTTP api_password, please check https://github.com/home-assistant/home-assistant/issues/15376 for more details.
I’m on 10.1.30-MariaDB-1~jessie (Docker) and had no issues with the migration.
The logger / recorder are not working after upgrading to this version 
I’m running a MariaDB on another server on my local network.
db_url: mysql://USERNAME:PASSWORD@IP-ADDRESS/hass_db?charset=utf8l
aug. 18 00:52:20 hass hass[24522]: 2018-08-18 00:52:20 INFO (MainThread) [homeassistant.bootstrap] Home Assistant core initialized
aug. 18 00:52:21 hass hass[24522]: 2018-08-18 00:52:21 INFO (MainThread) [homeassistant.loader] Loaded history from homeassistant.components.history
aug. 18 00:52:21 hass hass[24522]: 2018-08-18 00:52:21 INFO (MainThread) [homeassistant.loader] Loaded recorder from homeassistant.components.recorder
aug. 18 00:52:21 hass hass[24522]: 2018-08-18 00:52:21 INFO (MainThread) [homeassistant.loader] Loaded http from homeassistant.components.http
aug. 18 00:52:21 hass hass[24522]: 2018-08-18 00:52:21 INFO (MainThread) [homeassistant.loader] Loaded frontend from homeassistant.components.frontend
aug. 18 00:52:21 hass hass[24522]: 2018-08-18 00:52:21 INFO (MainThread) [homeassistant.loader] Loaded api from homeassistant.components.api
aug. 18 00:52:21 hass hass[24522]: 2018-08-18 00:52:21 INFO (MainThread) [homeassistant.loader] Loaded websocket_api from homeassistant.components.websocket_api
aug. 18 00:52:21 hass hass[24522]: 2018-08-18 00:52:21 INFO (MainThread) [homeassistant.loader] Loaded system_log from homeassistant.components.system_log
aug. 18 00:52:22 hass hass[24522]: 2018-08-18 00:52:22 INFO (MainThread) [homeassistant.loader] Loaded auth from homeassistant.components.auth
aug. 18 00:52:22 hass hass[24522]: 2018-08-18 00:52:22 INFO (MainThread) [homeassistant.loader] Loaded onboarding from homeassistant.components.onboarding
aug. 18 00:52:22 hass hass[24522]: 2018-08-18 00:52:22 INFO (MainThread) [homeassistant.loader] Loaded mqtt from homeassistant.components.mqtt
aug. 18 00:52:22 hass hass[24522]: 2018-08-18 00:52:22 INFO (MainThread) [homeassistant.loader] Loaded logger from homeassistant.components.logger
aug. 18 00:52:22 hass hass[24522]: 2018-08-18 00:52:22 INFO (MainThread) [homeassistant.setup] Setting up logger
aug. 18 00:52:25 hass hass[24522]: 2018-08-18 00:52:25 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8)
aug. 18 00:52:25 hass hass[24522]: 2018-08-18 00:52:25 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
aug. 18 00:52:25 hass hass[24522]: 2018-08-18 00:52:25 WARNING (MainThread) [homeassistant.components.http] Experimental auth api enabled and legacy_api_password support enabled. Please use access_token instead api_password, although you can still use legacy api_password
aug. 18 00:52:31 hass hass[24522]: 2018-08-18 00:52:31 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8)
aug. 18 00:52:31 hass hass[24522]: 2018-08-18 00:52:31 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
aug. 18 00:52:34 hass hass[24522]: 2018-08-18 00:52:34 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds.
aug. 18 00:52:34 hass hass[24522]: 2018-08-18 00:52:34 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8)
aug. 18 00:52:34 hass hass[24522]: 2018-08-18 00:52:34 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
aug. 18 00:52:37 hass hass[24522]: 2018-08-18 00:52:37 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8)
aug. 18 00:52:37 hass hass[24522]: 2018-08-18 00:52:37 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
aug. 18 00:52:41 hass hass[24522]: 2018-08-18 00:52:41 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8)
aug. 18 00:52:41 hass hass[24522]: 2018-08-18 00:52:41 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
aug. 18 00:52:44 hass hass[24522]: 2018-08-18 00:52:44 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8)
aug. 18 00:52:44 hass hass[24522]: 2018-08-18 00:52:44 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
aug. 18 00:52:47 hass hass[24522]: 2018-08-18 00:52:47 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8)
aug. 18 00:52:47 hass hass[24522]: 2018-08-18 00:52:47 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
aug. 18 00:52:50 hass hass[24522]: 2018-08-18 00:52:50 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8)
aug. 18 00:52:50 hass hass[24522]: 2018-08-18 00:52:50 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
aug. 18 00:52:53 hass hass[24522]: 2018-08-18 00:52:53 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8)
aug. 18 00:52:53 hass hass[24522]: 2018-08-18 00:52:53 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
aug. 18 00:52:57 hass hass[24522]: 2018-08-18 00:52:57 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8)
aug. 18 00:52:57 hass hass[24522]: 2018-08-18 00:52:57 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (_mysql_exceptions.OperationalError) (1060, "Duplicate column name 'context_id'") [SQL: 'ALTER TABLE events ADD COLUMN context_id CHARACTER(36)'] (Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
aug. 18 00:52:57 hass hass[24522]: 2018-08-18 00:52:57 ERROR (MainThread) [homeassistant.setup] Setup failed for recorder: Component failed to initialize.
aug. 18 00:52:57 hass hass[24522]: 2018-08-18 00:52:57 ERROR (MainThread) [homeassistant.setup] Unable to setup dependencies of history. Setup failed for dependencies: recorder
aug. 18 00:52:57 hass hass[24522]: 2018-08-18 00:52:57 ERROR (MainThread) [homeassistant.setup] Setup failed for history: Could not setup all dependencies.
aug. 18 00:52:59 hass hass[24522]: 2018-08-18 00:52:59 ERROR (MainThread) [homeassistant.setup] Unable to setup dependencies of history_graph. Setup failed for dependencies: history
aug. 18 00:52:59 hass hass[24522]: 2018-08-18 00:52:59 ERROR (MainThread) [homeassistant.setup] Setup failed for history_graph: Could not setup all dependencies.
aug. 18 00:52:59 hass hass[24522]: 2018-08-18 00:52:59 ERROR (MainThread) [homeassistant.setup] Unable to setup dependencies of logbook. Setup failed for dependencies: recorder
aug. 18 00:52:59 hass hass[24522]: 2018-08-18 00:52:59 ERROR (MainThread) [homeassistant.setup] Setup failed for logbook: Could not setup all dependencies.
Your db migration failed for some reason, and the migration process is not protected by transaction, so you either modify the database schema by yourself (see: 0.76 Migration Fails against MSSQL), or delete the database and home-assistant will recreate one for you.
Unable to click any sensors in the web UI after the update, nothing pops up. Also missing stuff from the config sections. It does work in the mobile browser however…not PC. Also getting the save password popup every time (have not added the new auth config).
nothing works, log is full with syntax errors. wtf
2018-08-18 12:54:27 ERROR (MainThread) [homeassistant.components.notify] Unknown notification service specified
Aug 18 12:54:27 raspberrypi hass[3005]: (standard_in) 1: syntax error
Aug 18 12:54:28 raspberrypi hass[3005]: 2018-08-18 12:54:28 ERROR (MainThread) [homeassistant.setup] Unable to setup dependencies of switch.mqtt. Setup failed for dependencies: mqtt
Aug 18 12:54:28 raspberrypi hass[3005]: 2018-08-18 12:54:28 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform switch.mqtt: Could not setup all dependencies.
Aug 18 12:54:28 raspberrypi hass[3005]: (standard_in) 1: syntax error
Aug 18 12:54:30 raspberrypi hass[3005]: 2018-08-18 12:54:30 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Did you update your configuration? There was a breaking change for the embedded MQTT broker
yes, all updated
x.0 releases…never works 
Please can someone help me?
I have updated using Hassio however the version still shows as 0.75.2 and i get the following error:
The following components and platforms could not be set up:
hassio
Please check your config.
Is it just me or is Rename Node gone from the Zwave control panel?
EDIT: Also the question marks in the zwave control panel are broken too. They don’t display any help text.
EDIT2: Reverting back to 0.75.3 didn’t work either. I know this was just working too. And I’m still getting the save login popup like i didn’t properly revert back to 0.75.3 but the info screen says 0.75.3. Anyone have any ideas?
Only to avoid annoying SAVE LOGIN popup if you don’t enable new auth
I reverted to 0.75.3 and now I can’t log on.
My duckdns url says ‘404 file not found’ and https://hassio.local:8123 hangs on ‘loading data’
1 reply
OK it sorted itself out after I did the update to 0.76.0 from the terminal.
As I answered in previous comment, this is bug and have been fixed. Please wait next update.
Confirmed here too, running Maria DB on Synology and no problems then i upgrade to 0.76 and recorder is now broken and any other component using recorder!!! 
2018-08-19 11:58:01 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (_mysql_exceptions.OperationalError) (1296, “Got error 64 ‘Temp file write failure’ from InnoDB”) [SQL: ‘ALTER TABLE events ADD COLUMN context_id CHARACTER(36)’] (Background on this error at: http://sqlalche.me/e/e3q8)
mine upgraded fine and also using mariadb.
No one can think about all the possibilities that can happen.
It’s always wise to have a good backup bevor updating.
There are lots of DB engines people are using, different DB has different way to do schema update. As an open source project, we would not be able to test all possible scenario, especially home-assistant is not a database focus application.
Welcome to join us as beta tester, if you have special setup and want to make sure it works in next release.
I just told jaymelweston his problem is lack of temp space. I didn’t saw your error log, didn’t know what happens during your upgrade process.
You can always modify the schema by yourself, I posed in previous comment a link that people are doing manual DB migration, you can look at it.
If your DB is only on an SD without backup it was anyway something due to happen… and you can always correct it manually…
probably 20-30 minutes in addition to DB migration
After updating, the developer tools were not working.
After rebooting the Pi, everything is back to working order.
I am running hassio (Resin OS) and I have had
Invalid Config. The following components and platforms could not be set up:
recorder
history
logbook
Please check your config.
I understand the conversion of DB might have failed? I don’t think I need my history or anything, so happy to delete database and start again. What do I need to do? Stop Home Assistant - delete home-assistant_v2.db and then restart home assistant?
Thanks,
James
1 reply
I’m having issues with the Tuya component. All was working well in 0.75.3 and with 0.76.1 I am getting the following exception:
2018-08-20 13:28:24 ERROR (MainThread) [homeassistant.setup] Error during setup of component tuya
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/setup.py”, line 148, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
File “/usr/lib/python3.5/asyncio/futures.py”, line 380, in iter
yield self # This tells Task to wait for completion.
File “/usr/lib/python3.5/asyncio/tasks.py”, line 304, in _wakeup
future.result()
File “/usr/lib/python3.5/asyncio/futures.py”, line 293, in result
raise self._exception
File “/usr/lib/python3.5/concurrent/futures/thread.py”, line 55, in run
result = self.fn(*self.args, **self.kwargs)
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/tuya.py”, line 65, in setup
tuya.init(username, password, country_code, platform)
File “/srv/homeassistant/lib/python3.5/site-packages/tuyapy/tuyaapi.py”, line 44, in init
self.get_access_token()
File “/srv/homeassistant/lib/python3.5/site-packages/tuyapy/tuyaapi.py”, line 68, in get_access_token
raise TuyaAPIException(message)
tuyapy.tuyaapi.TuyaAPIException: Get accesstoken failed. Username or password error!
I have verified that my credentials are valid (they didn’t change since I upgraded). I have also tried adding the new platform option to my tuya config set to both smart_life and tuya. All combinations result in the same exception.
I’m experiencing one issue with the Auth: component. I activated auth_providers: once I installed v 0.76 on my Hass.io system. All works well, including add-ons, except that doing a Snapshot Download to my iMac fails. I’ve tried it with Safari, Firefox, and Chrome. No file is transferred, and this error is generated:
“Please change to use bearer token access /api/hassio/snapshots/20379af5/download”
Any ideas? Thanks in advance.
1 reply
Thanks, this worked.
No web interface. I still have access to the file system via configurator on port 3218 after about 20 minutes.
I have a monitor attached.
any suggested command I should run
My system is giving these errors for lot’s of things. Also appdaemon keeps getting ip-banned because of wrong password…
1 reply
Finally user system is coming 
My system was getting these errors for several things also prior to v0.76, so I never left Auth activated. Now I’m leaving Auth activated since I only get the error when trying to download the Snapshot file.
Thanks for the reply.
Is anyone having issues with Magic Seaweed since updating? I installed it last update, because…why not, and noticed today that it was not working any more. Log gets the following error
Update for sensor.virgia_beach_surf_report_forecast fails
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 199, in async_update_ha_state
yield from self.async_device_update()
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 322, in async_device_update
yield from self.hass.async_add_job(self.update)
File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/sensor/magicseaweed.py", line 148, in update
self.data.update()
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/util/__init__.py", line 325, in wrapper
result = method(*args, **kwargs)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/sensor/magicseaweed.py", line 195, in _update
self.currently = forecasts.data[0]
IndexError: list index out of range
Same issue for me, ddwrt presence detector does not work anymore. I had to downgrade to 0.76.0 for it to work again.
1 reply
read the part about mqtt password, but i never used built in:
mqtt:
broker: 192.168.1.20
#port: 1883
protocol: 3.1
client_id: home-asssistant-1
keepalive: 60
username: hass
password: pass
and now with 76.2 i get errors about mqtt
edit: rolled back to 0.75.3, working again.
Ddwrt tracking eventually started to show the correct status again on my system after a few days. Don’t think it was due to any minor updates. Maybe it just got lost. Could it be that the database changes altered something?
Hi all,
I use the ios app and since some upgrades I always get this when starting the app:
Login attempt failed
Login attempt or request with invalid authentication from 192.xxx.xxx.xxx
Does anyone know how to solve that?
Thanks in advance
May I know how to change the default username for the embedded MQTT broker?
Did you add a password to the intergrated mqtt server, setting a password is required by the last update.
I don’t mean to sound flippant but sometimes a hard, I mean pull the power cord hard, reboot solves all kinds of “things that just mysteriously quit working”.
2 replies
Doing that on a Pi though runs a real risk of corrupting the SD card.
Really bad advice. Pulling the cable should only be the very last thing you try after trying everything else and you can’t reboot or shutdown in any other way. Likely to corrupt the sd card if they’re running on one.
1 reply
tbh i had to do that once or twice too… felt really bad, but no other way was possible.
no issues, or so it seems, related to the sd card, luckily.
still, is there a way to check these sd cards for errors, while in the Pi? a check every once in a while cant hurt?
1 reply
I did it too when there was no other way, but I would never advice someone to.
Fsck can only be done when not mounted I think, and that’s the only way I know of checking.
thank you, will adhere to the policy all-is-well-if-nothing-complains then.
I have upgraded from 75.3 to 76.2 without any problems. MariaDB add-on upgraded fine and no problems with MQTT running Mosquitto broker add-on. Maybe this upgrade path may help others that have a similar configuration.
Hi Nick!
I did, I read the following:
So, it seems I still need the Velbus component, but the bugger doesn’t seem to be recognized
BR
I’m not sure if this will go very far but…
I haven’t upgraded yet but I’ve heard that some of the z wave config page functionality has been removed with the new release. specifically, the ability to rename nodes.
If anyone who can do something about it is listening, I’m asking to reconsider your decision.
I understand that you want to streamline things but removing functioning operations that lots of people use doesn’t sound right to me.
I’ve been in several threads recently involving this and many people agree with my views that it should be left in.
One thread was talking about the person having 20 z wave devices (fibaro) and each device spawned up to 13 entities. To require them to edit all 260 entities is asinine considering it could be WAY more easily done with working functionality that was just arbitrarily removed.
I personally don’t see the problem leaving it in. No one is saying we have to use the z wave config to change things. If you want to edit your entity_registry file manually then go ahead. It makes sense to leave the other option available for people who want to use that way as well.
1 reply
Have you also read about the new device registry? I’m guessing this will have similar functionality to what is removed
1 reply
It’s in the upcoming release for this week! There’s stuff to read about it but I don’t remember where unfortunately. But hang tight until it’s released I say, maybe it’s exactly what you thought you’d miss!
1 reply
Hi Nick,
If I read the breaking changes correctly, I still need the Velbus component, followed by using discovery for velbus.
However, the old definition of the velbus component, which worked on 0.6x doesn’t anymore.
So, it seems that I have a problem.
I switched back to 0.6x.
Have you any advice for me?
Ward
Is the database migration backwards compatible ? I.e. can I go back to a previous version after the db was migrated ?
Lars