Very similar to many other threads I know, but all of them seemed to be able to be cleared up by clearing cache, deleting history and such.
I can’t seem to get past this at all.
It was working fine I hit the configure button for the Philips hue on the integrations pop up and it seemed like nothing happened. It froze the UI completely. I left it for about 10 mins before powering down my Pi.
Probably shouldn’t have done that, but too late.
So I have tried many different browsers, many different machines some of which have never connected to this hassio instance. Same thing. I can get to and use the HADashboard I was working on. It functions fine, but that is all I can do.
Most of these threads suggest looking at the logs…How do you do that if you can’t get logged in?
Any thoughts on what I can do to try to recover here?
The home-assistant.log is located in the same directory as your other config yaml files. You should be able to open that file in an editor and read it that way.
I use hassio image on a ras pi 3b+ and just use the configurator to edit the files.
It finally dawned on me that I might be able to get into that so I tried and was indeed able to get to it.
So now I at least have my configs backed up, but when I look at the home-assistant.log it says
WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.1.53
I know the username and password are correct, but can’t figure out how to get in still.
I think there is a way to reset all of your login info if you think that might be causing the issue.
My understanding to accomplish that then go into your config directory and delete the “auth”, “auth_provider.homeassistant” & 'onboarding" files. Then the next time you try to login you will have to recreate your credentials.
This is part of the reason why I dislike the hassio concept. It makes it a bear to troubleshoot if there is any issue at all with your HA since EVERYTHING is controlled from inside that portion of the OS.
Well I tried to delete all the auth stuff and it didn’t work…Same thing. It takes my credentials (even after deleting all that and restarting HA) and just says loading data.
Last thing in the logs before it stopped writing logs was this:
2018-09-30 16:06:15 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py”, line 347, in _async_add_entity
await entity.async_update_ha_state()
File “/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py”, line 242, in async_update_ha_state
device_attr = self.device_state_attributes
File “/usr/local/lib/python3.6/site-packages/homeassistant/components/isy994.py”, line 482, in device_state_attributes
for name, val in self._node.aux_properties.items():
AttributeError: ‘list’ object has no attribute ‘items’
2018-09-30 16:06:15 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py”, line 347, in _async_add_entity
await entity.async_update_ha_state()
File “/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py”, line 242, in async_update_ha_state
device_attr = self.device_state_attributes
File “/usr/local/lib/python3.6/site-packages/homeassistant/components/isy994.py”, line 482, in device_state_attributes
for name, val in self._node.aux_properties.items():
AttributeError: ‘list’ object has no attribute ‘items’
I’m going to wipe it and start over I guess. I’m going to look into doing it a different way though because like you say the hassio thing leaves you pretty much crippled in a situation like this.
I’ve found for some reason that my NUC Ubuntu based HassIO install now has two active IP addresses , one dynamic and one I’ve reserved/allocated via MAC address. This has only happened in recent builds,
If I logon via my previously working reserved address I have this problem but if I use the ‘new’ dynamic address then all works OK. Both are on my 192.168.1.x network… not a 172. Docker address.
have you already tried deleting the entire “.storage” folder? Doing so should reset the whole authentication thing.
After that, restart HASS.io and see if it works.
I’m not sure that’s a good idea. There are other files that get stored there besides the auth files. Like the wonderful entity_registry file. If you lose that file then all of your custom names & id’s for your devices stored there are wiped out.
He can always make a backup of the folder first, but deleting/renaming the entire folder does maybe solve the problem and then he could restore certain files again, if he wants to.
well I tried to delete everything in the storage folder except for the things that started with Core in the name, but now it won’t even start the webpage on :8123
Last thing I did before it went stupid on me was hit the configure button for hue lights. It was gone from then.
I think I’m going to go the installation section here to see if I can figure out how to install on a pi that I already have running and have to deal with using ssh to admin rather than the hassio since that really didn’t work out for me.
Thanks to all who replied and offered help.
Yeah, I recognized some limitations of hassio early on and just stuck with hassbian on a RPi. You lose the functionality of the ease of setting up add-ons but I don’t think I’ve ever not been able to get some feature that I needed to have running because of a lack of the add-on capability.
Then after i moved to HA installed in Docker things got even easier to install & maintain. I highly recommend it.
entity_registry file. If you lose that file then all of your custom names & id’s for your devices stored there are wiped out.