Announcement

Collapse
No announcement yet.

My new IP2SL is connecting to z-troller at 9600 baud, not 115,200 baud

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    My new IP2SL is connecting to z-troller at 9600 baud, not 115,200 baud

    The homeseer store says to connect the IP2SL at 115,200 baud. However, I'm only getting it to connect with the z-troller at 9600 baud. What might I be doing wrong?

    How do I get it to work at 115,200 baud?

    Both the IP2SL and the z-troller and running the latest available firmware respectively.

    #2
    Make sure the Z-Troller is set to the correct baud rate. Hold add/del down for a few seconds and you'll see the baud rate it's set to. It should show 115. If yours comes up 9600, release the buttons and press again to move it to 115.
    -Rupp
    sigpic

    Comment


      #3
      My z-troller is fairly new. It doesn't seem to show the baud rate using the method you suggested. According to Randman (http://board.homeseer.com/showthread.php?p=980738), the ability to switch baud rates with the buttons was removed.

      Is there some other way to set the baud rate?

      Comment


        #4
        Run the iHelp application for the IP2SL and you can set the baud rate there...

        Sent from my Xoom using Tapatalk HD
        HS4Pro Running on a Raspberry Pi4
        72 Z-Wave Nodes, 111 Events, 422 Devices
        Z-Wave, UPB, WiFi
        Plugins: EasyTrigger, weatherXML, OMNI, Z-Wave, Tuya, Device History
        HSTouch Clients: 3 Android, 1 Joggler

        Comment


          #5
          Yes, but when I change the IP2SL to the 115,200 baud, the communication with the z-troller breaks down:

          6/28/2013 11:58:47 PM - Z-Wave - Warning - failed receiving an interface acknowledgement for a controller command before timeout - the command may not have succeeded.
          6/28/2013 11:58:53 PM - Z-Wave - Warning - failed receiving an interface acknowledgement for a controller command before timeout - the command may not have succeeded.
          6/28/2013 11:58:57 PM - Warning - In Z-Wave init(A), no response getting initialization information.
          6/28/2013 11:58:57 PM - Warning - Trying to re-connect to Ethernet interface at IP 192.168.1.88...


          It would seem that the z-troller is at 9600 baud, but I don't know how to change it since that functionality (as confirmed by Randman) seems to have been removed. i.e. the 2 button method that Rupp suggested doesn't seem to be doing anything.

          At least it works at 9600 baud for now....
          Last edited by NeverDie; June 29, 2013, 12:01 AM.

          Comment


            #6
            According to MacroMark in http://board.homeseer.com/showthread.php?t=145905, only the z-troller firmwares of 1.15 and before support multiple baud rates. Firmware 1.16, according to MacroMark, does not.

            If z-troller's with firmware 1.17 now also only support one baud rate, does that baud rate happen to be 9600? That would seem to introduce noticeable latency into the system, especially in the case where a scene controller is using HomeSeer to activate scenes (which is what the HomeSeer technical people seem to recommend instead of using more direct and faster scene associations). There's enough latency in z-wave communications that adding more latency in communications between HSPRO and z-troller would make it all the more noticeable.

            Maybe I'm better off reverting my z-troller to firmware 1.15? I don't have z-wave door locks. Where can I find version 1.15?

            Comment


              #7
              The HomeSeer log should show the baud rate the device is connecting at. What does it report?

              Sent from my SCH-I535 using Tapatalk 4 Beta
              -Rupp
              sigpic

              Comment


                #8
                If it says it, I sure don't see it. Here's the log when I startup HSPRO:


                6/29/2013 10:16:11 AM - Startup -
                6/29/2013 10:16:11 AM - Startup - ************************************************************ ********************
                6/29/2013 10:16:11 AM - Startup - HomeSeer version 2.5.0.49 Starting Now (PRO Build)
                6/29/2013 10:16:11 AM - Startup - ************************************************************ ********************
                6/29/2013 10:16:11 AM - Startup -
                6/29/2013 10:16:11 AM - Startup - Using system's regional settings
                6/29/2013 10:16:13 AM - Startup - Creating Class Objects...
                6/29/2013 10:16:13 AM - Startup - COM port classes started.
                6/29/2013 10:16:13 AM - Startup - Application interface class started.
                6/29/2013 10:16:13 AM - Startup - Web server class started.
                6/29/2013 10:16:13 AM - Startup - E-Mail SEND class started.
                6/29/2013 10:16:13 AM - Startup - E-Mail RECEIVE class started.
                6/29/2013 10:16:13 AM - Startup - Z-Wave class started.
                6/29/2013 10:16:13 AM - Startup - Plug-In Interface class started.
                6/29/2013 10:16:13 AM - Startup - Speech recognition class started.
                6/29/2013 10:16:13 AM - Startup - HSPhone dialer class started.
                6/29/2013 10:16:13 AM - Startup - Loading Settings
                6/29/2013 10:16:13 AM - Startup - Settings Loaded.
                6/29/2013 10:16:13 AM - Startup - Current sunrise/sunset values calculated.
                6/29/2013 10:16:13 AM - Startup - HSPhone external interface class started.
                6/29/2013 10:16:13 AM - Startup - Local voice recognition class started.
                6/29/2013 10:16:13 AM - Startup - Database SAVE process started.
                6/29/2013 10:16:13 AM - Startup - Loading configuration file ...
                6/29/2013 10:16:13 AM - System - Loading device types file...
                6/29/2013 10:16:14 AM - Database - Opening (Mode=Read) up HomeSeer database: C:\Program Files (x86)\HomeSeer HSPRO\config\sample.mdb
                6/29/2013 10:16:14 AM - Database - Loading Devices...
                6/29/2013 10:16:14 AM - Load Config - 1 total devices loaded.
                6/29/2013 10:16:14 AM - Load Config - Checking device type settings for all devices...
                6/29/2013 10:16:14 AM - Load Config - Finished checking device type settings.
                6/29/2013 10:16:14 AM - Load Config - Loading Events...
                6/29/2013 10:16:14 AM - Load Config - 20 total events loaded.
                6/29/2013 10:16:14 AM - Database - HomeSeer configuration database C:\Program Files (x86)\HomeSeer HSPRO\config\sample.mdb has been closed.
                6/29/2013 10:16:14 AM - Startup - HomeSeer version is: 2.5.0.49
                6/29/2013 10:16:14 AM - Startup - Starting remoting (Remote client connection monitor)
                6/29/2013 10:16:14 AM - Startup - Creating Speaker Client Interface Object...
                6/29/2013 10:16:14 AM - Startup - Initializing phone interface...
                6/29/2013 10:16:14 AM - HSPhone - HomeSeer Phone Web Interface initializing.
                6/29/2013 10:16:14 AM - Startup - Checking for pending updates to be installed...
                6/29/2013 10:16:14 AM - Startup - Restoring Device Status...
                6/29/2013 10:16:14 AM - Z-Wave - :- :- :- :- :- :- :- :- Initializing Z-Wave Interface -: -: -: -: -: -: -: -:
                6/29/2013 10:16:14 AM - Z-Wave - Initializing Z-Wave Interface on Ethernet port: 4999 IP Address: 192.168.1.88
                6/29/2013 10:16:14 AM - Z-Wave - Z-Wave Ethernet at IP 192.168.1.88, connected to interface ok.
                6/29/2013 10:16:14 AM - Z-Wave - Getting node information from controller...
                6/29/2013 10:16:15 AM - Z-Wave - Z-Wave Serial API version: 4
                6/29/2013 10:16:15 AM - Z-Wave - Z-Wave interface node ID: 1, Home ID: 003D3D2A
                6/29/2013 10:16:15 AM - Z-Wave - Found 2 Z-Wave nodes in interface node ID 1
                6/29/2013 10:16:15 AM - Z-Wave - Controller Manufacturer: HomeSeer Tech, ID=0x2, Type=0x1
                6/29/2013 10:16:15 AM - Z-Wave - Controller firmware version: 1.17
                6/29/2013 10:16:16 AM - Z-Wave - This Z-Wave PC Controller Library Version is: Z-Wave 3.28 (ZDK Version 5.03)
                6/29/2013 10:16:16 AM - Z-Wave - This Z-Wave PC Controller is Type: ZW_LIB_INSTALLER
                6/29/2013 10:16:16 AM - Z-Wave - Z-Wave services for communications to nodes utilizing the SECURITY COMMAND CLASS were successfully started.
                6/29/2013 10:16:16 AM - Z-Wave - -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
                6/29/2013 10:16:16 AM - Startup - Checking for available plug-ins
                6/29/2013 10:16:16 AM - Startup - Initializing Plug-Ins
                6/29/2013 10:16:16 AM - Plug-In - Finished initializing X10 interface
                6/29/2013 10:16:17 AM - Plug-In - Finished initializing infrared interface
                6/29/2013 10:16:17 AM - Web Server - Local IP address (subnet) is: 192.168.1.72 (255.255.255.0)
                6/29/2013 10:16:17 AM - Web Server - Web Server started on port 81
                6/29/2013 10:16:17 AM - Web Server - UPNP Discovery started
                6/29/2013 10:16:17 AM - Startup - Creating ASP.NET application host...
                6/29/2013 10:16:18 AM - Startup - ASP.NET application host created
                6/29/2013 10:16:18 AM - Startup - Start automation engine...
                6/29/2013 10:16:18 AM - Startup - Initializing Speaker Client Interface
                6/29/2013 10:16:18 AM - Speech - Listening for remote speaker connections on port 8742
                6/29/2013 10:16:18 AM - Startup - HS2Sentry is disabled in Setup, sentry will not be started.
                6/29/2013 10:16:18 AM - Startup - Starting Event Scheduler...
                6/29/2013 10:16:18 AM - Z-Wave - Starting Z-Wave Polling...
                6/29/2013 10:16:18 AM - Z-Wave - Starting 'Z-Wave Health' Process Starter...
                6/29/2013 10:16:18 AM - Startup - Checking HTTP connection...
                6/29/2013 10:16:18 AM - Web Server - Web Server authorized local login successful from: 127.0.0.1 User: default
                6/29/2013 10:16:18 AM - Startup - Updater services starting...
                6/29/2013 10:16:18 AM - Startup - Starting DDNS service...
                6/29/2013 10:16:18 AM - Startup - Running the Startup.txt Script
                6/29/2013 10:16:18 AM - Startup - Scripting is OK and is now running Startup.txt
                6/29/2013 10:16:18 AM - Startup - Start up complete.

                Comment


                  #9
                  The IP2SL should enforce the 115200 since the serial port lives on the device. Do you have the other serial parms set right:
                  Attached Files
                  HS4Pro Running on a Raspberry Pi4
                  72 Z-Wave Nodes, 111 Events, 422 Devices
                  Z-Wave, UPB, WiFi
                  Plugins: EasyTrigger, weatherXML, OMNI, Z-Wave, Tuya, Device History
                  HSTouch Clients: 3 Android, 1 Joggler

                  Comment


                    #10
                    Presently, mine is set at 9600. If I set it to 115200 like yours, then the communication between the IP2SL and the z-troller stops working. The other parameters are the same, although the layout is a little different. I would attach a screen scrape like you did so that you can see, but I don't see how to do that: when I click on the insert image icon on this forum, it prompts me for the URL of the image rather than a file name. Do I have to post the image somewhere on the web in order to include it in this forum?

                    Also, between my post immediately above and now, I upgraded to HSPRO version 2.5.0.80, and there is no change in how it behaves regarding this issue.

                    Comment


                      #11
                      Originally posted by Rupp View Post
                      The HomeSeer log should show the baud rate the device is connecting at. What does it report?
                      Sent from my SCH-I535 using Tapatalk 4 Beta
                      Only direct serial connections shows the baud rate.

                      Z

                      Comment


                        #12
                        OK, I'll try hooking it up to a direct serial connection and see what it says.

                        Meanwhile, if I set the IP2SL to 115200, I get an error in the log that keeps repeating ad infinitum:

                        6/29/2013 10:59:24 AM - Warning - In Z-Wave init(A), no response getting initialization information.
                        6/29/2013 10:59:42 AM - Warning - In Z-Wave init(A), no response getting initialization information.
                        6/29/2013 10:59:42 AM - Warning - Trying to re-connect to Ethernet interface at IP 192.168.1.88...
                        6/29/2013 10:59:42 AM - Z-Wave - Z-Wave Ethernet at IP 192.168.1.88, connected to interface ok.
                        6/29/2013 10:59:42 AM - Z-Wave - Getting node information from controller...
                        6/29/2013 10:59:58 AM - Warning - In Z-Wave init(A), no response getting initialization information.
                        6/29/2013 11:00:16 AM - Warning - In Z-Wave init(A), no response getting initialization information.
                        6/29/2013 11:00:16 AM - Warning - Trying to re-connect to Ethernet interface at IP 192.168.1.88...
                        6/29/2013 11:00:17 AM - Z-Wave - Z-Wave Ethernet at IP 192.168.1.88, connected to interface ok.

                        Comment


                          #13
                          Interesting good news on something I did just now.

                          Yesterday, I received a second z-troller (from the same vendor as the first one, which I received about 3 weeks ago), because I'm planning to build a multi-z-troller system.

                          With the IP2SL set at 115200, I removed the first z-troller and inserted the second z-troller, which I literally just now removed from the box. The second z-troller works at 115200!

                          With the second z-troller, the log says:
                          6/29/2013 11:05:25 AM - Z-Wave - Z-Wave Ethernet at IP 192.168.1.88, connected to interface ok.
                          6/29/2013 11:05:25 AM - Z-Wave - Getting node information from controller...
                          6/29/2013 11:05:25 AM - Z-Wave - Z-Wave Serial API version: 4
                          6/29/2013 11:05:25 AM - Z-Wave - Z-Wave interface node ID: 1, Home ID: 003D2887
                          6/29/2013 11:05:25 AM - Z-Wave - Found 1 Z-Wave nodes in interface node ID 1
                          6/29/2013 11:05:25 AM - Z-Wave - Controller Manufacturer: HomeSeer Tech, ID=0x2, Type=0x1
                          6/29/2013 11:05:25 AM - Z-Wave - Controller firmware version: 1.17
                          6/29/2013 11:05:26 AM - Z-Wave - This Z-Wave PC Controller Library Version is: Z-Wave 3.28 (ZDK Version 5.03)
                          6/29/2013 11:05:26 AM - Z-Wave - This Z-Wave PC Controller is Type: ZW_LIB_INSTALLER

                          Plainly, it is also running firmware version 1.17.

                          I wonder why the second z-troller would work at 115,200 baud, but not the first z-troller?

                          Comment


                            #14
                            Originally posted by NeverDie View Post

                            I wonder why the second z-troller would work at 115,200 baud, but not the first z-troller?
                            Weird.

                            One thing you might try is to reflash the firmware on the one that has slower baud rate. It may reset it to the correct speed.

                            Comment


                              #15
                              Are you using the new cables or the old cables? I would try swapping cables to see if it makes a difference...
                              HS4Pro Running on a Raspberry Pi4
                              72 Z-Wave Nodes, 111 Events, 422 Devices
                              Z-Wave, UPB, WiFi
                              Plugins: EasyTrigger, weatherXML, OMNI, Z-Wave, Tuya, Device History
                              HSTouch Clients: 3 Android, 1 Joggler

                              Comment

                              Working...
                              X