Announcement

Collapse
No announcement yet.

3.1.0.6 INFO: Plugin start is pending

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

  • alexbk66
    started a topic 3.1.0.6 INFO: Plugin start is pending

    3.1.0.6 INFO: Plugin start is pending

    Updated plugin to 3.1.0.6 today, now in plugin management page it shows "INFO: Plugin start is pending"
    Anybody having the same problem? Can I try 3.1.0.5 back?

    [Update] Installed Beta 3.1.0.7 - same. IF IT AIN'T BROKE, DON'T FIX IT

    The only problem I can see in the log - it shows the message twice:
    Jan-12 20:25:58 Plug-In Finished initializing plug-in MeiHarmonyHub
    Jan-12 20:23:24 Plug-In Finished initializing plug-in MeiHarmonyHub

  • alexbk66
    replied
    Thanks again. alexdresko template project has postbuild step which moves all files except HSPI_* into bin/name folder.

    Leave a comment:


  • sirmeili
    replied
    Originally posted by bsobel View Post

    There is a list a mile long HS should catch....
    To be fairI think they mentioned this, but I also think it's buried in a post and not in the SDK where it should be (but maybe it is now?)

    Leave a comment:


  • sirmeili
    replied
    Originally posted by alexbk66 View Post
    I found the problem - after reinstalling whole system - which was just a waste of time - support is useless as always, but I'm not surprised.

    The solution was as simple as starting the plugin exe from command prompt and observing the problem. Which was CommandLine.dll - you are using old version 1.9.71.2, and alexdresko HSPI template uses 2.3.0.0 - so there's a conflict!

    I rebuilt my plugin using your version - now they both work.

    BUT - this is a temporary solution. Question is - how to avoid this king of conflicts in the future?
    Mine should use the version in my folder. make sure you have version, you put it in separate folder and set it in your app.config file. i.e. mine go in /bin/MeiHarmonyhub/

    <probing privatePath="/path to your dlls" />

    That should be in the assembly binding node.

    Leave a comment:


  • bsobel
    replied
    Originally posted by alexbk66 View Post
    Thank you @bsobel and @sparkman. I'll try.
    But still, HS should catch this kind of errors....
    There is a list a mile long HS should catch....

    Leave a comment:


  • alexbk66
    replied
    Thank you guys again, it worked. At least I have now a new clean HS install

    Leave a comment:


  • alexbk66
    replied
    Thank you @bsobel and @sparkman. I'll try.
    But still, HS should catch this kind of errors....

    Leave a comment:


  • bsobel
    replied
    Originally posted by alexbk66 View Post
    I found the problem - after reinstalling whole system - which was just a waste of time - support is useless as always, but I'm not surprised.

    The solution was as simple as starting the plugin exe from command prompt and observing the problem. Which was CommandLine.dll - you are using old version 1.9.71.2, and alexdresko HSPI template uses 2.3.0.0 - so there's a conflict!

    I rebuilt my plugin using your version - now they both work.

    BUT - this is a temporary solution. Question is - how to avoid this king of conflicts in the future?
    Never ever ever put dll's you include in your HS directory in the HS root directory, NEVER. Use the bin path as mentioned above...

    Leave a comment:


  • sparkman
    replied
    Originally posted by alexbk66 View Post
    I found the problem - after reinstalling whole system - which was just a waste of time - support is useless as always, but I'm not surprised.

    The solution was as simple as starting the plugin exe from command prompt and observing the problem. Which was CommandLine.dll - you are using old version 1.9.71.2, and alexdresko HSPI template uses 2.3.0.0 - so there's a conflict!

    I rebuilt my plugin using your version - now they both work.

    BUT - this is a temporary solution. Question is - how to avoid this king of conflicts in the future?
    Do you have CommandLine.dll in the root of the HS folder? If so, that is bad practice for exactly that reason. Create a plugin specific folder under the Bin folder and have the .config file point to it. That way multiple plugins can use different versions of the same DLLs.

    Leave a comment:


  • alexbk66
    replied
    And shouldn't HS catch plugin start-up errors and at least log them?!

    Leave a comment:


  • alexbk66
    replied
    I found the problem - after reinstalling whole system - which was just a waste of time - support is useless as always, but I'm not surprised.

    The solution was as simple as starting the plugin exe from command prompt and observing the problem. Which was CommandLine.dll - you are using old version 1.9.71.2, and alexdresko HSPI template uses 2.3.0.0 - so there's a conflict!

    I rebuilt my plugin using your version - now they both work.

    BUT - this is a temporary solution. Question is - how to avoid this king of conflicts in the future?

    Leave a comment:


  • alexbk66
    replied
    Further investigation... Disabled most plugins. So in log:

    Code:
    Jan-14 10:26:54         Plug-In    Found plug-in: Z-Wave, version: 3.0.2.240
    Jan-14 10:26:54         Plug-In    Found plug-in: MeiHarmonyHub, version: 3.1.0.6
    Jan-14 10:26:53         Plug-In    Found plug-in: EasyTrigger, version: 3.0.0.55
    Jan-14 10:26:53         Plug-In    Found plug-in: AK Smart Device, version: 1.0.0.2
    Code:
    Jan-14 10:26:54         Plug-In    Finished initializing plug-in MeiHarmonyHub
    Jan-14 10:26:54         Plug-In    Finished initializing plug-in AK Smart Device
    Jan-14 10:26:54         Plug-In    Finished initializing plug-in EasyTrigger
    Jan-14 10:26:54         Plug-In    Finished initializing plug-in Z-Wave
    At this stage I guess HS starts all found plugins and waits for connection, so plugin calls "Connect"
    Code:
    Jan-14 10:26:55         Info    Plugin AK Smart Device has connected. IP:127.0.0.1:65512
    Jan-14 10:26:55         Info    Plugin Z-Wave has connected. IP:127.0.0.1:65500
    Jan-14 10:26:55         Info    Plugin EasyTrigger has connected. IP:127.0.0.1:65502
    And now HS calls "InitIO":
    Code:
    Jan-14 10:27:01         Starting Plug-In    Initializing plugin Z-Wave ...
    Jan-14 10:27:00         Starting Plug-In    Initializing plugin AK Smart Device ...
    Jan-14 10:26:59         Starting Plug-In    Initializing plugin EasyTrigger ...
    Code:
    Jan-14 10:27:01         Starting Plug-In    Plugin Z-Wave started successfully in 630 milliseconds
    Jan-14 10:27:00         Starting Plug-In    Plugin AK Smart Device started successfully in 446 milliseconds
    Jan-14 10:26:59         Starting Plug-In    Plugin EasyTrigger started successfully in 24 milliseconds

    Leave a comment:


  • alexbk66
    replied
    Support suggested to repair HS installation, which didn't help. Kind of expected.

    Leave a comment:


  • alexbk66
    replied
    3.0.0.478

    Leave a comment:


  • sirmeili
    replied
    Originally posted by alexbk66 View Post
    [Update]
    1. I updated back my plugin to .NET 4.6.1 - still works.
    2. Installed MeiHarmonyHub 3.1.0.5 - still doesn't work.

    I contacted HS support, waiting for reply.

    What I noticed, when I install MeiHarmonyHub - in the plugin management page it stays at "installing plugin" until I refresh the page, but in the log it says
    Install/Update of package MeiHarmonyHub was successful

    So something is not quite right.
    what version of HS3?

    Leave a comment:

Working...
X