Announcement

Collapse
No announcement yet.

Alternative to the (broken) hs.OpenComPortTerm

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

    Alternative to the (broken) hs.OpenComPortTerm

    I have a couple of old serial devices that have been providing sterling service with HS3 but are no longer functioning as hs.OpenComPortTerm is broken in HS4.

    I'd be really grateful if anyone has a solution they could share.

    PS.... Yes, I've reported it to Homeseer support.

    #2
    Hi Jez,

    Luckily I tested my scripts and found this out before I migrated to HS4. I'm working with HST to hopefully get this fixed soon.

    HSCS-1413

    Comment


      #3
      Jez I'm assuming you are running Windows 10? What kind of COM port hardware do you have? Make/Model?

      Comment


        #4
        Yes, I'm running on Windows 10.
        I've got an old Meteor CID device and a Quasar 3145 with 4 temperature sensors. Both are old but work perfectly with HS3, the Meteor is kind of essential now.

        Comment


          #5
          Originally posted by kenm View Post
          Hi Jez,

          Luckily I tested my scripts and found this out before I migrated to HS4. I'm working with HST to hopefully get this fixed soon.

          HSCS-1413
          Is this the same kenm that’s actively encouraging HS users to migrate to Home Assistant yet you say you are working with HST on this issue. Interesting yet a little confusing at the same time indeed https://community.home-assistant.io/...gee/181820/228

          Comment


            #6
            Originally posted by kenm View Post
            Hi Jez,

            Luckily I tested my scripts and found this out before I migrated to HS4. I'm working with HST to hopefully get this fixed soon.

            HSCS-1413
            Can anybody else see this ticket? I'm told I don't have permission.
            HomeSeer Version: HS3 Pro Edition 3.0.0.548
            Operating System: Microsoft Windows 10 Pro - Work Station

            Enabled Plug-Ins
            3.0.0.6: AK Smart Device 3.0.1.9: AmbientWeather 2.0.63.0: BLBackup 3.0.55.0: BLGData 3.0.38.0: BLLock 2.0.26.0: BLUPS 3.2.0.1: Device History 3.0.0.73: EasyTrigger 3.25.614.1: HSBuddy 3.1.0.22: MeiHarmonyHub 3.1.0.2: SDJ-Health 19.10.7.1: TPLinkSmartHome 3.0.6681.34300: UltraCID3 3.0.6644.26753: UltraLog3 3.0.6554.33094: UltraMon3 3.0.5960.36744: UltraSighthoundVideo3 3.0.7806.23606: UltraWeatherWU3 3.0.2.0: Z-Wave

            Comment


              #7
              Originally posted by concordseer View Post

              Is this the same kenm that’s actively encouraging HS users to migrate to Home Assistant yet you say you are working with HST on this issue. Interesting yet a little confusing at the same time indeed https://community.home-assistant.io/...gee/181820/228
              Yes, same kenm. I don't know that I'd call it actively encouraging. As you can see from my posts, I initially ran away from HS4, and stated that I would be staying with HS3 After a few months of using HA, I moved everything back to HS3 except MQTT, which is how I'm feeding data to HA for a UI. I've also got involved in the pyhs3/homeseer Z-wave custom component with Mark Coombes, so I've been helping out with that as well.

              I agree it's a little confusing but I've been an HS user since 1999 so I feel almost obligated to help debug and fix a problem in HS4 once I find it. The situation I have right now is that I've moved my HS3 instance to a new platform, so I can't run HS3 and HS4 at the same time on that new platform.

              Comment


                #8
                Originally posted by ewkearns View Post

                Can anybody else see this ticket? I'm told I don't have permission.
                Let me check. Maybe I have to make it public or something.

                EDIT: It doesn't look like the new help desk software allows public access. Seems like a recipe for a bunch of duplicate tickets

                Comment


                  #9
                  Hi Jez ,

                  The Serial profile of the Big5 Plugin appears to be broken as well in HS4 so I'll add that info to my ticket. The only option I can think of at this point would be to use some kind of external serial program that could write data to a text file and then have a script read the data from the text file.

                  Ken

                  Comment


                    #10
                    mcsMQTT supports serial port devices.

                    Comment


                      #11
                      Originally posted by Michael McSharry View Post
                      mcsMQTT supports serial port devices.
                      Excellent. Can I presume it's all working with HS4? If so I'll install it and see how I get on.

                      Comment


                        #12
                        Other option is Node Red now has native support in HS4. Node Red also has serial com port modules available.

                        I am using this to read entered PIN numbers from a serially connected pinpad and store the pin as a device value in HS.

                        Comment


                          #13
                          Excellent. Can I presume it's all working with HS4? If so I'll install it and see how I get on.
                          Yes it is working with HS4. It is described in Section 12.4 of the mcsMQTT manual

                          Comment


                            #14
                            Originally posted by Fellhahn View Post
                            Other option is Node Red now has native support in HS4. Node Red also has serial com port modules available.

                            I am using this to read entered PIN numbers from a serially connected pinpad and store the pin as a device value in HS.
                            Yes Node Red will certainly negate the requirement for 3rd party solutions. I’d much prefer this route as it gives HS users more autonomy when it using different types of hardware/protocols.

                            Comment


                              #15
                              Pardon me if this is a dumb question, but does Node Red code run on the same system as HS4 or a different system? The reason I ask is because I have an 8-port USB-to-Serial adapter that needs to stay connected to my HS4 system. A program outside of HS4 also uses that serial adapter. If the same system, does it or can it start and stop along with HS4 or is it independent?

                              Thanks,
                              Ken

                              Comment

                              Working...
                              X