Any Alarm.com users out there?

Got a plugin almost ready for early access...

Yes, My security system provider uses the alarm.com system.

Pre-release 2022.0.0: https://github.com/FlyingDiver/Indigo-a ... g/2022.0.0

Currently supports System, Partition, and Sensor devices. The System device doesn't seem very useful to me, but it's part of the API so I left it in. The Partition device is the one that shows the current state of the alarm system, such as Disarmed, Armed Home, or Armed Away. It's also the device that has the actions to change the current alarm system mode. Sensor devices are the contact sensors, motion sensors, or smoke detectors. I only have those three types, but any other types that Alarm.com supports should just work. These are currently custom devices so they don't show an on/off state, but that will likely change before official release.

I don't currently have support in the plugin for other device types that Alarm.com supports, such as Locks, Lights, Garage Doors, etc. If anyone has those devices let me know and I'll add support for you to test them.

On first start, the plugin needs to authenticate with the Alarm.com servers as a "device" (like a mobile app). You'll need to enter your Alarm.com credentials in the plugin config dialog, then you'll get a prompt in the Indigo log to enter your OTP (one time password) in a plugin menu dialog. For me, that's a code generated by an OTP app like Authy. Some users might get an SMS code instead. I think the API requires that you have 2FA (Two Factor Authentication) enabled with Alarm.com for this to work. I already did, so I have no experience with what'll happen if you don't.

I just started working on this plugin about 48 hours ago, so it's still a little rough. Feedback appreciated.

Thanks for the quick work on this! I just tried to install it but get this error:

Code: Select all

Jul 4, 2022 at 11:43:13 AM
   Installing and enabling plugin Alarm.com v2022.0.0
   Loading plugin "Alarm.com 2022.0.0" using API v3.1
   Starting plugin "Alarm.com 2022.0.0" (pid 99042)
   Reloading plugin "Web Server 2022.1.1" using API v2.5
   Stopping plugin "Web Server 2022.1.1" (pid 18722)
   Web Server                      Stopping Indigo Web Server...
   Alarm.com Error                 Error in plugin execution InitializeMain:

  File "plugin.py", line 10, in <module>
type: No module named 'aiofiles'

   Stopping plugin "Alarm.com 2022.0.0" (pid 99042)
   Stopped plugin "Alarm.com 2022.0.0"


Apparently the error prevents the plug=in from being installed. I thought I might be able to create a new Alarm.com device in Indigo, but the plugin doesn't show up in the menu. The plug-in does show up in the Indigo main menu but with a red dot next to it.

My bad, I forgot to put that in the instructions. Do this in Terminal:

Code: Select all

pip3 install pyalarmdotcomajax aiohttp aiofiles


Ok, that cured the error.

I've now ben able to start the initialization process and have entered my confirming code. After doing that I get the following error:

Code: Select all

   Alarm.com Error                 Error in plugin execution GetUiDynamicList:

  File "plugin.py", line 247, in get_partition_list
type: local variable 'partitions' referenced before assignment


Not sure if those last two lines are from the plugin or from some other Indigo device that just coincidentally showed up at the same time.

Also, I can attempt to create a device, but the drop-down menu items are blank.

That's going to require a new release. Stand by.

https://github.com/FlyingDiver/Indigo-a ... g/2022.0.1

Installed the new version. Seems to install just fine and I've entered the OTC from Alarm.com where prompted.

When I try to create a new device after selecting the plugin the configuration box that drops down does not have anything in it. Its like the info isn't being downloaded as the data is just blank.

Will be away from the computer for a few hours....

When you get a chance, turn on detailed debugging, restart the plugin, then post the log.

Code: Select all

   Alarm.com Debug                 LogLevel = 5
   Alarm.com Debug                 updateFrequency = 300.0
   Reloading plugin "Alarm.com 2022.0.1" using API v3.1
   Stopping plugin "Alarm.com 2022.0.1" (pid 1385)
   Alarm.com Debug                 stop_concurrent_thread called
   Stopped plugin "Alarm.com 2022.0.1"
   Starting plugin "Alarm.com 2022.0.1" (pid 7725)
   Alarm.com Debug                 updateFrequency = 300.0
   Started plugin "Alarm.com 2022.0.1"
   Alarm.com Debug                 startup
   Alarm.com Debug                 run_async_thread starting
   Alarm.com Debug                 startup complete
   Alarm.com Debug                 async_main starting
   Alarm.com                       Alarm.com authentication successful
   Alarm.com Debug                 Alarm.com Provider: Strada Security
