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.
Thermostat. That was the other issue. Had my honeywell still under thermostat instead of climate.
The above thermostat comment did not fix my problem. Was just stating the other of the three things I was able to fix. Elevation, F and Thermostat.
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 retrievedNo services showing here either after the update to 0.31.0. Also hung on me until I redid all the zwave names.
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.
@carlostico
I’m seeing this as well. Seems like there is a stricter check on encoding of the yaml files?
Did you find out what caused your problem?
Hi , as suggested at the chat , I deleted the hidden files on the subdirectories and it started working
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’m also missing the Services list since updating to .31 from .30. I don’t have any Zwave devices. There are no errors in the log.
The service list is in the drop down now.
I am getting the async errors to. My zwave devices are through vera so that has not changed for me.
1 Like
Did a clean install of everything and am up and running. Only had a couple switches and Harmony stuff going. Wasn’t too bad. Thanks everyone.
After updating my zwave IDs, all is up and running normally except I’m getting the following error in my log file:
16-10-23 21:44:06 homeassistant.components.zwave: zwave not ready after 30 seconds, continuing anyway
Not sure what to do with this. Everything seems to be working…
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.
I can’t access my frontend either, but HASS is running. I don’t have any errors either. What could be preventing the frontend from loading?
1 Like
What version did you update from?
The latest one before it.
I found that having static wemo declarations like this, was causing the frontend to lock up.
wemo:
static:
- 192.168.2.151
- 192.168.2.152
Changing it to autodiscover fixed my problems:
wemo:I renamed my configuration file and it still didn’t start up, so something else seems to be very wrong, but didn’t start til after this update. How can I find out?
I had the same issue with my HASS 0.31.0 running on Win 10. Perhaps, the osramlightify module was responsible for that issue in my case. I solved (hopefully) that issue using the updated module from the development discussion regarding lightify.