Hahaha here we go again, I looked up the script mentioned, and it went from a free download in the forums, to a $30 Plug-In in the updater. Wow, this really is something that should be built into HS2 given its .net architecture and all.
Homeseer Network control of a device
- Thread starter JohnWPB
- Start date
Hahaha here we go again, I looked up the script mentioned, and it went from a free download in the forums, to a $30 Plug-In in the updater. Wow, this really is something that should be built into HS2 given its .net architecture and all.
It does and it supports EventGhost > Girder.
Also it allows in it's command line interface for issues like this.
EventGhost.exe -n 192.168.1.x:xxxx password eventname
You need not configure for any events, just have the newwork sender plugin installed.
On the HS box you would need the network reciever and each event configured which may be less then desirable but workable.
Ok, after a lot of research, and some tips in the HS forums, I came up with a sollution. I thought I would post it here if anyone is looking to do something similar. It is very basic in its current state, but is a good first building block.
Currently I have the script named "control.V B S" (The forum will not allow me to use the extension for Visual Basic scripts!)
So just running the script like this:
"Control.V B S A1"
Will toggel device A1
Here is the script:
-----------------------------------------------------------------------------
Dim hs
set objArgs = WScript.Arguments
for each strArg in objArgs
DeviceCalled = strArg
next
if devicecalled ="" then msgbox "No Device Code Sent"
'msgbox DeviceCalled
Set hsi = createobject("HomeSeer.application")
hsi.SetHost "johnsdesktop"
rval = hsi.Connect("default","default")
if rval <> "" then
msgbox "Client Not Found"
end if
Set hs = hsi.GetHSRef
'hs.speak "test"
MyDevice = hs.devicestatus(DeviceCalled)
if MyDevice = 3 then hs.ExecX10 DeviceCalled,"on"
if MyDevice = 2 then hs.ExecX10 DeviceCalled,"off"
if MyDevice = 4 then hs.ExecX10 DeviceCalled,"off"
Currently I have the script named "control.V B S" (The forum will not allow me to use the extension for Visual Basic scripts!)
So just running the script like this:
"Control.V B S A1"
Will toggel device A1
Here is the script:
-----------------------------------------------------------------------------
Dim hs
set objArgs = WScript.Arguments
for each strArg in objArgs
DeviceCalled = strArg
next
if devicecalled ="" then msgbox "No Device Code Sent"
'msgbox DeviceCalled
Set hsi = createobject("HomeSeer.application")
hsi.SetHost "johnsdesktop"
rval = hsi.Connect("default","default")
if rval <> "" then
msgbox "Client Not Found"
end if
Set hs = hsi.GetHSRef
'hs.speak "test"
MyDevice = hs.devicestatus(DeviceCalled)
if MyDevice = 3 then hs.ExecX10 DeviceCalled,"on"
if MyDevice = 2 then hs.ExecX10 DeviceCalled,"off"
if MyDevice = 4 then hs.ExecX10 DeviceCalled,"off"
Rupp
Senior Member
John,
Just so you know the Script Connector plugin uses the same software that the speaker app does so you can script using the speaker install for free.
I had thought about girder, as Road Runner supports it natively. But it can be a tangled mess to work with at times to say the least, and have been trying to avoid it :unsure:
Very nice Rupp, it may be worth the switch. I have downloaded and registered HS2.0 and figured I would start fresh with this and Road Runner. I did the ASP pages mainly for a touchscreen interface with 1.7x in the house on the touch screens. Using a web browser certainly has its limitations. Using Road Runner now, I am able to communicate back and forth directly to update the clients with status, and execute events, device status ect.
Here is a screen capture, in it's early stages. All of the buttons work perfectly, and even speaks on the client machines when a button is presses, such as after "Movie Time", you hear on the overhead speakers "Setting lights to optimal movie viewing level." All that is left is to set the indicators in the skin to see the status of the lights/devices.
Not in the screen capture, is the dimming control. When you press the far right of one of the buttons, a pop-up appears with a slider to control the dim level on the devices.
Thanks for all the help and suggestions!
EDIT: With my new found control
I was able to add a Pop-Up screen in Road Runner to show the caller ID and photo, if available, on the remote machines.
Very nice Rupp, it may be worth the switch. I have downloaded and registered HS2.0 and figured I would start fresh with this and Road Runner. I did the ASP pages mainly for a touchscreen interface with 1.7x in the house on the touch screens. Using a web browser certainly has its limitations. Using Road Runner now, I am able to communicate back and forth directly to update the clients with status, and execute events, device status ect.
Here is a screen capture, in it's early stages. All of the buttons work perfectly, and even speaks on the client machines when a button is presses, such as after "Movie Time", you hear on the overhead speakers "Setting lights to optimal movie viewing level." All that is left is to set the indicators in the skin to see the status of the lights/devices.
Not in the screen capture, is the dimming control. When you press the far right of one of the buttons, a pop-up appears with a slider to control the dim level on the devices.
Thanks for all the help and suggestions!
EDIT: With my new found control
I was able to add a Pop-Up screen in Road Runner to show the caller ID and photo, if available, on the remote machines.
huggy59
Active Member
Good work, John! FYI, most people had hiccups with DCOM over the network in two places: configuring DCOM for remote network operation, and permissions. Firewalls were added a bit later.
I got around most of the serious issues when I was using it with HS 1.7 because I ran all my machines on a Windows NT Domain using network user accounts - hence user/network permissions issues were already in place.
Looks like the newer stuff will be much easier to work with.
I got around most of the serious issues when I was using it with HS 1.7 because I ran all my machines on a Windows NT Domain using network user accounts - hence user/network permissions issues were already in place.
Looks like the newer stuff will be much easier to work with.
Yea, I am just scratching the surface now... In time it will be a really nice touch screen interface for HA for sure. With the built in flash capability, transparencies, changing font and background colors or wallpaper on the fly ect. Just pick a background, and you can have a touchscreen that matches the theme of the room ect. It would just be a matter of adding one more command(SetThemeMovieTIme) to the "Movie Time" button for instance to change the background to black, and the text to a dark gray, so the screen did not glare while watching a movie ect.
Here is the well known Apple looking wallpaper, with a light green font:
Huggy, I wish I knew how you did that before I decided to make the switch to HS2! Hahahah No I am trying to get that setup at the same time as developing the screens ect.
Similar threads
- Question