They look great! Personally I like 1 and 5. If you can do some with different colours, I'll definitely include them in the finished package (with credit).
Here are the 5's.
You said you like 1 also. 1a or 1b or together as a 2 state button?
I made #1 as an on and off, but maybe you are not gonna do 2 state buttons.
I've downloaded the beta and read the documentation, and am about to try installing. Some comments about the documentation while it is fresh in my mind:
(1) Button Action
Running Events
Example
extraneous "URL=" in the example
(2) Button Action
Display Action
examples only use MenuButtonDisplayxLiney
not Buttona-bLiney
At this section of the documentation, it is not clear that you can change the 2 lines of the display as part of each button action
From what I see of the documentation, looks like a product I would use instead of developing my own web pages for my n810 (although I enjoy doing that).
Suggestion: Another button action that would sendIR. It seems like a typical use of a small touchscreen might be to control AV equipment. I know I could define an event for each that sends the IR, but that seems silly. Actually, I probably would write a script with parameters, and just use the script button action with different parameters for each IR action, so I guess it is no big deal, but a sendIR action would be nice at some point.
It is assumed you know how to call a standard Homeseer webpage in a web browser.
If you call up \mycontrol\Mycontrol.ash in the browser, you will automatically be using information configured within the Jon00Control1.ini file. If you only wish to configure one page then it can be called in this manner.
If you wish to use multiple configurations, then the page must be called with extra parameters.
All ini files saved must be called Jon00ControlX.ini where X is a number starting at 1. The numbering does NOT need to be sequential.
If you have defined 3 pages with INI files called Jon00Control1.ini, Jon00Control2.ini and Jon00Control3.ini, you would call them with the following URL’s:
\mycontrol\Mycontrol.ash?Val=1 to use Jon00Control1.INI
\mycontrol\Mycontrol.ash?Val=2 to use Jon00Control2.INI
\mycontrol\Mycontrol.ash?Val=3 to use Jon00Control3.INI
the slashes are backwords?
Also, in clicking on the WEATHER button in your sample screen, I get:
Web Server Error 404, cannot serve file: C:\Program Files\HomeSeer 2\html/MyControl/Jon00Control.xml
The file is there, but I think you have the slashes wrong again.
I'm correcting some of the documentation as you spot them!
The XML error should go once the file is created. This file is only updated when required to do so. The weather button had nothing defined for the display so was not created. The display code still tried to read it hence the error.
If you had pushed another button with a display definition first, this would not have been spotted.
Suggestion: Another button action that would sendIR. It seems like a typical use of a small touchscreen might be to control AV equipment. I know I could define an event for each that sends the IR, but that seems silly. Actually, I probably would write a script with parameters, and just use the script button action with different parameters for each IR action, so I guess it is no big deal, but a sendIR action would be nice at some point. tenholde
Hi all
This is the trick for one button control.
For my pronto I have already built this.
First you have to define a event for every device you want to control
Event name must be starting with location then the device name
like "Outside GardenLamp"
you can set the trigger to manual
Action:
Start script
My toggle scrip
sub main()
dim eventname
eventname = hs.GetLastEvent
If hs.IsOnByName(eventname)Then
hs.ExecX10ByName eventname,"Off",0,0
Else
hs.ExecX10ByName eventname,"on",0,0
End If
End Sub
Things are moving nicely with this now. There have been some good feature requests which have now been added and several bugs un-covered. I'm hoping to issue Release candidate 1 to beta testers who have responded over the weekend.
Comment