Nowplaying 2005
- Thread starter jwilson56
- Start date
justonemore
Active Member
E. Remember that bathroom mirror project for a lcd you were kicking around? MAN.....I still think about that!
BraveSirRobbin
Moderator
Man, must be the moon phase tonight!jwilson56 said:
jwilson56
Senior Member
Moon phase has nothing to do with the price differences...lol
I like the flash and sparkle of ML but I have neither the money nor the horsepower on my cheap 400MHZ tablets to run it. Lets not even get into the fact that I could not do everything in ML that I did in NR Pro (maybe when ML3.0 PPC comes out).
I have often suggested either solution to people. I have nothing against ML and often have thought that one day I might migrate there when touch tablets that can run it get cheaper or I win the lottery.
The world is big enough for both platforms.
John
I like the flash and sparkle of ML but I have neither the money nor the horsepower on my cheap 400MHZ tablets to run it. Lets not even get into the fact that I could not do everything in ML that I did in NR Pro (maybe when ML3.0 PPC comes out).
I have often suggested either solution to people. I have nothing against ML and often have thought that one day I might migrate there when touch tablets that can run it get cheaper or I win the lottery.
The world is big enough for both platforms.
John
BraveSirRobbin
Moderator
Hehe, I know it John, just sitting here in my "moderator" mode monitoring all of the recent posts tonight!
BTW: Love your new look with Photoshop!
BSR
BTW: Love your new look with Photoshop!
BSR
Rupp
Senior Member
Owooooooooo (my feeble attempt at spelling a wolf howl). 
Anytime you get news of price increases from various directions it puts people on edge. We all want the lustiest toys and software but dang it it's getting hard to keep up.
BSR or was it Henry Kissinger the Doctor of Diplomacy is doing an excellent job of moderation tonight.
Anytime you get news of price increases from various directions it puts people on edge. We all want the lustiest toys and software but dang it it's getting hard to keep up.
BSR or was it Henry Kissinger the Doctor of Diplomacy is doing an excellent job of moderation tonight.
BraveSirRobbin
Moderator
Yea, it might be when they get resized. What resolution are you running them on?jwilson56 said:
justonemore
Active Member
YEAH...he is! Almost to the point of pissing on my fire. But that's what he's there for. Jeez. Tonight's the first night I ever flamed on CocoonTech. Just looking outside window and I'll be damned if there IS a full moon!
jwilson56
Senior Member
Well I wrote this up for a guy on HST but I figured I would post it here also.
I only wish I had the time to write something up in detail but until then I will do a quick attempt. I would assume your interested in the light control portion. I also assume you understand the basics of Homeseer scripts as this could not possible attempt to explain how to start changing the Netremote CFF and Homeseer scripts without some understanding of scripting.
Ok... if you load the CCF into Tonto and open the light control panel you can look over how its setup. Each light switch consists the actual switch graphics (for on and off). These two graphics for on and off are held in a 'button'. This button doesn't actually do anything but show the status of the light and is updated from Homeseer's nrlights.txt script as well as the nrlights_refresh.txt script.
The buttons 'ID Tag' is named 'STATE:LightPlate1'. The STATE command can be thought of as a simple toggle of 'TRUE' and '"FALSE'. The 'LightPlate1' name is used to identify which light plate to change. The actual STATE change is performed in two places. One is the 'nrlights.txt' script where the light is being turned off and on from the NR CCF Light Control Panel. The other is from a script in Homeseer called 'nrlights_refresh.txt' that is set to run an any X10 change. This allows the light switch to be update if the switch is changed from a Palmpad for instance. The actual statements that changes the switch graphics in the refresh script is:
if hs.Isonbyname(location(xs)) then
lstate = "1"
else
lstate = "0"
end if
hsg.NetRemote_Send "Set","LightPlate"& xs ,lstate
This would assume xs=1 for this example. The script checks to see the if the light is on or off and then sets the STATE of the switch (active or inactive).
The statements that changes the switch graphics in the nrlight.txt script is:
hsg.NetRemote_Send "Set","LightPlate"& xy ,"1"
where xy would be '1' for this example. For handling the graphics on the Light Control panel its that easy! To change the graphic to something you want you would just import the 'on' and 'off' graphic file to the appropreite state on the buttons.
Now we will discuss the actual 'on' and 'off' buttons and how they work. In the Tonto screen if you click above or below the center of the light switch (where you actual would click where you turn on or off the light) you will see that these are actually invisible buttons. These were made by selecting the entire button's color to be transparent. If you double click on the invisible 'ON' button for lightplate1 and bring up it's properties you will see that that the name of the button is {NP.lightlabel.1}. This button's name is actually used to
display the 'Label' for the button that will be sent from Homeseer. The {} are important in labels so don't forget them. The line in the Homeseer script that sets these lables is:
hsg.NetRemote_Send "Set", "NP.lightlabel." & xs , label(xs)
where xs is 1 and the array label(xs) contains the labels name. Its as simple as that to send text labels from Homeseer to a CCF panel in Netremote. This can be anything you want, like maybe the current tempurature for instance.
Now if you look at the 'Actions' sent for this button you will see that it is 'nrlights.on.1'. This is actually the 'payload' that is sent from Netremote to a hsGirder script. It is broken down into three items. The first item (nrlights) tells hsGirder what script to run. The second item (on) is used in a case statement that I use to tell the script which command is going to be run. In this case it would goto the case "on" section. The final item (1) tells the script which light is being turned on. This is how I used the hsGirder syntax to
handle the lights. This is by no means the exclusive way of handling it. So for this example pushing the invisible 'on' button would send the 'Action' of 'nrlights.on.1' and hsGirder would execute the nrlights.txt script and pass the 'action' to the script. The hsGirder routines would take the info passed into the script and brake it down via George's section of the script into four parameters.
nrIPAddr = hParm(0) ' The IP address of the NetRemote client
nrName = hParm(1) ' NetBios name, not guaranteed, of the NetRemote client
nrEvent = hParm(2) ' The Event name passed
nrPayload = hParm(3)
The script then uses splits up the 'nrevent' parameter (again part of George's section of the script) into the last two items of your 'Action' command from the CCF button. It uses the first (plist(1)) to find out what your button is suppose to do (on/off/dim) and the executes the proper case statement. It then uses the second (plist(2)) to find out which button the command is coming from. It then excutes the proper Homeseer command to turn the light on or off.
As for the IR portion of the button I have to tell you I never messed with any of them. I just copied and pasted from other peoples work. Just use the Now Playing buttons and redo the Action name to change it to your purposes but leave the IR codes the same (for the proper functions).
I hope this helps get you started. Also check out the HomeSeer_Girder_Interface_Server.doc in the HS directory.
John
This post
I only wish I had the time to write something up in detail but until then I will do a quick attempt. I would assume your interested in the light control portion. I also assume you understand the basics of Homeseer scripts as this could not possible attempt to explain how to start changing the Netremote CFF and Homeseer scripts without some understanding of scripting.
Ok... if you load the CCF into Tonto and open the light control panel you can look over how its setup. Each light switch consists the actual switch graphics (for on and off). These two graphics for on and off are held in a 'button'. This button doesn't actually do anything but show the status of the light and is updated from Homeseer's nrlights.txt script as well as the nrlights_refresh.txt script.
The buttons 'ID Tag' is named 'STATE:LightPlate1'. The STATE command can be thought of as a simple toggle of 'TRUE' and '"FALSE'. The 'LightPlate1' name is used to identify which light plate to change. The actual STATE change is performed in two places. One is the 'nrlights.txt' script where the light is being turned off and on from the NR CCF Light Control Panel. The other is from a script in Homeseer called 'nrlights_refresh.txt' that is set to run an any X10 change. This allows the light switch to be update if the switch is changed from a Palmpad for instance. The actual statements that changes the switch graphics in the refresh script is:
if hs.Isonbyname(location(xs)) then
lstate = "1"
else
lstate = "0"
end if
hsg.NetRemote_Send "Set","LightPlate"& xs ,lstate
This would assume xs=1 for this example. The script checks to see the if the light is on or off and then sets the STATE of the switch (active or inactive).
The statements that changes the switch graphics in the nrlight.txt script is:
hsg.NetRemote_Send "Set","LightPlate"& xy ,"1"
where xy would be '1' for this example. For handling the graphics on the Light Control panel its that easy! To change the graphic to something you want you would just import the 'on' and 'off' graphic file to the appropreite state on the buttons.
Now we will discuss the actual 'on' and 'off' buttons and how they work. In the Tonto screen if you click above or below the center of the light switch (where you actual would click where you turn on or off the light) you will see that these are actually invisible buttons. These were made by selecting the entire button's color to be transparent. If you double click on the invisible 'ON' button for lightplate1 and bring up it's properties you will see that that the name of the button is {NP.lightlabel.1}. This button's name is actually used to
display the 'Label' for the button that will be sent from Homeseer. The {} are important in labels so don't forget them. The line in the Homeseer script that sets these lables is:
hsg.NetRemote_Send "Set", "NP.lightlabel." & xs , label(xs)
where xs is 1 and the array label(xs) contains the labels name. Its as simple as that to send text labels from Homeseer to a CCF panel in Netremote. This can be anything you want, like maybe the current tempurature for instance.
Now if you look at the 'Actions' sent for this button you will see that it is 'nrlights.on.1'. This is actually the 'payload' that is sent from Netremote to a hsGirder script. It is broken down into three items. The first item (nrlights) tells hsGirder what script to run. The second item (on) is used in a case statement that I use to tell the script which command is going to be run. In this case it would goto the case "on" section. The final item (1) tells the script which light is being turned on. This is how I used the hsGirder syntax to
handle the lights. This is by no means the exclusive way of handling it. So for this example pushing the invisible 'on' button would send the 'Action' of 'nrlights.on.1' and hsGirder would execute the nrlights.txt script and pass the 'action' to the script. The hsGirder routines would take the info passed into the script and brake it down via George's section of the script into four parameters.
nrIPAddr = hParm(0) ' The IP address of the NetRemote client
nrName = hParm(1) ' NetBios name, not guaranteed, of the NetRemote client
nrEvent = hParm(2) ' The Event name passed
nrPayload = hParm(3)
The script then uses splits up the 'nrevent' parameter (again part of George's section of the script) into the last two items of your 'Action' command from the CCF button. It uses the first (plist(1)) to find out what your button is suppose to do (on/off/dim) and the executes the proper case statement. It then uses the second (plist(2)) to find out which button the command is coming from. It then excutes the proper Homeseer command to turn the light on or off.
As for the IR portion of the button I have to tell you I never messed with any of them. I just copied and pasted from other peoples work. Just use the Now Playing buttons and redo the Action name to change it to your purposes but leave the IR codes the same (for the proper functions).
I hope this helps get you started. Also check out the HomeSeer_Girder_Interface_Server.doc in the HS directory.
John
This post
