Firstly thank you for all the help.
Because of the problems with the “( )” brackets i eliminated them in all my entries and I changed the alarmdotcom sensor to read 14_Office Window.
So now the binary sensor code looks like
It seems that on my system for some reason it must have a name.
I thought that the name was optional or that it defaulted to alarm_com.
My system required the name to be inserted.
So I used this.
I switched to the alarmdotcomwebapi version and it appears to be working fine. With one issue, every few days it ceases to work and when i do a restart it is fine again. Guessing it is a authentication issue. Thinking a temp fix would be to use automation to do a restart every so often.
Any ideas, could we add a keepalive function to the code?
Yes, same here @samceccola re: WEBAPI version. Seeing these log errors this morning:
2020-03-26 08:38:56 ERROR (MainThread) [homeassistant.helpers.entity] Update for alarm_control_panel.work fails
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 474, in async_device_update
await self.async_update()
File "/config/custom_components/alarmdotcomwebapi/alarm_control_panel.py", line 74, in async_update
await self._alarm.async_update()
File "/config/custom_components/alarmdotcomwebapi/pyalarmdotcom.py", line 187, in async_update
response = self.command('STATUS')
File "/config/custom_components/alarmdotcomwebapi/pyalarmdotcom.py", line 160, in command
currentstate = result['data']['attributes']['state']
KeyError: 'data'
Also using the updated AJAX version, which seems stable, but we’re working thru an issue w/ allowing multiple accounts/locations to work/play nicely together. I have home/work locations, so that’s why I’m running both WEBAPI and AJAX versions concurrently, fwiw.
WOW, this new version is FANTASTIC. I really approve. Not only did it get my alarm.com integration working again, it also adds silent arming, which is a feature I have been wanting forever.
Is there a way to chose silent vs. non-silent arming? Not really a deal killer, just wondering if that is possible. After all, I am really pleased with this new integration as-is!
@Mr_Flibble, the integration does not provide a way to specify silent vs non-silent for each arming command issued, however the silent_arming flag can be configured in 4 different modes (“home”, “away”, “false” (never), “true” (always)), where “home” means always use silent arming during arm_home and “away” means always use silent arming during arm_away.
Worth reporting that I was able to install via HACS using these instructions, removing the previously created custom_component, and all is working well - including multiple locations. Thanks @aechelon and @uvjustin!
I had some trouble with this, so I want to make sure I am doing this correctly. I tried several variations of the integration repository in the SETTINGS page, and most resulted in errors. It finally came up when I entered “uvjustin/alarmdotcomajax”. Before I add the integration, I just want to verify - Is that correct?
You won’t get an explicit notification, however the HACS interface will show integrations that are out-of-date in orange. Clicking on the associated card will present an option to UPDATE the integration. I tested this with the Alarm.com integration earlier today and it worked without an issue.