Page 4 of 22 FirstFirst 12345678914 ... LastLast
Results 31 to 40 of 216

Thread: xAP Flash nee Joggler beta 5

  1. #31
    Automated Home Sr Member BodgeIT's Avatar
    Join Date
    Jul 2010
    Posts
    57

    Default The missing link

    now <xAP><on> and <xAP><off>
    Updated my config and now this works OK.

    I'll update the doc and send it to you.

    ** EDIT **
    Checking the documentation, there seems to be a discrepency in relation to the <xAP><schema>generic</schema></xAP> entry and the documentation.
    In one doc it's as above, in the main doc, it's detailed as:
    <generic>

    <Class>The class within the header to recognise (class=)

    <body>[INDENT]The body/block/section name within the message

    <parameter>The parameter name within the body

    <type>The type of parameter eg text, numeric or state - (not yet implemented, all treated as text)

    <context>If an additional parameter within the block further defines the 'context' of this parmeter.
    e.g. within the X10 schema device=A6 (not yet implemented)

    </generic>

    Can I just check which version is correct?
    Last edited by Kevin; 23rd September 2010 at 04:59 PM.

  2. #32
    Moderator Kevin's Avatar
    Join Date
    Jan 2004
    Location
    West Yorkshire
    Posts
    554

    Default

    Good spot - the old <xapon> and <xapoff> tags are still in the getting started doc , and the beta 5 doc doesn't document this change - and should have. I've added the new <xAP><on> and <xAP><off> tags to the tag spreadsheet too.

    I'll also post another (my) example xapconfig.xml file shortly.

    Re creating a generic schema - to do this you need to set the schema to generic <schema>generic</schema> and also include a <generic>...</generic> tag section

    <xAP>
    <schema>generic</schema>
    <generic>
    <Class>...</Class>
    <body>...</body>
    <parameter>...</parameter>
    <context>...</context>
    <type>...</type>
    </generic>
    </xAP>

    the <Class> tagname has to have a capital C - sorry can't be helped... also <context> and <type> are not yet implemented. When implemented context likely needs an additional tag to be added as we need to pick up both an additional xAP parameter name and its value.



    K
    Last edited by Kevin; 23rd September 2010 at 12:16 PM.

  3. #33
    Automated Home Sr Member kev_t's Avatar
    Join Date
    Jun 2004
    Location
    Lincolnshire
    Posts
    58

    Default generic messages

    I hae been looking at the parsing of the generic messages to but have not had any success

    This is the message from the weather station, and I want to extract tempc

    xap-header
    {
    v=12
    Hop=1
    UID=FF400200
    Class=Weather.Report
    Source=windy.weather.1
    }
    Weather.Report
    {
    tempf=68.9
    utc=12:06:08
    tempc=20.5
    icon=Sunny
    date=20100923
    windm= 4
    windk= 8
    airpressure=1001.5
    winddirc=W
    humidity=74
    rain=0.0
    extratemp1=-100.0
    extratemp2=-100.0
    extratemp3=-100.0
    extrahum1=-100
    extrahum2=-100
    extrahum3=-100
    }

    And this is the xAP section from the button

    <xAP>
    <uid>FF400200</uid>
    <source>windy.weather.1</source>
    <schema>generic</schema>
    <generic>
    <Class>Weather.Report</Class>
    <body>Weather.Report</body>
    <parameter>tempc</parameter>
    </generic>
    </xAP>

    Just double checked and Iserver has created a filter for windy.weather.1

    Any suggestions?

    KevinT
    Last edited by kev_t; 23rd September 2010 at 01:58 PM.

  4. #34
    Moderator Kevin's Avatar
    Join Date
    Jan 2004
    Location
    West Yorkshire
    Posts
    554

    Default

    I looked at that Weather.Display message and he has OD OA characters at the end of every line...(at least that's what a cut and paste from the post shows) is that the current version of Weather Display ? - if so it is still not to spec.
    If the hex view within xFX Viewer shows otherwise could you post it.

    xAP Flash would not match the values as it looks for

    tagvalue0A and he is sending tagvalue0D0A

    You may be able to kludge this by including that 0D at the end of the value between the tags - might have to use CDATA.
    K

  5. #35
    Automated Home Sr Member BodgeIT's Avatar
    Join Date
    Jul 2010
    Posts
    57

    Default Sorry to keep laying it on

    I've moved on to setting up an OSD from a xAP message generated by my HAH.
    Following the instructions in the beta5 guide, I have created this entry for my page:
    <page NAME="OSD">
    <visible>false</visible>
    <opacity>0.1</opacity>
    <group>Center</group>
    <textbox NAME="OSD">
    <gridX>1</gridX>
    <gridY>1</gridY>
    <width>120</width>
    <height>80</height>
    <fontsize>24</fontsize>
    <visible>true</visible>
    <text></text>
    <xAP>
    <schema>xAPBSC</schema>
    <uid>FF00D800</uid>
    <source>dbzoo.livebox.Plugboard</source>
    <Class>xAPBSC.cmd</Class>
    <parametertype>text</parametertype>
    <parameter>text</parameter>
    <parametername>text</parametername>
    </xAP>
    <mode>text</mode>
    </textbox>
    </page>

    As you can see I'm still a little unsure of which "parameter*" entry will get me my info(as I haven't yet seen any), so I'm headging my bets.
    I have this situated this as the very last page in my config.
    Essentially what happens is the xAPFlash tries to start but never actually finishes loading. No xAP entry appears in XFX for the ahscs5.

    Have I missed something?

  6. #36
    Automated Home Sr Member kev_t's Avatar
    Join Date
    Jun 2004
    Location
    Lincolnshire
    Posts
    58

    Default generic messages

    I updated weather display after the last problem when you highlighted this

    There are no OD's in the message, so the version I have is to spec on this point at least

    78 61 70 2d 68 65 61 64 65 72 0a 7b 0a 76 3d 31 xap-header { v=1
    32 0a 48 6f 70 3d 31 0a 55 49 44 3d 46 46 34 30 2 Hop=1 UID=FF40
    30 32 30 30 0a 43 6c 61 73 73 3d 57 65 61 74 68 0200 Class=Weath
    65 72 2e 52 65 70 6f 72 74 0a 53 6f 75 72 63 65 er.Report Source
    3d 77 69 6e 64 79 2e 77 65 61 74 68 65 72 2e 31 =windy.weather.1
    0a 7d 0a 57 65 61 74 68 65 72 2e 52 65 70 6f 72 } Weather.Repor
    74 0a 7b 0a 74 65 6d 70 66 3d 36 38 2e 39 0a 75 t { tempf=68.9 u
    74 63 3d 31 32 3a 30 36 3a 30 38 0a 74 65 6d 70 tc=12:06:08 temp
    63 3d 32 30 2e 35 0a 69 63 6f 6e 3d 53 75 6e 6e c=20.5 icon=Sunn
    79 0a 64 61 74 65 3d 32 30 31 30 30 39 32 33 0a y date=20100923
    77 69 6e 64 6d 3d 20 34 0a 77 69 6e 64 6b 3d 20 windm= 4 windk=
    38 0a 61 69 72 70 72 65 73 73 75 72 65 3d 31 30 8 airpressure=10
    30 31 2e 35 0a 77 69 6e 64 64 69 72 63 3d 57 0a 01.5 winddirc=W
    68 75 6d 69 64 69 74 79 3d 37 34 0a 72 61 69 6e humidity=74 rain
    3d 30 2e 30 0a 65 78 74 72 61 74 65 6d 70 31 3d =0.0 extratemp1=
    2d 31 30 30 2e 30 0a 65 78 74 72 61 74 65 6d 70 -100.0 extratemp
    32 3d 2d 31 30 30 2e 30 0a 65 78 74 72 61 74 65 2=-100.0 extrate
    6d 70 33 3d 2d 31 30 30 2e 30 0a 65 78 74 72 61 mp3=-100.0 extra
    68 75 6d 31 3d 2d 31 30 30 0a 65 78 74 72 61 68 hum1=-100 extrah
    75 6d 32 3d 2d 31 30 30 0a 65 78 74 72 61 68 75 um2=-100 extrahu
    6d 33 3d 2d 31 30 30 0a 7d 0a 0a 0a m3=-100 }


    KevinT

  7. #37
    Moderator Kevin's Avatar
    Join Date
    Jan 2004
    Location
    West Yorkshire
    Posts
    554

    Default

    Quote Originally Posted by BodgeIT View Post
    I've moved on to setting up an OSD from a xAP message generated by my HAH.
    Ahah - moving fast eh.. The OSD is an area that i know is going to need some tweaking but that's what the beta testing is for...
    As you can see I'm still a little unsure of which "parameter*" entry will get me my info(as I haven't yet seen any), so I'm headging my bets.
    The parameter tags you're referring to are for use within generic schema <schema>generic</schema> only and then should be within a <generic> section . They would be named <Class> <parameter>and <type> and you would need a <body> tag too. You are however using schema<xAPBSC> so they are not used here.

    The spreadsheet is really your bible here as it is I believe correct and clearly shows the valid tag names and the levels at which they may be used. <on> and <off> are missing from the <xAP> section
    - only valid within a <button> section.

    The OSD was really intended for use with the xAP-OSD and message.display schema although there is no reason I guess why it shouldn't be available to other schema. I'll need to look at the code to see quite how that might be handled currently though , especially with BSC.
    Essentially what happens is the xAPFlash tries to start but never actually finishes loading.
    I have some code to protect against <pages> that contain no <button> elements but it looks like it's not catching this case. FTTB just add an invisible <button> element to the page and xAP Flash will load your XML. BTW you are using an <opacity> tag which is not supported and it should be <alpha>01.</alpha> (which is pretty transparent).

    I've got various fixes , and a feature change that I hope you'll like... just not sure when I'll post an update based on the subsequent questions. The OSD (for all schema) is not one I'll look to address in the next release as I'd rather spend a bit more time considering the permutations but I would like to get KT's weather.display issue investigated.

    K
    Last edited by Kevin; 23rd September 2010 at 04:14 PM.

  8. #38
    Automated Home Sr Member BodgeIT's Avatar
    Join Date
    Jul 2010
    Posts
    57

    Default

    Thanks Kevin, I've rem'd it out for now.
    Can we get a wiki up? This might help with disseminating new info.

    I'll get on to Brett and beg him to put OSD schema into his new xAP library that he's writing for the HAH.

  9. #39
    Moderator Kevin's Avatar
    Join Date
    Jan 2004
    Location
    West Yorkshire
    Posts
    554

    Default

    I'm not sure OSD sits conveniently within HAH, maybe if there were alarm thresholds or something. Maybe you could use the scripting to create a xAP OSD message from one of the existing endpoint changes ? I can see that incoming SMS might warrant OSD though.

    Alternatively some other xAP controller could listen to the HAH messages and send OSD messages as needed ?

    I will get around to looking at how BSC might trigger an OSD but I dont expect it will be a much wanted feature and it would have to only be on events and not infos. The OSD schema have additional fields like target, duration and priority to better support which devices display messages and for how long and which take precedence etc..

    K

  10. #40
    Moderator Kevin's Avatar
    Join Date
    Jan 2004
    Location
    West Yorkshire
    Posts
    554

    Default beta version 5c

    beta version 5c of the SWF is posted...

    Fixes:

    textbox elements now register source filters with iServer at startup.

    display of recovered generic schema parameter within 'text' mode buttons or textbox elements.

    New Feature:

    xAP message macros.

    You can now include any number of xAP messages each separately contained within an <on> or <off> tag inside a <button><xAP> element. They will be sent whenever the button is pressed on or off and in the order they are entered in the XML. There is no pacing of these so they will all get sent really fast, if you include a lot of messages double check your targets cope.
    This is useful to create a series of xAP commands for example to set scenes or turn things off at night. Using wildcards where possible is advantageous.

    ... when and if you were able to change button states via xAP you'd be able to trigger macros via a xAP command too

    K
    Last edited by Kevin; 23rd September 2010 at 05:34 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •