Premise jQuery Mobile MiniBrowser UI - Preview

123 said:

...

Remote Control Interface
You can have a remote program control Premise objects using simple URLs. For example, assume you have a light called WallSconce whose location is: /home/apartment/foyer.

To turn it ON, use:
http://PremiseServer/sys/home/apartment/fo...once?d??mbOn(1)
To turn it OFF, use:
http://PremiseServer/sys/home/apartment/fo...nce?d??mbOff(1)
To toggle it, use:
http://PremiseServer/sys/home/apartment/fo...?d??mbToggle(1)
To brighten it by 10% use:
http://PremiseServer/sys/home/apartment/fo...once?d??mbUp(1)
To dim it by 10% use:
http://PremiseServer/sys/home/apartment/fo...ce?d??mbDown(1)
To determine its current operating state use:
http://PremiseServer/sys/home/apartment/fo...e?d??mbState(1)
To increase the setpoint temperature of a thermostat by 1 degree (Fahrenheit), you'd use:
http://PremiseServer/sys/home/apartment/ha...stat?d??mbUp(1)

You're probably asking, what's with the "(1)" at the end of the command? The number indicates the reply format.

0 = User-Interface mode
This is reserved for use by MiniBrowser to display a user-interface.
1 = HTML mode
HTML mode simply returns the object's name in order to provide a basic visual confirmation that the message was received.
2 = XML mode
XML looks like this:
<premise version="1.0">
<Object ID="{3536D217-DF2F-476E-91DF-A3B9E8D627B5}" Name="WallSconce" Class="sys://Schema/Device/Lighting/Sconce" PowerState="-1" Brightness="0.33" PresetDim="0.31" />
</premise>
The XML response is useful for a remote application because it provides greater detail and can be easily parsed. Browsers will not normally display this response.
3 = Quiet mode
This mode simply returns an empty string and nothing will be seen in the browser.

XML mode does not always return information in a palatable format! Requesting the state of a MediaZone will not reveal anything 'human readable' (i.e. you'll get a pile of GUIDs).

Click here to download this file

Click to expand...

etc6849 said:

I love the looks of the interface! Were you able to get two way status feedback to work with this?

Click to expand...

• Lights
• Fans
• Appliances
• relayDevices

• MediaZones
• Thermostats
• SecuritySystems
• Keypads
• Buttons
• CustomPanelButtons
• All Sensors

123 said:

w8no1,

MiniBrowser's current implementation of a MediaZone is limited to Music. However, if you're not already aware, a MediaZone is far more than that. I encourage you to experiment with a MediaZone and observe the results in AutomationBrowser. A MediaZone encompasses all Audio Visual gear including TV, DVD players, Receivers, AV switchers, CD players, Satellite and Cable boxes, etc. Whatever you include in a MediaZone, AutomationBrowser will render a suitable UI for it. In a perfect world, MiniBrowser should behave the same way. However, you can spend weeks laying out the UI for all the AV gear supported by a MediaZone. I suggest you limit yourself to Music now but consider how your code may have to be structured to handle the extra gear in a future release.

If you add a TV to a MediaZone you will need to bind the TV object to a TV Device (driver) before AutomationBrowser bothers to render it. Where do you get a TV driver? Just use the Class Wizard to construct the framework of a TV driver. It guides you through the process of specifying the type of device, it's inputs and outputs, and then cranks out a Module-based driver.

Click to expand...