Texecom COM IP - Problem Notification (and test call)

[marky9074]

Rather than resurrect this thread COM IP - Problem Notification (and test call) | DIYnot Forums thought I would create a new one (though essentially the problem is almost the same).

I have followed the COM-IP instructions to the letter and am not getting any notifications, and test call does not seem to work. I have the COM-IP on COM1 and can access both internally and externally OK on both the app and Wincom (so port forwarding is working - though I obviously had to manually set my external IP in the app).

I've taken a few photos of the keypad, to hopefully show that its correct.

A couple of things I have read on here is to reset the Com port, and to set the polling to 1 min (because if its working it should eventually update itself to 15 minutes and therefore is working).

Any other suggestions would be much appreciated.

 

[marky9074]

And some more photos:

 

[secureiam]

So what happens when you do a tests call.

 

[marky9074]

Not a lot by the looks of things. I'm not at home at the moment. This was what I saw last time:

 

[secureiam]

So you set this up for the old keypad app?
Comip can only be sending out or used for a connection.

 

[marky9074]

Yeah, says Texecom rkp v2.0.9.1 for the Android app. When I re-click on 'Register Account' I get:

User already registered
Account located
Sitename updated
Email address updated
Check for token
Token already registered

I did wonder if I could install Montex locally and at least see if panel does push anything out? I will try the Com reset first (when I get home)

 

[marky9074]

So you set this up for the old keypad app?
Comip can only be sending out or used for a connection.

Just to confirm, when on this page and I do make a remote connection with the app I do see the 'Com1 Connected' (or something like that). My understanding is that it wont push with anything connected (App/Wintex), but have tried numerous times with a test call.

 

[secureiam]

thought your ip addresses for your network and gateway looked a bit strange.

 

[marky9074]

thought your ip addresses for your network and gateway looked a bit strange.

It is a TP-Link Deco M9 mesh network. It fired up with the 68 subnet and I just went with it. All my 'mission critical' stuff is on fixed IP's from 125 upwards.

 

[marky9074]

OK, got home and had a bit of a play. Compared my settings with a good friend who is very knowledgeable about this panel. In his config, within Wintex I could see that under 'Communication Options / Options' the area accounts had the account number under them (generated from the app). In addition, under 'Communication Options / ARCs' within the 'Protocol Options 2' all the ComPorts were selected. I changed this and did a test run and it looked like something was happening (could see traffic messages on ComPort 1 on the keypad). However, I still did not receive any notifications in the Android app or by email.

 

[marky9074]

Following this, I set up Montex and changed the ARC's IP addresses and did another test call. This seems to have been successful, so can only assume that there is an issue getting out of the network, or being received at the Texecom end.....

 

[secureiam]

Firstly the comport in use should be the comport used for com ip module.

so sending data if plugged on comport 2 then comport to inthe second configuration in program digital would be set screen of keypad not shown.

the wintex profile shows all 3 comports in use which it shouldn’t but that won’t affect signal so much other than it tries to send on all 3 ports potentially,

note 1 way traffic at a time so connecting via app or wintex can stop out going messages.

can’t comment on what state the Texecom severs are for the old app as don’t use them these days and havent for some years.

texecom may have a list of alternatives on their forum of comip manuals

 

[marky9074]

I did wonder why he had all com ports enabled also, and did last night change it to just com port 1. That said, when doing a test call it still seemed to try all com ports when looking at the keypad...

My last test last night was to define three ARC tabs. The first was IP addresses as per manual, using my account number. The second was a duplicate but with a different account number (my partners with an iPhone). The third was my local Montex IP address. The test call seemed to go through the motions and I got the notification of test within Montex.

Then I tried it again with the ARC's defined as 'Contact ID' instead of 'SAI2'. I got a weird account connection on Montex (showing on the SAI2 tab), and nothing at all showing in the 'Contact ID' notifications. Then something threw an ATS path fault, which for the life of me I could not clear and had to power off and pull battery on panel...

Once back up set it all back to 'SAI2' and did another test call. Again, only Montex seemed to register a response (with nothing by email or as notifications to the app).

Then, sometime later.... We both got emails and app notifications of 'Program Mode exit' - 'Area 1' - 'Device Panel'. I assume this is some time out on the panel and it logged itself off of engineer?

 

[secureiam]

when the smart com was introduced they changed the program digi to include which comports it send data through.

so 1 x comip module connected to comport 1 you would program to comport 1 for sending the signal out in config 2, your screen shots are up to config with ip mode and text selected.

PE panels are only capable of one way communication, either outbound or inbound without issue, hence why the smart com has two connections, smart com for the connection and iopcom for the outgoing messages.

There has also been reports with some issues with Texecom servers over the weekend specifically those using Texecom connect, starting around Thursday 21st April, not sure exactly how wide spread this is as not all the systems we look after were affected.

 

[marky9074]

Thanks for all your help on this. Today I seem to have to have taken two steps back. Now when I log on/off as engineer I get a notification on the app (though curiously no email now). However, when doing a test call I don't even get a message to Montex anymore... (but I do get the engineer on/off message).....

I looked at Smart Com last night, is this a subscription based service? Seems cheap enough to purchase, and I even saw it state it could be mounted inside the panel?

As a test I did set the polling to 1 and a while later it was back at 15 minutes, so at least that is working...!