Upgraded to 0.48.1 Breaks Z-Wave

Configuration
1

Home Assistant release (hass --version):
0.48.1
Python release (python3 --version):
Python 3.4.2

I just upgraded to 0.48.1 and noticed that after the upgrade the frontend wouldn’t start. I’m not getting any warnings/errors in the home-assistant.log. I commented out my zwave configuration and the frontend started.

Here is my zwave configuration:

zwave:
  usb_path: /dev/ttyACM0
  new_entity_ids: true
  config_path: /srv/homeassistant/lib/python3.4/site-packages/python_openzwave/ozw_config
  polling_interval: 30000
  device_config:
    light.ge_14294_porch_level:
      polling_intensity: 1
      refresh_value: true
    light.ge_14294_exterior_side_level:
      polling_intensity: 1
      refresh_value: true
2

It may take 15 to 20 minutes for the backend update processes to complete once you have gone through the update.

1 Like
3

How many zwave devices do you have?

4

@zarthan Thanks, I just wasn’t waiting long enough. All working now. Appreciate it.

5

If you have ever really had an update disaster in the past, it is a little disconcerting that HA doesn’t come up immediately. The waiting can seem like forever.
Glad it is working.

1 Like
6

my zwave stops working after 1-2 hours after upgrading… most odd

1 Like
7

yea, I know. What I do under unix is do a

ps -ef | grep home

it shows several lines, but if it’s doing updates there will be one showing the component that it’s installing. That helps me when I’m feeling impatient. :slight_smile:

1 Like
8

Are you using z-wave through HA or through another hub like Wink? There have been problems in the past with this type of behavior from devices connected through wink. Also are you on 0.48.1?

9

I bet I know why it seems to be taking so long this time. Adding that index to the states table can take quite a while if you have a large amount of history. I did mine manually a week or so ago, and it took a good 10 minutes…