SMS HS Server - beta 0.0.1

[antoon]

It is working again.
Had some problem with the driver from my Nokia 6230i
Thanks for adding the option.

[skaar]

Skaar,

I have installed the latest version.
Received SMS on a trigger set to * has worked for 3 times but now nothing wokrs anymore.
Also not when I trigger on a number.
When I set on debug and look in the log I see this.

24.11.2009 20:29:01.249: ERROR: Server: SmsComLib: Failed to set message index
24.11.2009 20:32:18.854: ERROR: Server: SmsComLib: Failed to set message index
24.11.2009 20:36:10.586: ERROR: Server: SmsComLib: Failed to set message index
24.11.2009 20:37:47.373: ERROR: Server: SmsComLib: Failed to set message index
24.11.2009 20:38:48.564: ERROR: Server: SmsComLib: Failed to set message index
24.11.2009 20:39:55.130: DEBUG: Saving configuration
24.11.2009 20:39:55.146: DEBUG: Server: Saved configuration data.
24.11.2009 20:39:55.162: DEBUG: PagePut: Config data parsed and saved
24.11.2009 20:40:22.429: DEBUG: Server: SmsComLib: RCV: +CMTI: "ME",16
24.11.2009 20:40:22.460: DEBUG: Server: SmsComLib: SEND: AT+CPMS="ME"
24.11.2009 20:40:22.491: DEBUG: Server: SmsComLib: RCV: +CPMS: 6,150,10,10,16,160OK
24.11.2009 20:40:22.804: DEBUG: Server: SmsComLib: SEND: AT+CMGR=16
24.11.2009 20:40:22.804: ERROR: Server: SmsComLib: Failed to set message index
24.11.2009 20:40:22.819: DEBUG: Server: SmsComLib: RCV: +CMS ERROR: 321
24.11.2009 20:41:50.074: DEBUG: GenPage: Creating page content
24.11.2009 20:41:50.074: DEBUG: GenPage: Create page content completed

Hi antoon. I don't think this is related to the new feature. +CMS ERROR: 321 means "Invalid memory index", issued from the device after i try to get the message from index 16 in the ME storage. According to the "RCV: +CMTI: "ME",16", that is where the new message should be. According to the +CPMS there should still be storage available for new messages, but you could check it anyway. Try to delete old test messages if you don't need them anymore.

[skaar]

It is working again.
Had some problem with the driver from my Nokia 6230i
Thanks for adding the option.

Ohh good. I did not see any reason why you should suddenly end up with this problem.

[skaar]

Skaar,

Just tested with my Siemens M20, received a SMS, it was logged but the trigger was not only fired once. Next SMS's did not fire the trigger anymore because they did not appear in the log anymore. It seemed that devices [1 and [2 allready existed, they where created bij BLWeather. I temporarily deleted those 2 devices and after a restart SMS HS Server did create them, but I'am sure the next time BLWeather will refresh they are overwritten.

The reason the new received SMS's did not appear anymore is the AT+CNMI parameter. When I connect to the M20 with hyperterminal and set +CNMI=1,2,0,0,1 the messages will roll out of the M20 at once, this is also the setting Stippus SMS-connector is using and is working fine. Your software is sending AT+CNMI=1,2,0,0,0

Please make it possible to manualy add the AT-string in the setup and to select a housecode in the software, or try to create a ini-file which can be editted by the user.

If necessary, i will add the options. But first, i would like to see a debug log, if possible. Enable debug in the SMS HS Server plug-in configuration, and restart the plug-in. Then receive a SMS, and post the log. Thank you.

[william.abbo]

Skaar,

