Reply to thread

Thanks for starting this plugin, apart from the new TV Engine this is the next most important feature to me.  So much so I was about to start work on this plugin myself.  My goals were a bit more limited though.

I wanted to be able to send commands and see status of devices and sensors (both binary and variable sensors eg. temperature). From this I wanted to be able have a screen-pop appear in MediaPortal (like the Caller-ID Plugin) when an item changed state or reached a pre-defined threshold, eg when my front door PIR is triggered I would get a screen-pop telling me there is someone at the door.

Using the My Programs plugin I can already turn my xAP devices on/off/bright/dim by using xap-send.exe and a number of text files. This functions well but stops the Video/Audio while I am in My Programs sending the command, this is a real pain!

I have been trying to test your plugin, this is what I've got so far.

Using Edward's X10 Connector (which supports both xAP X10 schema and xAP BSC schema v1.3)

    http://www.edjo.pwp.blueyonder.co.uk/edward/xAP/X10/x10_main.htm

The following command from your plugin does not register in the x10 Connector, but I can see it on the network:

    xap-header

    {

        v=12

        hop=1

        uid=FFABCD00

        class=xAPBSC.cmd

        source=MEPO.BHAConn.Abit-ic7

        target=ERSP.X10.Shuttle-sk41g:BedRoom.Blanket

    }

    output.state

    {

        id=*

        state=TOGGLE

    }

By changing "output.state" to "output.state.1" the command works.  I don't know enough about the BSC schema and it's interpretation to understand which is correct, but I do know which one works.

I also use Edward's Quasar 3145 Temperature Sensor Connector

    http://www.edjo.pwp.blueyonder.co.uk/edward/xAP/quasar3145.htm

It does not use xAP BSC schema, I assume because BSC has no mechanism for values, limits and units.  This is where TSC is supposed to come in, but that might happen this year, might not, might not even happen at all! It produces xAP in the following format:

    xap-header

    {

        v=12

        hop=1

        uid=FE123401

        class=xap-temp.notification

        source=ERSP.telemetry.Shuttle-sk41g.com2ensor1

    }

    temperature.current

    {

        temp=24.19

        seq=2

        location=Sensor1

        unit=C

    }

Anyway my questions are:

Can you have a look at the "output.state" issue?

Do you plan on implementing event driven screen-pops?

Do you plan to allows devices and connectors that do not use strict BSC schema? as we could be waiting a very long time for TSC and every connector to be rewritten to the new schema.

A big thank you for starting this plugin.