| Author |
|
cmhardwick
Senior Member
Joined: July 08 2006
Location: United States
Online Status: Offline
Posts: 290
|
| Posted: July 09 2007 at 08:35 | IP Logged
|
|
|
I would LOVE someone to write a plugin for the old XL and the new XL that would use the UDP broadcasts and directly send to PH (must be able to be configured to send to remote machine as most people don't run both on the same machine.
i'm still working on the macro in PH to update all my XL buttons hehehe. just lazy on that side lol
__________________
Cicero, Enjoying automation!
|
| Back to Top |
|
| |
eHomeCreations
Groupie
Joined: February 02 2007
Location: Ukraine
Online Status: Offline
Posts: 64
|
| Posted: July 19 2007 at 11:39 | IP Logged
|
|
|
hhhhhhhhmmmmmmmmmmmmm.... Just playing.
Sorry Manny... Your my goto sample data guy...
__________________
--Steve http://www. ehomecreations.com
|
| Back to Top |
|
| |
eHomeCreations
Groupie
Joined: February 02 2007
Location: Ukraine
Online Status: Offline
Posts: 64
|
| Posted: July 19 2007 at 12:07 | IP Logged
|
|
|
hhhhhhhhmmmmmmmmmmmmm.... Just playing. But its truly embedded into eHome. Its a child Window now... 
Much better!!!!! I just love the Win API!!!
Again... Sorry Manny... Your my goto sample data guy...
Wish I had a way to change the TAB colors and frame color...
__________________
--Steve http://www. ehomecreations.com
|
| Back to Top |
|
| |
Manny
Senior Member
Joined: March 23 2003
Location: United States
Online Status: Offline
Posts: 172
|
| Posted: July 19 2007 at 12:32 | IP Logged
|
|
|
Congrats. 
Rushed out of a meeting this morning when I got the email on my Treo.
At least by showing my ugly CC I know it's the real deal...
The embedded CC is good.
Now the question is
Will you be incorporating the UDP functionality in any other ways?
__________________
PowerHomeFanSite/Guestbook
|
| Back to Top |
|
| |
crisx
Groupie
Joined: September 14 2006
Location: United States
Online Status: Offline
Posts: 72
|
| Posted: August 28 2007 at 23:49 | IP Logged
|
|
|
Remote Device Status is very cool. I got it to work quickly on my laptop with XP. However, I can't get it to work with Vista on my desktop. I copied the .ini file directly from the XP machine, so it isn't a typo. I'm sure it has to do with Vista security issues. Any ideas? Has anyone got Remote Device Status client to work on Vista?
I tried 'Run as administrator' and got the following error: "Error accessing external object property autoresolve at line 7 in function f_init of object uo_phssrq"
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: September 02 2007 at 19:15 | IP Logged
|
|
|
Cris,
The problem you're having is that Vista is not seeing the Catalyst Socket ActiveX control that the Remote DS is using. The "autoresolve" property is a property of this control.
Im not familiar with Vista yet so am not sure what tricks will need to be done but you must "register" the activeX control as the user who is also executing the Remote DS program. In this case, it sounds as if it's the administrator.
In Windows XP, I would go to Start|Run and type
Code:
| regsvr32.exe "c:\windows\system32\cswsk32.ocx" |
|
|
and press enter.
Not sure what the Vista equivalent would be (it may be the same), but it's probably close.
Dave.
|
| Back to Top |
|
| |
keepersg
Newbie
Joined: July 23 2007
Location: United States
Online Status: Offline
Posts: 29
|
| Posted: October 04 2007 at 01:08 | IP Logged
|
|
|
Just thought I would share what I'm doing with the remote clients. I've been able to install both RCC and RDS on a salvaged Wyse 9235LE thin client which I got on e-bay for $30. The 9235 runs windows XPe and I was able to make enough room on it for the install. Its a very small machine and fits on the back of the touchscreen in wall with room to spare. I'm using it to run an ELOS 15" touchscreen that I got for $100 from Michael Santiago who I met over on Cocoontech. He's very reliable and very much into providing excellent service to his customers. The 9235 already had the Elos touch screen drivers on it but if you get one that doesn't you can install them from the Elos website. The 9235 was easy to network, has IE on it and easily handles shared drives so I was able to use the PH graphics folder on my main machine. Net result is a touchscreen home automation controller for about $150 with the shipping. Additionally, the 9235 can be used to browse the web independently so you can use the web center on it right out of the box. Its also an RDP client. Wyse doesn't make them anymore and is replacing the product line so there may be more around on e-bay.
I also picked up a Wyse 3235 also discontinued by Wyse. These run Windows CE and have a web browser and RDP client. I was able to run the PH web device controller on it. When Dave gets the CE version of the remote clients done, I'll experiment and see if I can get them to work on the 3235. There are alot of these available on e-bay at very reasonable prices.
|
| Back to Top |
|
| |
krommetje
Super User
Joined: December 29 2004
Location: Netherlands
Online Status: Offline
Posts: 695
|
| Posted: April 08 2008 at 09:12 | IP Logged
|
|
|
Dave? How far are you with writing remote Clients for Windows CE (WinCe)?
Peter...
see 
Peter
|
| Back to Top |
|
| |
Jerrem
Newbie
Joined: December 23 2008
Location: United States
Online Status: Offline
Posts: 16
|
| Posted: December 27 2008 at 23:15 | IP Logged
|
|
|
When using the ph remote client 21b applications (both ANSI and unicode versions, I am seeing the applications defaulting to IP 192.168.0.10. I have updated the phremotecc.ini to reflect my ph machine IP, but this does not seem to change their behaviour. I was completely succesful running the Remote device status client.
Has anyone else seen this behaviour, or am I missing something obvious?
Thank you
Jerry
|
| Back to Top |
|
| |
Jerrem
Newbie
Joined: December 23 2008
Location: United States
Online Status: Offline
Posts: 16
|
| Posted: December 31 2008 at 10:36 | IP Logged
|
|
|
Just an update on my previous post. I installed the remote client on a different machine, updated the phremotecc.ini prior to running the control center and it worked wonderfully. Not sure why the previous install on a different machine is having issues  . I have searched for other phremotecc.ini files on the on the non working system and have not found any. Could it be that the ini file only referenced at the first exectuion of the application?????
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: PowerHome Remote Clients Available
