Alarm.com issue

Configuration
21

This didn’t work for me. I have a Pi with AIO install. I get this error: PermissionError: [Errno 13] Permission denied: ‘ghostdriver.log’… Hmm.

22

I was briefly able to get Alarm.com working. Renamed by /deps folder so it would download everything on reboot and it worked.

It broke on next reboot:
ERROR:homeassistant.bootstrap:Not initializing alarm_control_panel.alarmdotcom because could not install dependency https://github.com/Xorso/pyalarmdotcom/archive/0.1.1.zip#pyalarmdotcom==0.1.1

23

I’m having the exact same issues. I tried following the steps in the reddit post, and running chown -R hass on it but no changes, still doesn’t have permission. Has anyone got this working while NOT using the AiO on the pi?

24

Same issue with hassbian.

25

I found a possible fix for that just now, run this command:
$ sudo touch /ghostdriver.log && sudo chmod 777 /ghostdriver.log

1 Like
26

sudo touch /ghostdriver.log && sudo chmod 777 /ghostdriver.log

This worked for me.

1 Like
27

This worked for me as well. Thanks Jordandrako!!!

28

What’s the rootdir you’re running that command in?

Thanks guys!

29

It works when run from any directory, since it specifies to make the file in the root directory.

1 Like
30

Well, crap. Still getting the same error after creating that chmod’d ghostdriver.log. What the heck?

 16-12-06 18:38:33 homeassistant.components.alarm_control_panel: Error while setting up platform alarmdotcom
    Traceback (most recent call last):
     File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 150, in _async_setup_platform entity_platform.add_entities, discovery_info
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/alarm_control_panel/alarmdotcom.py", line 42, in setup_platform
    add_devices([AlarmDotCom(hass, name, code, username, password)], True)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/alarm_control_panel/alarmdotcom.py", line 51, in __init__
    self._alarm = Alarmdotcom(username, password, timeout=10)
  File "/home/hass/.homeassistant/deps/pyalarmdotcom/pyalarmdotcom.py", line 82, in __init__
    if not self._login():
  File "/home/hass/.homeassistant/deps/pyalarmdotcom/pyalarmdotcom.py", line 95, in _login
    self._driver = webdriver.PhantomJS()
  File "/home/hass/.homeassistant/deps/selenium/webdriver/phantomjs/webdriver.py", line 51, in __init__
    log_path=service_log_path)
  File "/home/hass/.homeassistant/deps/selenium/webdriver/phantomjs/service.py", line 50, in __init__
    service.Service.__init__(self, executable_path, port=port, log_file=open(log_path, 'w'))
PermissionError: [Errno 13] Permission denied: 'ghostdriver.log'
31

That’s the same error I got and this worked for me after using putty to ssh into the RPi.

32

Welp - did a full re-image of raspbian with raspbian jesse lite (vs. the full which is what I had before), using the AIO script. I had to install phantomjs per the reddit thread on this topic, as I was getting the “phantomjs must be in PATH” error after the re-install. I also created and chmod’d ghostdriver.log for good measure. Following all that, it works!

1 Like