Announcement

Collapse
No announcement yet.

SMS HS Server - beta 0.0.1

Collapse
This topic is closed.
X
This is a sticky topic.
X
X
Collapse
 
  • Page of 4
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 4 template Next
    #46
    It seems like the Siemens devices are a bit different than the rest of devices i have tried. You could try to send ATZ from hyper terminal prior to starting the SMS HS Server.

    And as always, make sure you have an updated firmware. I have reading a bit about Siemens devices lately, and it seems like the ones with old firmware might be a bit dodgy. But that goes for all hardware i guess.

    I will test with more devices as get my hands on them, including siemens.

    Comment

      #47
      Originally posted by skaar View Post
      It seems like the Siemens devices are a bit different than the rest of devices i have tried. You could try to send ATZ from hyper terminal prior to starting the SMS HS Server.

      And as always, make sure you have an updated firmware. I have reading a bit about Siemens devices lately, and it seems like the ones with old firmware might be a bit dodgy. But that goes for all hardware i guess.

      I will test with more devices as get my hands on them, including siemens.
      It's running the latest firmware I could get my hands on: v1.03.
      The ATZ command didn't help.

      Comment

        #48
        Hi Skaar,

        I have some problems with receiving SMS.
        Sending SMS is always working fine.
        Today I received a SMS as you can see in the LOG ( first line)
        This SMS was working fine and the trigger was execute.
        After that I was receiving more SMS but no trigger was fired.
        When I look in the cellphone I see that all the SMS are in there,what normally is not.
        Further in the LOG you see some SMS but thy where not send today.
        I think this are older SMS wich are in my cellphone.


        30.11.2009 19:01:57.278: # RCV SMS: +316xxxxxxxx, "lamp uit"
        30.11.2009 19:11:36.030: ERROR: Server: SmsComLib: Failed to set message index
        30.11.2009 19:12:29.752: ERROR: Server: SmsComLib: Failed to set message index
        30.11.2009 19:17:38.785: ERROR: Server: SmsComLib: Failed to set message index
        30.11.2009 19:23:08.851: HS Ver. 2.4.0.2
        30.11.2009 19:23:08.867: ************************************************************ ************
        30.11.2009 19:23:08.882: Skaar Production
        30.11.2009 19:23:08.882: SMS HS Server
        30.11.2009 19:23:08.898: hspi_smsHsServer, Version=0.0.4.0, Culture=neutral, PublicKeyToken=null
        30.11.2009 19:23:08.898: Beta version, expires 1-1-2010
        30.11.2009 19:23:08.913: ************************************************************ ************
        30.11.2009 19:24:01.510: ERROR: Server: SmsComLib: Failed to set message index
        30.11.2009 19:30:41.830: HS Ver. 2.4.0.2
        30.11.2009 19:30:41.830: ************************************************************ ************
        30.11.2009 19:30:41.846: Skaar Production
        30.11.2009 19:30:41.846: SMS HS Server
        30.11.2009 19:30:41.846: hspi_smsHsServer, Version=0.0.4.0, Culture=neutral, PublicKeyToken=null
        30.11.2009 19:30:41.861: Beta version, expires 1-1-2010
        30.11.2009 19:30:41.861: ************************************************************ ************
        30.11.2009 19:34:09.014: ERROR: Server: SmsComLib: Failed to set message index
        30.11.2009 19:44:45.755: DEBUG: Saving configuration
        30.11.2009 19:44:45.771: DEBUG: Server: Saved configuration data.
        30.11.2009 19:44:45.771: DEBUG: PagePut: Config data parsed and saved
        30.11.2009 19:45:24.695: DEBUG: Server: SmsComLib: RCV: +CMTI: "ME",16
        30.11.2009 19:45:24.695: DEBUG: Server: SmsComLib: SEND: AT+CPMS="ME"
        30.11.2009 19:45:24.742: DEBUG: Server: SmsComLib: RCV: AT+CPMS="ME"+CPMS: 6,150,10,10,16,160OK
        30.11.2009 19:45:25.055: DEBUG: Server: SmsComLib: SEND: AT+CMGR=16
        30.11.2009 19:45:25.289: ERROR: Server: SmsComLib: Failed to set message index
        30.11.2009 19:45:25.305: DEBUG: Server: SmsComLib: RCV: AT+CMGR=16+CMS ERROR: 321
        30.11.2009 19:51:26.297: DEBUG: Server: SmsComLib: RCV: +CMTI: "ME",17
        30.11.2009 19:51:26.297: DEBUG: Server: SmsComLib: SEND: AT+CPMS="ME"
        30.11.2009 19:51:26.312: DEBUG: Server: SmsComLib: RCV: AT+CPMS="ME"+CPMS: 7,150,10,10,17,160OK
        30.11.2009 19:51:26.625: DEBUG: Server: SmsComLib: SEND: AT+CMGR=17
        30.11.2009 19:51:26.890: ERROR: Server: SmsComLib: Failed to set message index
        30.11.2009 19:51:26.890: DEBUG: Server: SmsComLib: RCV: AT+CMGR=17+CMS ERROR: 321
        30.11.2009 20:16:53.519: DEBUG: Formatting trigger setup
        30.11.2009 20:16:53.535: DEBUG: SMS HS ServerRecieved SMS+316xxxxxxxxlamp aan
        30.11.2009 20:16:53.551: DEBUG: Parsing trigger information
        30.11.2009 20:16:53.551: DEBUG: "SMS HS ServerRecieved SMS+316xxxxxxxxlamp uit"
        30.11.2009 20:16:53.566: DEBUG: Parsing and verifying trigger data
        30.11.2009 20:16:53.566: DEBUG: "SMS HS ServerRecieved SMS+316xxxxxxxxlamp aan"
        30.11.2009 20:16:53.582: DEBUG: Formatting trigger setup completed
        30.11.2009 20:16:53.598: DEBUG: Formatting trigger setup
        30.11.2009 20:16:53.598: DEBUG: SMS HS ServerRecieved SMS*lamp aan
        30.11.2009 20:16:53.598: DEBUG: Parsing trigger information
        30.11.2009 20:16:53.613: DEBUG: "SMS HS ServerRecieved SMS*lamp aan"
        30.11.2009 20:16:53.613: DEBUG: Parsing and verifying trigger data
        30.11.2009 20:16:53.613: DEBUG: "SMS HS ServerRecieved SMS*lamp aan"
        30.11.2009 20:16:53.629: DEBUG: Formatting trigger setup completed
        30.11.2009 20:16:53.629: DEBUG: Formatting trigger setup
        30.11.2009 20:16:53.644: DEBUG: SMS HS ServerRecieved SMS*lamp uit
        30.11.2009 20:16:53.644: DEBUG: Parsing trigger information
        30.11.2009 20:16:53.644: DEBUG: "SMS HS ServerRecieved SMS*lamp uit"
        30.11.2009 20:16:53.660: DEBUG: Parsing and verifying trigger data
        30.11.2009 20:16:53.660: DEBUG: "SMS HS ServerRecieved SMS*lamp uit"
        30.11.2009 20:16:53.660: DEBUG: Formatting trigger setup completed
        30.11.2009 20:17:05.192: DEBUG: Server: 127.0.0.1 was granted access.
        30.11.2009 20:17:05.208: DEBUG: Server: SmsComLib: Sending message in TEXT mode
        30.11.2009 20:17:05.255: DEBUG: Server: SmsComLib: SEND: AT+CMGS="+316xxxxxxxx"
        30.11.2009 20:17:05.567: DEBUG: Server: SmsComLib: RCV: AT+CMGS="+316xxxxxxxx"
        30.11.2009 20:17:05.567: DEBUG: Server: SmsComLib: RCV: >
        30.11.2009 20:17:05.864: DEBUG: Server: SmsComLib: SEND: ** HomeSeer Bericht **
        De postbode is zojuist geweest.
        Er is weer post.
        30.11.2009 20:17:10.692: DEBUG: Server: SmsComLib: RCV: ** HomeSeer Bericht **De postbode is zojuist geweest.Er is weer post.> > +CMGS: 23OK
        30.11.2009 20:17:10.708: # SEND SMS: 127.0.0.1, +316xxxxxxxx, "** HomeSeer Bericht **
        De postbode is zojuist geweest.
        Er is weer post."
        30.11.2009 20:17:26.740: DEBUG: Server: 127.0.0.1 was granted access.
        30.11.2009 20:17:26.740: DEBUG: Server: SmsComLib: Sending message in TEXT mode
        30.11.2009 20:17:26.756: DEBUG: Server: SmsComLib: SEND: AT+CMGS="+316xxxxxxxx"
        30.11.2009 20:17:27.068: DEBUG: Server: SmsComLib: RCV: AT+CMGS="+316xxxxxxxx"
        30.11.2009 20:17:27.068: DEBUG: Server: SmsComLib: RCV: >
        30.11.2009 20:17:27.365: DEBUG: Server: SmsComLib: SEND: ** HomeSeer Bericht **
        Nieuwe melding op RFXCOM Alarm paneel
        30.11.2009 20:17:32.163: DEBUG: Server: SmsComLib: RCV: ** HomeSeer Bericht **Nieuwe melding op RFXCOM Alarm paneel> +CMGS: 24OK
        30.11.2009 20:17:32.163: # SEND SMS: 127.0.0.1, +316xxxxxxxx, "** HomeSeer Bericht **
        Nieuwe melding op RFXCOM Alarm paneel"
        30.11.2009 20:18:10.806: DEBUG: Server: SmsComLib: RCV: +CMTI: "ME",18
        30.11.2009 20:18:10.806: DEBUG: Server: SmsComLib: SEND: AT+CPMS="ME"
        30.11.2009 20:18:10.837: DEBUG: Server: SmsComLib: RCV: AT+CPMS="ME"+CPMS: 8,150,10,10,18,160OK
        30.11.2009 20:18:11.134: DEBUG: Server: SmsComLib: SEND: AT+CMGR=18
        30.11.2009 20:18:11.399: ERROR: Server: SmsComLib: Failed to set message index
        30.11.2009 20:18:11.399: DEBUG: Server: SmsComLib: RCV: AT+CMGR=18+CMS ERROR: 321
        30.11.2009 20:27:07.340: DEBUG: Formatting trigger setup
        30.11.2009 20:27:07.340: DEBUG: SMS HS ServerRecieved SMS+316xxxxxxxxlamp aan
        30.11.2009 20:27:07.340: DEBUG: Parsing trigger information
        30.11.2009 20:27:07.356: DEBUG: "SMS HS ServerRecieved SMS+316xxxxxxxxlamp uit"
        30.11.2009 20:27:07.356: DEBUG: Parsing and verifying trigger data
        30.11.2009 20:27:07.356: DEBUG: "SMS HS ServerRecieved SMS+316xxxxxxxxlamp aan"
        30.11.2009 20:27:07.371: DEBUG: Formatting trigger setup completed
        30.11.2009 20:27:07.371: DEBUG: Formatting trigger setup
        30.11.2009 20:27:07.387: DEBUG: SMS HS ServerRecieved SMS*lamp aan
        30.11.2009 20:27:07.387: DEBUG: Parsing trigger information
        30.11.2009 20:27:07.387: DEBUG: "SMS HS ServerRecieved SMS*lamp aan"
        30.11.2009 20:27:07.402: DEBUG: Parsing and verifying trigger data
        30.11.2009 20:27:07.402: DEBUG: "SMS HS ServerRecieved SMS*lamp aan"
        30.11.2009 20:27:07.402: DEBUG: Formatting trigger setup completed
        30.11.2009 20:27:07.418: DEBUG: Formatting trigger setup
        30.11.2009 20:27:07.418: DEBUG: SMS HS ServerRecieved SMS*lamp uit
        30.11.2009 20:27:07.418: DEBUG: Parsing trigger information
        30.11.2009 20:27:07.434: DEBUG: "SMS HS ServerRecieved SMS*lamp uit"
        30.11.2009 20:27:07.434: DEBUG: Parsing and verifying trigger data
        30.11.2009 20:27:07.434: DEBUG: "SMS HS ServerRecieved SMS*lamp uit"
        30.11.2009 20:27:07.449: DEBUG: Formatting trigger setup completed

        Comment

          #49
          Hi,
          i can can start by explaining a bit about the different messages. I have taken the last message as an example.

          ## This is were we are notified about a new message. "ME" states in which storage the message is stored in the phone/device. 18 states what the index of the message is in that particular storage.
          == RCV: +CMTI: "ME",18

          ## Based on the information we have, we tell the device that we will use the "ME" storage.
          == SEND: AT+CPMS="ME"

          ## As a response to our previous message, the device informs us about the storage status and ends the message with OK.
          == RCV: AT+CPMS="ME"+CPMS: 8,150,10,10,18,160OK

          ## Then we ask the device to return message with index 18 from storage "ME"
          SEND: AT+CMGR=18

          ## Error message from the plug-in
          == Failed to set message index

          ## This is a response that tells us that the device fails to get message with index 18, and ERROR 321 is according to 3GPP: "invalid memory index"
          == RCV: AT+CMGR=18+CMS ERROR: 321


          So I am not sure how to help you out. This is the exact same error as you had previously when you were strugling with the device driver. The plug-in is simply trying to get the message the device says it has stored.

          Comment

            #50
            I am sure I have no driver problem now.
            Sending SMS is still working.
            When I now send a SMS to HomeSeer I see that it is coming on my cellphone instead of HomeSeer.
            I am sure when I restart my HS server that it is working again for a short time.

            Comment

              #51
              pinballwizard,
              I have just tested with a Siemens MC35i rev 1.0.3 and done some adjustments to the plug-in. (Rev. Beta 0.0.5) My current tests shows that it is working very well now with this device. I used 9600-8N1 on the connecting serial port.

              Comment

                #52
                Originally posted by skaar View Post
                pinballwizard,
                I have just tested with a Siemens MC35i rev 1.0.3 and done some adjustments to the plug-in. (Rev. Beta 0.0.5) My current tests shows that it is working very well now with this device. I used 9600-8N1 on the connecting serial port.
                Thank you Skaar! I will test the beta 0.0.5 and put my results in this thread.

                pbw

                Comment

                  #53
                  Sorry to disappoint you Skaar, but still not working. This is the log:

                  10.12.2009 20:30:20.4218: HS Ver. 2.4.0.1
                  10.12.2009 20:30:20.4218: ************************************************************ ************
                  10.12.2009 20:30:20.4375: Skaar Production
                  10.12.2009 20:30:20.4375: SMS HS Server
                  10.12.2009 20:30:20.4375: hspi_smsHsServer, Version=0.0.5.0, Culture=neutral, PublicKeyToken=null
                  10.12.2009 20:30:20.4375: Beta version, expires 1/01/2010
                  10.12.2009 20:30:20.4375: ************************************************************ ************
                  10.12.2009 20:30:20.8125: DEBUG: Server: Configuring SMS service ...
                  10.12.2009 20:30:20.8125: DEBUG: Server: Starting SMS service ...
                  10.12.2009 20:30:20.8281: DEBUG: Server: SmsComLib: hspi_smsHsServer, Version=0.0.5.0, Culture=neutral, PublicKeyToken=null
                  10.12.2009 20:30:20.8281: DEBUG: Server: SmsComLib: Starting recieve thread ...
                  10.12.2009 20:30:20.8281: DEBUG: Server: SmsComLib: Starting send thread ...
                  10.12.2009 20:30:20.8593: DEBUG: Server: SmsComLib: Init complete
                  10.12.2009 20:30:20.8593: DEBUG: Server: Register tcp channel ...
                  10.12.2009 20:30:20.8593: DEBUG: Server: Init complete.
                  10.12.2009 20:30:20.8593: DEBUG: Loaded configuration
                  10.12.2009 20:30:20.8750: DEBUG: Searching for devices ...
                  10.12.2009 20:30:20.8750: DEBUG: Found existing device, HC: ^, DC: 2
                  10.12.2009 20:30:20.8750: DEBUG: Found existing device, HC: ^, DC: 1
                  10.12.2009 20:30:20.8750: DEBUG: Done creating device
                  10.12.2009 20:30:20.8750: DEBUG: Register the server object ...
                  10.12.2009 20:30:20.8750: DEBUG: The service started successfully.
                  10.12.2009 20:30:20.8906: DEBUG: Server: SmsComLib: Initializing AT commands ...
                  10.12.2009 20:30:20.9062: DEBUG: Server: SmsComLib: Applying port configuration
                  10.12.2009 20:30:20.9062: DEBUG: Server: SmsComLib: Opening port
                  10.12.2009 20:30:20.9062: DEBUG: Server: SmsComLib: Flushing port buffer
                  10.12.2009 20:30:20.9062: DEBUG: Server: SmsComLib: Testing device connectivity ...
                  10.12.2009 20:30:20.9218: DEBUG: Server: SmsComLib: SEND: AT
                  10.12.2009 20:30:35.9218: ERROR: Server: SmsComLib: Operation towards the serial port timed out
                  10.12.2009 20:30:35.9218: DEBUG: Server: SmsComLib: RCV:
                  10.12.2009 20:30:35.9218: ERROR: Server: SmsComLib: Failed to communicate with device. Check serial port setting
                  10.12.2009 20:30:35.9218: DEBUG: Server: SmsComLib: Closing port
                  10.12.2009 20:30:35.9375: DEBUG: Instantiate config web page
                  10.12.2009 20:30:35.9375: DEBUG: Instantiate config web page completed
                  10.12.2009 20:31:19.7500: DEBUG: GenPage: Creating page content
                  10.12.2009 20:31:19.7500: DEBUG: GenPage: Create page content completed

                  There is no reaction to the AT command. Doesn't this command need more arguments?

                  pbw

                  Comment

                    #54
                    pinballwizard, that is strange. I have never had any problems connecting to the MC35i i have at home now. It worked the first time i tried. There was some other issues that i have fixed in the current version of the plug-in.
                    "AT" is used without parameters as the first message just to check the connectivity to the device. Please see the log from my installation:



                    10.12.2009 22:06:11.5597: HS Ver. 2.4.0.1
                    10.12.2009 22:06:11.5597: ************************************************************ ************
                    10.12.2009 22:06:11.5597: Skaar Production
                    10.12.2009 22:06:11.5597: SMS HS Server
                    10.12.2009 22:06:11.5597: hspi_smsHsServer, Version=0.0.5.0, Culture=neutral, PublicKeyToken=null
                    10.12.2009 22:06:11.5597: Beta version, expires 01.01.2010
                    10.12.2009 22:06:11.5597: ************************************************************ ************
                    10.12.2009 22:06:11.5754: DEBUG: Server: Configuring SMS service ...
                    10.12.2009 22:06:11.5754: DEBUG: Server: Starting SMS service ...
                    10.12.2009 22:06:11.5754: DEBUG: Server: SmsComLib: hspi_smsHsServer, Version=0.0.5.0, Culture=neutral, PublicKeyToken=null
                    10.12.2009 22:06:11.5754: DEBUG: Server: SmsComLib: Starting recieve thread ...
                    10.12.2009 22:06:11.5754: DEBUG: Server: SmsComLib: Starting send thread ...
                    10.12.2009 22:06:11.5754: DEBUG: Server: SmsComLib: Init complete
                    10.12.2009 22:06:11.5754: DEBUG: Server: Register tcp channel ...
                    10.12.2009 22:06:11.5754: DEBUG: Server: Init complete.
                    10.12.2009 22:06:11.5754: DEBUG: Loaded configuration
                    10.12.2009 22:06:11.5754: DEBUG: Searching for devices ...
                    10.12.2009 22:06:11.5754: DEBUG: Found existing device, HC: [, DC: 1
                    10.12.2009 22:06:11.5754: DEBUG: Found existing device, HC: [, DC: 2
                    10.12.2009 22:06:11.5754: DEBUG: Done creating device
                    10.12.2009 22:06:11.5754: DEBUG: Register the server object ...
                    10.12.2009 22:06:11.5754: DEBUG: The service started successfully.
                    10.12.2009 22:06:11.5910: DEBUG: Server: SmsComLib: Initializing AT commands ...
                    10.12.2009 22:06:11.5910: DEBUG: Server: SmsComLib: Applying port configuration
                    10.12.2009 22:06:11.5910: DEBUG: Server: SmsComLib: Opening port
                    10.12.2009 22:06:11.7004: DEBUG: Server: SmsComLib: Flushing port buffer
                    10.12.2009 22:06:11.7004: DEBUG: Server: SmsComLib: Testing device connectivity ...
                    10.12.2009 22:06:11.7004: DEBUG: Server: SmsComLib: SEND: AT
                    10.12.2009 22:06:11.7472: DEBUG: Server: SmsComLib: RCV: ATOK
                    10.12.2009 22:06:12.0441: DEBUG: Server: SmsComLib: Getting manufacturer identification ...
                    10.12.2009 22:06:12.0441: DEBUG: Server: SmsComLib: SEND: AT+CGMI
                    10.12.2009 22:06:12.1223: DEBUG: Server: SmsComLib: RCV: AT+CGMISIEMENSOK
                    10.12.2009 22:06:12.4348: DEBUG: Server: SmsComLib: Getting model identification ...
                    10.12.2009 22:06:12.4348: DEBUG: Server: SmsComLib: SEND: AT+CGMM
                    10.12.2009 22:06:12.4973: DEBUG: Server: SmsComLib: RCV: AT+CGMMMC35iOK
                    10.12.2009 22:06:12.7941: DEBUG: Server: SmsComLib: Getting revision identification ...
                    10.12.2009 22:06:12.7941: DEBUG: Server: SmsComLib: SEND: AT+CGMR
                    10.12.2009 22:06:12.8879: DEBUG: Server: SmsComLib: RCV: AT+CGMRREVISION 01.03OK
                    10.12.2009 22:06:13.1848: DEBUG: Server: SmsComLib: Setting PDU mode SMS ...
                    10.12.2009 22:06:13.1848: DEBUG: Server: SmsComLib: SEND: AT+CMGF=0
                    10.12.2009 22:06:13.2473: DEBUG: Server: SmsComLib: RCV: AT+CMGF=0OK
                    10.12.2009 22:06:13.5441: DEBUG: Server: SmsComLib: Setting Calling Line Identification Presentation ...
                    10.12.2009 22:06:13.5441: DEBUG: Server: SmsComLib: SEND: AT+CLIP=1
                    10.12.2009 22:06:13.6066: DEBUG: Server: SmsComLib: RCV: AT+CLIP=1OK
                    10.12.2009 22:06:13.9035: DEBUG: Server: SmsComLib: Checking +CNMI support ...
                    10.12.2009 22:06:13.9035: DEBUG: Server: SmsComLib: SEND: AT+CNMI=?
                    10.12.2009 22:06:14.0285: DEBUG: Server: SmsComLib: RCV: AT+CNMI=?+CNMI: (0-3),(0,1),(0,2,3),(0,2),(1)OK
                    10.12.2009 22:06:14.3254: DEBUG: Server: SmsComLib: Setting New Message Indication ...
                    10.12.2009 22:06:14.3254: DEBUG: Server: SmsComLib: SEND: AT+CNMI=2,1,0,0,1
                    10.12.2009 22:06:14.4192: DEBUG: Server: SmsComLib: RCV: AT+CNMI=2,1,0,0,1OK
                    10.12.2009 22:06:14.4192: DEBUG: Server: SmsComLib: AT init complete
                    10.12.2009 22:06:14.4192: DEBUG: Instantiate config web page
                    10.12.2009 22:06:14.4192: DEBUG: Instantiate config web page completed

                    Comment

                      #55
                      Skaar, if I understand this right I must receive (in Hyperterminal) a response to the "AT" command looking like "AT OK". I definetly don't get that! No reply from the modem.

                      But "ATI" is responding with 3 lines:

                      SIEMENS
                      MC35i
                      Revision 01.03

                      Also AT&V is responding with a hole list of registers. I have a second MC35i doing exactly the very same thing.

                      pbw

                      Comment

                        #56
                        Problem solved

                        Skaar, I took the manual and found a command to restore the factory defaults: AT&F. After that the modem responds to the AT command with OK and your plugin loads without errors.

                        I guess I can start testing your plugin now!

                        Many thanks for your support,

                        pbw

                        Comment

                          #57
                          I have build up my new HS system and want to use this plugin again,but there is not much activity here anymore.
                          Is the plugin still working or has the date expire?

                          Comment

                            #58
                            Looks like the plugin has an expiry date, which is a shame..
                            ---------------------------------------------------http://weather.penicuik.org

                            Comment

                            Previous 1 2 3 4 template Next
                            Working...
                            X