Announcement

Collapse
No announcement yet.

Davis Airlink local API

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

    #16
    Originally posted by avpman View Post
    thanks, that worked. Is there a way to eliminate the prefix "Pressure:" to be consistent with all the other devices? For example, Temperature, humidity, etc are not prefixed by their purpose. I'm using this on a HSTouch screen and the prefixing is taking up too much space.
    That's not simple, the HS device is "Description" and I use it for all 40 providers. Normally the provider has some kind of weather description, then I append the pressure trend if available.

    Actually, I may check if the description is empty. But for other users it may be confusing it there's just a word i.e. "Stable".

    Better option would be to add a separate HS device for pressure trend...

    Comment


      #17
      Is that something you would do? Or can I create a virtual, and somehow link it? BTW - really enjoying putting together weather screens with the data from your plugin.

      Originally posted by alexbk66 View Post

      Better option would be to add a separate HS device for pressure trend...

      Comment


        #18
        Not sure what is best, need to think. What's your opinion?

        Comment


          #19
          Originally posted by alexbk66 View Post
          Not sure what is best, need to think. What's your opinion?
          Any way that I can get the prefix stripped is fine with me. Perhaps add a checkbox to the device "Remove prefix?" defaulted to No so that other users with different providers won't be affected. But they could use it too.

          Comment


            #20
            Originally posted by avpman View Post

            Any way that I can get the prefix stripped is fine with me. Perhaps add a checkbox to the device "Remove prefix?" defaulted to No so that other users with different providers won't be affected. But they could use it too.
            Ver 4.0.4.49 - Added "Pressure Trend" device

            Click image for larger version  Name:	2022-12-29.png Views:	0 Size:	14.6 KB ID:	1583514

            [EDIT]

            For trigger you should use the device value (state), not the string.

            Comment


              #21
              Originally posted by alexbk66 View Post

              Ver 4.0.4.49 - Added "Pressure Trend" device

              Click image for larger version Name:	2022-12-29.png Views:	0 Size:	14.6 KB ID:	1583514

              [EDIT]

              For trigger you should use the device value (state), not the string.
              Thanks!

              Comment


                #22
                Originally posted by alexbk66 View Post

                Ver 4.0.4.49 - Added "Pressure Trend" device

                Click image for larger version Name:	2022-12-29.png Views:	0 Size:	14.6 KB ID:	1583514

                [EDIT]

                For trigger you should use the device value (state), not the string.
                Looks good! Small typo, Pressure VAL:8 "Rasing" should be "Rising"

                Comment


                  #23
                  Originally posted by avpman View Post

                  Looks good! Small typo, Pressure VAL:8 "Rasing" should be "Rising"
                  Thank you, it was actually "Raising"

                  [EDIT]

                  I'll fix in the next release, but in the mean time you can fix the typo in the device Status/Graphics page yourself.

                  Comment


                    #24
                    Originally posted by alexbk66 View Post

                    Thank you, it was actually "Raising"

                    [EDIT]

                    I'll fix in the next release, but in the mean time you can fix the typo in the device Status/Graphics page yourself.
                    Already did . Thanks!

                    Comment

                    Working...
                    X