New user issues: Can't register my Alarm.com LTE Hub

I’m attempting to sign up for Surety, but it says my device may not be compatible, and I’m looking for some clarity.

I have an Alarm.com Hub, Model ADC-NK-200T-A
It has a Verizon LTE connection.
This hub is not a security panel, it’s an Alarm.com ZWave Hub provided through my previous Alarm.com partner. It’s just for my Alarm.com thermostat and moisture monitor and such.

When I first ran the compatibility check for my IMEI, the Surety site said “Your IMEI is already associated with an account. Have your provider delete it.” My current Alarm.com partner is ending their partnership with Alarm.com, but hadn’t deleted the account yet, so that made sense.

I contacted the partner and they deleted my account. Then I ran the compatibility check again, and the message was different; said it wasn’t compatible instead.

I’m really confused. The hub is branded Alarm.com. It has a cellular connection. It was registered in my old partner’s Alarm.com system and working very recently. What am I missing here?

My previous Alarm.com partner is looking for a company to recommend their customers transfer to (they’re primarily an HVAC company and are getting out of the Smart Thermostat support game, I guess), so I know there are going to be other potential users in the same boat as me.

The Alarm.com Hub ADC-NK-200T-A for home automation devices is not compatible with service through Surety.

In order to use Alarm.com service through Surety, you would need a different alarm panel, you can find a list of compatible panels here:

Then I ran the compatibility check again, and the message was different; said it wasn’t compatible instead.

As a quick follow up, unfortunately when a registered module is checked (one connected to an Alarm.com account at the time), Alarm.com will not provide any details about that module in the reply data. We can only tell it is registered. This makes sense as dealers shouldn’t be able to view data about another dealer’s customer or their system. However it means that the tool cannot verify the model of panel when a registered module is checked, only when the module is unregistered.

I apologize for any confusion there.