Announcement

Collapse
No announcement yet.

DayDate0 now has Date AND Time

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

  • CFGuy
    replied
    On the Device Management page there is a column labeled Address. (Unless you have it turned off in HS settings.) You can also view by clicking the device name like you were going to edit the device. Go to the advanced tab and the second line is Technology Address.

    Endgame was well worth seeing. I went last Friday evening with a group of 7.

    Leave a comment:


  • BigBadBuzz
    replied
    Jeff:

    I was not familiar with the Device Tech Address - are those relatively new? It would make the code more legible than just using a device RefID.

    I would love to update all my HSTouch screens tonight, but I'm off to see "Avengers: Endgame"...

    BBB

    Leave a comment:


  • CFGuy
    replied
    Originally posted by BigBadBuzz View Post
    Jeff:

    Thanks! It was the script form that I needed! I started reading about VSPairs in the HS3Help file and my eyes started rolling back in my head...

    Paul
    It takes a while and quite a bit of just playing with code to get that lightbulb moment dealing with the status graphic pairs in scripting.

    Leave a comment:


  • CFGuy
    replied
    Or if you prefer using the non changing Device Tech Address.

    hs.DeviceVSP_GetStatus(hs.GetDeviceRef("Location 1 HST Name 0"), hs.DeviceValue(hs.GetDeviceRef("Location 1 HST Name 0")), ePairStatusControl.Status)

    Just replace 0 with the number for the day you want to display.

    Leave a comment:


  • BigBadBuzz
    replied
    Jeff:

    Thanks! It was the script form that I needed! I started reading about VSPairs in the HS3Help file and my eyes started rolling back in my head...

    Paul

    Leave a comment:


  • CFGuy
    replied
    Use Status Text.
    and if you want to use it in a script.
    hs.DeviceVSP_GetStatus(RefID, hs.DeviceValue(RefID), ePairStatusControl.Status)



    Click image for larger version

Name:	Capture.PNG
Views:	215
Size:	12.5 KB
ID:	1302852

    Leave a comment:


  • BigBadBuzz
    replied

    To try to be more succinct,
    Code:
    [$SCRIPT=&hs.DeviceString(xxx)]
    No longer works, nor does &hs.DeviceValue(xxx)

    Leave a comment:


  • BigBadBuzz
    replied
    Jeff with the way you are doing the day names now (looks like a full week's worth, value is chosen based on numeric value), how do I use that in HSTouch?

    Puzzled

    Leave a comment:


  • CFGuy
    replied
    No problem. I would still recommend that you take a look at the Locations tab and view the date formats in the dropdown. There are 3 new ones. I've been using the 3/26/19 format.

    Leave a comment:


  • BigBadBuzz
    replied
    Jeff:

    Okay, chalk this up to "ye of little patience" -- I had just created the Day 2-7 Date devices, but it appears they hadn't hit the forecast update cycle - when I came back to my system, they now all are of the same format. Sorry about that, chief...

    Regards,
    Paul

    Leave a comment:


  • CFGuy
    replied
    Try this. Go to the Locations tab in wxml. Near the top is Date Format for this location. Click on the dropdown and select a format. The next time that the forecast runs check to see if the date matches the selected format.

    Leave a comment:


  • BigBadBuzz
    replied
    Hmm -

    Seems to be inconsistency in Day Dates 0-1 and Day Dates 2-7; maybe I'm missing something?

    Click image for larger version

Name:	Inconsistent_Day_Dates.JPG
Views:	245
Size:	63.9 KB
ID:	1295267

    Leave a comment:


  • BigBadBuzz
    replied
    Jeff and sparkman:

    Will do - thanks.

    BBB

    Leave a comment:


  • CFGuy
    replied
    Definately, move to using the device string. I have been moving away from ini files as there have been many times that they have gotten corrupted and I have had to pull out my backups. weatherXML used to have 6 ini files but I am down to 3 now. When I rewrite the alerts section that will get rid of one more ini file.

    Leave a comment:


  • sparkman
    replied
    Should just be able to do this:

    Code:
    [$SCRIPT=&hs.DeviceString(5678)]
    Change 5678 to the reference ID of the DayDate0 device.

    Leave a comment:

Working...
X