New Source 2.22 version available for beta users.

[Rene]

I am not running Windows7 but still WindowsXp.

[TANE]

Just install the new FTDI drivers from the FTDI website.
Latest version 2.8.24.0
Date 10-4-2012

OS Windows XP

[Rene]

I did, still the Source cannot find the stick. I reinstalled an old version of the source with the 2.6.0.0 version of the FTDI driver (which is unsigned). This works. Then I upgraded the Source again which installed the new FTDI driver. This does not work. I rolled the driver back to version 2.6.0.0, and it still does not work.

[Rene]

I go to bed now but my Plugwise setup is still not working. What a mess these guys from Plugwise made of this upgrade!

[Bwired]

I also had problems in the past
Are you mentioning the exact comport in the plugwise settingsfile, this might help
Otherwise plugwise is searching for the right comport, this gave problems for me......

[Rene]

Good tip, but where do I do this (I am currently not at home so cannot check)?

[Bwired]

try combining this both or only shortcut option

Make a shortcut for the source software and change the Target in the shortcut to:
"C:\Program Files\Plugwise\Plugwise Source\PlugwisePC.exe" /comport=comX
X = your comport which plugwise uses (check in device-manager which comport you need)

Make a Setting.ini and place in the folder where your source is located normally
C:\Program Files\Plugwise\Plugwise Source
In the settings.ini put
comport="comX"

[Rene]

Thanks Pieter, I will try this tonight.

[Rene]

It didn't work. I created a Windows7 VM installed plugwise on it, restored my database and now all is working again.

[Rene]

At least once a day, the Source crashes with the message ' access to port denied'. Restarting the Source fixes it.

[Bwired]

Make the comport settings as discussed, i had the same problem

[Rene]

Just created the settings.ini, let's wait and see.

[Bwired]

also create the shortcut if this does not work
I had these problems on W2K8, this solved it for me
good luck!

[Rene]

I noticed another bug in the web interface. All device images link to /pwimg/32/unknown.png. Besides this is an error, the unknown.png image also does not exist resulting in a cross in the browser. It also results in a broken statistics.xml output used by the Homeseer plugin. I attached a fixed statistics.xml that can be used until the bug is fixed in the Source Webserver.

EDIT: Restarting the Plugwise Server (not the Source) fixed this making the modified statistics.xml file no longer necessary. I will try to reproduce this.

[Rene]

@Pieter: I added the /comport parameter to the shortcut and now it is running stable for 3 days in a row! Thanks.