For running the plugin remotely:
UPDATE: This is the new process as of build 1.0.26 of the plug-in.
UPDATE: As of 1.0.27, if the plugin is running remotely, the INI will be saved in the same folder as the HSPI_BLLED.exe file on your remote machine. Otherwise it is stored in the normal config folder on the HS3 machine
You will create a folder on your remote machine (eg: C:\BLLED)
From your main HS3 machine, copy the following files to your new folder on your remote machine. I will use C:\BLLED as the example folder on your remote machine
1. Copy the following files (left side is main HS3 machine, right side is remote machine)
[hs root]\HSPI_BLLED.exe ---> C:\BLLED
[hs root]\HomeSeerAPI.dll ---> C:\BLLED
[hs root]\HSCF.dll ---> C:\BLLED
[hs root]\Scheduler.dll ---> C:\BLLED
[hs root]\BIN\BLLED\betabriteusb.dll ---> C:\BLLED
2. You will need to run the plugin as follows from the C:\BLLED folder on your remote machine
To specify an instance
UPDATE: This is the new process as of build 1.0.26 of the plug-in.
UPDATE: As of 1.0.27, if the plugin is running remotely, the INI will be saved in the same folder as the HSPI_BLLED.exe file on your remote machine. Otherwise it is stored in the normal config folder on the HS3 machine
You will create a folder on your remote machine (eg: C:\BLLED)
From your main HS3 machine, copy the following files to your new folder on your remote machine. I will use C:\BLLED as the example folder on your remote machine
1. Copy the following files (left side is main HS3 machine, right side is remote machine)
[hs root]\HSPI_BLLED.exe ---> C:\BLLED
[hs root]\HomeSeerAPI.dll ---> C:\BLLED
[hs root]\HSCF.dll ---> C:\BLLED
[hs root]\Scheduler.dll ---> C:\BLLED
[hs root]\BIN\BLLED\betabriteusb.dll ---> C:\BLLED
2. You will need to run the plugin as follows from the C:\BLLED folder on your remote machine
Code:
HSPI_BLLED.exe server=[ip address of your main HS3 machine]
Code:
HSPI_BLLED.exe server=[ip address of your main HS3 machine] instance=[instance name]
Comment