Just updated from .21 to .31. Installed .21 through the all in one. Running Pi3. Here are the steps that led me to the update. Ran the update through the all in one update steps on the site.
Bought Ecobee and installed. Added to HA and worked great.
Had a new harmony hub up and running and never added stuff to HA Bridge to control through Alexa.
Added step 2 hub to HABridge and synced up Alexa. Devices were seen and all seemed good.
Alexa didn’t control them. Did a few restarts of HA and HABridge.
Figured I hadn’t updated in a while so did it.
Can’t get to frontend now.
Here is the HA log:
16-10-22 20:27:28 plexapi: http://192.168.1.80:32400: HTTPConnectionPool(host=‘192.168.1.80’, port=32400): Max retries exceeded with url: /?X-Plex-Token=xxxxxxxxxxxxxxxxx (Caused by NewConnectionError(’<requests.packages.urllib3.connection.HTTPConnection object at 0x6ee59390>: Failed to establish a new connection: [Errno 113] No route to host’,))
That is all there is. I know enough about this to be dangerous so I apologize if the above is obvious to fix but I am not sure why the plexapi may be causing this or if it is causing it. Any suggestions? Can add my config file if needed. I # out the Plex info in the config file hoping that would help but it did not.
That is what I was thinking could be going on but it is only pointing to that. I only use it right now for a couple switches and the HA Bridge. Just testing the waters for the moment. Found a couple issues before posting that were hitting the log. Had an elevation, fahrenheit and something else issue. Those are gone now and this is the only one left.
Mine takes much longer to start up now, and I’ve just discovered I don’t seem to have services showing any more. (:8123/dev-service). I have the Call a service from a component bit but the right hand side with a list of services to call has disappeared.
Besides the normal log errors
Not sure how to properly post error log…
async loop error is the only thing that stands out as new. and I have no idea what http://172.17.42.1:8096 is
16-10-23 18:03:08 netdisco.ssdp: Error fetching description at http://127.0.0.1:8096/dlna/a88351a89d11084d89af5baef10ce1d7/description.xml
16-10-23 18:03:10 homeassistant.components.zwave: zwave not ready after 30 seconds, continuing anyway
16-10-23 18:05:15 netdisco.ssdp: Error fetching description at http://172.17.42.1:8096/dlna/c43591b57714c0b8f03d9de139f488f2/description.xml
16-10-23 18:05:27 homeassistant.components.light.hue: Error connecting to the Hue bridge at 192.168.1.114
16-10-23 18:08:10 homeassistant.core: Error inside async loop: Task exception was never retrieved
16-10-23 18:10:21 pychromecast.socket_client: Error communicating with socket, resetting connection
16-10-23 18:10:21 pychromecast.socket_client: Failed to connect, retrying in 5.000000s
Traceback (most recent call last):
File "/home/hass/.homeassistant/deps/pychromecast/socket_client.py", line 239, in initialize_connection
self.socket.connect((self.host, self.port))
File "/usr/lib/python3.4/ssl.py", line 840, in connect
self._real_connect(addr, False)
File "/usr/lib/python3.4/ssl.py", line 827, in _real_connect
socket.connect(self, addr)
ConnectionRefusedError: [Errno 111] Connection refused
16-10-23 18:15:10 homeassistant.core: Error inside async loop: Task exception was never retrieved
I have done the Z-wave and didn’t have any hanging, just a slow reboot. After the last reboot my error log is somewhat smaller. netdisco and and the async loop errors persist.
16-10-23 18:21:01 netdisco.ssdp: Error fetching description at http://127.0.0.1:8096/dlna/a88351a89d11084d89af5baef10ce1d7/description.xml
16-10-23 18:21:01 netdisco.ssdp: Error fetching description at http://172.17.42.1:8096/dlna/c43591b57714c0b8f03d9de139f488f2/description.xml
16-10-23 18:21:04 homeassistant.components.light.hue: Error connecting to the Hue bridge at 192.168.1.114
16-10-23 18:21:04 homeassistant.components.zwave: zwave not ready after 30 seconds, continuing anyway
16-10-23 18:48:39 homeassistant.core: Error inside async loop: Task exception was never retrieved
16-10-23 19:31:40 homeassistant.core: Error inside async loop: Task exception was never retrieved
There is a casperboo asking about the zwave change on the 0.31 blog post. I can’t seem to comment there but for me, an extra digit was added to the end of the device names, "_8" became "_8_0" and "_8_3" and so on.
Even doing a find change with atom project wide changing “…temperature_4” to “.temperature_4_1” and so on for all my ZW stuff took me 45 mins. It’s very possible I broke something but everything seems to be working. I accidentally did it on one device twice and ended up with “…temperature_4_1_1” everywhere it appeared.
So you are saying get rid of these in my file and have the contents in that file in the main config file?
customize: !include customize.yaml
Also, the zwave naming. I have zwave stuff and I read of the naming changes. Maybe I am misunderstanding. Sounded to me like once HA started the zwave may not work because it renamed some. Example, I have a switch named switch.ge_12722_onoff_relay_switch_switch_4. That may have been changed to switch.ge_12722_onoff_relay_switch_switch_4_1. So once HA started I would be able to see that, change my files and then just restart. Is that correct? If so, I can’t even get HA to start and the only thing that is showing is the above plexapi thing. I can’t see a front end. I can see the HA Bridge front end and the zwave files say it is running.
I have always had that error @cynicated - I think I remember reading that you can change a setting somewhere to wait until the network is ready before booting homeassistant but can’t find it now.
