Announcement

Collapse
No announcement yet.

Jon00PerMonHS3

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • NicolaiL
    replied
    Originally posted by jon00 View Post
    No, Homeseer 3 has no password protection for remote plugins at this time.
    OK - Thanks.

    Leave a comment:


  • jon00
    replied
    No, Homeseer 3 has no password protection for remote plugins at this time.

    Leave a comment:


  • NicolaiL
    replied
    Yup, that was it. I had a password set on the default account.

    I've looked through the pdf and can't find anything that describes how I can specific a user/password. Is this possible?? (not overly comfortable having the default account wide open).

    Thanks

    Leave a comment:


  • jon00
    replied
    Have you deleted the default account in setup/network?

    Leave a comment:


  • NicolaiL
    replied
    Originally posted by jon00 View Post
    Do you see the plugin connect with Homeseer in the log and the message Waiting to reference on 5 minute duration?

    Did you use the ini file from Homeseer 2? If you did it will not work without changes.
    Nope, nothing in the log re connections.

    I did a clean install and am using the ini file that came with the HS3 version in its unmodified form.

    In task manager I can see that the plugin is running so at least the start up file is firing the launch event.

    Leave a comment:


  • jon00
    replied
    Do you see the plugin connect with Homeseer in the log and the message Waiting to reference on 5 minute duration?

    Did you use the ini file from Homeseer 2? If you did it will not work without changes.

    Leave a comment:


  • NicolaiL
    replied
    I have just installed this and cannot get it to work. I know the Jon00PerfMonHS3 process is running (verified via task manager), but for some reasons no devices are created??

    I'm running the latest HS3 3.0.0.46 on a Win8 64bit box.

    Leave a comment:


  • jon00
    replied
    Originally posted by jon00 View Post
    Strange...I am still using startup.txt and it is working fine here.
    Well I updated to the latest version of Homeseer 3 and it looks like Startup.txt has been disabled/removed.

    Therefore you now need to add the following in startup.vb just above the 'end Sub'

    hs.Launch (hs.GetAppPath & "\Jon00PerfMonHS3.exe","","",0)

    Leave a comment:


  • jon00
    replied
    Strange...I am still using startup.txt and it is working fine here.

    Leave a comment:


  • jlrichar
    replied
    There was something wrong with my installation. I had started with the first public beta, and upgraded to each subsequent. Evidently something broke along the way. After a wipe, and fresh install of *.42 there is only startup.vb in scripts. After I adding the test below to that results in the appropriate entry in the log.

    Code:
    hs.writelog ("Test","This is startup.vb")
    And adding the command you suggested above results in perfmon running at startup correctly.

    Code:
    hs.Launch (hs.GetAppPath() & "\Jon00PerfMonHS3.exe","","",0)
    In short there was some cruft that built up that caused the problem.

    Leave a comment:


  • jon00
    replied
    For starters, we need to know if startup.txt and/or startup.vb are being run.

    Add the following to startup.txt:

    hs.writelog "Test","This is startup.txt"

    Then add the following to startup.vb:

    hs.writelog ("Test","This is startup.vb")

    Then restart Homeseer and see what the log shows.

    Leave a comment:


  • jlrichar
    replied
    Originally posted by jon00 View Post
    As HST have made some changes to HS3 since I wrote this version (July), I'll update it to reflect the changes.

    That said, the start up procedure would be the same.

    You can try the following in startup.vb:

    hs.Launch (hs.GetAppPath() & "\Jon00PerfMonHS3.exe","","",0)
    For some reason I am still not able to get this to start with homeseer even after adding the above command in startup.vb. When I start manually all is fine.

    Not sure what is going on.

    Leave a comment:


  • jon00
    replied
    The update will make little difference. It will just be a replacement exe file.

    Leave a comment:


  • jlrichar
    replied
    Originally posted by jon00 View Post
    As HST have made some changes to HS3 since I wrote this version (July), I'll update it to reflect the changes.

    That said, the start up procedure would be the same.

    You can try the following in startup.vb:

    hs.Launch (hs.GetAppPath() & "\Jon00PerfMonHS3.exe","","",0)
    hmmm. Perhaps I will wait for any updates you make.

    Thanks.

    Leave a comment:


  • jon00
    replied
    As HST have made some changes to HS3 since I wrote this version (July), I'll update it to reflect the changes.

    That said, the start up procedure would be the same.

    You can try the following in startup.vb:

    hs.Launch (hs.GetAppPath() & "\Jon00PerfMonHS3.exe","","",0)

    Leave a comment:

Working...
X