The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: Re: HouseBot Plug-in



------=_NextPart_000_0154_01CA3DCA.C011A370
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

Thanks for the screenshots - it's the only really clear way of
communicating
a HouseBot setup. One of it's few -ve points.



One thing I can't see in the shots though is the detailed settings for the
'xAP Message Target'. And it occurs to me that the behaviour you depict is
exactly what would happen if the checkbox 'Allow Same Value Settings' for
this property was unchecked. Can you check the setting of that please.



From: xap_automation@xxxxxxx [mailto:xap_automation@xxxxxxx]
On Behalf Of zagknut
Sent: 24 September 2009 20:00
To: xap_automation@xxxxxxx
Subject: [xap_automation] Re: HouseBot Plug-in





I have attached a screenshot of the device for the first task in my last
e-mail.

Device
<http://groups.yahoo.com/group/xap_automation/photos/album/940785096/pic/825
06861/view?picmode=large&mode=tn&order=ordinal&start=1&dir=asc>
 screen shot


Regards, Brad


--- In xap_automation@xxxxxxx, "Edward Pearson"
<edward.mailgroup@...> wrote:
>
> writing a value, even if it's the same as the existing value, from a
task
> action into the target property of the sender device is the right way
to
> trigger the message send.
>
>
>
> So you should have
>
> 1) a HB button that calls a task,
>
> 2) the task makes changes to a sender device, the last one being the
> target property
>
> 3) the sender device transmits the xAP message to SqueezeCenter
>
>
>
> Not sure I follow your description below. A screen shot of the task
might
> help.
>
>
>
> From: xap_automation@xxxxxxx
[mailto:xap_automation@xxxxxxx]
> On Behalf Of zagknut
> Sent: 23 September 2009 23:02
> To: xap_automation@xxxxxxx
> Subject: [xap_automation] HouseBot Plug-in
>
>
>
>
>
> So, I made it past the hurdle of communicating with the Squeezeboxes,
now
I
> am stumped on the HouseBot Plug-in. Let me know if there is a better
forum
> for these questions.
>
> I have created a Sender device in HouseBot that will send the button
> commands to the correct squeezebox when I click on the "Click to
test and
> send message". So, I try to create a "macro" using
Tasks, but no luck;
> nothing is sent. In the help section of HouseBot on xAP Sender Devices
it
> says "Writing a value to the xAP Message Target property triggers
the xAP
> message", so I use "add Action" item and chage my
button name (favorites,
> play, etc) and then the name of the target. Unfortunately, the target
name
> is not changed between the "marco" calls and the command is
not sent. So,
I
> try changing the target field to "-", which creates an error
message in
xFx
> Viewer, but no problem. This works. Great I think, until I realize
BOTH
> Squeezeboxes are changing! I have the same problem with all commands,
other
> than power and level. Any guidance on where I'm going astray would be
MOST
> appreciated. Again, I am looking to simulate button pushes on the
unit,
such
> as next track, pause, play, and a macro (favorites, down, play).
>
> Thanks in advance for any help you may be able to offer.
> Brad
>




------=_NextPart_000_0154_01CA3DCA.C011A370
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7bit





<head>

<style type="text/css">
<!--

/* start of attachment style */
.ygrp-photo-title{
clear: both;
font-size: smaller;
height: 15px;
overflow: hidden;
text-align: center;
width: 75px;
}
div.ygrp-photo{
background-position: center;
background-repeat: no-repeat;
background-color: white;
border: 1px solid black;
height: 62px;
width: 62px;
}

div.photo-title
a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;
}

div.attach-table div.attach-row {
clear: both;
}

div.attach-table div.attach-row div {
float: left;
/* margin: 2px;*/
}

p {
clear: both;
padding: 15px 0 3px 0;
overflow: hidden;
}

div.ygrp-file {
width: 30px;
valign: middle;
}
div.attach-table div.attach-row div div a {
text-decoration: none;
}

div.attach-table div.attach-row div div span {
font-weight: normal;
}

