Hi, ever since I installed my UCM/GSM4(3G) module last year I've always been convinced it doesn't quite work correctly when there is an AC power failure. Initially I assumed the local cell maybe also failed at the same time (although unlikely) and each time I have a power failure there seem to be some missing SMS messages but I never get around to investigating further at it works normally again after that. "Normal" means that various zones trigger SMS messages and I also use various Control menus via SMS.
However, this time, the first power failure for 7 months happened when I'm away (we normally get ~1 power cut per month on average). Comfort dialled me via Landline and reported a power failure. I did also receive one Power Fail and a Power Restore SMS message but then the power went down again for a couple of hours.
Now that power is back I can dial-up comfort via the landline and that is okay but it is refusing to respond to SMS texts and if I phone the SMS module it answers (with silence) and then disconnects.
I've managed to get a VPN connection and retrieve my event log and I can see various failures where it tried to send me other SMS messages about power failure and restore but more worryingly I can see various events that I don't understand: "SMS Dial Failure #89" events and also 98 /99 / 100 / 16 at various points and also "SMS Trouble ID # UCM 2" and "SMS Restore ID # UCM 2".
From the Comfigurator "Get Status" mechanism I can see in the toolbar that UCM status of the GSM Module is showing that it does have a good network signal and then the status message status "Normal/No error".
The event log should show the dialing attempt as well the successful acknowledgement of the SMS by the mobile network provider
egDial Number #3 means there was a dial out to phone 3. This may be Voice Phone or SMSIf the selected phone is an SMS Phone Type then the next event should be "Remote Signin - User # SMS Acknowledge". That shows that the message was deleivered, not that you received the message, as there may be delays through the SMS network.
If the SMS fails to send there should be "SMS Dial Failure". Comfort will resend up to 5 times . SMS Dial Failure #89 - you can ignore the #89 or other numbers. The evemt log listing has to incliude a number parameter but in the case of SMS Dial Failure a random number appears. So just treat them as SMS Dial Failiure. We may change that in the future version of Comfigurator
05/15 17:49 Mode Change # Away Mode
05/15 17:49 Dial Number # 3
05/15 17:49 Remote Signin - User # SMS Acknowledge
05/16 07:31 Zone Activation # StoreMainDoor (33)
If you dial the GSM number and there is silence, it could be that the 5 way audio cable was not connected betwen the GSM and Comfort PCB in the first place. I wonder if you have tried to dial before?
Try a remote reset from Comfigurator using Transfer > Reset System
Hi, I've used the voice dial-in to the GSM module before so it's unlikely to be a cable fault.
Looks like everything returned to normal about 3:30am so at least it is working now.
I saw a couple of the "SMS Acknowledge" events that you mentioned for when it did initially text me - I assume they only get set on dial-out activities and not for custom SMS message sending as I don't see them anywhere else in the event log?
If I ignore the 2 digit number on the end of the SMS Dial Failure messages then all I see in the log for a while is repeats of those plus these two messages:
SMS Trouble ID # UCM 2SMS Restore ID # UCM 2
I've connected this morning and downloaded the event log again but there is nothing new since my forum post last night and nothing around 3:30am when the custom text messages suddenly got sent. So, perhaps it was due to the local cell partially failing since the SMS module did say it had a good network signal.
If the "Trouble" messages above don't give any clues then I will have to do some specific power fail tests when I get back.
Yes I believe that it was a failure of the SMS provider to send messages even thpough the signal was good
Send SMS messages is not recorded in the event log as it is not considered to be an alarm event