Unit home-assistant.service entered failed state

I have discovered that HASS stopped working today. Around 10:38 when nobody was home and without much activity in the home automation system, my installation decided to throw a towel.
I have found the following in the logs:

Jan 17 10:38:31 raspi1 hass[4347]: terminate called after throwing an instance of 'std::length_error'
Jan 17 10:38:31 raspi1 hass[4347]: what():  basic_string::_S_create
Jan 17 10:38:31 raspi1 systemd[1]: home-assistant.service: main process exited, code=killed, status=6/ABRT
Jan 17 10:38:31 raspi1 systemd[1]: Unit home-assistant.service entered failed state.

I would appreciate your help in trying not to repeat this situation.

Config:

  • Raspi2 + MySQL for data logger
  • 0.36.0 release
  • InfluxDB + Graffana
  • Zwave stick + 5 Zwave devices (including generating a lot of traffic Aeotec power consumption logger)

I got this again:

Jan 20 03:59:07 raspi1 hass[1609]: terminate called after throwing an instance of 'std::length_error'
Jan 20 03:59:07 raspi1 hass[1609]: what():  basic_string::_S_create
Jan 20 03:59:07 raspi1 systemd[1]: home-assistant.service: main process exited, code=killed, status=6/ABRT
Jan 20 03:59:07 raspi1 systemd[1]: Unit home-assistant.service entered failed state.

2 times in the same week

Iā€™m tracking this same issue in https://github.com/home-assistant/home-assistant/issues/5272 but I think the real problem is in an issue I opened on OpenZwave library: https://github.com/OpenZWave/open-zwave/issues/1099.

Check OZW_Log.txt for things like:

2017-01-15 22:12:08.703 Info, Node004,     Previous value was 424.126W, received 120 seconds ago.
2017-01-15 22:12:08.703 Detail, Node004, Refreshed Value: old value=424.126, new value=424.126, type=decimal
2017-01-15 22:12:08.703 Detail, Node004, Changes to this value are not verified
2017-01-15 22:12:08.703 Detail, Node004, Refreshed Value: old value=120, new value=120, type=int
2017-01-15 22:12:08.704 Detail, Node004, Changes to this value are not verified
2017-01-15 22:12:08.704 Detail, Node004, Notification: ValueChanged

That would make sense, I have the same power monitor.

I had to change the home-assistant.service settings to allow for automatic restart when the failed state happens again. This is now working very well for me and I will be waiting patiently for the ZWave issue to be solved.

I too am having the same issues as you two. We have the same zwave controller and smart switch. would you mind showing me what you did to get the service to auto restart when HA enters the failed state?

This might help you:

2 Likes