Here is the requested logfile. At starting the plugin you can see the devices are created again although BLWeather had allready created them again. So now I have 2 times [1 and [2. After a restart of HS I have send 2 SMS's, they do not appear as you can see. When I look in the M20 with the CNMI=1,2,0,0,1 setting they appear immediatly.

[skaar]

Skaar,

Here is the requested logfile. At starting the plugin you can see the devices are created again although BLWeather had allready created them again. So now I have 2 times [1 and [2. After a restart of HS I have send 2 SMS's, they do not appear as you can see. When I look in the M20 with the CNMI=1,2,0,0,1 setting they appear immediatly.

Thanks for the log. I tested with the BLWeather plug-in, but it caused my HS installation to hang during startup, so i had to remove it.
I am pretty sure that i am following the HomeSeer implementation guidelines with regards to the HouseCode, but I will discuss this further with HomeSeer support.

Regarding the new message indication. My default devices only supports mode 2 and mt 0,1 or 3. According to 3GPP 07.05 rel. 98, the only reason mode 2 mt 1 would not send the indication, is if the message is not stored successfully, e.g receiving Class0 SMS. The current implementation is based on indication of storage and index, and then the plug-in will get the message manually from the storage. By using mt 3, the current implementation will not handle Class3 SMS, but i might even implement support for that as well.

Can you try if the M20 supports +CNMI=2,3,0,0,0?

[skaar]

Skaar,

Just tested with my Siemens M20, received a SMS, it was logged but the trigger was not only fired once. Next SMS's did not fire the trigger anymore because they did not appear in the log anymore. It seemed that devices [1 and [2 allready existed, they where created bij BLWeather. I temporarily deleted those 2 devices and after a restart SMS HS Server did create them, but I'am sure the next time BLWeather will refresh they are overwritten.

The reason the new received SMS's did not appear anymore is the AT+CNMI parameter. When I connect to the M20 with hyperterminal and set +CNMI=1,2,0,0,1 the messages will roll out of the M20 at once, this is also the setting Stippus SMS-connector is using and is working fine. Your software is sending AT+CNMI=1,2,0,0,0

Please make it possible to manualy add the AT-string in the setup and to select a housecode in the software, or try to create a ini-file which can be editted by the user.

What do you mean by ".. received a SMS, it was logged but ..". Where was it logged, and what was in the log?

[william.abbo]

What do you mean by ".. received a SMS, it was logged but ..". Where was it logged, and what was in the log?

The received sms was logged in the SMS HS Server log, only the first SMS fired the the trigger. A second send SMS was also written in this log but did not fire the trigger. FYI this was not on the log-file I send you.

[william.abbo]

Thanks for the log. I tested with the BLWeather plug-in, but it caused my HS installation to hang during startup, so i had to remove it.
I am pretty sure that i am following the HomeSeer implementation guidelines with regards to the HouseCode, but I will discuss this further with HomeSeer support.

Regarding the new message indication. My default devices only supports mode 2 and mt 0,1 or 3. According to 3GPP 07.05 rel. 98, the only reason mode 2 mt 1 would not send the indication, is if the message is not stored successfully, e.g receiving Class0 SMS. The current implementation is based on indication of storage and index, and then the plug-in will get the message manually from the storage. By using mt 3, the current implementation will not handle Class3 SMS, but i might even implement support for that as well.

Can you try if the M20 supports +CNMI=2,3,0,0,0?

Skaar,

AT+CNMI=2,3,0,0,0 is supported by the M20, that is: it is accepted, but when I send a sms nothing will show up in hyperterminal, although the sms is received and stored. Switching back to CNMI=1,2,0,0,1 will bring up all new unread stored messages when a new sms is received. Mybe the manual will be more helpfull, I hope.
A lot of people are using the M20 and your program has nice features, so I (we) hope you will find a solution.

Here you have the link to the full M20 manual:
http://files.binkey.nl/Manuals/GSM%20Modules/m20_v5.pdf

[skaar]

The received sms was logged in the SMS HS Server log, only the first SMS fired the the trigger. A second send SMS was also written in this log but did not fire the trigger. FYI this was not on the log-file I send you.

But that means that +CNMI=2,1,0,0,0 is actually working on M20, but there is something wrong with the trigger. Can you do a debug log where this is actually recorded, and i'll have a look.

[william.abbo]

But that means that +CNMI=2,1,0,0,0 is actually working on M20, but there is something wrong with the trigger. Can you do a debug log where this is actually recorded, and i'll have a look.

What exactly do you want me to do?

[skaar]

What exactly do you want me to do?

You stated: "The received sms was logged in the SMS HS Server log, only the first SMS fired the the trigger. A second send SMS was also written in this log but did not fire the trigger. FYI this was not on the log-file I send you."

Enable debug, and do the same things you did the last time when the SMS was logged in the SMS HS Server log.

[william.abbo]

But that means that +CNMI=2,1,0,0,0 is actually working on M20, but there is something wrong with the trigger. Can you do a debug log where this is actually recorded, and i'll have a look.

O.k. I hope this is what you want to see: enabled the plugin, restarted HS, send a few sms's. The HS event is not triggered as you can see.
BLWeather is using [1 and [2.

Success and greetings

Edit: after this test I disabled your plugin and re-enabled the SMS-connector plugin, at that moment the test sms's I send to your plugin came out of the M20.

[skaar]

Ok, thanks. I'll see if i can get my hands on a M20, and implement support for it.

[pinballwizard]

Hi Skaar,

I've tested it once more on the same port used by the SMSConnector plugin. I disabled the SMSConnector and enabled both your plugins, then rebooted HS2Pro. My MC35i is on COM 4 but gives an error on startup of HS2Pro (HomeTroller). This is in the log:

24.11.2009 10:49:32.828: HS Ver. 2.4.0.1
24.11.2009 10:49:32.828: ************************************************************ ************
24.11.2009 10:49:32.828: Skaar Production
24.11.2009 10:49:32.828: SMS HS Server
24.11.2009 10:49:32.828: hspi_smsHsServer, Version=0.0.4.0, Culture=neutral, PublicKeyToken=null
24.11.2009 10:49:32.828: Beta version, expires 1/01/2010
24.11.2009 10:49:32.828: ************************************************************ ************
24.11.2009 10:49:32.937: DEBUG: Server: Configuring SMS service ...
24.11.2009 10:49:32.937: DEBUG: Server: Starting SMS service ...
24.11.2009 10:49:32.953: DEBUG: Server: SmsComLib: hspi_smsHsServer, Version=0.0.4.0, Culture=neutral, PublicKeyToken=null
24.11.2009 10:49:32.953: DEBUG: Server: SmsComLib: Starting recieve thread ...
24.11.2009 10:49:32.968: DEBUG: Server: SmsComLib: Starting send thread ...
24.11.2009 10:49:33.000: DEBUG: Server: SmsComLib: Init complete
24.11.2009 10:49:33.000: DEBUG: Server: Register tcp channel ...
24.11.2009 10:49:33.000: DEBUG: Server: Init complete.
24.11.2009 10:49:33.000: DEBUG: Loaded configuration
24.11.2009 10:49:33.000: DEBUG: Searching for devices ...
24.11.2009 10:49:33.000: DEBUG: Found existing house code, hc: ^
24.11.2009 10:49:33.000: DEBUG: Found existing house code, hc: ^
24.11.2009 10:49:33.000: DEBUG: Done creating device
24.11.2009 10:49:33.000: DEBUG: Register the server object ...
24.11.2009 10:49:33.015: DEBUG: The service started successfully.
24.11.2009 10:49:33.015: DEBUG: Server: SmsComLib: Initializing AT commands ...
24.11.2009 10:49:33.031: DEBUG: Server: SmsComLib: Applying port configuration
24.11.2009 10:49:33.046: DEBUG: Server: SmsComLib: Opening port
24.11.2009 10:49:33.046: DEBUG: Server: SmsComLib: Flushing port buffer
24.11.2009 10:49:33.046: DEBUG: Server: SmsComLib: Testing device connectivity ...
24.11.2009 10:49:33.046: DEBUG: Server: SmsComLib: SEND: AT
24.11.2009 10:49:48.062: ERROR: Server: SmsComLib: Operation towards the serial port timed out
24.11.2009 10:49:48.062: DEBUG: Server: SmsComLib: RCV:
24.11.2009 10:49:48.078: ERROR: Server: SmsComLib: Failed to communicate with device. Check serial port setting
24.11.2009 10:49:48.078: DEBUG: Server: SmsComLib: Closing port
24.11.2009 10:49:48.093: DEBUG: Instantiate config web page
24.11.2009 10:49:48.093: DEBUG: Instantiate config web page completed

Can you please solve my problem?

Ivo

Have you checked the COM port settings? Configure the port parameters in SMS HS according to your previous configuration that you know is working. I'm not sure how to do this with HomeTroller, but on Win XP, I would check with hyper terminal or similar, to verify that the port settings are working. (baud rate, data bits, ....)

Hello Skaar,

I've tested my modem on COM4 using Hyper terminal. If I send a command like in the log:
24.11.2009 10:49:33.046: DEBUG: Server: SmsComLib: SEND: AT
it does not respond, but if I send AT&V it answers as expected. I'm not an expert in modems, but is the AT command in the log complete? This modem has the same settings as SMS connector and that plugin is working. I'm using no parity, 8 Dbits, 1 Stopbit, no HW handshaking.

Cheers,

Ivo