xAP for Xlobby

by **Aaron** on Thu Oct 13, 2005 7:05 am

Can anyone help on the crashes?

should I post in the Bug section?

by **rbziggy** on Mon Oct 24, 2005 2:56 pm

I'm just wondering... after having had a look through this whole thread... whether it is possible to use this xAP plugin to communicate with and control a) Squeezebox and b) Comfort Alarm system.

I know both the above have xAP plugins but I'm not clear whether the XL xAP plugin has the ability to format and send any xAP message (I guess that also goes for the incoming side of receiving and interpreting any xAP message from the network).

I noted there is a thread elsewhere on the forum about using XL to control a squeezebox. I wondered if the xAP route is a possibility here (which may be more flexible than just a direct interface).

(I've dabbled with xAP in the past to the extent of getting it up and running and displaying weather info on the PC desktop but have not tried to use it for serious work. Before I invest some 'learning' time in this, it would be great to get some views.)

Thanks

Richard

by **ptrinchi** on Mon Oct 24, 2005 9:35 pm

No problem Richard, with the xAP3 version (last one) you have the ability to send every kind of xAP messages you want to every xAP modules on your network.

You have also the ability to give indication on witch messages Xlobby will take information for displaying states, texts or images.

Actually, I have X10-xAP interface, a xAP mail monitor, a xAP Text to speech working with my Xlobby and I can display new mail when arriving, switch on or off all my light (and display image states on Xlobby, tell Xlobby to say wathever I want. Test If my X10 alarm is on... and so on.

by **Aaron** on Mon Oct 24, 2005 11:38 pm

ptrinchi,
I'm getting a crash when I try using xAP. I hit the test button and it throws an error.

Here's the info..

Code: Select all: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** KCS.xAP.Framework.xAPException: The xAP message value is malformed No part of the address value may contain space characters at KCS.xAP.Framework.Message.xAPAddressBase..ctor(String address) at KCS.xAP.Framework.Message.xAPTargetAddress..ctor(String target) at xAPSpace.xAP.Execute(String command) at xlobby2.Command.Run(Control control) at xlobby2.Setup.button56_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll ---------------------------------------- xlobby2 Assembly Version: 1.0.2098.28537 Win32 Version: 1.0.2098.28537 CodeBase: file:///C:/Storage/Electronics/xlobby2/xlobby2/xlobby2.exe ---------------------------------------- System.Drawing Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll ---------------------------------------- System.Windows.Forms Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll ---------------------------------------- System Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll ---------------------------------------- XPluginSDK Assembly Version: 1.0.2020.31144 Win32 Version: 1.0.2020.31144 CodeBase: file:///C:/Storage/Electronics/xlobby2/xlobby2/XPluginSDK.DLL ---------------------------------------- System.Xml Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll ---------------------------------------- System.Runtime.Remoting Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/assembly/gac/system.runtime.remoting/1.0.5000.0__b77a5c561934e089/system.runtime.remoting.dll ---------------------------------------- CDEX Assembly Version: 1.0.1685.4787 Win32 Version: 1.0.1685.4787 CodeBase: file:///c:/storage/electronics/xlobby2/xlobby2/plugins/cdex.dll ---------------------------------------- xusbuirt Assembly Version: 1.0.1767.29466 Win32 Version: 1.0.1767.29466 CodeBase: file:///c:/storage/electronics/xlobby2/xlobby2/plugins/xusbuirt.dll ---------------------------------------- xAP-Xlobby Assembly Version: 1.0.2121.36041 Win32 Version: 1.0.2121.36041 CodeBase: file:///c:/storage/electronics/xlobby2/xlobby2/plugins/xap-xlobby/xap-xlobby.dll ---------------------------------------- xAPTransport Assembly Version: 1.2.9.2 Win32 Version: 1.2.9.2 CodeBase: file:///C:/Storage/Electronics/xlobby2/xlobby2/xAPTransport.DLL ---------------------------------------- KCS.Utilities Assembly Version: 1.1.2.1 Win32 Version: 1.1.2.1 CodeBase: file:///C:/Storage/Electronics/xlobby2/xlobby2/KCS.Utilities.DLL ---------------------------------------- xAPMessage Assembly Version: 1.2.9.12 Win32 Version: 1.2.9.12 CodeBase: file:///C:/Storage/Electronics/xlobby2/xlobby2/xAPMessage.DLL ---------------------------------------- XoapWeather Assembly Version: 1.1.1729.14788 Win32 Version: 1.1.1729.14788 CodeBase: file:///c:/storage/electronics/xlobby2/xlobby2/plugins/xoapweather/xoapweather.dll ---------------------------------------- System.Data Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll ---------------------------------------- ldwwifuf Assembly Version: 0.0.0.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll ---------------------------------------- XWeather Assembly Version: 1.0.1855.39961 Win32 Version: 1.0.1855.39961 CodeBase: file:///c:/storage/electronics/xlobby2/xlobby2/plugins/xweather/xweather.dll ---------------------------------------- Interop.Shell32 Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Storage/Electronics/xlobby2/xlobby2/Interop.Shell32.DLL ---------------------------------------- AxInterop.SHDocVw Assembly Version: 1.1.0.0 Win32 Version: 1.1.0.0 CodeBase: file:///C:/Storage/Electronics/xlobby2/xlobby2/AxInterop.SHDocVw.DLL ---------------------------------------- Interop.ActiveHomeScriptLib Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Storage/Electronics/xlobby2/xlobby2/Interop.ActiveHomeScriptLib.DLL ---------------------------------------- System.Management Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/assembly/gac/system.management/1.0.5000.0__b03f5f7f11d50a3a/system.management.dll ---------------------------------------- ************** JIT Debugging ************** To enable just in time (JIT) debugging, the config file for this application or machine (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the machine rather than being handled by this dialog.

by **rbziggy** on Tue Oct 25, 2005 3:36 am

ptrinchi wrote:No problem Richard, with the xAP3 version (last one) you have the ability to send every kind of xAP messages you want to every xAP modules on your network.

You have also the ability to give indication on witch messages Xlobby will take information for displaying states, texts or images.

Great news. Looks like I'll have to give this a go. Is xAP3 available or are you still finishing the beta?

Regards

Richard

by **lar282** on Tue Oct 25, 2005 6:13 am

its in the plugin section!

http://www.xlobby.com/forum/viewtopic.php?t=3656

//Lasse

by **ptrinchi** on Tue Oct 25, 2005 8:02 am

Aaron > I recommend you not to test with the test button on the right of the setup windows because the variable parameter will not be send to the plugin and an error will occurred.

If you wanted to test a xAP event, create it (be careful with the little bug of xlobby on the variable field, the first time you create the event, this field is lost, you have to re-enter in the event and to re-field the variable) then test with the test button on the left only or assign it to a button and press the button in your screen :wink:

If you still have an error, go to the plugin cofiguration on tab general, activate the debug on outgoing message then test an other time. A popup windows with your outoing message will appear, post-it and I will tell you what's wrong.

by **Aaron** on Tue Oct 25, 2005 5:58 pm

my outgoing msg below, does it look right?

xap-header
{
v=12
hop=1
uid=FFABCD00
class=xAPBSC.cmd
source=PTrinchi.Xlobby.office
target=mcs.Xap.Q.*:DiningRoom.WallLights
}
output.state.1
{
id=*
state=Toggle
}

by **ptrinchi** on Tue Oct 25, 2005 7:45 pm

I don't know exactly what xAP message the msc plugin for homeseer expect.
I have made my tests with the mi4 plugin and not the msc.

This message seams ok (good header and good body) Your Xlobby is on the office computer and your homeseer on the Q computer isn't it?

Are you sure that msc accept toggle order?

What is the response of msc plugin?

by **damage** on Sat Aug 26, 2006 3:08 pm

ptrinchi wrote:
Is there anyway to make the 0 - 100 png files generic instead device specific?

Yes, it's a good idea. If the png does'nt exist the plug could load a generic png file (without the device name) perhaps in the next version

any chance this will be updated in the near future?