Announcement

Collapse
No announcement yet.

Support for HSM100 Planned ?

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

    Support for HSM100 Planned ?

    Now that I have both HSM100 working (one inside and one outside) at my second home it would be nice to plot and graph the data. Day high and lows time stamped by date .... etc.

    #2
    If the sensor interface places the data in individual virtual devices then you can chart them with mcsTemperature. I do not run zwave here so I am not familiar with how HST presents the data from the multi-sensor.

    Comment


      #3
      I've got a couple of them. I just added one to mcsTemperature. The device value appears to be multiplied by 10. So right now it shows as 805 degrees rather than 80.5. What I am going to do is create a virtual device and an event to set that virtual device to the HSM temp value divided by 10 triggered by value change on the HSM temp device, and use the virtual device with mcsTemperature.

      Bill

      Comment


        #4
        I just got one of these things too. It seems to be working so I was going to do the same thing.

        But is there an easier way? I feel like I am missing something.

        Comment


          #5
          What does HST put into the DeviceString for the HSM100 as its display value? My recollection is that mcsTemperature will use the DeviceString it finds a number in there otherwise it will go to the DeviceValue. I believe that when mcsTemperature does the hardware interface such as with 1-wire then it will also scale the sensor value to deal with the lack of a decimal in the DeviceValue. It also places a displayable reading in the DeviceString.

          Comment


            #6
            The device string looks like this..

            75.8 Degrees F

            or
            HTML Code:
            <img align="absmiddle" src="/images/HomeSeer/Thermometer.gif">
            ;75.8 Degrees F
            James

            Running HS 3 on Win10 .

            Comment


              #7
              It looks to me that if you have mcsTemperature setup to display only Temperature icons (checkbox setting) then it will get the data from the DeviceValue. If you have it setup to include both icon and text, such as the HSM100 is formatted, then it will fetch the number from the DeviceString. There exists no logic in mcsTemperature to have one souce show only icons and another source to show both icons and value. It supports either, but not a mix and match assortment.

              Comment

              Working...
              X