SMS HS Server - beta 0.0.1

[skaar]

antoon,
i have uploaded an update that includes a device where you can see the last SMS received.

[william.abbo]

M20

Anyone tested this plugin with the Siemens M20? This plugin looks like a very usefull piece of software, hopefully the M20 is supported.

Maybe some-one is willimg to put some screenshot of the package on the forum?

[antoon]

antoon,
i have uploaded an update that includes a device where you can see the last SMS received.

Thats great,I will instal and test it tomorrow.
Thanks,

[skaar]

Hi william.abbo,
i see no reason why the M20 should not work.

I have updated the initial post with links to screenshots.

[antoon]

Install the new version and devices with latest call and sms is working perfect.

I have two questions.

First, When I want to switch on a lamp by a trigger of my cellphone with the number and text it is working.
But when I put in the * instead of a number and try again the lamp is not going on.
Can I only trigger by a number I put in?

Second one,can there only be set one device for received SMS?
I see no option in the configuration page to set more.

Thanks,

[skaar]

antoon,
currently you cannot use * for any with the trigger, it has to be a phone number. But i could change that. Please note that any phone could then execute the trigger, given they know the text string.

Yes, there can only be one device for received SMS or received phone call. The plug-in is only supporting one modem, and there is one device per modem.

[pinballwizard]

MC35i SIEMENS

Hello Skaar,

any chance your plugin might work with the Siemens MC35i terminal modem. All AT commands can be found here: http://telematika.com.ua/index2.php?...id=9&Itemid=29

The log shows a port timeout after the first AT command. I got this modem working with SMSconnector but I prefer to use your way to send and receive SMS.

Cheers,

Ivo

[skaar]

I see no reason why MC35i should not work. Please make sure you have selected the correct com port in the plug-in setup, and that the port is not in use.

[william.abbo]

M20

Skaar,

This week I will test the software with the Siemens M20, I will keep you informed.

[skaar]

I have now added an option to use * to allow any phone to fire the SMS trigger in SMS HS Server, according to the request from antoon. Version 0.0.4.0

[pinballwizard]

Siemens MC35i

I see no reason why MC35i should not work. Please make sure you have selected the correct com port in the plug-in setup, and that the port is not in use.

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

[skaar]

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, ....)

[pinballwizard]

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, ....)

Thank you for your fast response. I will double check baud rate, data bits, parity and handshaking once more this evening. I tried to open the com port from the CMD window but HomeTroller is using WIN XP embedded, so not all functionality is standard available.

I'll get back to you later,

Ivo

[antoon]

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

[william.abbo]

M20

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.