Texecom Alarm connect app issues (help!)

[@henry1]

It was the to do with the way I set up Texecom cloud.

Just have some other issues with the system to fix and it should be up and running (thanks everyone for the help)

 

[@henry1]

I've since added all the users to the app and it works fine

 

[Alphamoon]

I'm having the exact same issue. I have a new DIY cloud account so I have my Installer ID, and I can generate an app code from the panel. When I login into the app and enter all of these details along with either the master or standard panel code. I get access to panel denied. can you give any more detail on how you got this fix?

 

[secureiam]

there was an issue in the cloud account.
added to my account and then released for them to add to teres and this seemed to work.

Without seeing what it says in your cloud account its hard to say.

I suspect the wrong service level may have ben selected in the cloud.
However I did a few basics once panel was added before removing it from my system so henry could add it to his and looks like everything is fine now.

 

[Alphamoon]

@secureiam Thanks for the info and help. Texecom's tech support and Cloud team have gone in and fixed the issue for me. It's all working fine this morning. I have to say that I found Texecom support to be superb and lightning-fast.

Result!

 

[@henry1]

This is off-topic but I thought I may as well post it here rather than start another thread, I have a Zone programming dilemma so long story short I have two cats which sometimes bypass my Pet-Friendly Capture PIRs as they jump on things and no it is not possible to confine them to an un-monitored room or replace/move PIRs, as a result I have the Kitchen and Lounge sensors Beam Paired with each other so they both are required to activate the alarm but is there anyway I can set it so that it needs the Lounge and any other device to activate without the Kitchen specifically? I'm aware I could enable the double knock attribute on the Lounge but I thought I would ask about this first.

 

[secureiam]

This should be a separate thread

 

[@henry1]

This should be a separate thread

No worries