Does the web api version (or the new ajax version for that matter) support silent arming?
uvjustin has repackaged the ajax version into a proper HA custom component.
@mikeg1130 neither version (ajax or web api) support silent arming at this time. I don’t think the original plugin supported this functionality either, but it seems to be available in the homebridge node interface here.
I’ll reach out to uvjustin to see if this is something we can add.
Got this working, and I’m up again. My wife (remembering to manually arm) thanks you.
One note – the repo link no longer works per the pending update. I got it from here:
https://github.com/home-assistant/core/tree/master/homeassistant/components/alarmdotcom
This absolutely does not work for me. There is no alarm_control_panel in my list of entities when using alarmdotcomajax as my platform in my config file. If I try to use the alarmdotcomwebapi, I can see an alarm_control_panel but cannot do anything with it at all.
Right, the original didn’t support silent arming either. If you are able to add this feature, I will be so pumped. Thanks for looking into it!
Dumb question… Are we now good to go with the standard HA integration? I was temporarily using the custom component. Should I now revert back? And to do so, should we just remove the alarmdotcomajax custom component folder and change configuration.yaml back to “platform: alarmdotcom”?
The handling of the files involved caused this to fail for me until I figured that out. Here are the things I did initially that caused problems (perhaps you are doing one or more):
- Using “save link as” to try saving the files from the links in the various repositories listed. That saved “Py” files that were in fact html files.
- Copy/pasting the text of the Py files into those files that had been created.
- Picking the individual files from the zip archives and dropping them straight into the custom components folder via Samba Share.
It only worked once I downloaded the entire zip archives of the full repositories (via the download link on Github) and then fully extracted that before dropping the file into the custom components folder via Samba Share. There may be a simpler way, but I never figured it out. This is probably stuff that is obvious to those who work with the repositories frequently, but some others (i.e., me) will learn the hard way.
My understanding is that the standard (alarmdotcom) integration does not work and will never be corrected. In fact, it is being removed from HA entirely. Those who rely on this are moving to a custom component. Although i understand the CCs are now moving in the direction of relying on an API, they still rely on web scraping and so are not permitted as part of the core HA functionality.
When I tried this I can see the state of the alarm, but can not arm it. I get the following error message when I try.
Error executing service <ServiceCall alarm_control_panel.alarm_arm_home (c:939f2e6f14bf4741a77070c6ba247aa5): entity_id=[‘alarm_control_panel.alarm_com’]>
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/core.py”, line 1242, in _safe_execute
await self._execute_service(handler, service_call)
File “/usr/src/homeassistant/homeassistant/core.py”, line 1257, in _execute_service
await handler.func(service_call)
File “/usr/src/homeassistant/homeassistant/helpers/entity_component.py”, line 198, in handle_service
self._platforms.values(), func, call, required_features
File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 402, in entity_service_call
future.result() # pop exception if have
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 599, in async_request_call
await coro
File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 433, in _handle_entity_call
await result
File “/config/custom_components/alarmdotcomajax/alarm_control_panel.py”, line 120, in async_alarm_arm_home
await self._alarm.async_alarm_arm_home()
AttributeError: ‘Alarmdotcom’ object has no attribute ‘async_alarm_arm_home’
Connection lost. Reconnecting…
Any how to increase the frequency of polling? Seems minutes need to go by if an open door in order for my sensors to update. Is the Ajax version better or worse than the webapi for this reason?
uvjustin added a silent arming flag and I’ve forked all of the necessary files for easier distribution.
Installation and configuration are covered in the README.
I’ve also added documentation for configuring Binary Sensors using the sensor_status variable.
Just switched to the alarmdotcomwebapi version, and the status and sensors appear to be working correctly, however, when attempting to arm home alarm to STAY:
I’m seeing this error:
I’m seeing the same error Markus99 posted when trying to arm stay with your custom component
Failed to call service alarm_control_panel/alarm_arm_home. ‘Alarmdotcom’ object has no attribute ‘async_alarm_arm_home’
I updated my files to the newest version, and added the silent_arming: true option in the config. Arming and disarming via the UI works great, however, it is still not silent. Is there something I might be missing?
Thanks again for looking into the silent arming functionality!
Will this new install method work if the system is being deprecated.
Also there have been a few posts about installing.
Which one as of March 23 the one to follow?
Thanks
Just curious - Will this be added to HACS?
@carltonb The official module is being deprecated. The custom component should continue to function… so long as the alarm.com website is available anyway.
@_Mike I wasn’t planning on it, but it’s a good idea. Maybe after it gets a little more testing.
1 Like
Awesome! That would be a great addition, and would make it much easier to install it and keep it updated. Thanks for all the hard work! We appreciate it!
Hmmm, getting this after switching back to the AJAX version (per the link you provided) just now:
EDIT: Might be a cache issue, trying to reboot again now.