[Removed email address here]
   Alarm.com Debug                 async_system_refresh_loop: starting
   Alarm.com Debug                 Systems (1)
   Alarm.com Debug                 Name: House, id_: 2650920, unit_id: None
   Alarm.com Debug                 Partitions (1)
   Alarm.com Debug                 Name: Panel (92613667-127), State: DeviceState.DISARMED, System: 2650920
   Alarm.com Debug                 Sensors (12)
   Alarm.com Debug                 Name: Dining Room (92613667-4), State: DeviceState.CLOSED, System: 2650920, Partition: 92613667-127
   Alarm.com Debug                 Name: Front BR (92613667-5), State: DeviceState.CLOSED, System: 2650920, Partition: 92613667-127
   Alarm.com Debug                 Name: Front Door (92613667-12), State: DeviceState.CLOSED, System: 2650920, Partition: 92613667-127
   Alarm.com Debug                 Name: Garage Door (92613667-1), State: DeviceState.CLOSED, System: 2650920, Partition: 92613667-127
   Alarm.com Debug                 Name: Glass break (92613667-11), State: DeviceState.CLOSED, System: 2650920, Partition: 92613667-127
   Alarm.com Debug                 Name: MBath (92613667-7), State: DeviceState.CLOSED, System: 2650920, Partition: 92613667-127
   Alarm.com Debug                 Name: MBR 1 (92613667-9), State: DeviceState.CLOSED, System: 2650920, Partition: 92613667-127
   Alarm.com Debug                 Name: MBR 2 (92613667-10), State: DeviceState.CLOSED, System: 2650920, Partition: 92613667-127
   Alarm.com Debug                 Name: Motion (2) (92613667-2), State: DeviceState.ACTIVE, System: 2650920, Partition: 92613667-127
   Alarm.com Debug                 Name: Office (92613667-6), State: DeviceState.CLOSED, System: 2650920, Partition: 92613667-127
   Alarm.com Debug                 Name: Sliders (92613667-3), State: DeviceState.CLOSED, System: 2650920, Partition: 92613667-127
   Alarm.com Debug                 Name: Smoke/Heat (8) (92613667-8), State: DeviceState.CLOSED, System: 2650920, Partition: 92613667-127
   Alarm.com Debug                 known_systems: {'2650920': <pyalarmdotcomajax.devices.System object at 0x106788af0>}
   Alarm.com Debug                 known_partitions: {'2650920': {'92613667-127': <pyalarmdotcomajax.devices.Partition object at 0x106a09870>}}
   Alarm.com Debug                 known_sensors: {'2650920': {'92613667-127': {'92613667-4': <pyalarmdotcomajax.devices.Sensor object at 0x106a0b9a0>, '92613667-5': <pyalarmdotcomajax.devices.Sensor object at 0x106a09810>, '92613667-12': <pyalarmdotcomajax.devices.Sensor object at 0x106a092d0>, '92613667-1': <pyalarmdotcomajax.devices.Sensor object at 0x106a096f0>, '92613667-11': <pyalarmdotcomajax.devices.Sensor object at 0x106a099c0>, '92613667-7': <pyalarmdotcomajax.devices.Sensor object at 0x106a0bb20>, '92613667-9': <pyalarmdotcomajax.devices.Sensor object at 0x106a09720>, '92613667-10': <pyalarmdotcomajax.devices.Sensor object at 0x106a098a0>, '92613667-2': <pyalarmdotcomajax.devices.Sensor object at 0x106a09780>, '92613667-6': <pyalarmdotcomajax.devices.Sensor object at 0x106a097b0>, '92613667-3': <pyalarmdotcomajax.devices.Sensor object at 0x106a09750>, '92613667-8': <pyalarmdotcomajax.devices.Sensor object at 0x106a096c0>}}}
   Alarm.com Debug                 active_systems: {}
   Alarm.com Debug                 active_partitions:   {}
   Alarm.com Debug                 active_sensors: {}
   Alarm.com Debug                 async_system_refresh_loop: starting timer for 300.0 seconds


Interesting in that it seems to have the info from the system.

After doing the above, I went in and created a new device for the sensors and sure enough they show up in Indigo! Not sure why the Panel and System devices don't populate.

Yeah, the data is there for the System and Partition, but something is failing in the device creation. I'll dig into it.

Been trying to replicate this error on my system, and can't do it. I deleted all the devices, deleted the plugin preferences, and restarted everything. No issues creating all the devices.

When you get a chance, please restart the plugin using the "Reload in Interactive Shell" option (with detailed debugging enabled), then try to create the partition device. Post the log and the terminal output. Thanks.

Oddly enough, I just re-started the plug-in and it works!!!

Well, a bit more detail. I read your post, when in and turned on detailed debugging and then did a restart (without the interactive sheet option since I don't know what that is) of the plug in. It all appeared normal in the log. I went in and deleted the existing devices I had made and then made new ones, starting with System, then Partition and then Sensor. They all seem to create just fine.

I'll try out various things like setting the arming, triggering off a sensor change. When I get a chance. But for now everything seems to be there.

Thanks for your work on this!!