div.ygrp-file-title {
font-weight: bold;
}
/* end of attachment style */
-->
</style>
</head>
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns:x="urn:schemas-microsoft-com:office:excel"
xmlns:p="urn:schemas-microsoft-com:office:powerpoint"
xmlns:a="urn:schemas-microsoft-com:office:access"
xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"
xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882"
xmlns:rs="urn:schemas-microsoft-com:rowset"
xmlns:z="#RowsetSchema"
xmlns:b="urn:schemas-microsoft-com:office:publisher"
xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet"
xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet"
xmlns:odc="urn:schemas-microsoft-com:office:odc"
xmlns:oa="urn:schemas-microsoft-com:office:activation"
xmlns:html="http://www.w3.org/TR/REC-html40";
xmlns:q="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:rtc="http://microsoft.com/officenet/conferencing";
xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/";
xmlns:mt="http://schemas.m
icrosoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml";
xmlns:ppda="http://www.passport.com/NameSpace.xsd";
xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/";
xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/";
xmlns:ds="http://www.w3.org/2000/09/xmldsig#";
xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp";
xmlns:udc="htt
p://schemas.microsoft.com/data/udc"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/";
xmlns:ec="http://www.w3.org/2001/04/xmlenc#";
xmlns:sp="http://schemas.microsoft.com/sharepoint/";
xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:udcs="http://schemas.microsoft.com/data/u
dc/soap"; xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile";
xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart";
xmlns:wf="http://schemas.microsoft.com/sharepoin
t/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup";
xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig";
xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature";
xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006";
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml";
xmlns:mrels="http://schemas.openxmlformats.org/package/2006/re
lationships"; xmlns:spwp="http://microsoft.com/sharepoint/webpartpages";
xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types";
xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages";
xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/";
xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService";
xmlns:Z="urn:schemas-microsoft-com:"
xmlns:st="&#1;" xmlns="http://www.w3.org/TR/REC-html40";>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;
charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered
medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
code
{mso-style-priority:99;
font-family:"Courier New";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.left
{mso-style-name:left;}
span.bld
{mso-style-name:bld;}
p.ad, li.ad, div.ad
{mso-style-name:ad;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad1, li.ad1, div.ad1
{mso-style-name:ad1;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad2, li.ad2, div.ad2
{mso-style-name:ad2;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad3, li.ad3, div.ad3
{mso-style-name:ad3;
mso-margin-top-alt:auto;
margin-right:0cm;
margin-bottom:7.5pt;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.replbq, li.replbq, div.replbq
{mso-style-name:replbq;
margin:3.0pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.yshortcuts
{mso-style-name:yshortcuts;}
p.ad4, li.ad4, div.ad4
{mso-style-name:ad4;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad5, li.ad5, div.ad5
{mso-style-name:ad5;
mso-margin-top-alt:auto;
margin-right:0cm;
margin-bottom:7.5pt;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad6, li.ad6, div.ad6
{mso-style-name:ad6;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.yshortcuts1
{mso-style-name:yshortcuts1;
font-family:"Verdana","sans-serif";
font-weight:bold;}
span.yshortcuts2
{mso-style-name:yshortcuts2;
font-family:"Verdana","sans-serif";
font-weight:normal;}
span.EmailStyle35
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:661198139;
mso-list-template-ids:2105460030;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=white lang=EN-GB link=blue vlink=purple>


<!-- **begin egp html banner** -->

<br><br>

<!-- **end egp html banner** -->




<div class=Section1>

<p class=MsoNormal><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks for the screenshots &#8211; it&#8217;s the
only really clear way of communicating
a HouseBot setup. One of it&#8217;s few &#8211;ve
points.<o:p></o:p></span></p>

<p class=MsoNormal><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>One thing I can&#8217;t see in the shots though is
the detailed
settings for the &#8216;xAP Message Target&#8217;. And it occurs to
me that the behaviour
you depict is exactly what would happen if the checkbox &#8216;Allow
Same Value
Settings&#8217; for this property was unchecked. Can you check the
setting of that
please.<o:p></o:p></span></p>

<p class=MsoNormal><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm
4.0pt'>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm
0cm 0cm'>

<p class=MsoNormal><b><span lang=EN-US
style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span
lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>
xap_automation@xxxxxxx
[mailto:xap_automation@xxxxxxx]
<b>On Behalf Of </b>zagknut<br>
<b>Sent:</b> 24 September 2009 20:00<br>
<b>To:</b> xap_automation@xxxxxxx<br>
<b>Subject:</b> [xap_automation] Re: HouseBot
Plug-in<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>&nbsp; <o:p></o:p></p>

<div id=ygrp-mlmsg>

<div id=ygrp-msg>

<div id=ygrp-text>

<p>I have attached a screenshot of the device for the first task in
my last
e-mail.<o:p></o:p></p>

<p><a
href="http://groups.yahoo.com/group/xap_automation/photos/album/940785096/pic/82506861/view?picmode=large&amp;mode=tn&amp;order=ordinal&amp;start=1&amp;dir=asc";>Device
screen shot</a>&nbsp;<o:p></o:p></p>

<p>Regards, Brad<o:p></o:p></p>

<p><br>
--- In xap_automation@xxxxxxx, &quot;Edward Pearson&quot;
&lt;edward.mailgroup@...&gt; wrote:<br>
&gt;<br>
&gt; writing a value, even if it's the same as the existing value, from
a task<br>
&gt; action into the target property of the sender device is the right
way to<br>
&gt; trigger the message send.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; So you should have<br>
&gt; <br>
&gt; 1) a HB button that calls a task,<br>
&gt; <br>
&gt; 2) the task makes changes to a sender device, the last one being
the<br>
&gt; target property<br>
&gt; <br>
&gt; 3) the sender device transmits the xAP message to
SqueezeCenter<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; Not sure I follow your description below. A screen shot of the
task might<br>
&gt; help.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; From: xap_automation@xxxxxxx [mailto:xap_automation@xxxxxxx]<br>
&gt; On Behalf Of zagknut<br>
&gt; Sent: 23 September 2009 23:02<br>
&gt; To: xap_automation@xxxxxxx<br>
&gt; Subject: [xap_automation] HouseBot Plug-in<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; So, I made it past the hurdle of communicating with the
Squeezeboxes, now
I<br>
&gt; am stumped on the HouseBot Plug-in. Let me know if there is a
better forum<br>
&gt; for these questions. <br>
&gt; <br>
&gt; I have created a Sender device in HouseBot that will send the
button<br>
&gt; commands to the correct squeezebox when I click on the
&quot;Click to test
and<br>
&gt; send message&quot;. So, I try to create a
&quot;macro&quot; using Tasks,
but no luck;<br>
&gt; nothing is sent. In the help section of HouseBot on xAP Sender
Devices it<br>
&gt; says &quot;Writing a value to the xAP Message Target property
triggers the
xAP<br>
&gt; message&quot;, so I use &quot;add Action&quot; item
and chage my button
name (favorites,<br>
&gt; play, etc) and then the name of the target. Unfortunately, the
target name<br>
&gt; is not changed between the &quot;marco&quot; calls and the
command is not
sent. So, I<br>
&gt; try changing the target field to &quot;-&quot;, which
creates an error
message in xFx<br>
&gt; Viewer, but no problem. This works. Great I think, until I realize
BOTH<br>
&gt; Squeezeboxes are changing! I have the same problem with all
commands,
other<br>
&gt; than power and level. Any guidance on where I'm going astray would
be MOST<br>
&gt; appreciated. Again, I am looking to simulate button pushes on the
unit,
such<br>
&gt; as next track, pause, play, and a macro (favorites, down,
play).<br>
&gt; <br>
&gt; Thanks in advance for any help you may be able to offer.<br>
&gt; Brad<br>
&gt;<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal><span
style='color:white'><o:p></o:p></span></p>

</div>

</div>

</div>





<!-- **begin egp html banner** -->

<br>



<br>

<!-- **end egp html banner** -->


<div width="1" style="color: white; clear:
both;"/>__._,_.___</div>

<!-- Start Recommendations -->
<!-- End Recommendations -->



<!-- **begin egp html banner** -->

<img src="http://geo.yahoo.com/serv?s=97476590/grpId=9674343/grpspId=1705007709/msgId=4504/stime=1253870852";
width="1" height="1"> <br>

<!-- **end egp html banner** -->


<!-- **begin egp html banner** -->

<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px
solid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href="http://groups.yahoo.com/group/xap_automation/join;_ylc=X3oDMTJmZHFqZDVoBF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEyNTM4NzA4NTI-";>Change
settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:xap_automation-digest@xxxxxxx?subject=Email
Delivery: Digest">Switch delivery to Daily Digest</a>  <a
href = "mailto:xap_automation-fullfeatured@xxxxxxx?subject=Change
Delivery Format: Fully Featured">Switch to Fully Featured</a>
<br>
<a href="http://groups.yahoo.com/group/xap_automation;_ylc=X3oDMTJkc2gwZDNlBF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMjUzODcwODUy";>
Visit Your Group
</a>
<a href="http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href="mailto:xap_automation-unsubscribe@xxxxxxx?subject=Unsubscribe";>
Unsubscribe
</a>
<br>
</div>
<br>

<!-- **end egp html banner** -->


<div style="color: white; clear:
both;"/>__,_._,___</div>
</body>

</html>

------=_NextPart_000_0154_01CA3DCA.C011A370--


xAP_Automation Main Index | xAP_Automation Thread Index | xAP_Automation Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.