clickster
(Peter Mills)
July 20, 2017, 2:39pm
1
Hi,
I am a HomeAssistant newbie. This is my first attempt to install on a small platform. I am using the platform I have on hand, a Beaglebone Black Version C. Using a fresh install of Debian Jessie 8.7 and following the instructions for installation using a Linux based Virtualenv, I have progressed to the point where I start HomeAssistant in my virtual environment. Startup proceeds for several minutes and then hangs up consistantly at the same place: at what seems to be a description of the sunrise and sunsets at my location. Here is that last few lines of the install output.
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=sun.sun, old_state=<state sun.sun=above_horizon; next_midnight=2017-07-21T05:01:18+00:00, next_rising=2017-07-21T09:39:58+00:00, next_dawn=2017-07-21T09:07:49+00:00, azimuth=84.61, friendly_name=Sun, next_setting=2017-07-21T00:23:21+00:00, elevation=25.76, next_dusk=2017-07-21T00:55:35+00:00, next_noon=2017-07-20T17:01:13+00:00 @ 2017-07-20T07:26:44.333955-04:00>, new_state=<state sun.sun=above_horizon; next_midnight=2017-07-21T05:01:18+00:00, next_rising=2017-07-21T09:39:58+00:00, next_dawn=2017-07-21T09:07:49+00:00, azimuth=84.76, friendly_name=Sun, next_setting=2017-07-21T00:23:21+00:00, elevation=25.95, next_dusk=2017-07-21T00:55:35+00:00, next_noon=2017-07-20T17:01:13+00:00 @ 2017-07-20T07:26:44.333955-04:00>>
I have tried redoing the install several times, always using a fresh Debian image. HomeAssistant always hangs up at the same place.
Does anyone have any ideas?
Thank you for your help.
clickster
(Peter Mills)
July 20, 2017, 2:42pm
2
My initial post clipped my log output. Here is another try to include the last few lines of the terminal output:
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=sun.sun, old_state=<state sun.sun=above_horizon; next_midnight=2017-07-21T05:01:18+00:00, next_rising=2017-07-21T09:39:58+00:00, next_dawn=2017-07-21T09:07:49+00:00, azimuth=84.61, friendly_name=Sun, next_setting=2017-07-21T00:23:21+00:00, elevation=25.76, next_dusk=2017-07-21T00:55:35+00:00, next_noon=2017-07-20T17:01:13+00:00 @ 2017-07-20T07:26:44.333955-04:00>, new_state=<state sun.sun=above_horizon; next_midnight=2017-07-21T05:01:18+00:00, next_rising=2017-07-21T09:39:58+00:00, next_dawn=2017-07-21T09:07:49+00:00, azimuth=84.76, friendly_name=Sun, next_setting=2017-07-21T00:23:21+00:00, elevation=25.95, next_dusk=2017-07-21T00:55:35+00:00, next_noon=2017-07-20T17:01:13+00:00 @ 2017-07-20T07:26:44.333955-04:00>>
Thanks again,
Clickster
clickster
(Peter Mills)
July 20, 2017, 2:44pm
3
My ignorance is showing. I guess I don’t know how to include my terminal output in a post. I tried cut and paste.
Is there another techniqe?
Apologies
clickster
(Peter Mills)
July 20, 2017, 3:31pm
4
Here is another try to include my last bit of my terminal output at hangup:
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=sun.sun, old_state=<state sun.sun=above_horizon; next_midnight=2017-07-21T05:01:18+00:00, next_rising=2017-07-21T09:39:58+00:00, next_dawn=2017-07-21T09:07:49+00:00, azimuth=84.61, friendly_name=Sun, next_setting=2017-07-21T00:23:21+00:00, elevation=25.76, next_dusk=2017-07-21T00:55:35+00:00, next_noon=2017-07-20T17:01:13+00:00 @ 2017-07-20T07:26:44.333955-04:00>, new_state=<state sun.sun=above_horizon; next_midnight=2017-07-21T05:01:18+00:00, next_rising=2017-07-21T09:39:58+00:00, next_dawn=2017-07-21T09:07:49+00:00, azimuth=84.76, friendly_name=Sun, next_setting=2017-07-21T00:23:21+00:00, elevation=25.95, next_dusk=2017-07-21T00:55:35+00:00, next_noon=2017-07-20T17:01:13+00:00 @ 2017-07-20T07:26:44.333955-04:00>> ```
There we go.
Sorry for the first time jitters.
treno
(travis reno)
July 20, 2017, 4:18pm
5
Can’t really help with your error, but it may comfort you to know that I am running a test HA instance on Beaglebone Black with no issues.
clickster
(Peter Mills)
July 20, 2017, 5:31pm
6
That is good to hear. I will keep trying. Persistence is a virtue, they say.