Announcement

Collapse
No announcement yet.

HS3 Build 3.0.0.128 Beta with JSON

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

    #91
    I do agree, I think provided users have the ability to turn on and off the various features so as to control resources it does make sense to expand connectivity. Reality is that the world is becoming more and more connected and if various controller apps (e.g. Demopad or other touchscreen devices) can interface with HS3 then that is great news.

    The concern is that resources don't get diverted away from adding so many new features from the core bugfixes, but if it exists in the core already, then it is not reinventing the wheel .
    HS3 PRO, Win10, WeatherXML, HSTouch, Pushover, UltraGCIR, Heaps of Jon00 Plugins, Just sold and about to move so very slim system.

    Facebook | Twitter | Flickr | Google+ | Website | YouTube

    Comment


      #92
      We are adding the TCP connection to HS3, it will be enabled/disable in setup. This will enable you to use a third party app to connect directly to HS using a TCP connection, and then issue the simple text commands as well as get notified of device changes. It will be in build 3.0.0.149 which I will be posting shortly.

      Originally posted by travisdh View Post
      I do agree, I think provided users have the ability to turn on and off the various features so as to control resources it does make sense to expand connectivity. Reality is that the world is becoming more and more connected and if various controller apps (e.g. Demopad or other touchscreen devices) can interface with HS3 then that is great news.

      The concern is that resources don't get diverted away from adding so many new features from the core bugfixes, but if it exists in the core already, then it is not reinventing the wheel .
      💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

      Comment


        #93
        Originally posted by rjh View Post
        We are adding the TCP connection to HS3, it will be enabled/disable in setup. This will enable you to use a third party app to connect directly to HS using a TCP connection, and then issue the simple text commands as well as get notified of device changes. It will be in build 3.0.0.149 which I will be posting shortly.
        That sounds great! I hope it will include some form of authentication as well?
        Nicolai L

        Comment


          #94
          Very good news. Thanks for that!


          Sent from my iPad using Tapatalk

          Comment


            #95
            Dream come true, great !! Thanks

            Comment


              #96
              Originally posted by rjh View Post
              We are adding the TCP connection to HS3, it will be enabled/disable in setup. This will enable you to use a third party app to connect directly to HS using a TCP connection, and then issue the simple text commands as well as get notified of device changes. It will be in build 3.0.0.149 which I will be posting shortly.
              Is this similar to how HSTouch (and I assume myHomeSeer) is communicating with the server?

              Comment


                #97
                Originally posted by ihomeautomate View Post
                Is this similar to how HSTouch (and I assume myHomeSeer) is communicating with the server?
                I believe you can get most of the information here http://homeseer.com/support/homeseer...nk/default.htm where the protocol is explained and port numbers specified for both control interfaces (ASCII, JSON).

                Comment


                  #98
                  Originally posted by rjh View Post
                  We are adding the TCP connection to HS3, it will be enabled/disable in setup. This will enable you to use a third party app to connect directly to HS using a TCP connection, and then issue the simple text commands as well as get notified of device changes. It will be in build 3.0.0.149 which I will be posting shortly.
                  That's really good news! Gotta love marketing

                  Verstuurd vanaf mijn Nexus 5 met Tapatalk

                  Comment


                    #99
                    Originally posted by rjh View Post
                    We are adding the TCP connection to HS3, it will be enabled/disable in setup. This will enable you to use a third party app to connect directly to HS using a TCP connection, and then issue the simple text commands as well as get notified of device changes. It will be in build 3.0.0.149 which I will be posting shortly.
                    This is GREAT !

                    Comment


                      Originally posted by rjh View Post
                      We are adding the TCP connection to HS3, it will be enabled/disable in setup. This will enable you to use a third party app to connect directly to HS using a TCP connection, and then issue the simple text commands as well as get notified of device changes. It will be in build 3.0.0.149 which I will be posting shortly.
                      and this other post [ http://http://board.homeseer.com/sho...0&postcount=67 ]

                      Originally posted by rjh View Post
                      I need to take a look at this. The problem is that the status in HS is updated after the action takes place. So the plugin that controls the hardware is responsible for updating HS. What I need to do is wait for this response to happen before the call returns.
                      Rich,

                      In reference to the upcoming TCP connection feature (A2Z-Link), I have a few questions. These have to do with what packets to expect. In the following points, I distinguish between 'replies' as we know them when using JSON commands, and 'status updates' as unsollicited messages sent out by HS on port 11000.

                      1- I will be able to send JSON commands through the defined Web server port (default 80) and port 11000, correct?

                      2- Currently, if an external app sends a control command for a device using JSON through port 80, HS would reply with the previous status of the device on port 80. So with A2Z-Link and sending either ASCII or JSON control commands to port 11000, I imagine we would see the same behavior, that is, seeing a reply with the previous status on port 11000, correct?

                      3- If I send a JSON control command through port 80, will the status reply come back only on the same port (80, not on port 11000) ?

                      Here's my assumption:

                      1- Control commands sent to HS will trigger replies on the same port with the previous status of the device

                      2- At the same time or soon after HS will send out unsollicitated status updates (the revised status) on port 11000?

                      If my assumption is correct, then the issue raised in a another post in this thread regarding "the status replied being the one prior to the plugin(s) updating" would not be problematic. I would listen and parse on port 11000 for the 'true' current status of a device. I would send JSON control commands on port 80 and not listen for replies about status on that port.

                      P.S. Any ETA for the version of HS opening up port 11000 ?

                      Comment


                        Originally posted by claude View Post
                        and this other post [ http://http://board.homeseer.com/sho...0&postcount=67 ]



                        Rich,

                        In reference to the upcoming TCP connection feature (A2Z-Link), I have a few questions. These have to do with what packets to expect. In the following points, I distinguish between 'replies' as we know them when using JSON commands, and 'status updates' as unsollicited messages sent out by HS on port 11000.

                        1- I will be able to send JSON commands through the defined Web server port (default 80) and port 11000, correct?

                        2- Currently, if an external app sends a control command for a device using JSON through port 80, HS would reply with the previous status of the device on port 80. So with A2Z-Link and sending either ASCII or JSON control commands to port 11000, I imagine we would see the same behavior, that is, seeing a reply with the previous status on port 11000, correct?

                        3- If I send a JSON control command through port 80, will the status reply come back only on the same port (80, not on port 11000) ?

                        Here's my assumption:

                        1- Control commands sent to HS will trigger replies on the same port with the previous status of the device

                        2- At the same time or soon after HS will send out unsollicitated status updates (the revised status) on port 11000?

                        If my assumption is correct, then the issue raised in a another post in this thread regarding "the status replied being the one prior to the plugin(s) updating" would not be problematic. I would listen and parse on port 11000 for the 'true' current status of a device. I would send JSON control commands on port 80 and not listen for replies about status on that port.

                        P.S. Any ETA for the version of HS opening up port 11000 ?
                        Rich,

                        I know we're getting close to Christmas, but any chance of getting a reply on this, especially on the ETA ?

                        Comment


                          Bump... Any ETA on activating the A2Z-Link code in HS3 for access from port 11000 ?

                          Comment


                            When using https, the user and password info can be specified in the URL. However, when using http, HomeSeer does not use the user and password specified in the URL (HomeSeer returns HTTP Status 401, meaning invalid login). Granted, http isn't as secure as https, but I have a need to use http. I have a number of Pronto remotes that I program using JavaScript. Unfortunately, the Pronto remotes don't support https. They only support http. I only use my Pronto remotes at home, so specifying user and password info via http is minimal risk. Also, my router does NOT port forward the http port.

                            Question: Is there any way HS3 can support having user and password in the URL for http?

                            I tested that if I go into HomeSeer->Setup->Network, I can check the option that allows access to HomeSeer without having to login, if the connection is coming from the local network. If I check this, then http JSON requests work fine without specifying the user and password info. However, this feels quite a bit less secure than specifying user and password in an http URL. Thus, any way to allow specifying user and password info in http URL?

                            Thanks

                            Comment


                              Unless I am missing something (very possible), there is no way to set the device value to an arbitrary value (not just 0 or one for control) or device string via the JSON interface. Is this correct?

                              I would like to have a few HS3 devices that that I populate the values (and strings) from an external application.

                              Is this possible? If not, can this be added to the wish list?

                              Thanks

                              Comment


                                Originally posted by gerlin View Post
                                Unless I am missing something (very possible), there is no way to set the device value to an arbitrary value (not just 0 or one for control) or device string via the JSON interface. Is this correct?

                                I would like to have a few HS3 devices that that I populate the values (and strings) from an external application.

                                Is this possible? If not, can this be added to the wish list?

                                Thanks
                                This isn't a limitation of the JSON API. It's a limitation of HS. Try creating a virtual device and setting controls values to anything other than numeric. It won't let you.

                                Comment

                                Working...
                                X